Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Simon\Desktop\f\090511-24055-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*
Executable search path is:
Windows Longhorn Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Kernel base = 0x82e14000 PsLoadedModuleList = 0x82f5d4f0
Debug session time: Mon Sep 5 13:39:31.271 2011 (GMT+2)
System Uptime: 0 days 0:16:24.221
Loading Kernel Symbols
.................................................. .................................................. .................................................. .................
Loading unloaded module list
.....
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )
Followup: MachineOwner
---------
0: kd> .reload
Loading Kernel Symbols
.................................................. .................................................. .................................................. .................
Loading unloaded module list
.....
Loading User Symbols
0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
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: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8f68f1d1 to 82e55d1b
STACK_TEXT:
a656788c 8f68f1d1 badb0d00 00000000 a6567900 nt!KiSystemFatalException+0xf
a6567970 83046e50 0000001d b482f9a0 89cf56a8 blbdrive!RtlULongLongToLongLong <PERF> (blbdrive+0x1d1)
a65679b8 83043299 0000001d aba49f78 a6567a70 nt!CmPostCallbackNotification+0x55
a6567b48 83039b56 aae3cfd0 84cda728 8520e318 nt!CmpParseKey+0x14b2
a6567bc4 83049f68 00000024 a6567c18 00000040 nt!ObpLookupObjectName+0x4fa
a6567c20 83047e99 00e5d414 84cda728 8303e701 nt!ObOpenObjectByName+0x165
a6567d00 83024b71 00e5d558 00020019 00e5d414 nt!CmOpenKey+0x1f4
a6567d1c 82e521fa 00e5d558 00020019 00e5d414 nt!NtOpenKeyEx+0x18
a6567d1c 779070b4 00e5d558 00020019 00e5d414 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00e5d3c0 00000000 00000000 00000000 00000000 0x779070b4
FOLLOWUP_IP:
nt!KiSystemFatalException+f
82e55d1b c3 ret
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiSystemFatalException+f
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02a389
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Simon\Desktop\f\090511-24055-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*

Executable search path is:
Windows Longhorn Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Kernel base = 0x82e14000 PsLoadedModuleList = 0x82f5d4f0
Debug session time: Mon Sep 5 13:39:31.271 2011 (GMT+2)
System Uptime: 0 days 0:16:24.221
Loading Kernel Symbols
.................................................. .................................................. .................................................. .................
Loading unloaded module list
.....
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )
Followup: MachineOwner
---------
0: kd> .reload
Loading Kernel Symbols
.................................................. .................................................. .................................................. .................
Loading unloaded module list
.....
Loading User Symbols
0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
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: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8f68f1d1 to 82e55d1b
STACK_TEXT:
a656788c 8f68f1d1 badb0d00 00000000 a6567900 nt!KiSystemFatalException+0xf
a6567970 83046e50 0000001d b482f9a0 89cf56a8 blbdrive!RtlULongLongToLongLong <PERF> (blbdrive+0x1d1)
a65679b8 83043299 0000001d aba49f78 a6567a70 nt!CmPostCallbackNotification+0x55
a6567b48 83039b56 aae3cfd0 84cda728 8520e318 nt!CmpParseKey+0x14b2
a6567bc4 83049f68 00000024 a6567c18 00000040 nt!ObpLookupObjectName+0x4fa
a6567c20 83047e99 00e5d414 84cda728 8303e701 nt!ObOpenObjectByName+0x165
a6567d00 83024b71 00e5d558 00020019 00e5d414 nt!CmOpenKey+0x1f4
a6567d1c 82e521fa 00e5d558 00020019 00e5d414 nt!NtOpenKeyEx+0x18
a6567d1c 779070b4 00e5d558 00020019 00e5d414 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00e5d3c0 00000000 00000000 00000000 00000000 0x779070b4
FOLLOWUP_IP:
nt!KiSystemFatalException+f
82e55d1b c3 ret
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiSystemFatalException+f
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02a389
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------






