Bluescreen przy wyłączaniu komputera
|
tomson007
Nowy
Liczba postów: 5
|
Bluescreen przy wyłączaniu komputera
Witam. Od kilku miesięcy mam problem z bluescreenami przy wyłączaniu komputera. Nie raz tez komputer po prostu się wiesza przy zamykaniu, ale zazwyczaj zamyka się dobrze. Problem występuje tylko i wyłącznie przy zamykaniu systemu. System to Windows 7 x64 aktualizowany, do tego zainstalowanego mam KIS 2012. Płyta główna to Asus p5n-e sli. Problem pojawił sie gdy padła mi karta dźwiękowa , i przeinstalowałem system i przesiadłem sie z KIS 2011 na KIS 2012. Wcześniej przez lata było ok. Może na to jakieś znaczenie, a może to tylko zbieg okoliczności ale wole podać wszystko co wydaje mi sie podejrzane. No i ostatnio spalił się mi tez zasilacz 650w corsair. może to wszystko zbieg okoliczności i przyczyna jest całkiem inna a moze mam jakieś zwarcie? Niby sprawdzałem RAM ramtestem i kompa sprawdzali mi w serwisie przy wymianie zasilacza na zastępczy... ale jakoś nie ufam zbytnio serwisom zwłaszcza ze nadal cos jest nie tak. No ale moze wina lezy w czymś innym? Sterowniki? KIS? jak co to mam pliki dump. Tylko mi to one za wiele nie mówią. A do tej pory wydawalo mi sie ze sie w tym orientuje z góry dzięki za pomoc , poniżej wrzucam 3 rożne pliki dump. a tutaj mozna sciagnac moje 13 plikow dmp Minidump1.rar
Kod:
plik dump nr 1 :
...............................................................................................................................................
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\Minidump\031512-29811-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 \SystemRoot\system32\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
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02a5e000 PsLoadedModuleList = 0xfffff800`02ca2650
Debug session time: Thu Mar 15 02: 59: 18.869 2012 (GMT+2)
System Uptime: 0 days 0: 07: 08.866
*********************************************************************
* 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 \SystemRoot\system32\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
Loading unloaded module list
.........
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80045d5028, b2000040, 800}
***** 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 \SystemRoot\system32\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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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
---------
plik dump nr 2
..............................................................................................................................................
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\Minidump\040512-20826-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 \SystemRoot\system32\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
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e91650
Debug session time: Thu Apr 5 06: 31: 41.596 2012 (GMT+2)
System Uptime: 0 days 7: 02: 33.593
*********************************************************************
* 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 \SystemRoot\system32\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
Loading unloaded module list
.........
Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {c08a5, 0, 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!_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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : Ntfs.sys ( Ntfs+21d5 )
Followup: MachineOwner
---------
plik dump nr 3
..............................................................................................................................................
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\Minidump\052712-21075-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 \SystemRoot\system32\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
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e90670
Debug session time: Sun May 27 11: 09: 30.762 2012 (GMT+2)
System Uptime: 0 days 11: 51: 52.322
*********************************************************************
* 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 \SystemRoot\system32\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
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 30, 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!_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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntoskrnl.exe ( nt+7f1c0 )
Followup: MachineOwner
Notatka została dodana 12.06.2012 10:20 . Ostatnia edycja dokonana 12.06.2012 10:20 przez peciaq:
Logi łapiemy w znaczniki CODE.
|
Podziękowania od: |
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Bluescreen przy wyłączaniu komputera
Jak dla mnie płyta główna albo pamięci RAM lub obie rzeczy na raz. Memtest nie jest na 100% wiarygodny bo się już nie raz o tym przekonałem. To co może powiązać te rzeczy to błędy 0xc0000001A (memory management) oraz 0xc00000124. Jeszcze miałeś tam błąd 0xc00000024 ntfs.sys więc proponowałbym gruntownie zrobić diagnostykę dysku twardego (odczyt powierzchni+smart).
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp17\052712-21075-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e90670
Debug session time: Sun May 27 11: 09: 30.762 2012 (UTC + 2: 00)
System Uptime: 0 days 11: 51: 52.322
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 30, 0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ? : FNODOBFM: `string'+45a45 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41287
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: audiodg.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88006b2f650 -- (.trap 0xfffff88006b2f650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000ffffffff
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002da61f5 rsp=fffff88006b2f7e0 rbp=fffff88006b2f840
r8=fffff80002c4c000 r9=0000000000000001 r10=0000058000000000
r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiResolvePageFileFault+0x1115:
fffff800`02da61f5 8b4830 mov ecx,dword ptr [rax+30h] ds: 0004: 00000000`00000030=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c5b3be to fffff80002ccb1c0
STACK_TEXT:
fffff880`06b2f4e8 fffff800`02c5b3be : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : nt!KeBugCheckEx
fffff880`06b2f4f0 fffff800`02cc92ee : 00000000`00000000 00000000`00000030 00000000`00000000 00000000`fffff8a0 : nt! ? : FNODOBFM: `string'+0x45a45
fffff880`06b2f650 fffff800`02da61f5 : fffff8a0`00000048 00000000`ffffffff fffff700`01080488 fffff700`01080000 : nt!KiPageFault+0x16e
fffff880`06b2f7e0 fffff800`02d39c28 : 000007fe`f627ab87 fffff8a0`00000050 fffffa80`07b753f8 00000000`00000000 : nt!MiResolvePageFileFault+0x1115
fffff880`06b2f920 fffff800`02ce7ac3 : 00000000`00003463 000007fe`f627ab87 fffff683`ff7b13d0 fffffa80`07b753f8 : nt! ? : FNODOBFM: `string'+0x38aa7
fffff880`06b2f9b0 fffff800`02cd7769 : 00000000`00000000 000007fe`f627ab87 00000000`000007ff 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`06b2fac0 fffff800`02cc92ee : 00000000`00000008 000007fe`f627ab87 fffff880`06b2fc01 00000000`00000000 : nt!MmAccessFault+0x359
fffff880`06b2fc20 000007fe`f627ab87 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`00a5fc68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f627ab87
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ? : FNODOBFM: `string'+45a45
fffff800`02c5b3be cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ? : FNODOBFM: `string'+45a45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4f76721c
FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_: FNODOBFM: _string_+45a45
BUCKET_ID: X64_0x1a_41287_nt!_??_: FNODOBFM: _string_+45a45
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp17\052612-31637-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02c66000 PsLoadedModuleList = 0xfffff800`02eaa670
Debug session time: Sat May 26 12: 11: 51.562 2012 (UTC + 2: 00)
System Uptime: 0 days 0: 12: 22.560
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 30, 0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ? : FNODOBFM: `string'+45a45 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41287
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: TrustedInstall
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800d077650 -- (.trap 0xfffff8800d077650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000ffffffff
rdx=000000000000000c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002dc01f5 rsp=fffff8800d0777e0 rbp=fffff8800d077840
r8=fffff80002c66000 r9=0000000000000001 r10=0000058000000000
r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiResolvePageFileFault+0x1115:
fffff800`02dc01f5 8b4830 mov ecx,dword ptr [rax+30h] ds: 7780: 00000000`00000030=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c753be to fffff80002ce51c0
STACK_TEXT:
fffff880`0d0774e8 fffff800`02c753be : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d0774f0 fffff800`02ce32ee : 00000000`00000000 00000000`00000030 00000000`00000000 00000000`fffff8a0 : nt! ? : FNODOBFM: `string'+0x45a45
fffff880`0d077650 fffff800`02dc01f5 : fffff8a0`00000078 00000000`ffffffff fffffa80`07200010 fffff800`02d4c514 : nt!KiPageFault+0x16e
fffff880`0d0777e0 fffff800`02d53c28 : 00000000`76c401d0 fffff8a0`00000080 fffffa80`06ec9b08 00000000`00000000 : nt!MiResolvePageFileFault+0x1115
fffff880`0d077920 fffff800`02d01ac3 : 00000000`000034a4 00000000`76c401d0 fffff680`003b6200 fffffa80`06ec9b08 : nt! ? : FNODOBFM: `string'+0x38aa7
fffff880`0d0779b0 fffff800`02cf1769 : 00000000`00000000 00000000`76c401d0 00000000`00000000 fffff800`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0d077ac0 fffff800`02ce32ee : 00000000`00000008 00000000`76c401d0 fffffa80`06157b01 00000000`00000000 : nt!MmAccessFault+0x359
fffff880`0d077c20 00000000`76c401d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`00c7ee48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76c401d0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ? : FNODOBFM: `string'+45a45
fffff800`02c753be cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ? : FNODOBFM: `string'+45a45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4f76721c
FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_: FNODOBFM: _string_+45a45
BUCKET_ID: X64_0x1a_41287_nt!_??_: FNODOBFM: _string_+45a45
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp17\051812-22011-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e63670
Debug session time: Fri May 18 13: 44: 13.895 2012 (UTC + 2: 00)
System Uptime: 0 days 15: 10: 39.892
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa7fffffffb0, 0, fffff88007e32537, 7}
Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT: TrimAllProcesses+10b )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa7fffffffb0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88007e32537, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecd100
fffffa7fffffffb0
FAULTING_IP:
dxgmms1!VIDMM_SEGMENT: TrimAllProcesses+10b
fffff880`07e32537 488b01 mov rax,qword ptr [rcx]
MM_INTERNAL_CODE: 7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800dc76640 -- (.trap 0xfffff8800dc76640)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a00ed19f90 rbx=0000000000000000 rcx=fffffa7fffffffb0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007e32537 rsp=fffff8800dc767d0 rbp=fffff8a001668e50
r8=fffff8800dc767a8 r9=0000000000000000 r10=fffff8a010fab320
r11=fffff88007f13a08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
dxgmms1!VIDMM_SEGMENT: TrimAllProcesses+0x10b:
fffff880`07e32537 488b01 mov rax,qword ptr [rcx] ds: fffffa7f`ffffffb0=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c44ea7 to fffff80002c9e1c0
STACK_TEXT:
fffff880`0dc764d8 fffff800`02c44ea7 : 00000000`00000050 fffffa7f`ffffffb0 00000000`00000000 fffff880`0dc76640 : nt!KeBugCheckEx
fffff880`0dc764e0 fffff800`02c9c2ee : 00000000`00000000 fffffa7f`ffffffb0 00000000`00000000 00000000`0000000c : nt! ? : FNODOBFM: `string'+0x43cd1
fffff880`0dc76640 fffff880`07e32537 : fffffa80`03dadc60 fffff8a0`01668e50 fffffa80`00000000 fffff8a0`0e689dd0 : nt!KiPageFault+0x16e
fffff880`0dc767d0 fffff880`07e240a5 : fffffa80`09265ad0 fffff880`0000000c 00000000`00000000 fffff880`0dc768e0 : dxgmms1!VIDMM_SEGMENT: TrimAllProcesses+0x10b
fffff880`0dc768a0 fffff880`07e1fa8f : fffff8a0`0e7edc30 fffff8a0`0e7edc30 fffffa80`07591000 fffffa80`07523280 : dxgmms1!VIDMM_GLOBAL: AllocateResourceForPinnedAllocation+0x55
fffff880`0dc76920 fffff880`07e1f38f : fffff880`0dc76c78 00080000`00000000 fffff880`0dc76bf0 fffff880`0dc76c88 : dxgmms1!VIDMM_GLOBAL: ProcessDeferredCommand+0x19f
fffff880`0dc76a40 fffff880`07e39231 : 00000000`00000001 fffff880`07e0b0d4 fffffa80`03d3e260 fffffa80`03d3e260 : dxgmms1!VidMmiProcessSystemCommand+0x23
fffff880`0dc76a70 fffff880`07e383bc : fffff880`0dc76bd0 00000000`00000000 fffffa80`051a2ec0 00000000`00000001 : dxgmms1!VidSchiSubmitSystemCommand+0x39
fffff880`0dc76aa0 fffff880`07e0a77a : 00000000`00000000 fffffa80`03d3e260 fffffa80`051a2ec0 fffffa80`051a2ec0 : dxgmms1!VidSchiSubmitQueueCommand+0x74
fffff880`0dc76ad0 fffff880`07e3a927 : fffffa80`0746b0e0 fffffa80`06582000 fffffa80`051a2ec0 6d4d6956`0947b21e : dxgmms1!VidSchiSubmitQueueCommandDirect+0x1e6
fffff880`0dc76b60 fffff880`07e1f4b9 : fffffa80`00000001 fffffa80`066ed0a0 fffffa80`07591000 fffff880`0dc76c78 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x15f
fffff880`0dc76bd0 fffff880`07e1f8dc : fffff880`0dc76d30 fffff8a0`0e7edc30 fffff880`0dc76d30 fffff8a0`0e7edc30 : dxgmms1!VIDMM_GLOBAL: QueueSystemCommandAndWait+0xf9
fffff880`0dc76c40 fffff880`07e1afaa : 00000000`00000000 00000000`00000000 fffffa80`07591000 fffff8a0`00f82590 : dxgmms1!VIDMM_GLOBAL: QueueDeferredCommandAndWait+0x4c
fffff880`0dc76cb0 fffff880`07e01aa7 : fffff8a0`0cf848b0 fffff8a0`0c541a60 fffff880`0dc76e20 00000000`00000020 : dxgmms1!VIDMM_GLOBAL: OpenOneAllocation+0x2da
fffff880`0dc76d90 fffff880`07f36469 : 00000000`00000000 fffff880`0dc77260 00000000`00000000 fffff8a0`038a1140 : dxgmms1!VidMmOpenAllocation+0xeb
fffff880`0dc76de0 fffff880`07f2f610 : fffff880`0dc77048 fffff8a0`0a4b64e0 fffff880`0dc77220 fffff880`0dc77220 : dxgkrnl!DXGDEVICE: CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x291
fffff880`0dc76e70 fffff880`07f312ef : fffff8a0`01117000 fffff880`0dc774d0 00000000`00000000 fffff8a0`01117000 : dxgkrnl!DXGDEVICE: CreateAllocation+0xca8
fffff880`0dc77470 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE: CreateStandardAllocation+0x367
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_SEGMENT: TrimAllProcesses+10b
fffff880`07e32537 488b01 mov rax,qword ptr [rcx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VIDMM_SEGMENT: TrimAllProcesses+10b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_SEGMENT: TrimAllProcesses+10b
BUCKET_ID: X64_0x50_dxgmms1!VIDMM_SEGMENT: TrimAllProcesses+10b
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp17\040512-20826-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e91650
Debug session time: Thu Apr 5 06: 31: 41.596 2012 (UTC + 2: 00)
System Uptime: 0 days 7: 02: 33.593
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {c08a5, 0, 0, 0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000000c08a5
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x24
PROCESS_NAME: DTShellHlp.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8800122a1d5 to fffff80002cc9d40
STACK_TEXT:
fffff880`0a9556f8 fffff880`0122a1d5 : 00000000`00000024 00000000`000c08a5 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a955700 fffff880`01229e28 : 00000001`00000000 00000000`00000000 00000000`00000000 00000745`17350000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`0a955800 fffff880`01002bcf : fffffa80`05e34fb0 fffffa80`05e34c10 fffffa80`072f17e0 00000000`00000000 : Ntfs! ? : FNODOBFM: `string'+0x8ba9
fffff880`0a9558b0 fffff880`010016df : fffffa80`045d8ca0 fffffa80`05190601 fffffa80`045d8c00 fffffa80`05e34c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0a955940 fffff800`02cf1125 : fffffa80`05e34c30 fffffa80`04cf8aa0 fffffa80`03dd6cc0 fffff880`039d3180 : fltmgr!FltpDispatch+0xcf
fffff880`0a9559a0 fffff800`02cf0bf9 : 00000000`00f80001 00000000`00f80001 fffffa80`03dd6c00 00000000`00100020 : nt!IoPageRead+0x255
fffff880`0a955a30 fffff800`02cd749a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x255
fffff880`0a955ac0 fffff800`02cc7e6e : 00000000`00000000 00000000`001a000c 00000000`00222901 00000000`00000000 : nt!MmAccessFault+0x146a
fffff880`0a955c20 00000000`77b17c9c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0008e9b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b17c9c
STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs!NtfsPagingFileIo+155
fffff880`0122a1d5 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs!NtfsPagingFileIo+155
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d79997b
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155
BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155
Followup: MachineOwner
---------
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
(Ten post był ostatnio modyfikowany: 12.06.2012 10:23 przez thermalfake.)
12.06.2012 10:16
|
Podziękowania od: |
tomson007
|
|
tomson007
Nowy
Liczba postów: 5
|
RE: Bluescreen przy wyłączaniu komputera
A czym proponujesz zrobic test Ram? i kazda kosc testowac z osobna czy moga byc wszystkie na raz? Do dysku co byś polecił? Płyta wydaje mi sie podejrzana odkad padl mi 1 zasilacz, teraz juz 2. 1 byl Coolermastera a 2 Corsair. Wogole to w ciagu 4,5 roku na tym komputerze padly mi 2 zasilacze + karta dziekowa Creative + karta zintegrowana.
Notatka została dodana 12.06.2012 21:52 . Ostatnia edycja dokonana 12.06.2012 21:52 przez peciaq:
Proszę popraw brak polskich znaków w swoich postach.
|
Podziękowania od: |
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Bluescreen przy wyłączaniu komputera
Problem w tym, że nie ma lepszego narzędzia jak memtest. Ewentualnie alternatywą jest test obciążeniowy systemu np Orthos (on jest na procesory 2 rdzeniowe), AMD Overdrive, OCCT itp.
Do dysku HDTune, MHDD, Victoria (ze wskazaniem na ten ostatni - nie działa pod vistą/7 ale jest jako narzędzie diagnostyczne na wielu systemach livecd). Zasilaczy wcale nie łączyłbym z płytą, po prostu miałeś pecha do tych egzemplarzy. Chociaż już raz przechodziłem uwalania zasilaczy przez płytę główną ale jednorazowo i nie po czasie.
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
Podziękowania od: |
|
|
tomson007
Nowy
Liczba postów: 5
|
RE: Bluescreen przy wyłączaniu komputera
HDtune nie pokazuje smarta pod Windows 7 wiec odpada, MHDD zrobię w nocy skan ale ciężko ze screenem przy uruchamianiu z cd wiec będę musical strzelić zdjęcie wyników SMART. A do chyba dopiero jutro jak dorwę aparat. OCCT zaraz zarzucę ( procesor core 2 quad wiec pozostałe programy do testów ram chyba odpadają) zalaczam screen z crystaldiscinfo. rewelacji nie ma chyba?
(Ten post był ostatnio modyfikowany: 14.06.2012 20:31 przez tomson007.)
14.06.2012 20:29
|
Podziękowania od: |
|
|
peciaq
VIP
Liczba postów: 5.100
|
RE: Bluescreen przy wyłączaniu komputera
HDTune również u mnie nie pokazujesz danych SMART. Używam zatem CrystalDisk Info, polecam go również tobie.
|
Podziękowania od: |
|
|
tomson007
Nowy
Liczba postów: 5
|
RE: Bluescreen przy wyłączaniu komputera
no właśnie wyżej wrzuciłem screen z CrystalDisk Info OCCT sobie idzie właśnie, na jaki czas ustawic?
(Ten post był ostatnio modyfikowany: 14.06.2012 20:38 przez tomson007.)
14.06.2012 20:32
|
Podziękowania od: |
|
|
tomson007
Nowy
Liczba postów: 5
|
RE: Bluescreen przy wyłączaniu komputera
(14.06.2012 20:32)tomson007 napisał(a): no właśnie wyżej wrzuciłem screen z CrystalDisk Info OCCT sobie idzie właśnie, na jaki czas ustawic?
W OCCT nic nie wyszło. To samo w MHDD. Ale co z tym realekowanymi sektorami?
(Ten post był ostatnio modyfikowany: 15.06.2012 16:29 przez tomson007.)
15.06.2012 16:29
|
Podziękowania od: |
|
|
peciaq
VIP
Liczba postów: 5.100
|
RE: Bluescreen przy wyłączaniu komputera
Zapuść mu defragmentację.
|
Podziękowania od: |
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Bluescreen przy wyłączaniu komputera
(15.06.2012 16:29)tomson007 napisał(a): (14.06.2012 20:32)tomson007 napisał(a): no właśnie wyżej wrzuciłem screen z CrystalDisk Info OCCT sobie idzie właśnie, na jaki czas ustawic?
W OCCT nic nie wyszło. To samo w MHDD. Ale co z tym realekowanymi sektorami?
Na razie nic. Nie jest to dobra oznaka kondycji dysku twardego.
http://dyski.cdrinfo.pl/artykuly/smart/strona3.php
Bacznie obserwuj ten parametr. Jeśli będzie się nadal powiększał z czasem dysk będzie musiał iść na śmietnik. System też pośle ostrzeżenia o wykonaniu kopii zapasowej monitorując smart'a.
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
Podziękowania od: |
|
|