BSOD While Running Sims 3

I attached a .zip of my Minidump file; there was only one. I also filled out as much as I know off of the top of my head about my computer. Everything about it is the HP standard for it, aside from an LCD screen replacement and an upgrade from Vista to Seven.

CobaltKairi said:

This morning, I was running the Sims 3 World Adventures PC game and walked away for a moment. When I returned, I had the blue screen error. My computer automatically rebooted and I had it start up normally. It searched for solutions and never turned up a response. Any assistance or information would be greatly appreciated.


Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem
042910-28298-01.dmp
sysdata.xml
WERInternalMetadata.xml

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 1000007e
BCP1: C0000005
BCP2: 91B6BEAE
BCP3: 8CEE3B64
BCP4: 8CEE3740
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1



EDIT: I just rechecked my error log and found six video hardware crashes since 4/19, three of which happened yesterday between 7:00 PM and 9:00 PM EST. They all have the same files except for the first file, which is always a .dmp beginning with WD. The only differences are the last four digits. Here is one of them:

Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem
WD-20100427-1903.dmp
sysdata.xml
WERInternalMetadata.xml

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 117
BCP1: AC796008
BCP2: 91425080
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

This crash was caused your video driver. I would completely removed the current driver using the mfr uninstall tool, and download and install just the driver and not the other components.

I would also run a system file check to verify your system files.
(type cmd in search>right click and run as admin>sfc /scannow)

Let us know the results and if you need help.

Code:

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
---------

Thanks for your help. I reinstalled the driver and haven't had a crash yet. I have yet to run the system file check, but will do that probably later on today.

CobaltKairi said:

Thanks for your help. I reinstalled the driver and haven't had a crash yet. I have yet to run the system file check, but will do that probably later on today.

Let us know the result please.

I had another crash a few minutes ago. Following the error, I reinstalled the driver again.
EDIT: The system check scan that I started shortly after this post was made has finished. The result is that "Windows Resource Protection did not find any integrity violations."

Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem
050310-23478-01.dmp
sysdata.xml
WERInternalMetadata.xml

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 119
BCP1: 00000001
BCP2: 0000DD00
BCP3: 0000DDEB
BCP4: 0000DDEA
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1