BSOD while gaming (DirectX-games)

Hi,

I'd like to start by thanking you for at least taking a look at my problem.

Since recently I have been getting BSOD's while playing Counter-Strike:Source (hl2.exe), it started completely random which is the odd part.

The first BSOD I had was an issue related to dxgmms1.sys - after that first one, plenty followed. All of them seemed to happen within 20 minutes of playing. I eventually formatted my harddisk and reinstalled Windows 7 Ultimate x64, hoping for a fix.

However, instead of a fix, I've been getting BSOD's (within 20 minutes of playing, again) on this fresh install. The only things installed on my computer, at this point in time, are my drivers and Counter-Strike:Source since I wanted to see if it was caused by software.

I will run a memory test tonight and update you first thing tomorrow.


Sincerely,

Alexander Kerckhofs

fakeskuH said:

Hi,

I'd like to start by thanking you for at least taking a look at my problem.

Since recently I have been getting BSOD's while playing Counter-Strike:Source (hl2.exe), it started completely random which is the odd part.

The first BSOD I had was an issue related to dxgmms1.sys - after that first one, plenty followed. All of them seemed to happen within 20 minutes of playing. I eventually formatted my harddisk and reinstalled Windows 7 Ultimate x64, hoping for a fix.

However, instead of a fix, I've been getting BSOD's (within 20 minutes of playing, again) on this fresh install. The only things installed on my computer, at this point in time, are my drivers and Counter-Strike:Source since I wanted to see if it was caused by software.

I will run a memory test tonight and update you first thing tomorrow.


Sincerely,

Alexander Kerckhofs

Alexander hi and welcome

Three of these crashes point directly to your video driver. while it is a fairly current driver it may have become corrupt. I would download and install a fresh copy.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper


The other two mention but dont point to your audio driver so perhaps it would be a good idea to re-install it as well.

The rest of your drivers are fairly current, and there are only a few other things that might be causing the problem. Lets try these two drivers first and if they do not repair the problem we can move on to other things



Let us know if you need further assistance

Jan

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\Windows_NT6_BSOD_jcgriff2\082910-18406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e5ae50
Debug session time: Sun Aug 29 10:20:08.976 2010 (GMT-4)
System Uptime: 0 days 0:13:43.008
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8045788658, 2, 1, fffff8800436ab3d}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa8045788658, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800436ab3d, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec50e0
 fffffa8045788658 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d
fffff880`0436ab3d f0834018ff      lock add dword ptr [rax+18h],0FFFFFFFFh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffd4a0 -- (.trap 0xfffff88002ffd4a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8045788640 rbx=0000000000000000 rcx=fffffa80056c30d8
rdx=fffffa800591d420 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800436ab3d rsp=fffff88002ffd630 rbp=fffffa8005609c90
 r8=000000000000001b  r9=fffffa800598b290 r10=0000000000000000
r11=000000000000000a r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d:
fffff880`0436ab3d f0834018ff      lock add dword ptr [rax+18h],0FFFFFFFFh ds:e5f0:fffffa80`45788658=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8e469 to fffff80002c8ef00

STACK_TEXT:  
fffff880`02ffd358 fffff800`02c8e469 : 00000000`0000000a fffffa80`45788658 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02ffd360 fffff800`02c8d0e0 : 00000000`00000000 fffffa80`07ae0d90 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02ffd4a0 fffff880`0436ab3d : 00000000`00000000 00000000`00000000 fffffa80`07ebe5f0 fffffa80`066b9010 : nt!KiPageFault+0x260
fffff880`02ffd630 fffff880`0436e677 : fffffa80`07ae0d90 fffffa80`05609c90 fffffa80`07f89ec0 fffff880`04891f40 : dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+0x7d
fffff880`02ffd660 fffff880`0436de00 : 00000000`00000000 fffffa80`066b9010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x253
fffff880`02ffd700 fffff880`0436dc4c : fffffa80`00000000 fffffa80`066b9010 fffffa80`07b4bfd0 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`02ffd750 fffff880`042741cf : fffffa80`06ec7040 00000000`00000246 fffff880`02ffd7c8 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02ffd7a0 fffff880`0488205c : fffffa80`07b43000 00000000`00000000 fffffa80`07b43000 00001f80`00000b01 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02ffd7d0 fffffa80`07b43000 : 00000000`00000000 fffffa80`07b43000 00001f80`00000b01 fffff880`02ffd9e8 : atikmdag+0x5505c
fffff880`02ffd7d8 00000000`00000000 : fffffa80`07b43000 00001f80`00000b01 fffff880`02ffd9e8 fffff880`04891f40 : 0xfffffa80`07b43000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d
fffff880`0436ab3d f0834018ff      lock add dword ptr [rax+18h],0FFFFFFFFh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

BUCKET_ID:  X64_0xD1_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d

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

Hope the fresh driver install helped- in my case, the driver install never worked, so I checked my earliest time when the same BSOD started to appear, and went through my drivers update and found out that I updated my graphics driver just that day- rolled back a couple of versions, and now it's been working fine *knock on wood*. Try out other archived versions of the driver.