*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {21, fffff8a005467000, 1650, 1550}
Probably caused by : [COLOR=Red]dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+7e )[/COLOR]
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[COLOR=Red]
BAD_POOL_HEADER (19)[/COLOR]
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: 0000000000000021, the data following the pool block being freed is corrupt. Typically this means the consumer (call stack ) has overrun the block.
Arg2: fffff8a005467000, The pool pointer being freed.
Arg3: 0000000000001650, The number of bytes allocated for the pool block.
Arg4: 0000000000001550, The corrupted value found following the pool block.
Debugging Details:
------------------
BUGCHECK_STR: 0x19_21
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80003505100
fffff8a005467000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: bf3.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800034009b2 to fffff800032d61c0
STACK_TEXT:
fffff880`0a437fe8 fffff800`034009b2 : 00000000`00000019 00000000`00000021 fffff8a0`05467000 00000000`00001650 : nt!KeBugCheckEx
fffff880`0a437ff0 fffff800`032df3d4 : 00000000`00000000 fffff8a0`0541ec90 fffffa80`74536d4d fffffa80`00000000 : nt!ExDeferredFreePool+0xfaa
fffff880`0a4380a0 fffff880`0463548e : fffff8a0`0541ec90 fffffa80`0fd7c060 fffffa80`118fec30 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`0a438100 fffff880`04620b5a : 00000000`00000000 fffff8a0`05392e00 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x7e
fffff880`0a438130 fffff880`0461b523 : fffffa80`100496f0 00000000`00000001 fffff8a0`0541ec90 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`0a4381e0 fffff880`04601ecc : 00000000`00000000 fffff8a0`00000000 fffffa80`116da000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0a4382b0 fffff880`04711ccc : 00000000`00000000 fffff8a0`03a03000 fffff8a0`03a03000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0a4382e0 fffff880`0471165f : fffff8a0`03a03000 fffff8a0`03a04300 fffff8a0`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0a4383d0 fffff880`0473f74f : 00000000`00000000 fffff8a0`0af75e40 fffff8a0`043ea2f0 fffff880`0a4387f0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0a438420 fffff880`0473ee7b : fffff8a0`00000799 fffff8a0`043ea2f0 fffff880`0a438780 fffff880`0a4387b0 : dxgkrnl!DXGCONTEXT::Present+0x2cb
fffff880`0a438740 fffff960`001f03a8 : fffffa80`0ff5db50 00000000`e6585000 fffff8a0`08649510 fffff8a0`00000010 : dxgkrnl!DxgkPresent+0x543
fffff880`0a438ab0 fffff800`032d5453 : 00000000`04b72348 fffff880`0a438b60 00000000`ffffffff 00000000`00000001 : win32k!NtGdiDdDDIPresent+0x18
fffff880`0a438ae0 00000000`74aa15da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0525e558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74aa15da
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_PROCESS_HEAP::Free+7e
fffff880`0463548e eb22 jmp dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2 (fffff880`046354b2)
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Free+7e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
FAILURE_BUCKET_ID: [COLOR=Red]X64_0x19_21_dxgmms1!VIDMM_PROCESS_HEAP::Free+7e[/COLOR]
BUCKET_ID: [COLOR=Red] X64_0x19_21_dxgmms1!VIDMM_PROCESS_HEAP::Free+7e
[/COLOR]
Followup: MachineOwner
---------
3: kd> lmvm dxgmms1
start end module name
fffff880`04600000 fffff880`04646000 dxgmms1 (pdb symbols) c:\symcache\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
Loaded symbol image file: dxgmms1.sys
Mapped memory image file: c:\symcache\dxgmms1.sys\4CE799C146000\dxgmms1.sys
Image path: \SystemRoot\System32\drivers\dxgmms1.sys
Image name: dxgmms1.sys
Timestamp: Sat Nov 20 15:49:53 2010 (4CE799C1)
CheckSum: 00047A89
ImageSize: 00046000
File version: 6.1.7601.17514
Product version: 6.1.7601.17514
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: [COLOR=Red]dxgmms1.sys[/COLOR]
OriginalFilename: [COLOR=Red]dxgmms1.sys[/COLOR]
ProductVersion: 6.1.7601.17514
FileVersion: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.