Nie wiedziałem który z szczęściu błędów wybrać, wiec wstawiłem wszystkie
Oto pierwszy, wstwilem go w calości.
Microsoft (R) Windows Debugger Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032807-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
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Mar 28 18:19:59.375 2007 (GMT+2)
System Uptime: 0 days 2:56:29.085
*********************************************************************
* 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, bfb08c98, b552eb00, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : nv4_disp.dll ( nv4_disp+134c98 )
Followup: MachineOwner
---------
Oto drugi, wstawilem tylko istotna czesc.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfb08c98, 9e3a9b00, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : nv4_disp.dll ( nv4_disp+134c98 )
Followup: MachineOwner
---------
Trzeci :
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {81, 2, 0, 89c04ca0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : ntoskrnl.exe ( nt+6e0bf )
Followup: MachineOwner
---------
Czwarty:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfb09c98, 8b4c9ac8, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : nv4_disp.dll ( nv4_disp+134c98 )
Followup: MachineOwner
---------
Piąty:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {8977fa08, 8973fb10, bacebcbc, 1}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*********************************************************************
* 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+ *
*********************************************************************
ERROR - could not read driver name for bugcheck parameter 3
Unable to load image prosync1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for prosync1.sys
*** ERROR: Module load completed but symbols could not be loaded for prosync1.sys
Probably caused by : nv4_disp.dll ( nv4_disp+1eeed )
Followup: MachineOwner
---------
No i szósty :
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {e4f7d88c, 0, bfcdbbb4, 1}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : nv4_disp.dll ( nv4_disp+306bb4 )
Followup: MachineOwner
---------
Miłego czytania
[ Dodano: Dzisiaj o 10:36 ] Mike013 napisał(a):ykes, pobierz ten program => http://www.strefabezpieczenstwa.pl/viewtopic.php?t=183
i zastasuj się do
Cytat:
Debugging Tools for Windows i pliki minidump
Byłbym zapomniał, mój poprzedni post dotyczy tego
