Memory Dump File

Status
Not open for further replies.
OK.. I have a windows 2003 server fully patched with the latest service packs and critical patches...
About once or twice a week, it reboots after a memdump.

here is the dump, I followed the instructions on how to format the dump.. FINALLY get to see what a dump looks like.. Man that sounds funny.
Thanks for your help!!
 

Attachments

  • debuglog.txt
    14.1 KB · Views: 6
Hi,

I find the footprint of nt!MmAccessFault at the stack trace and it is the sign of faulty ram. Run memtest to stress test the ram.

STACK_TEXT:
b8e87ac4 80847a69 badb0d00 00000015 80840440 nt!KiTrap0E+0x2a7
b8e87b58 8082f2b2 000fffff fa13846c bf908994 nt!MiRemovePageByColor+0x21
b8e87b90 8082f796 e19d3460 00008000 00000001 nt!MiResolveMappedFileFault+0x508
b8e87bc4 8084a5e8 00000000 bf908994 c02fe420 nt!MiResolveProtoPteFault+0x1a6
b8e87c5c 80849ce5 00000001 bf908994 c02fe420 nt!MiDispatchFault+0x834
b8e87cb8 80837d0a 00000000 bf908994 00000000 nt!MmAccessFault+0x64a
b8e87cb8 bf908994 00000000 bf908994 00000000 nt!KiTrap0E+0xdc
b8e87d40 bf87f76c 00000000 b8e87d64 0012fcac win32k!_GetKeyboardType
b8e87d54 80834d3f 00000000 00000029 0012fcb8 win32k!NtUserCallOneParam+0x23
b8e87d54 7c82ed54 00000000 00000029 0012fcb8 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fcb8 00000000 00000000 00000000 00000000 0x7c82ed54
 
Status
Not open for further replies.
Back