Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\040811-15359-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02ca2e90
Debug session time: Fri Apr 8 13:35:50.552 2011 (UTC - 4:00)
System Uptime: 0 days 3:53:52.130
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff880026a0ff8, 0, fffff880051c2614, 0}
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!memmove+204 )
Followup: MachineOwner
---------
2: 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: fffff880026a0ff8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880051c2614, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0e0e8
fffff880026a0ff8
FAULTING_IP:
dxgmms1!memmove+204
fffff880`051c2614 488b040a mov rax,qword ptr [rdx+rcx]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880026a6f50 -- (.trap 0xfffff880026a6f50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80039fbae0
rdx=fffffdfffeca5518 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880051c2614 rsp=fffff880026a70e8 rbp=fffff880026a7720
r8=0000000000000018 r9=0000000000000003 r10=0000000000000000
r11=fffffa8003a02208 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
dxgmms1!memmove+0x204:
fffff880`051c2614 488b040a mov rax,qword ptr [rdx+rcx] ds:fffff880`026a0ff8=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a892ac to fffff80002add640
STACK_TEXT:
fffff880`026a6de8 fffff800`02a892ac : 00000000`00000050 fffff880`026a0ff8 00000000`00000000 fffff880`026a6f50 : nt!KeBugCheckEx
fffff880`026a6df0 fffff800`02adb76e : 00000000`00000000 fffff880`026a0ff8 00000000`00000000 00000000`0006f249 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`026a6f50 fffff880`051c2614 : fffff880`051ef617 00000000`0006f249 fffff880`026a7720 fffffa80`05b02af0 : nt!KiPageFault+0x16e
fffff880`026a70e8 fffff880`051ef617 : 00000000`0006f249 fffff880`026a7720 fffffa80`05b02af0 00000000`00000000 : dxgmms1!memmove+0x204
fffff880`026a70f0 fffff880`04154165 : fffff880`ffffd66c 00000000`00000000 00000000`00000002 fffff880`026a7720 : dxgmms1!VidSchSubmitCommand+0x2eb
fffff880`026a7150 fffff880`0414fdb7 : 00000000`00000000 00000000`00000000 fffff8a0`40001180 fffff880`00000000 : dxgkrnl!DXGCONTEXT::SubmitPresent+0x1535
fffff880`026a7560 fffff880`0414de7b : fffff8a0`40001180 fffff8a0`000005a0 fffff880`026a78c0 fffff880`026a78f0 : dxgkrnl!DXGCONTEXT::Present+0x1933
fffff880`026a7880 fffff960`0022cb50 : fffffa80`05b68a60 00000000`00000000 fffff8a0`03a481d0 00000000`00000010 : dxgkrnl!DxgkPresent+0x543
fffff880`026a7bf0 fffff800`02adc8d3 : fffffa80`05b68a60 fffff880`026a7ca0 00000000`00000000 00000000`00000020 : win32k!NtGdiDdDDIPresent+0x18
fffff880`026a7c20 000007fe`fe17145a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03d7ea48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe17145a
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!memmove+204
fffff880`051c2614 488b040a mov rax,qword ptr [rdx+rcx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!memmove+204
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!memmove+204
BUCKET_ID: X64_0x50_dxgmms1!memmove+204
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\040811-16500-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c52e90
Debug session time: Wed Apr 6 18:39:32.552 2011 (UTC - 4:00)
System Uptime: 0 days 1:55:11.193
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa800204d530, fffffa800204d5b0, 408c700}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 )
Followup: MachineOwner
---------
0: 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: fffffa800204d530, The pool entry we were looking for within the page.
Arg3: fffffa800204d5b0, The next pool entry.
Arg4: 000000000408c700, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbe0e8
fffffa800204d530
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002bb7cae to fffff80002a8d640
STACK_TEXT:
fffff880`05efb558 fffff800`02bb7cae : 00000000`00000019 00000000`00000020 fffffa80`0204d530 fffffa80`0204d5b0 : nt!KeBugCheckEx
fffff880`05efb560 fffff880`0481b5ec : 00000000`00000000 00000000`00000001 fffff8a0`7ffffa80 00000000`00000001 : nt!ExDeferredFreePool+0x12da
fffff880`05efb610 fffff880`04801ecc : fffffa80`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x264
fffff880`05efb6e0 fffff880`044feccc : 00000000`00000000 fffff8a0`0278c000 fffff8a0`0278c000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`05efb710 fffff880`044fe65f : fffff8a0`0278c000 fffff8a0`0278d300 fffff8a0`00000000 00000000`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`05efb800 fffff880`044fe8e1 : fffff8a0`0278c000 fffff8a0`0278c000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`05efb850 fffff880`0450279c : fffff8a0`07c81100 fffff880`05efbca0 fffffa80`055f1000 fffff880`044c93af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`05efb8a0 fffff880`04504e57 : fffff8a0`0278c000 fffff880`05efb9b0 00000000`7efdb001 00000000`00000001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`05efb930 fffff960`0018c882 : 00000000`7efdb000 fffffa80`01cbab60 00000000`00000020 00000000`72755f08 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`05efbbf0 fffff800`02a8c8d3 : fffffa80`01cbab60 fffff880`05efbca0 00000000`7efdb000 fffffa80`01be6060 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`05efbc20 00000000`7277120a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0014dd18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7277120a
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264
fffff880`0481b5ec 488b4b20 mov rcx,qword ptr [rbx+20h]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
FAILURE_BUCKET_ID: X64_0x19_20_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264
BUCKET_ID: X64_0x19_20_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264
Followup: MachineOwner
---------