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\DMP\010111-27656-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0321a000 PsLoadedModuleList = 0xfffff800`03457e50
Debug session time: Sat Jan 1 22:37:33.917 2011 (UTC - 5:00)
System Uptime: 0 days 0:48:15.464
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, a77f0, 2, a77bd}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000a77f0, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000000a77bd, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: GameOverlayUI.
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff8000331a38c to fffff8000328a740
STACK_TEXT:
fffff880`09b10f98 fffff800`0331a38c : 00000000`0000004e 00000000`00000099 00000000`000a77f0 00000000`00000002 : nt!KeBugCheckEx
fffff880`09b10fa0 fffff800`032fc9e5 : 00000000`00000000 fffff680`00013ab0 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`09b10fe0 fffff800`0325ec23 : fffffa80`042ca060 fffff700`0000610f 0000007f`fffffff8 fffff8a0`027e3bb0 : nt! ?? ::FNODOBFM::`string'+0x3222c
fffff880`09b11070 fffff800`0325d68a : fffffa80`042ca060 fffffa80`00000000 fffff880`000041ca fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`09b11920 fffff800`0356fdcf : fffff8a0`0cba85f0 fffff880`09b11c20 00000000`00000000 fffffa80`04598b60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`09b11970 fffff800`03548635 : 00000000`00000001 fffff8a0`0cec7d01 00000000`7ef89000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`09b11a30 fffff800`032671db : 00000000`7ef89000 fffffa80`042c8740 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`09b11a60 fffff800`03267620 : 00000000`1184fedc fffff880`09b11ae0 fffff800`0354874c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`09b11ae0 fffff800`03289a37 : fffffa80`04598b60 00000000`7ef89000 00000000`000000c0 00000000`7ef89000 : nt!KiInitiateUserApc+0x70
fffff880`09b11c20 00000000`77b0165a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`1174e7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b0165a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`0331a38c cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiBadShareCount+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
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\DMP\010111-21859-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03218000 PsLoadedModuleList = 0xfffff800`03455e50
Debug session time: Sun Jan 2 01:23:02.373 2011 (UTC - 5:00)
System Uptime: 0 days 0:09:47.919
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff88001a1f191}
Probably caused by : tdx.sys ( tdx!TdxMessageTlRequestComplete+181 )
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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff88001a1f191
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80003287ca9 to fffff80003288740
STACK_TEXT:
fffff800`00ba4d28 fffff800`03287ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`03286172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`01a1f191 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tdx!TdxMessageTlRequestComplete+0x181
STACK_COMMAND: kb
FOLLOWUP_IP:
tdx!TdxMessageTlRequestComplete+181
fffff880`01a1f191 5f pop rdi
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: tdx!TdxMessageTlRequestComplete+181
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tdx
IMAGE_NAME: tdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc16b
FAILURE_BUCKET_ID: X64_0x7f_8_tdx!TdxMessageTlRequestComplete+181
BUCKET_ID: X64_0x7f_8_tdx!TdxMessageTlRequestComplete+181
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\DMP\010111-37484-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03204000 PsLoadedModuleList = 0xfffff800`03441e50
Debug session time: Sat Jan 1 18:07:23.344 2011 (UTC - 5:00)
System Uptime: 0 days 0:28:23.891
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {1f, fffff8a00bd38010, 1, cc90}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+12b )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000001f, The subtype of the bugcheck:
Arg2: fffff8a00bd38010
Arg3: 0000000000000001
Arg4: 000000000000cc90
Debugging Details:
------------------
BUGCHECK_STR: 0x10e_1f
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88001bb122f to fffff80003274740
STACK_TEXT:
fffff880`05e84768 fffff880`01bb122f : 00000000`0000010e 00000000`0000001f fffff8a0`0bd38010 00000000`00000001 : nt!KeBugCheckEx
fffff880`05e84770 fffff880`052addc3 : 00000000`0000cc90 fffffa80`0625d000 00000000`0000cc90 fffff8a0`0bd38010 : watchdog!WdLogEvent5+0x11b
fffff880`05e847c0 fffff880`052a9e88 : 00000000`00000000 00000000`00000000 00000000`00000c3a fffff880`05e84870 : dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x12b
fffff880`05e84840 fffff880`052b6cf0 : 00000000`00000000 fffffa80`0625d000 fffff8a0`0bd38010 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::DiscardAllocationInternal+0x154
fffff880`05e849c0 fffff880`052a725d : fffffa80`0624b2d0 fffff8a0`0bd38010 fffffa80`04084f00 fffffa80`0625d000 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x530
fffff880`05e84b30 fffff880`052a2358 : fffffa80`05c83350 00000000`00000000 00000000`00000000 fffff880`05e84ca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
fffff880`05e84c50 fffff880`052c016d : 00000000`00000000 fffffa80`0624c010 00000000`00000000 00000000`00000001 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
fffff880`05e84ca0 fffff880`052bf3f8 : fffff800`00b96080 fffffa80`062ced50 00000000`00000000 fffffa80`0624c010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`05e84cd0 fffff880`052bee96 : 00000000`000222f0 fffffa80`03f3e010 00000000`00000080 fffffa80`0624c010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`05e84d00 fffff800`03518c06 : 00000000`0319d3ed fffffa80`06231060 fffffa80`03cd0040 fffffa80`06231060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05e84d40 fffff800`03252c26 : fffff800`033eee80 fffffa80`06231060 fffff800`033fcc40 fffff880`01418534 : nt!PspSystemThreadStartup+0x5a
fffff880`05e84d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+12b
fffff880`052addc3 c7842490000000c5f3ffff mov dword ptr [rsp+90h],0FFFFF3C5h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+12b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+12b
BUCKET_ID: X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+12b
Followup: MachineOwner
---------