Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\012110-99700-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82852000 PsLoadedModuleList = 0x8299a810
Debug session time: Thu Jan 21 10:56:16.500 2010 (GMT-5)
System Uptime: 0 days 0:00:19.874
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {d, 0, 0, 0}
Probably caused by : tpm.sys ( tpm!TpmEntropyInit+c0 )
Followup: MachineOwner
---------
2: 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: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 909cb3d8 to 82898f2b
STACK_TEXT:
8d79bb4c 909cb3d8 badb0d00 909c9014 8b45fc95 nt!KiSystemFatalException+0xf
8d79bbf4 909ca227 00000000 79cbbdc0 86344450 tpm!TpmEntropyInit+0xc0
8d79bc1c 8b484301 000000a1 79cbbdc0 79cbbd50 tpm!TpmEvtDevicePrepareHardware+0x221
8d79bc38 8b484543 79cbbd50 86344450 01344958 Wdf01000!FxPkgPnp::PnpPrepareHardware+0x77
8d79bc4c 8b483484 86344450 863444f8 86344450 Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x2b
8d79bc74 8b483db2 00000108 86344504 86344450 Wdf01000!FxPkgPnp::PnpEnterNewState+0x104
8d79bc98 8b484503 8d79bcc8 8281e700 863444f8 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x149
8d79bcac 8b487d1c 86344450 8d79bcc8 86344030 Wdf01000!FxPkgPnp::_PnpProcessEventInner+0x26
8d79bcdc 8b488ff8 86344188 851e9070 8d79bd00 Wdf01000!FxEventQueue::EventQueueWorker+0x6f
8d79bcec 82a727b5 00000000 863444f8 851f0648 Wdf01000!FxWorkItemEventQueue::_WorkItemCallback+0x21
8d79bd00 828bff2b 86344188 00000000 851f0648 nt!IopProcessWorkItem+0x23
8d79bd50 82a6066d 00000001 a9be9130 00000000 nt!ExpWorkerThread+0x10d
8d79bd90 829120d9 828bfe1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
tpm!TpmEntropyInit+c0
909cb3d8 c9 leave
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: tpm!TpmEntropyInit+c0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tpm
IMAGE_NAME: tpm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf74
FAILURE_BUCKET_ID: 0x7f_d_tpm!TpmEntropyInit+c0
BUCKET_ID: 0x7f_d_tpm!TpmEntropyInit+c0
Followup: MachineOwner
---------
