What’s wrong on earth, gurus please help me!!
This is part of the output when I open one minidump file using windbg:
"
Loading User Symbols
Loading unloaded module list
…
ERROR: Unable to find system thread 2
ERROR: The thread being debugged has either exited or cannot be accessed
ERROR: Many commands will not work properly
ERROR: Exception 80000003 occurred on unknown thread 2
"
And below is from dumpchk:
Microsoft (R) Windows Debugger Version 6.0.6001.18000
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\zh\DriverProjects\crashReport\deploy\crashReport deploy v3.18\192.168.0.94 08-24-12 11;47;03.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 2
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
Kernel base = 0x804d5000 PsLoadedModuleList = 0x8055b720
Debug session time: Sun Feb 13 10:34:57.897 17420 (GMT+8)
System Uptime: not available
ERROR: Unable to find system thread 2
ERROR: The thread being debugged has either exited or cannot be accessed
ERROR: Many commands will not work properly
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 2
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
…
The call to LoadLibrary(ext) failed, Win32 error 2
“Can not find specified file.”
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 2
“Can not find specified file.”
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kext) failed, Win32 error 2
“Can not find specified file.”
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kdexts) failed, Win32 error 2
“Can not find specified file.”
Please check your debugger configuration and/or network access.
ERROR: Exception 80000003 occurred on unknown thread 2
WARNING: The debugger does not have a current process or thread
WARNING: Many commands will not work
----- 32 bit Kernel Mini Dump Analysis
DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
KdSecondaryVersion 00000000
DirectoryTableBase 0aa90020
PfnDataBase 805600c8
PsLoadedModuleList 8055b720
PsActiveProcessHead 805618b8
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 0000007e
BugCheckParameter1 c0000005
BugCheckParameter2 805008ba
BugCheckParameter3 b791c8bc
BugCheckParameter4 b791c5b8
PaeEnabled 00000001
KdDebuggerDataBlock 8054b2e0
MiniDumpFields 00000dff
TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000ce8
DriverListOffset 000038f8
DriverCount 0000008b
StringPoolOffset 00006240
StringPoolSize 00001370
BrokenDriverOffset 00000000
TriageOptions 000000c1
TopOfStack b791c318
DebuggerDataOffset 00003668
DebuggerDataSize 00000290
DataBlocksOffset 000075b0
DataBlocksCount 00000003
b83b0000 - b83b0fff at offset 000075e0
895f7000 - 895f7fff at offset 000085e0
804fd000 - 804fdfff at offset 000095e0
Max offset a5e0, 5a20 from end of file
WARNING: The debugger does not have a current process or thread
WARNING: Many commands will not work
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d5000 PsLoadedModuleList = 0x8055b720
Debug session time: Sun Feb 13 10:34:57.897 17420 (GMT+8)
System Uptime: not available
WARNING: The debugger does not have a current process or thread
WARNING: Many commands will not work
^ Illegal thread error in ‘lmt’
WARNING: The debugger does not have a current process or thread
WARNING: Many commands will not work
The call to LoadLibrary(ext) failed, Win32 error 2
“Can not find specified file.”
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 2
“Can not find specified file.”
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kext) failed, Win32 error 2
“Can not find specified file.”
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kdexts) failed, Win32 error 2
“Can not find specified file.”
Please check your debugger configuration and/or network access.
No export analyze found
Finished dump check</symbol_path></symbol_path>