BSOD issues while gaming

Heimdall · Mar 23, 2010

Some time into playing a game (so far I've only been playing Dungeons and Dragons Online but before the reinstall it happened with a few other games as well) I'm greeted with a lovely bluescreen, which almost always points at dxgmms1.sys. It happens randomly, it could crash 30 minutes in, or after a number of hours. Gaming aside, everything else appears to be stable so far.

I've tried reinstalling the OS, updating the chipsets first thing, then the latest audio and video drivers available after that, updating DirectX, etc. I still cannot fix it. I ran Memtest86+ and let it go for 5 passes with no errors, so I don't think it's an issue with my RAM, though I could be wrong.

I've got a few of my crash dumps that occured while playing the game attached. Any help would be very appreciated.

System specs:

OS: Windows 7 x64 Retail

CPU: Wolfdale Intel Core 2 Duo E8400 3.00GHz

Motherboard: GIGABYTE GA-EP45-DS4P

Memory: G.SKILL 2x2GB 240-pin Model F2-9600CL5D-4GBPI

Graphics Card(s): SAPPHIRE Radeon HD 4890 1GB Vapor-X

Sound Card: Creative Sound Blaster XFi Titanium Model 70SB08860000

There's something else that I noticed. I went to the website of my RAM manufacturer and it said my particular model needs 2.1v. I looked at my BIOS settings and it has DRAM set to 1.8v. Could that be a part of my problem?

takker · Mar 24, 2010

Hi Heimdall,

This looks very similar to another thread in this forum that zigzag3143 has troubleshot. Check it out and see if that advice works for you. If it does, please post back in this thread.

Your mini-dump Debug Code:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Terry\Desktop\crashdump\032310-19812-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02e9ee50
Debug session time: Tue Mar 23 18:05:36.789 2010 (UTC - 7:00)
System Uptime: 0 days 14:15:40.396
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a18afd1dc0, 1, fffff880043cf421, 5}
 
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+31 )
Followup: MachineOwner
---------
0: 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: fffff8a18afd1dc0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880043cf421, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
 
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f090e0
fffff8a18afd1dc0 
FAULTING_IP: 
dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
fffff880`043cf421 ff0b dec dword ptr [rbx]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88005fff690 -- (.trap 0xfffff88005fff690)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000008000400 rbx=0000000000000000 rcx=fffff8a00b3d71d0
rdx=fffffa80078a8230 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880043cf421 rsp=fffff88005fff828 rbp=0000000000000000
r8=fffffa80078a81e0 r9=fffff8a00b3d71d0 r10=fffff8a00a4f34a0
r11=fffff8a00b640010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x31:
fffff880`043cf421 ff0b dec dword ptr [rbx] ds:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d50b91 to fffff80002cd2f00
STACK_TEXT: 
fffff880`05fff528 fffff800`02d50b91 : 00000000`00000050 fffff8a1`8afd1dc0 00000000`00000001 fffff880`05fff690 : nt!KeBugCheckEx
fffff880`05fff530 fffff800`02cd0fee : 00000000`00000001 fffff8a1`8afd1dc0 fffff8a0`00000000 fffffa80`000000aa : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`05fff690 fffff880`043cf421 : fffff880`043c85c0 fffffa80`057f6000 fffff8a0`0a4f34a0 fffffa80`057f54b0 : nt!KiPageFault+0x16e
fffff880`05fff828 fffff880`043c85c0 : fffffa80`057f6000 fffff8a0`0a4f34a0 fffffa80`057f54b0 fffffa80`057f5630 : dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x31
fffff880`05fff830 fffff880`043caff3 : fffff8a0`0994d588 fffff8a0`0a4f35a8 fffff8a0`0994d588 fffff8a0`0a4f35a8 : dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x38
fffff880`05fff860 fffff880`043c7ee4 : fffff8a0`0a4f34a0 fffffa80`07835428 fffffa80`057f6000 fffffa80`057b4410 : dxgmms1!VIDMM_GLOBAL::EvictAllocation+0x67
fffff880`05fff8a0 fffff880`043c4ed3 : 00000000`00000000 fffffa80`04849160 00000000`000000af 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x218
fffff880`05fff8d0 fffff880`043df65d : 00000000`00000000 fffff8a0`0b3d71d0 fffffa80`00000000 fffffa80`07a6d010 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`05fffaa0 fffff880`043df398 : fffff800`00b96080 fffff880`043ded00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`05fffc90 fffff880`043dee96 : 00000000`00000000 fffffa80`04ba9010 00000000`00000080 fffffa80`057aa010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`05fffcc0 fffff800`02f76166 : 00000000`0363e112 fffffa80`057f54b0 fffffa80`03cf0040 fffffa80`057f54b0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05fffd00 fffff800`02cb1486 : fffff800`02e4be80 fffffa80`057f54b0 fffff800`02e59c40 fffff880`01266534 : nt!PspSystemThreadStartup+0x5a
fffff880`05fffd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND: kb
FOLLOWUP_IP: 
dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
fffff880`043cf421 ff0b dec dword ptr [rbx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
 
IMAGE_NAME: [COLOR=darkred]dxgmms1.sys[/COLOR]
 
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
BUCKET_ID: X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
Followup: MachineOwner
---------

Heimdall · Mar 24, 2010

Alright, I'll reinstall my video drivers, though I'm a bit skeptical since that didn't help me before I reinstalled the OS

I'll do a system file check as well. I'll show the results when it's finished. Thank you for your time ^^

Edit: Ok, SFC tells me that it found corrupt files and was unable to fix some of them. What should I do from here?

Edit 2: Reinstalled my video drivers. I'll reply back if it works or not.

Heimdall · Mar 24, 2010

Nope, that didn't help. Bluescreen again.

zigzag3143 · Mar 24, 2010

Heimdall said:
Nope, that didn't help. Bluescreen again.

Still pointing to the directx portion of the video driver. Are you sure you are removing all remnants of the old one?

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\032410-17986-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e44e50
Debug session time: Wed Mar 24 02:24:31.738 2010 (GMT-4)
System Uptime: 0 days 1:31:06.221
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8b8371b69d0, 1, fffff88003c28421, 5}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+31 )

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

0: 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: fffff8b8371b69d0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88003c28421, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eaf0e0
 fffff8b8371b69d0 

FAULTING_IP: 
dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
fffff880`03c28421 ff0b            dec     dword ptr [rbx]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880037f4690 -- (.trap 0xfffff880037f4690)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000080fffff8 rbx=0000000000000000 rcx=fffff8a00a36a230
rdx=fffffa80043aa110 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003c28421 rsp=fffff880037f4828 rbp=0000000000000000
 r8=fffffa80043aa0c0  r9=fffff8a00a36a230 r10=fffff8a00983ca60
r11=fffff8a009ac97c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x31:
fffff880`03c28421 ff0b            dec     dword ptr [rbx] ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cf6b91 to fffff80002c78f00

STACK_TEXT:  
fffff880`037f4528 fffff800`02cf6b91 : 00000000`00000050 fffff8b8`371b69d0 00000000`00000001 fffff880`037f4690 : nt!KeBugCheckEx
fffff880`037f4530 fffff800`02c76fee : 00000000`00000001 fffff8b8`371b69d0 fffff8a0`00000000 fffffa80`000000aa : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`037f4690 fffff880`03c28421 : fffff880`03c215c0 fffffa80`07456000 fffff8a0`0983ca60 fffffa80`07437060 : nt!KiPageFault+0x16e
fffff880`037f4828 fffff880`03c215c0 : fffffa80`07456000 fffff8a0`0983ca60 fffffa80`07437060 fffffa80`074371e0 : dxgmms1!VIDMM_DEVICE::RemoveCommitment+0x31
fffff880`037f4830 fffff880`03c23ff3 : fffff8a0`08a44e68 fffff8a0`0983cb68 fffff8a0`08a44e68 fffff8a0`0983cb68 : dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x38
fffff880`037f4860 fffff880`03c20ee4 : fffff8a0`0983ca60 fffffa80`040de718 fffffa80`07456000 fffffa80`07430000 : dxgmms1!VIDMM_GLOBAL::EvictAllocation+0x67
fffff880`037f48a0 fffff880`03c1ded3 : 00000000`00000000 fffffa80`048787b0 00000000`0000002c 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x218
fffff880`037f48d0 fffff880`03c3865d : 00000000`00000000 fffff8a0`0a36a230 fffffa80`00000000 fffffa80`074f0cf0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`037f4aa0 fffff880`03c38398 : fffff880`009ebec0 fffff880`03c37d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`037f4c90 fffff880`03c37e96 : 00000000`00000000 fffffa80`07fa6990 00000000`00000080 fffffa80`0742c010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`037f4cc0 fffff800`02f1c166 : 00000000`0300f443 fffffa80`07437060 fffffa80`03ccf040 fffffa80`07437060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`037f4d00 fffff800`02c57486 : fffff880`009e7180 fffffa80`07437060 fffff880`009f1f40 fffff880`01251bf0 : nt!PspSystemThreadStartup+0x5a
fffff880`037f4d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_DEVICE::RemoveCommitment+31
fffff880`03c28421 ff0b            dec     dword ptr [rbx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_DEVICE::RemoveCommitment+31

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_DEVICE::RemoveCommitment+31

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

0: kd> lmvm dxgmms1
start             end                 module name
fffff880`03c00000 fffff880`03c46000   dxgmms1    (pdb symbols)          f:\symbols\dxgmms1.pdb\685AF9F266284BE19008B39B739A572B1\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: F:\symbols\dxgmms1.sys\4A5BC57846000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Mon Jul 13 19:38:32 2009 (4A5BC578)
    CheckSum:         0004AD44
    ImageSize:        00046000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    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:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Heimdall · Mar 24, 2010

I assumed I was. I uninstalled the driver through device manager, and uninstalled the catalyst programs, then rebooted and reinstalled the driver. Was there something else that I should have done?

zigzag3143 · Mar 24, 2010

Heimdall said:
I assumed I was. I uninstalled the driver through device manager, and uninstalled the catalyst programs, then rebooted and reinstalled the driver. Was there something else that I should have done?

You might want to see if the vid card mfr has an un-install tool. Often that is the only way to nuke all the fragments.

BSOD issues while gaming

Heimdall

New member

My Computer

takker

New member

My Computer

Heimdall

New member

My Computer

Heimdall

New member

My Computer

zigzag3143

New member

My Computer

Heimdall

New member

My Computer

zigzag3143

New member

My Computer

Similar threads