Witam
Niedawno, tzn. w sobote ( 19.01.08) postawiłem nowy system na nowym dysku. Dysk to nowa Baracuda 500GB z 32MB cache, działa sprawnie, więc ona nie jest źródłem problemu. Sprawdzałem również pamięć ram programem memtest ale nie pamiętam juz, w jakiej on był wersji. Z pamięcią wszystko ok. Zakładam ze procesor jest sprawny, ponieważ mogę to do was napisać i nawet przy dużym obciążeniu przez dłuższy czas nic mu się nie dzieje. Problem jest natomiast taki, że nie potrafię sprawdzić płyty głównej i nie wiem czy to ona przypadkiem nie generuje problemu. A problem wygląda następująco:
Pojawiają mi się podczas normalnej pracy, a nawet podczas nic nie robienia (komp działa) plus winamp nagłe resety - bluescreen i takie tam.
Po każdym z nich sprawdzam plik minidump z tego wydarzenia i sprawdzam pliki, które prawdopodobnie powodują reset. Podaje je w kolejności powodowania kolejnych padów:
-
ntfs.sys
-
sptd.sys
-
nv4_mini.sys
Ten ostatni problem spowodował dwa razy.
Sytuacja nie jest nowa, miałem tak bardzo często przy poprzednim systemie, jednak stwierdziłem ze to przez dysk twardy, a ze miałem w planie kupno nowego to jakoś tą sytuacje znosiłem i nie chciałem jej rozwiązywać. W momencie, gdy zainstalowałem normalny system na nowym dysku (wcześniej miałem win MX 4) i sytuacja się powtórzyła postanowiłem cos zrobić.
I w tym miejscu prószę was o pomoc. Nie wiem jak sobie z tym poradzić. Gdyby to jeden plik powodował te resety to podejrzewam ze wymiana go mogłaby sytuacje naprawić. Jednak w momencie, gdy problem powodują losowe pliki to juz nie wiem, co zrobić. Nie wiem, dlaczego ale o cala sytuacje podejrzewam Zone Alarm-a. Takowego mam zainstalowanego. Przełączyłem się teraz na zaporę Windows. Załączam do posta plik dziennika, w którym zostawiłem tylko ostrzeżenia i błędy. Nie wiem jak to interpretować. Prószę tutaj również o pomoc.
Z góry za nią serdecznie dziękuje.
Typ Data Godzina Źródło Kategoria Zdarzenie Użytkownik Komputer
Ostrzeżenie 2008-01-23 22:29:29 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-23 22:02:10 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-23 21:48:30 Tcpip Brak 4226 Brak PAZUZU
Błąd 2008-01-23 21:48:13 System Error (102) 1003 Brak PAZUZU
Błąd 2008-01-23 21:47:54 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:47:54 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:47:54 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 21:47:35 Service Control Manager Brak 7034 Brak PAZUZU
Ostrzeżenie 2008-01-23 21:20:06 Tcpip Brak 4226 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:08:11 SideBySide Brak 32 Brak PAZUZU
Ostrzeżenie 2008-01-23 21:06:23 Tcpip Brak 4226 Brak PAZUZU
Błąd 2008-01-23 21:05:47 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:05:47 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 21:05:47 SideBySide Brak 32 Brak PAZUZU
Ostrzeżenie 2008-01-23 18:35:46 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-23 17:41:09 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-23 17:13:50 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-23 17:00:10 Tcpip Brak 4226 Brak PAZUZU
Błąd 2008-01-23 16:59:59 System Error (102) 1003 Brak PAZUZU
Błąd 2008-01-23 16:59:52 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 16:59:52 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 16:59:52 SideBySide Brak 32 Brak PAZUZU
Ostrzeżenie 2008-01-23 14:10:20 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-23 12:21:05 Tcpip Brak 4226 Brak PAZUZU
Błąd 2008-01-23 12:14:31 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 12:14:31 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 12:14:31 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 11:41:23 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:41:23 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:41:23 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 11:41:01 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:41:01 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:41:01 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 11:40:06 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:40:06 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:40:06 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 11:40:06 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:40:06 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:40:06 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 11:39:46 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:39:46 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:39:46 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 11:39:44 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:39:44 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:39:44 SideBySide Brak 32 Brak PAZUZU
Błąd 2008-01-23 11:39:39 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:39:39 SideBySide Brak 59 Brak PAZUZU
Błąd 2008-01-23 11:39:39 SideBySide Brak 32 Brak PAZUZU
Ostrzeżenie 2008-01-23 11:26:27 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-23 10:59:09 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-23 10:45:29 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-22 23:45:58 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-22 21:56:44 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-22 21:02:07 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-22 20:34:47 Tcpip Brak 4226 Brak PAZUZU
Ostrzeżenie 2008-01-22 20:21:07 Tcpip Brak 4226 Brak PAZUZU
Błąd 2008-01-21 04:00:01 System Error (102) 1003 Brak PAZUZU
Błąd 2008-01-20 23:12:26 atapi Brak 11 Brak PAZUZU
Błąd 2008-01-20 23:12:26 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 23:12:16 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 23:12:06 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 23:11:56 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 23:11:46 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:56:14 atapi Brak 11 Brak PAZUZU
Błąd 2008-01-20 22:56:14 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:56:04 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:55:54 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:55:44 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:55:34 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:51:09 atapi Brak 11 Brak PAZUZU
Błąd 2008-01-20 22:51:09 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:50:59 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:50:49 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:50:39 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:50:29 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:47:36 atapi Brak 11 Brak PAZUZU
Błąd 2008-01-20 22:47:36 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:47:26 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:47:16 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:47:06 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:46:56 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:45:12 atapi Brak 11 Brak PAZUZU
Błąd 2008-01-20 22:45:12 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:45:02 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:44:52 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:44:42 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 22:44:32 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-20 21:17:10 System Error (102) 1003 Brak PAZUZU
Ostrzeżenie 2008-01-20 20:26:37 USER32 Brak 1073 SYSTEM PAZUZU
Ostrzeżenie 2008-01-20 20:25:09 USER32 Brak 1073 SYSTEM PAZUZU
Ostrzeżenie 2008-01-20 18:13:19 Print Brak 20 SYSTEM PAZUZU
Ostrzeżenie 2008-01-20 17:59:53 Print Brak 20 SYSTEM PAZUZU
Ostrzeżenie 2008-01-20 17:18:46 USER32 Brak 1073 SYSTEM PAZUZU
Ostrzeżenie 2008-01-20 17:18:36 USER32 Brak 1073 SYSTEM PAZUZU
Ostrzeżenie 2008-01-20 17:17:39 USER32 Brak 1073 SYSTEM PAZUZU
Błąd 2008-01-19 21:25:41 atapi Brak 11 Brak PAZUZU
Błąd 2008-01-19 21:25:41 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-19 21:25:31 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-19 21:25:21 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-19 21:25:11 atapi Brak 9 Brak PAZUZU
Błąd 2008-01-19 21:25:01 atapi Brak 9 Brak PAZUZU
Dołączam również pliki wynikowe z poszczególnych Dump Files: 1. Plik ntfs.sys
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C]
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 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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Sun Jan 20 21:15:56.765 2008 (GMT+1)
System Uptime: 0 days 0:49:01.349
*********************************************************************
* 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 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 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, {1902fe, b764a650, b764a34c, 804f2e79}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for fltMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltMgr.sys
*************************************************************************
******
******
***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 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : Ntfs.sys ( Ntfs+2d5c5 )
Followup: MachineOwner
---------
-
sptd.sys
Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C]
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 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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Mon Jan 21 03:58:36.046 2008 (GMT+1)
System Uptime: 0 days 4:48:29.778
-
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 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 USBPORT.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
-
-
Bugcheck Analysis *
-
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {10, 5, 0, 804d90aa}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
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 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 argument when starting the debugger. *
-
using .sympath and .sympath+ *
Probably caused by : sptd.sys ( sptd+11243 )
Followup: MachineOwner
-
-
Plik nv4_mini.sys dwa razy. a)
Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C]
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 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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Wed Jan 23 16:58:33.875 2008 (GMT+1)
System Uptime: 0 days 6:15:52.530
-
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 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_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
-
-
Bugcheck Analysis *
-
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {badb0d08, 9, 0, f7dd459f}
***** 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
-
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 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 argument when starting the debugger. *
-
using .sympath and .sympath+ *
Probably caused by : nv4_mini.sys ( nv4_mini+5d59f )
Followup: MachineOwner
-
b) drugi raz
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C]
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 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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Wed Jan 23 21:46:30.234 2008 (GMT+1)
System Uptime: 0 days 0:41:51.842
*********************************************************************
* 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 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_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {81, 9, 0, f7dd4578}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for amdk7.sys
*** ERROR: Module load completed but symbols could not be loaded for amdk7.sys
*************************************************************************
******
******
***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 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : nv4_mini.sys ( nv4_mini+5d578 )
Followup: MachineOwner
---------