Overclock.net › Forums › Graphics Cards › AMD/ATI › ....And so it begins. Blue Screens galore, DirectX corrupt?
New Posts  All Forums:Forum Nav:

....And so it begins. Blue Screens galore, DirectX corrupt?

post #1 of 13
Thread Starter 
I will do my best to explain my issue, please read carefully.

So I have been bluescreening lately, not frequently... but enough to piss me off. The causes are ALWAYS usually the following:

atikmdag.sys
ntoskrnl.exe
dxgmms1.sys

At first I thought it was core voltage being too low because they were 0X1ee BSOD's, then it hit me in the face.... Two out of those three have to do with graphics drivers/software that has to do with the graphics card. One of them involves DirectX, the other involves ATI. I did a quick Google search of atikmdag.sys BSOD and apparently people are plagued with this BSOD.

This problem has been occurring for a few weeks. It ONLY HAPPENS when I am in a video game/launching a video game/exiting a video game, etc. It never happens when I am idle browsing OCN or anything else.

Another weird thing is if I enable DirectX11 in World of Warcraft, restart the client, MSI AB OSD will say it's running D3D11. However, a day later or so it'll reset itself back to D3D9.
  • The blue screens happened before I was crossfired.
  • The blue screens happened before I updated to 11.4 from 11.2
  • The blue screens only happen while gaming, exiting a game, or starting a game. They are not incredibly frequent, but they will not disappear.

Here's the DMP files:

1.
Quote:
On Fri 5/6/2011 1:06:08 AM GMT your computer crashed
crash dump file: C:\\Windows\\Minidump\\050511-20014-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA4C9B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EA4C9B, 0xFFFFF880035850A8, 0xFFFFF88003584900)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\\Windows\\system32\
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
2.
Quote:
On Fri 5/6/2011 1:06:08 AM GMT your computer crashed
crash dump file: C:\\Windows\\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80002EA4C9B, 0xFFFFF880035850A8, 0xFFFFF88003584900)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

3.
Quote:
On Mon 5/2/2011 12:58:26 AM GMT your computer crashed
crash dump file: C:\\Windows\\Minidump\\050111-14476-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1B507)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005531507, 0xFFFFF8800D157BF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\\Windows\\system32\\drivers\\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
There... as much information as I can think of.

What do you guys think?
post #2 of 13
What is the clock on the GPU?
post #3 of 13
Thread Starter 
Quote:
Originally Posted by Roll Cam Tide View Post
What is the clock on the GPU?
Both GPUs are stock.
post #4 of 13
Quote:
Originally Posted by E-Peen View Post
Both GPUs are stock.
So there are no artifacts on the screen and it runs normally besides the BSOD right?
post #5 of 13
Thread Starter 
Quote:
Originally Posted by Roll Cam Tide View Post
So there are no artifacts on the screen and it runs normally besides the BSOD right?
That is correct!
post #6 of 13
Could you play wow in safemode? Maybe you could try that and see if it still crashes. It does sound like a driver issue to me though.
post #7 of 13
Thread Starter 
Quote:
Originally Posted by Roll Cam Tide View Post
Could you play wow in safemode? Maybe you could try that and see if it still crashes. It does sound like a driver issue to me though.
Yeah, it definitely sounds like a software issue to me as well. I am going to reformat, I've wanted to reformat for a few weeks for multiple reasons anyways.

If the problem continues after a reformat, it's most likely unfortunately a hardware issue. Which I doubt at this juncture, but you never know.
post #8 of 13
Quote:
Originally Posted by E-Peen View Post
Yeah, it definitely sounds like a software issue to me as well. I am going to reformat, I've wanted to reformat for a few weeks for multiple reasons anyways.

If the problem continues after a reformat, it's most likely unfortunately a hardware issue. Which I doubt at this juncture, but you never know.
Good luck, and let us know if it works. I think it will.
post #9 of 13
Hey E-Peen! Bummer on the BSOD's. Zip up the DMP files and I'll run them through the debugger for you and see maybe if we can pinpoint more info about what's causing the problems!
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
post #10 of 13
Thread Starter 
Quote:
Originally Posted by GanjaSMK View Post
Hey E-Peen! Bummer on the BSOD's. Zip up the DMP files and I'll run them through the debugger for you and see maybe if we can pinpoint more info about what's causing the problems!
Long time no talk my dude! Unfortunately, I'm on my backup PC right next to me because I'm already reformatting, so we're outta luck on that one! After the reformat if I still see the same BSODs I will definitely come to you with the DMP files.

I'm really hoping a reformat will fix it in hope that it was a simple software issue.
Edited by pjBSOD - 5/5/11 at 7:55pm
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD/ATI
Overclock.net › Forums › Graphics Cards › AMD/ATI › ....And so it begins. Blue Screens galore, DirectX corrupt?