Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\XXX\Desktop\081910-20092-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c62000 PsLoadedModuleList = 0xfffff800`02e9fe50
Debug session time: Thu Aug 19 14:47:04.758 2010 (GMT+2)
System Uptime: 0 days 0:25:18.490
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
...............................
Loading User Symbols
Loading unloaded module list
.....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 1097, 10304, fffff8a00ca2b230}
GetPointerFromAddress: unable to read from fffff80002f0a0e0
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmCloseAllocation+5d )
Followup: MachineOwner
---------
0: kd> !analyze –v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 1097, 10304, fffff8a00ca2b230}
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmCloseAllocation+5d )
Followup: MachineOwner
---------
0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000000010304, Memory contents of the pool block
Arg4: fffff8a00ca2b230, Address of the block of pool being deallocated
Debugging Details:
------------------
POOL_ADDRESS: fffff8a00ca2b230
FREED_POOL_TAG: ViMm
BUGCHECK_STR: 0xc2_7_ViMm
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Bioshock.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002e0560e to fffff80002cd2740
STACK_TEXT:
fffff880`0a0be508 fffff800`02e0560e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`00010304 : nt!KeBugCheckEx
fffff880`0a0be510 fffff880`04173ee5 : 00000000`00000000 fffffa80`00000000 00000000`6d4d6956 00000000`00000174 : nt!ExDeferredFreePool+0x11eb
fffff880`0a0be5c0 fffff880`040b5c10 : 00000000`00000000 fffff8a0`036a1000 fffff8a0`036a1000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x5d
fffff880`0a0be5f0 fffff880`040c867c : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE:estroyAllocations+0x248
fffff880`0a0be6e0 fffff880`040ad815 : 00000000`fffffeda fffff8a0`0911a8f0 fffff8a0`036a1000 fffffa80`05b0e000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0a0be750 fffff880`040ebca6 : 00000000`00000000 fffffa80`05b0e000 fffff8a0`0911a8f0 fffff8a0`0911a970 : dxgkrnl!DXGADAPTER:estroyDevice+0x1c9
fffff880`0a0be780 fffff880`040eb63c : fffff900`c25ad010 00000000`00000000 00000000`00000001 fffff900`c25ad010 : dxgkrnl!DXGPROCESS:estroy+0xba
fffff880`0a0be830 fffff960`00164a54 : 00000000`00000d28 fffff900`c25ad010 00000000`00000000 fffff900`c25ad010 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0a0be8c0 fffff960`00164157 : fffffa80`0506b300 fffff880`0a0bec20 00000000`00000000 fffff880`0a0bec20 : win32k!GdiProcessCallout+0x244
fffff880`0a0be940 fffff800`02fb7a01 : fffffa80`0506b360 00000000`00000000 00000000`00000000 fffffa80`06725b60 : win32k!W32pProcessCallout+0x6b
fffff880`0a0be970 fffff800`02f90635 : 00000000`00000001 00000000`00000001 00000000`78457300 fffffa80`0456cb60 : nt!PspExitThread+0x561
fffff880`0a0bea30 fffff800`02caf1db : fffffa80`05b36ed0 fffffa80`06d3d460 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`0a0bea60 fffff800`02caf620 : 00000000`30a1fedc fffff880`0a0beae0 fffff800`02f9074c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0a0beae0 fffff800`02cd1a37 : fffffa80`06725b60 00000000`7ef65000 fffff880`000000c0 00000000`7ef65000 : nt!KiInitiateUserApc+0x70
fffff880`0a0bec20 00000000`7771165a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`26a0e7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7771165a
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidMmCloseAllocation+5d
fffff880`04173ee5 33d2 xor edx,edx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VidMmCloseAllocation+5d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0xc2_7_ViMm_dxgmms1!VidMmCloseAllocation+5d
BUCKET_ID: X64_0xc2_7_ViMm_dxgmms1!VidMmCloseAllocation+5d
Followup: MachineOwner