Code:
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\121710-36691-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`03098e50
Debug session time: Sat Dec 18 01:40:45.617 2010 (UTC - 5:00)
System Uptime: 0 days 5:30:46.365
Loading Kernel Symbols
...............................................................
...............Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff80002ed318e}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
3: 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: fffff80002ed318e
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: MOM.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002ecc469 to fffff80002eccf00
STACK_TEXT:
fffff880`02fdace8 fffff800`02ecc469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02fdacf0 fffff800`02eca932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fdae30 fffff800`02ed318e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`06a8ffd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x8b
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02eca932 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
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\121710-25989-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Sat Dec 18 02:00:35.094 2010 (UTC - 5:00)
System Uptime: 0 days 0:10:14.826
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa80061f4090, fffffa80061f40d0, 4040009}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_DereferenceDeviceHandle+ff )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa80061f4090, The pool entry we were looking for within the page.
Arg3: fffffa80061f40d0, The next pool entry.
Arg4: 0000000004040009, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c10e0
fffffa80061f4090
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002fbc6d3 to fffff80002e8af00
STACK_TEXT:
fffff880`02ffda08 fffff800`02fbc6d3 : 00000000`00000019 00000000`00000020 fffffa80`061f4090 fffffa80`061f40d0 : nt!KeBugCheckEx
fffff880`02ffda10 fffff880`03f8b557 : 00000000`54627255 00000000`000000e0 fffffa80`70627375 fffffa80`051701a0 : nt!ExFreePool+0xda4
fffff880`02ffdac0 fffff880`03f765bc : fffffa80`05170050 fffffa80`04ae2302 00000000`00000000 fffffa80`051701a0 : USBPORT!USBPORT_DereferenceDeviceHandle+0xff
fffff880`02ffdb20 fffff880`03f76ab7 : fffffa80`03b95c02 fffffa80`04fd3500 00000000`ffffffff fffffa80`05170ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x9f8
fffff880`02ffdc00 fffff880`03f7464f : fffffa80`05170ea8 fffffa80`051701a0 fffffa80`05171040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02ffdc60 fffff880`03f65f89 : fffffa80`05170050 00000000`00000000 fffffa80`05170e02 fffffa80`05170ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02ffdca0 fffff800`02e965dc : fffff880`02fd5180 fffffa80`05170ea8 fffffa80`05170ec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffdcd0 fffff800`02e936fa : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`03f65db0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_DereferenceDeviceHandle+ff
fffff880`03f8b557 8a5c2468 mov bl,byte ptr [rsp+68h]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: USBPORT!USBPORT_DereferenceDeviceHandle+ff
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07
FAILURE_BUCKET_ID: X64_0x19_20_USBPORT!USBPORT_DereferenceDeviceHandle+ff
BUCKET_ID: X64_0x19_20_USBPORT!USBPORT_DereferenceDeviceHandle+ff
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\121810-20763-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`03046e50
Debug session time: Sat Dec 18 12:36:03.102 2010 (UTC - 5:00)
System Uptime: 0 days 0:12:45.850
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8004beb3e76, 1, fffff80002eb3cb6, 5}
Could not read faulting driver name
Probably caused by : hardware ( nt!RtlInitializeExtendedContext+3a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8004beb3e76, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002eb3cb6, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b10e0
fffff8004beb3e76
FAULTING_IP:
nt!RtlInitializeExtendedContext+3a
fffff800`02eb3cb6 8325b90100498d and dword ptr [fffff800`4beb3e76],0FFFFFF8Dh
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: Launch.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880062dd1e0 -- (.trap 0xfffff880062dd1e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000f rbx=0000000000000000 rcx=0000000000100000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eb3cb6 rsp=fffff880062dd370 rbp=fffff880062dd8d0
r8=fffff880062dd3b8 r9=0000000000010040 r10=000000000011001f
r11=fffff880062dd3d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!RtlInitializeExtendedContext+0x3a:
fffff800`02eb3cb6 8325b90100498d and dword ptr [fffff800`4beb3e76],0FFFFFF8Dh ds:0001:fffff800`4beb3e76=????????
Resetting default scope
EXCEPTION_RECORD: fffff880062ddb78 -- (.exr 0xfffff880062ddb78)
ExceptionAddress: 0000000005f068ac
ExceptionCode: 10000004
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000151
MISALIGNED_IP:
nt!RtlInitializeExtendedContext+3a
fffff800`02eb3cb6 8325b90100498d and dword ptr [fffff800`4beb3e76],0FFFFFF8Dh
LAST_CONTROL_TRANSFER: from fffff80002ef8b91 to fffff80002e7af00
STACK_TEXT:
fffff880`062dd078 fffff800`02ef8b91 : 00000000`00000050 fffff800`4beb3e76 00000000`00000001 fffff880`062dd1e0 : nt!KeBugCheckEx
fffff880`062dd080 fffff800`02e78fee : 00000000`00000001 fffff880`062ddb78 00000000`00000000 ffffdc66`a9171c5e : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`062dd1e0 fffff800`02eb3cb6 : fffff880`062dd500 00000000`00000200 fffff880`062dda40 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`062dd370 fffff800`02eb5130 : fffff880`062ddb78 fffff880`062ddc20 fffff900`c2c31000 00000000`00000001 : nt!RtlInitializeExtendedContext+0x3a
fffff880`062dd3a0 fffff800`02e7a542 : fffff880`062ddb78 00000000`00000035 fffff880`062ddc20 00000000`17880530 : nt!KiDispatchException+0xb0
fffff880`062dda40 fffff800`02e790ba : 00000000`00000000 00000000`00000035 00000000`11569401 00000000`7efdb000 : nt!KiExceptionDispatch+0xc2
fffff880`062ddc20 00000000`05f068ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`0018efd4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5f068ac
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!RtlInitializeExtendedContext+3a
fffff800`02eb3cb6 8325b90100498d and dword ptr [fffff800`4beb3e76],0FFFFFF8Dh
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!RtlInitializeExtendedContext+3a
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
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\121810-17503-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e4d000 PsLoadedModuleList = 0xfffff800`0308ae50
Debug session time: Sat Dec 18 12:54:54.088 2010 (UTC - 5:00)
System Uptime: 0 days 0:17:17.821
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff8a00c454650, fffff8a00c444650, fffff8a00c454650}
Probably caused by : Pool_Corruption ( nt!ExFreePool+75b )
Followup: Pool_corruption
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a00c454650, the pool entry being checked.
Arg3: fffff8a00c444650, the read back flink freelist value (should be the same as 2).
Arg4: fffff8a00c454650, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Launch.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ff010b to fffff80002ebef00
STACK_TEXT:
fffff880`06cd04b8 fffff800`02ff010b : 00000000`00000019 00000000`00000003 fffff8a0`0c454650 fffff8a0`0c444650 : nt!KeBugCheckEx
fffff880`06cd04c0 fffff800`02ff24c1 : 00000000`00000001 fffff8a0`0d07a260 00000000`00000000 00000000`00000000 : nt!ExFreePool+0x75b
fffff880`06cd0550 fffff880`0401ac83 : fffff8a0`07dbc4e0 00000000`00000000 00000000`6d4d6956 00000000`00000174 : nt!ExFreePoolWithTag+0x411
fffff880`06cd0600 fffff880`0400198f : fffffa80`0419db40 fffff8a0`03f91470 fffffa80`05ae8000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+0x2ab
fffff880`06cd06e0 fffff880`04119fb3 : 00000000`00000000 00000000`00000000 fffff8a0`07999000 00000000`00000174 : dxgmms1!VidMmDestroyAllocation+0x4f
fffff880`06cd0710 fffff880`0411954b : fffff8a0`07999000 00000000`00000000 fffff8a0`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x5eb
fffff880`06cd0800 fffff880`04119825 : fffff8a0`07999000 fffff8a0`07999000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`06cd0850 fffff880`0411d6e0 : fffff8a0`09de4300 fffff880`06cd0ca0 fffffa80`05ac8000 fffff880`040e43af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`06cd08a0 fffff880`0411fd9b : fffff8a0`07999000 fffff880`06cd09b0 00000000`7efdb001 fffff880`040e5001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`06cd0930 fffff960`0027b242 : 00000000`0008e1b0 fffffa80`04255b60 00000000`00000020 00000000`737e5f08 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`06cd0bf0 fffff800`02ebe153 : 00000000`08412e70 fffff880`06cd0ca0 00000000`00000000 00000000`08430ca0 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`06cd0c20 00000000`7380120a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7380120a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExFreePool+75b
fffff800`02ff010b cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExFreePool+75b
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExFreePool+75b
BUCKET_ID: X64_0x19_3_nt!ExFreePool+75b
Followup: Pool_corruption
---------