Elektroda.pl
Elektroda.pl
X
Proszę, dodaj wyjątek dla www.elektroda.pl do Adblock.
Dzięki temu, że oglądasz reklamy, wspierasz portal i użytkowników.

Zawieszanie komputera kilka razy dziennie

22 Cze 2013 17:51 1800 14
  • Poziom 13  
    Witam. Od razu chcę napisać że długo szukałem rozwiązania mojego problemu nie tylko na tym forum ale i u dziadka Google :wink:

    Od około pół roku nęka a wręcz nie daje mi żyć taki problem.
    Zwykle gdy korzystam z przeglądarki (Firefox) czasem też podczas słuchania muzyki system nagle staje z Crashem dźwięku. Taka sytuacja następuję średnio ok. 5 razy dziennie.
    Gdy już zrestartuję komputer to gdy się uruchomi wyświetla mi się okienko "System odzyskał sprawność po nie oczekiwanym zamknięciu" i po rozwinięciu listy na samej górze widnieje napis Blue Screen i poniżej ścieżka do pliku (C:\Windows\Minidump). Tego typu zawieszenia miałem już około 25-30 w 7-14 dni
    Dziwne jest też w tym wszystkim to że na wszystkie 25-30 zawieszeń (czyli 25-30 plików) w których jest raport to ani razu nie wyświetlił mi się Blue Screen system po prostu zatrzymywał się za każdym razem i pomagał jedynie restart.

    Jeśli trzeba to załączę wielką kolekcje 15 raportów :D


    Proszę o pomoc bo już nie wiem co mam zrobić nawet w tej chwili system może stanąć.
  • R.I.P. Zasłużony dla elektroda
    Już jedziemy do Ciebie aby zobaczyć konfigurację komputera i zainstalowany system operacyjny.
  • Poziom 13  
    Oj uśmiałem się i to bardzo. Przepraszam już podaje konfiguracje

    Dodano po 5 [minuty]:

    Procesor - AMD Anthlon II X4 640 3.00 GHz
    Karta graficzna - Palit NVIDIA GeForce GTX 460 SE 1024MB GDDR5
    Płyta główna - Asus MRN68T-M LE V2
    Pamięć RAM - Exeleram 2x2048MB DDR3
    Dysk twardy - Western Digital WD5000AAKX 16MB Cache
    System operacyjny - Windows 7 Ultimate 64bit
  • Poziom 28  
    A zasilacz?Podaj także screen z crystal disk info.
  • Poziom 13  
    Zasilacz za 100 zł.
    "Pokaż analizę pliku dump."
    Nie rozumiem? Mam załączyć paczkę dump'ów? Nie umiem otwierać tych plików
  • Poziom 13  
    Pokazać analize jednego pliku? Bo ja tych plików mam w chwili obecnej 15 więc nie wiem co zrobić.
  • Poziom 38  
    TermalDJ napisał:

    Pokazać analize jednego pliku?

    Jednego, najnowszego.
  • Poziom 13  
    Przepraszam za opóźnioną odpowiedź. Oto raport z najnowszego Crasha.


    Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\062513-36426-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`030a3670
    Debug session time: Tue Jun 25 18:48:51.189 2013 (GMT+2)
    System Uptime: 0 days 0:00:09.781
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ........................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa8004da6038, 0, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    Unable to load image PSHED.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PSHED.dll
    *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : hardware

    Followup: MachineOwner
    ---------

    Dodano po 18 [minuty]:

    Wygląda na to że coś z tym raportem jest nie tak i nie wyświetla jakiś symboli jak to widzę.
    Nie mogę sobie z tym programem poradzić próbuje dodać te symbole z tego poradnika i konsola jakby staje/zawiesza się. Restartowałem parę razy i za każdym razem załadowało się mniej lub więcej informacji. Może jednak łatwiej będzie gdy wrzucę ten plik tutaj?
  • Poziom 38  
    TermalDJ napisał:
    oże jednak łatwiej będzie gdy wrzucę ten plik tutaj?


    Niech będzie.
  • Użytkownik usunął konto  
  • Poziom 13  
    Problem rozwiązany. Temat do zamknięcia