Windbg analiza

**Posty:** 1175 · przez **Manieq** 12 Sty 2011, 20:55

Witam. Otóż składałem nowy komputer, no i wrzuciłem Windowsa 7. Przy graniu codziennie wyskakuje jakiś bluescreen.
Tutaj treść jednego z logów:

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\010611-14648-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 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e8ce50 Debug session time: Thu Jan 6 20:45:18.103 2011 (UTC + 1:00) System Uptime: 0 days 3:04:33.508 ********************************************************************* * 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 D1, {fffff880013000fc, 2, 8, fffff880013000fc} 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 ***** 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 *** *** *** ************************************************************************* Probably caused by : Ntfs.sys ( Ntfs+f50fc ) Followup: MachineOwner ---------

Co można zrobić ? Wgrywałem na nowo system, bez efektu.

**Posty:** 565 · przez **KamilK** 12 Sty 2011, 21:19

Problemem jest plik Ntfs.sys.Jest to pliczek sterownika który umożliwia dyskowi odczyt/zapis na partycjach sformatowanych w NTFS. W parze przeważnie wyskakuje z BSODEM odnośnie karty graficznej nVidi. Napisałeś że występuje podczas grania wiec problemu szukamy w sterowniku karty graficznej...Zainstaluj inne sterowniki wg tego sposobu:
http://forum.programosy.pl/reinstalacja-update-sterownika-karty-graficznej-vt103090.html. Daj znać co wyszło. Profilaktycznie podaj marke i moc zasilacza.

Manieq napisał(a):jakiś bluescreen

Dobrze by też było gdybyś podał dokładne komunikaty błędów.

**Posty:** 1175 · przez **Manieq** 12 Sty 2011, 22:32

Sterowniki zainstalowane, błąd nadal wyskakuje. Niema podanego konkretnie numeru jak to bywało np. w XP.
Zasilacz to Corsair 500W [CMPSU-500CXEU]
Jutro komputer będę miał u siebie, miałem zamiar wrzucić 32bitowy system ale zapomniałem iż nie przeczyta on 4GB ram. Więc system mija się z celem, spróbuje odpalić zaraz te komendy u znajomego zdalnie.

**Posty:** 9184 · przez **MUTOPOMPKA** 12 Sty 2011, 22:34

KamilK napisał(a):Dobrze by też było gdybyś podał dokładne komunikaty błędów.

A po co? Przecież wszystko widać jak na dłoni:

Manieq napisał(a):BugCheck D1, {fffff880013000fc, 2, 8, fffff880013000fc}

.
Kod błędu: 0xD1
Nazwa błędu: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Znany często błąd. Związany ze sprzętem oraz systemem/oprogramowaniem/sterownikami. Poniżej podana solucja do wszystkich możliwych wywołań BSOD-a 0xD1. Ale wg mnie, gdy wywala Ci błąd w pliku ntfs.sys spowodowane jest to błędem zapisu na dysk, więc p[rzetestować wszystkie partycje komendą: chkdsk x: /f /r gdzie x: to Twoje oznaczenia partycji dysku.

Proszę jeszcze popatrzeć: ---> TUTAJ <---

**Posty:** 1175 · przez **Manieq** 13 Sty 2011, 18:49

Chkdsk nie wykazało żadnych błędów. Jakieś pomysły ? Dzisiaj pojawił się u znajomego dwa razy bluescreen.
Dorzucam log z najnowszego błędu:

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\010111-14601-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: symsrv symsrv.dll * e *: * symbole http://msdl.microsoft.com/download/symbols Executable search path is: Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e86e50 Debug session time: Sat Jan 1 11:45:50.588 2011 (UTC + 1:00) System Uptime: 0 days 0:00:14.383 Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** 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 3B, {c000001d, fffff80002c6b652, fffff88003a11bf0, 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 *** *** *** ************************************************************************* Probably caused by : hardware ( nt+22652 ) Followup: MachineOwner ---------

Windbg analiza

Windbg analiza

Windbg analiza

Windbg analiza

Windbg analiza

Windbg analiza

Kto jest na forum