Windows 2000Post your Windows 2000 related questions here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
Hi, My exchange server is crashing frequently and it will only boot by choosing the "last known good configuration". I have run the great utility you have on this site, can anyone give me some ideas on this?
Opened log file 'c:\debuglog.txt'
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINNT\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINNT;C:\WINNT\system32;C:\WINNT\system32\drivers
Missing image name, possible corrupt data.
Unable to add module at 00000000
Debugger can not determine kernel base address
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Product: LanManNt, suite: TerminalServer SingleUserTS
Kernel base = 0x80400000 PsLoadedModuleList = 0x80480780
Debug session time: Mon Jan 17 15:19:31 2005
System Uptime: 0 days 0:00:29.292
WARNING: Unable to reset page directories
Missing image name, possible corrupt data.
Unable to add module at 00000000
Debugger can not determine kernel base address
Loading Kernel Symbols
Missing image name, possible corrupt data.
.Unable to add module at 00000000
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 0, 0, 0}
***** Debugger could not find nt in module list, module list might be corrupt.
***** Followup with Debugger team
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Probably caused by : Unknown_Image
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt.
***** Followup with Debugger team
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
eax=ffdff13c ebx=0000007f ecx=80036000 edx=00000000 esi=00000000 edi=00000000
eip=80465d49 esp=8046daf8 ebp=00000000 iopl=0 nv up di ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000086
80465d49 ebef jmp 80465d3a
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x80465d49
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000 - HRESULT 0x80004005
start end module name
Closing open log file c:\debuglog.txt
Didn't find the information you thought to find? Check out these Similar Threads
This dump is corrupt, or at least in a state inconsistant enough to not be readable by the machine.
You can try getting a new dump and seeing if its toast as well, or you'll have to call microsoft to have them read the dump by hand, or kajigger the system into giving you a good dump.
![BenMcDonald[MS]'s Avatar](http://www.WindowsBBS.com/avatars/benmcdonald-ms-.gif?dateline=1103157319)
