BSOD while playing games or listening to music

Code:

BugCheck D1, {fffffa0008aa8f88, 2, 1, fffff880053a2b3d}

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

Update your ATI/AMD display driver.
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Still it is a display related issue.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff8000308a045}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchWaitForEvents+f5 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000308a045, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bf100
GetUlongFromAddress: unable to read from fffff800032bf1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForMultipleObjects+1cd
fffff800`0308a045 f00fba2e07      lock bts dword ptr [rsi],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880060192c0 -- (.trap 0xfffff880060192c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000011
rdx=000000000007792a rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000308a045 rsp=fffff88006019450 rbp=fffffa8009212c70
 r8=fffff880060197b8  r9=fffff88002fd7180 r10=0000000000000000
r11=fffff88006019780 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe nc
nt!KeWaitForMultipleObjects+0x1cd:
fffff800`0308a045 f00fba2e07      lock bts dword ptr [rsi],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003087169 to fffff80003087bc0

STACK_TEXT:  
fffff880`06019178 fffff800`03087169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`06019180 fffff800`03085de0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000011`ca12b4cb : nt!KiBugCheckDispatch+0x69
fffff880`060192c0 fffff800`0308a045 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`06019450 fffff880`0fd320b5 : 00000000`00000000 fffff880`06019838 00000000`00000001 fffffa80`00000000 : nt!KeWaitForMultipleObjects+0x1cd
fffff880`06019710 fffff880`0fd60e79 : 00000000`00000000 fffffa80`08330410 00000000`00000000 fffffa80`08330410 : dxgmms1!VidSchWaitForEvents+0xf5
fffff880`06019770 fffff880`0fd5ce21 : fffffa80`09213000 ffffffff`feced300 fffffa80`0a28cec0 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x139
fffff880`060197b0 fffff880`0fd5cfd9 : fffffa80`09213000 fffffa80`08330410 fffffa80`09214700 00000000`00000000 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
fffff880`060198a0 fffff880`0fd5beb8 : 00000000`00000192 00000000`003632ae fffffa80`0a28cec0 fffffa80`08330410 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x171
fffff880`060199a0 fffff880`0fd5b514 : fffff880`02fdbf00 fffff880`0fd5af00 fffffa80`00000000 fffffa80`00007c80 : dxgmms1!VidSchiSubmitRenderCommand+0x920
fffff880`06019b90 fffff880`0fd5b012 : 00000000`00000000 fffffa80`0887f010 00000000`00000080 fffffa80`08330410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`06019bc0 fffff800`033242ea : 00000000`01ea386b fffffa80`09212b50 fffffa80`06cd9040 fffffa80`09212b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`06019c00 fffff800`030788e6 : fffff880`02fd7180 fffffa80`09212b50 fffff880`02fe1fc0 00000000`000e718b : nt!PspSystemThreadStartup+0x5a
fffff880`06019c40 00000000`00000000 : fffff880`0601a000 fffff880`06014000 fffff880`06019540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchWaitForEvents+f5
fffff880`0fd320b5 8be8            mov     ebp,eax

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dxgmms1!VidSchWaitForEvents+f5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidSchWaitForEvents+f5

BUCKET_ID:  X64_0xA_dxgmms1!VidSchWaitForEvents+f5

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

3: kd> lmvm atikmpag
start             end                 module name
fffff880`02c50000 fffff880`02cee000   atikmpag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Aug 31 04:02:32 2013 (52211D80)
    CheckSum:         0009C9D2
    ImageSize:        0009E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Let us know the results.

Actually Arc that was the first thing that struck me - PSU some info on it would be good.

adamfalkofske said:

I'm thinking I should remove one of the gfx cards and maybe see if that helps? I don't really need two of them.

Remove one and see what happens.

My 2cents again if that is an idle temp for the CPU then I would seriously look at finding out why it is a tad on the high side (for me) unless the ambient temp is very high of course. What cooling has it and the case for that matter got??

The GPU temps are well not what I would want to see on just an idle. It will be good to see what taking one out does.