Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\121310-22479-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image Unknown_Module_3954ce3c, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_3954ce3c
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_3954ce3c
Debugger can not determine kernel base address
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a53000 PsLoadedModuleList = 0x82b9b810
Debug session time: Mon Dec 13 11:16:59.802 2010 (UTC - 5:00)
System Uptime: 0 days 0:55:48.487
Unable to load image Unknown_Module_3954ce3c, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_3954ce3c
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_3954ce3c
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {d, 0, 0, 0}
*** WARNING: Unable to verify timestamp for Unknown_Module_3954ce3c
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_3954ce3c
Unknown module 'Unknown_Module_3954ce3c' found on stack, using vad to reload module.
!vad_reload -1 0x3954ce3c
Failed to get old VAD root
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
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:
------------------
Unknown module 'Unknown_Module_3954ce3c' found on stack, using vad to reload module.
!vad_reload -1 0x3954ce3c
Failed to get old VAD root
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82abc042 to 82abc15a
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
a39f3c58 82abc042 00000000 00000000 8b8c2808 0x82abc15a
a39f3c8c 82abbfb6 82b7cd20 00000000 00000000 0x82abc042
a39f3cb0 82aba753 82b7cd20 8b8c2800 00000000 0x82abbfb6
a39f3cdc 82c890d6 8b8c2800 00000001 00000000 0x82aba753
a39f3d24 82a9644a 00000460 00000000 1bf0ff20 0x82c890d6
a39f3d34 771f64f4 badb0d00 1bf0ff18 00000000 0x82a9644a
a39f3d38 badb0d00 1bf0ff18 00000000 00000000 Unknown_Module_3954ce3c+0x3dca96b8
a39f3d3c 1bf0ff18 00000000 00000000 00000000 0xbadb0d00
a39f3d40 00000000 00000000 00000000 00000000 0x1bf0ff18
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\121310-37471-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a0e000 PsLoadedModuleList = 0x82b56810
Debug session time: Mon Dec 13 12:59:34.744 2010 (UTC - 5:00)
System Uptime: 0 days 0:40:33.398
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {d, 0, 0, 0}
Probably caused by : amdk8.sys ( amdk8!C1Halt+4 )
Followup: MachineOwner
---------
1: 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: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 82e2131a to 82a54f6b
STACK_TEXT:
807dfbb4 82e2131a badb0d00 0001503b 8b8640f8 nt!KiSystemFatalException+0xf
807dfc28 86023bb6 00000000 00000000 0db73f68 hal!HalpClockInterruptPn+0x42
807dfc98 82a936b5 8b8659c8 807c8800 807c3000 amdk8!C1Halt+0x4
807dfd20 82a7600d 00000000 0000000e 00000000 nt!PoIdle+0x538
807dfd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd
STACK_COMMAND: kb
FOLLOWUP_IP:
amdk8!C1Halt+4
86023bb6 c3 ret
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: amdk8!C1Halt+4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: amdk8
IMAGE_NAME: amdk8.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07
FAILURE_BUCKET_ID: 0x7f_d_VRF_amdk8!C1Halt+4
BUCKET_ID: 0x7f_d_VRF_amdk8!C1Halt+4
Followup: MachineOwner
---------