Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\dbickel\Desktop\M
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\websymbols*http://m
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS
Built by: 3790.srv03_sp2_gdr.090319-
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Sun Apr 26 08:27:07.625 2009 (GMT-4)
System Uptime: 0 days 23:57:16.671
Loading Kernel Symbols
..........................
..........................
Loading User Symbols
Loading unloaded module list
.........
**************************
* *
* Bugcheck Analysis *
* *
**************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, d0000002, 1, b9706650}
Unable to load image \SystemRoot\system32\DRIVE
*** WARNING: Unable to verify timestamp for tmtdi.sys
*** ERROR: Module load completed but symbols could not be loaded for tmtdi.sys
Probably caused by : tmtdi.sys ( tmtdi+1650 )
Followup: MachineOwner
---------
Main Topics
Browse All Topics
by: NaturaTekPosted on 2009-04-26 at 09:09:32ID: 24236565
It would be super if you could save and post the dump file to debug it. You can attempt to view it on your own. Simple instructions are here: http://blogs.technet.com/p
My prediagnosis opinion, don't think it's ram. I seen the 0000..d1 error before and it always related to a driver/service that's crashing. Notorious ones are the symantec services (antivirus), raid controller drivers, like intel raid, etc. Some type of backup service like veritas..again from symantec..and others.
You can view the dump file, and you'll usually see the offending file/service in there. Once I learned to use the debugging tools, the basics..it has been a godsend to help analyze.
My personal opinion for future disaster prevention: Once a pc/server is running, leave automatic updates OFF. Windows want to update drivers for known items and at times it can just cause things to go haywire. I always do updates manually and I read each update to see what it does/fixes. Something crashes, you know the last thing done.
I would browse thru event viewer, see if any logs hints toward the problems. Try to remember anything that was done/installed and problem started happening. If new driver, roll back. New software, uninstall it and/or go back to previous version see if it remedies problem. If so, check with manufacturer for any hotfixes/updates.
Do standard quick maintenance on your own..chkdsk /f, oh and delete the pagefile.sys, some corrupted pagefiles causes havoc, especially when they are set static. Boot into some type of dos environment, attrib -h -s -r pagefile.sys, then del pagefile.sys. Booting back in windows creates a new one.
See if you can post debug from dump file.