Blue screen 0x0000008e i nv4_disp.dll

**Posty:** 87 · przez **Hurassus** 27 Kwi 2010, 15:42

No więc ostatnio podczas gry w Gothica pojawił się takowy... Tutaj daję odczyt pliku DMP:

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini042510-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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Sun Apr 25 16:07:44.546 2010 (GMT+2) System Uptime: 0 days 4:30:37.280 ********************************************************************* * 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 Loading unloaded module list .................... Unable to load image nv4_disp.dll, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nv4_disp.dll *** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, bfbd7be4, abfc7aa8, 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 *** *** *** ************************************************************************* ********************************************************************* * 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 : nv4_disp.dll ( nv4_disp+204be4 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: bfbd7be4, The address that the exception occurred at Arg3: abfc7aa8, Trap Frame Arg4: 00000000 Debugging Details: ------------------ ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 481c0584 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo FAULTING_IP: nv4_disp+204be4 bfbd7be4 8b5500 mov edx,dword ptr [ebp] TRAP_FRAME: abfc7aa8 -- (.trap 0xffffffffabfc7aa8) ErrCode = 00000000 eax=93f01338 ebx=0000006e ecx=00000001 edx=00770002 esi=e1665808 edi=0000006e eip=bfbd7be4 esp=abfc7b1c ebp=0c552ffe iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 nv4_disp+0x204be4: bfbd7be4 8b5500 mov edx,dword ptr [ebp] ss:0010:0c552ffe=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E LAST_CONTROL_TRANSFER: from bfbd7ffd to bfbd7be4 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. abfc7b44 bfbd7ffd e2a005c0 e2b03800 000000db nv4_disp+0x204be4 abfc7b48 e2a005c0 e2b03800 000000db 00000001 nv4_disp+0x204ffd abfc7b4c e2b03800 000000db 00000001 000001b6 0xe2a005c0 abfc7b50 00000000 00000001 000001b6 e2a005c0 0xe2b03800 STACK_COMMAND: kb FOLLOWUP_IP: nv4_disp+204be4 bfbd7be4 8b5500 mov edx,dword ptr [ebp] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nv4_disp+204be4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nv4_disp IMAGE_NAME: nv4_disp.dll BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------

Dlaczego się pojawił? I dwa razy jeszcze wcześniej trochę pojawiały mi się Blue screeny page_fault_in_nonpaged_area, ale nie ma ich w folderze minudup.

**Posty:** 1916 · przez **lamar** 27 Kwi 2010, 17:02

Kod: Zaznacz wszystko: Może to być wina sterowników grafiki, ale przyjrzałbym się także innym rzeczom: 1. Temp. grafiki w czasie gry. A także stabilność po przetaktowaniu. BSOD z info o nv4_disp.dll występuje, gdy zbytnio ją przetaktuję. 2. Zasilanie. Może zasilacz daje za niskie napięcie na grafikę, lub ma chwilowe skoki mocy. 3. Taktowanie szyny PCIe. Może zmiana ustawień taktowania szyny PCIe w biosie z Auto na 100 lub 101MHz, zwiększy stabilność systemu w 3D. 4. Sterowniki do chipsetu płyty głównej, zwłaszcza odpowiedzialny za szynę PCIe? Może jest nowsza wersja sterowników do chipsetu?

Zainstaluj najnowsze stery do grafiki.
reinstalacja-update-sterownika-karty-graficznej-vp792393.html

**Posty:** 87 · przez **Hurassus** 27 Kwi 2010, 19:46

To pomoże?

**Posty:** 12734 · przez **Mikou@j** 27 Kwi 2010, 19:47

Hurassus napisał(a):To pomoże?

Nie zaszkodzi.

**Posty:** 87 · przez **Hurassus** 27 Kwi 2010, 20:08

Aa, jeśli chodzi już o kartę graficzną, to jak już jakiś dłuższy czas pogram w jakąś grę, to komputer zaczyna choćby przyspieszać i zwalniać... To znaczy chwilę tak głośniej pobuczy, przestanie, i znowu buczy. Jak wyłączy się grę to mija to. Może to mieć coś wspólnego z tym blue screenem?

**Posty:** 1916 · przez **lamar** 27 Kwi 2010, 22:01

Podaj markę i moc zasilacza i screena z Evresta Ultimate zakładka czujnik.

**Posty:** 87 · przez **Hurassus** 28 Kwi 2010, 09:14

Zasilacz ModeCom 500W Premium.

Screen z Everesta:

http://www.i-point.nazwa.pl/host/upload/1435/1272438692674541.JPG

**Posty:** 10264 · przez **Mike** 28 Kwi 2010, 10:48

Brakuje jeszcze najważniejszego - podaj całą konfigurację kompa.

**Posty:** 87 · przez **Hurassus** 28 Kwi 2010, 15:42

Procesor:
Core 2 Duo (775) Intel E7400 2.80 GHz 3MB BOX

Właściwości procesora
Typ procesora Intel Pentium III Xeon, 2800 MHz (8 x 350)
Zbiór instrukcji x86, x86-64, MMX, SSE, SSE2, SSE3
Oryginalna częstotliwość taktowania 2800 MHz
Pamięć podręczna L1 kodu 32 KB
Pamięć podręczna L1 danych 32 KB
Pamięć podręczna L2 3 MB (On-Die, ATC, Full-Speed)

Multi CPU
ID płyty głównej SE2
CPU #0 Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz, 2799 MHz
CPU #1 Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz, 2799 MHz

Producent procesora
Nazwa firmy Intel Corporation
Informacje o produkcie http://www.intel.com/products/browse/processor.htm

Wykorzystanie procesora
Procesor nr 1 / rdzeń nr 1 / układ HTT nr 1 0 %
Procesor nr 1 / rdzeń nr 1 / układ HTT nr 2 9 %

Pamięć:

DDRAM2 Kingstone 2048 MB 800MHz CL5 (x2)
Pamięć fizyczna
W sumie 3327 MB
Użytych 631 MB
Wolne 2695 MB
Wykorzystanie 19 %

Rozmiar pliku wymiany
W sumie 5210 MB
Użytych 524 MB
Wolne 4686 MB
Wykorzystanie 10 %

Pamięć wirtualna
W sumie 8537 MB
Użytych 1155 MB
Wolne 7382 MB
Wykorzystanie 14 %

Physical Address Extension (PAE)
Obsługiwane przez system operacyjny Tak
Obsługiwane przez procesor Tak
Aktywna Tak

Płyta główna:
Socket 775 Asus P5Q SE2 (P45 PCI-E DDR2)

Pole Wartość
Właściwości płyty głównej
ID płyty głównej 64-0601-000001-00101111-042909-Eaglelake$A1121001_BIOS DATE: 04/29/09 10:58:25 VER: 08.00.14
Nazwa płyty głównej Nieznane

Właściwości magistrali FSB
Typ magistrali Intel AGTL+
Szerokość magistrali 64-bitowy(a)
Rzeczywista częstotliwość taktowania 350 MHz
Efektywna częstotliwość taktowania 350 MHz
Przepustowość 2800 MB/sek

Karta graficzna:
PCI-E Asus GF 9600GT 512 MB 256 bit

Właściwości karty wideo
Opis urządzenia NVIDIA GeForce 9600 GT
Napis z karty GeForce 9600 GT
Napis z BIOS'u Version 62.94.54.00.00
Typ mikroukładu GeForce 9600 GT
Typ konwertera DAC Integrated RAMDAC
Zainstalowane sterowniki nv4_disp (6.14.11.7516 - nVIDIA ForceWare 75.16)
Rozmiar pamięci 512 MB

Producent karty wideo
Nazwa firmy NVIDIA Corporation
Informacje o produkcie http://www.nvidia.com/view.asp?PAGE=products
Uaktualnienie sterowników http://www.nvidia.com/content/drivers/drivers.asp

Zasilacz:
ModeCom 500W Premium

**Posty:** 10264 · przez **Mike** 28 Kwi 2010, 18:10

Na początek:

lamar14 napisał(a):Zainstaluj najnowsze stery do grafiki.
http://forum.programosy.pl/reinstalacja-update-sterownika-karty-graficznej-vp792393.html

Oczywiście stosuj się do poradnika.
Sterowniki zainstaluj te => 197.45
Możliwe, że jest uszkodzony sterownik od karty graficznej lub nieprawidłowo został zainstalowany.

Jeżeli to nie pomoże, to pożycz od kogoś markowy zasilacz o mocy przynajmniej 400W i przetestuj na swoim kompie.
Ten, który masz nie ukrywając nie należy do najlepszych.
http://forum.programosy.pl/czarna-lista-zasilaczy-czyli-jaki-zasilacz-kupic-vt113278.html

**Posty:** 87 · przez **Hurassus** 28 Kwi 2010, 19:29

A właśnie-pytanie dotyczące tego mam.

Jak już włączę tryb awaryjny, użyje Driver Sweepera to wystarczy dać uruchom ponownie, i komputer sam się włączy nie w trybie awaryjnym, ale normalnie?

**Posty:** 1903 · przez **MichuPower** 28 Kwi 2010, 19:32

Tak - włączy się normalnie.

**Posty:** 10264 · przez **Mike** 28 Kwi 2010, 19:32

Dokładnie tak jak mówisz.
Jak dasz uruchom ponownie w awaryjnym, to system włączy się już w trybie normalnym (no chyba, że podczas uruchamiania wciśniesz znowu F8).

**Posty:** 87 · przez **Hurassus** 28 Kwi 2010, 19:34

Aha, ok. Dodam też, że całkiem niedawno były wymieniane wszystkie komponenty w komputerze prócz dysku twardego. Był on jednak formatowany. Mogły zostać tam jakieś stare części po sterownikach? Bo o to praktycznie chodzi.

**Posty:** 10264 · przez **Mike** 28 Kwi 2010, 20:12

Dysk był formatowany, więc taka opcja odpada.
Zastosuj się do tego, co napisałem wcześniej.

**Posty:** 87 · przez **Hurassus** 28 Kwi 2010, 20:19

Była jednak formatowana tylko partycja C, więc może na D coś zostało, bo kiedyś bawiłem się sterownikami, a ważniejsze dane z C przeniosłem na D...

Czyli mam niby ten zasilacz przetestować czyiś? Problem w tym, że raczej bym tego nie potrafił zrobić... Nie ma innego sposobu na diagnostyke zasilacza?

**Posty:** 10264 · przez **Mike** 28 Kwi 2010, 20:36

Hurassus napisał(a):yła jednak formatowana tylko partycja C, więc może na D coś zostało, bo kiedyś bawiłem się sterownikami, a ważniejsze dane z C przeniosłem na D...

Sterowniki były w systemie - skoro go usunąłeś, to sterowniki także zostały skasowane.

Hurassus napisał(a):Czyli mam niby ten zasilacz przetestować czyiś?

Tak - pożyczyć od kogoś markowy zasilacz o mocy co najmniej 400W i podłącz go do swojego komputera, aby przetestować.
Nie ma w tym nic trudnego - odłączysz obecny i podłączasz zastępczy. Kabli nie pomylisz, bo każdy rodzaj wtyku jest inny.

Sterowniki przeinstalowałeś wg. poradnika?

**Posty:** 87 · przez **Hurassus** 28 Kwi 2010, 20:38

Jeszcze tego nie zrobiłem... Poza tym nie byłoby takie łatwe zobaczyć, czy to od tego, bo ten Blue sreen wyświetlił mi się tylko 3 razy (2 razy jeden i raz inny), i nie wiem kiedy pojawił by się następny...

Dodano Dzisiaj, 15:23:
Dziś, zaraz po włączeniu komputera pojawił się jeszcze jeden Blue screen... Tutaj DMP:

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini050510-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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Wed May 5 13:25:22.671 2010 (GMT+2) System Uptime: 0 days 0:00:33.405 ********************************************************************* * 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 Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 805c19c8, b56efa48, 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ea9c8 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 805c19c8, The address that the exception occurred at Arg3: b56efa48, Trap Frame Arg4: 00000000 Debugging Details: ------------------ ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: nt FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0d EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo FAULTING_IP: nt+ea9c8 805c19c8 8b4e1c mov ecx,dword ptr [esi+1Ch] TRAP_FRAME: b56efa48 -- (.trap 0xffffffffb56efa48) ErrCode = 00000000 eax=b56efbb8 ebx=8a15b950 ecx=00000000 edx=00000000 esi=00000001 edi=00000000 eip=805c19c8 esp=b56efabc ebp=b56efb8c iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 nt+0xea9c8: 805c19c8 8b4e1c mov ecx,dword ptr [esi+1Ch] ds:0023:0000001d=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E LAST_CONTROL_TRANSFER: from 805cf6bd to 805c19c8 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. b56efb8c 805cf6bd 8a15b968 b56efbb8 001f0fff nt+0xea9c8 b56efce4 805cf9dd 00bce348 001f0fff 00000000 nt+0xf86bd b56efd38 8054060c 00bce348 001f0fff 00000000 nt+0xf89dd b56efd64 7c90eb94 badb0d00 00bcdf6c b540ad98 nt+0x6960c b56efd68 badb0d00 00bcdf6c b540ad98 b540adcc 0x7c90eb94 b56efd6c 00bcdf6c b540ad98 b540adcc 00000000 0xbadb0d00 b56efd70 b540ad98 b540adcc 00000000 00000000 0xbcdf6c b56efd74 b540adcc 00000000 00000000 00000000 0xb540ad98 b56efd78 00000000 00000000 00000000 00000000 0xb540adcc STACK_COMMAND: kb FOLLOWUP_IP: nt+ea9c8 805c19c8 8b4e1c mov ecx,dword ptr [esi+1Ch] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt+ea9c8 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------

Co on znaczy? Coś tam widzę z Driver Fault, może ktoś pomóc zinterpretować jego treść?

**Posty:** 1916 · przez **lamar** 05 Maj 2010, 19:26

Wejdź do konsoli odzyskiwania:

Wpisz MAP ARC
zapamiętaj pod, którą literą jest napęd

Wpisz:
expand X:\i386\ntoskrnl.ex_ C:\WINDOWS\System32\

x-cdrom, c- dysk systemowy

Zauważ, że po expand i przed C:\windows\... jest spacja
expand<spacja>X:\i386\ntoskrnl.ex_<spacja>C:\WINDOWS\System32\

Wpisz exit i zrestartuj komputer.

**Posty:** 87 · przez **Hurassus** 06 Maj 2010, 13:37

Nie rozumiem... W jakim celu? Po zresetowaniu komputera, gdy BSOD mi wyskoczył, włączył się już bez problemu...

Kto jest na forum