Windows 7: BSOD While Running Sims 3

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\042910-28298-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82c0d000 PsLoadedModuleList = 0x82d55810
Debug session time: Thu Apr 29 11:50:32.833 2010 (GMT-4)
System Uptime: 6 days 10:34:01.581
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 91b6beae, 8cee3b64, 8cee3740}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+18 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 91b6beae, The address that the exception occurred at
Arg3: 8cee3b64, Exception Record Address
Arg4: 8cee3740, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_DEVICE::RemoveCommitment+18
91b6beae 8b4f48          mov     ecx,dword ptr [edi+48h]

EXCEPTION_RECORD:  8cee3b64 -- (.exr 0xffffffff8cee3b64)
ExceptionAddress: 91b6beae (dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x00000018)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000048
Attempt to read from address 00000048

CONTEXT:  8cee3740 -- (.cxr 0xffffffff8cee3740)
eax=8532db78 ebx=00000000 ecx=86a0c198 edx=8cee3cf8 esi=00000000 edi=00000000
eip=91b6beae esp=8cee3c2c ebp=8cee3c3c iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x18:
91b6beae 8b4f48          mov     ecx,dword ptr [edi+48h] ds:0023:00000048=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000048

READ_ADDRESS: GetPointerFromAddress: unable to read from 82d75718
Unable to read MiSystemVaType memory at 82d55160
 00000048 

FOLLOWUP_IP: 
dxgmms1!VIDMM_DEVICE::RemoveCommitment+18
91b6beae 8b4f48          mov     ecx,dword ptr [edi+48h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 91b6061e to 91b6beae

STACK_TEXT:  
8cee3c3c 91b6061e 8532db78 8532db78 00000000 dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x18
8cee3c54 91b674c4 8532db78 00000000 00000000 dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x1e
8cee3cc4 91b67e66 8cee3ce0 00000000 8cee3cf8 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x406
8cee3cf0 91b694c8 00000000 8cee3d18 91b7d2cd dxgmms1!VIDMM_GLOBAL::ProcessTerminationCommand+0x40
8cee3cfc 91b7d2cd 869f12c0 f100b6d0 f100b6d0 dxgmms1!VidMmiProcessTerminationCommand+0x10
8cee3d18 91b7e27d 9b29a008 b1391008 8cee3d3c dxgmms1!VidSchiSubmitDeviceCommand+0x33
8cee3d28 91b7e4cc f100b6d0 82c493e1 864e34d0 dxgmms1!VidSchiSubmitQueueCommand+0xaf
8cee3d3c 91b7e573 864e34d0 00000000 864f1948 dxgmms1!VidSchiRun_PriorityTable+0x24
8cee3d50 82e1b66d 864e34d0 ab1943bc 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8cee3d90 82ccd1d9 91b7e4f4 864e34d0 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_DEVICE::RemoveCommitment+18

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc265

STACK_COMMAND:  .cxr 0xffffffff8cee3740 ; kb

FAILURE_BUCKET_ID:  0x7E_dxgmms1!VIDMM_DEVICE::RemoveCommitment+18

BUCKET_ID:  0x7E_dxgmms1!VIDMM_DEVICE::RemoveCommitment+18

Followup: MachineOwner
---------