Got the BSOD on a PC. No indication what file/driver could be at fault, though.
I just went online and learned how to debug the mini.dmp file. Attached is mine. It says Memory Corruption.
Can anyone please help me analyze this further and tell me what the problem is and how I might fix?
Thank you.
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [H:\Informtation Technology\RC\MemDump\Mini
080408-03.
dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*
http://msdl.microsoft.com/download/symbolsExecutable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2
254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Aug 4 17:00:39.734 2008 (GMT-4)
System Uptime: 0 days 0:00:21.437
Loading Kernel Symbols
..........................
..........
..........
..........
..........
..........
..........
..........
..........
..........
........
Loading User Symbols
Loading unloaded module list
.....
**************************
**********
**********
**********
**********
**********
***
* *
* Bugcheck Analysis *
* *
**************************
**********
**********
**********
**********
**********
***
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
**************************
**********
**********
**********
**********
**********
***
* *
* Bugcheck Analysis *
* *
**************************
**********
**********
**********
**********
**********
***
UNEXPECTED_KERNEL_MODE_TRA
P_M (1000007f)
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: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: winlogon.exe
LAST_CONTROL_TRANSFER: from 805780f6 to 8057f4bb
STACK_TEXT:
f3d27d00 805780f6 0000000c 00000000 00000000 nt!IopXxxControlFile+0x513
f3d27d34 8054086c 0000000c 00000000 00000000 nt!NtFsControlFile+0x2a
f3d27d34 7c90eb94 0000000c 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006f234 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
6 errors : !nt (8057f2ab-8057fbfb)
8057f2a0 ff 75 e0 e8 44 ae f7 ff 8b 4d e0 *e0 aa 66 fa ff .u..D....M...f..
...
8057f380 0f 95 c1 83 c1 0d 89 0f 89 77 18 *89 4d 2c 89 4f .........w..M,.O
...
8057f4b0 03 00 00 00 3b c8 75 0d 39 45 2c *65 08 89 43 08 ....;.u.9E,e..C.
...
8057f930 a2 f7 57 80 ff b5 f4 fc ff ff e8 *30 d3 ff ff 85 ..W........0....
...
8057fbd0 7d b0 f3 ab 8d 85 64 ff ff ff 50 *68 4c 8d 45 b0 }.....d...PhL.E.
...
8057fbf0 0a 00 85 c0 7c 2a 8b 45 b8 83 c0 *7e 66 89 85 7c ....|*.E...~f..|
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:
0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------
0: kd> lmvm memory_corruption
start end module name
Start Free Trial