Afterburner triggers BSODs due to driver conflicts or hardware incompatibility.

F5F Stay Refreshed Software Operating Systems Afterburner triggers BSODs due to driver conflicts or hardware incompatibility.

willjupe
Junior Member

10-18-2016, 02:25 AM

willjupe

10-18-2016, 02:25 AM #1

Frinex10
Posting Freak

806

10-19-2016, 01:56 AM

It might be one of two scenarios. First, your GPU was overclocked and isn't stable. Second, the recent Windows updates might be triggering the BSOD whenever you enable afterburner. These are likely the primary possibilities I noticed.

Frinex10

10-19-2016, 01:56 AM #2

Milaze
Junior Member

10-24-2016, 04:28 AM

I should have noted that I didn’t overclock anything. It’s at the stock factory setting of 1000/1260MHz. My GPU is the Asus R9 290 OC. Also, I’ve been gaming for a couple of days with Afterburner off and haven’t experienced any BSODs. I also had a crash on my system when playing a video in Chrome with hardware acceleration enabled.

Milaze

10-24-2016, 04:28 AM #3

ManMallow
Member

223

10-26-2016, 01:03 AM

Have you checked if your system is running the latest version? The newest release has led to many machines freezing when they start up.

ManMallow

10-26-2016, 01:03 AM #4

Have you checked if your system is running the latest version? The newest release has led to many machines freezing when they start up.

saukeuchiuchi
Senior Member

621

10-26-2016, 07:51 AM

I received all the latest updates via Windows Update. Additionally, the issue was resolved with a bugcheck ID of 0xa0000001. The two affected drivers were atikmdag.sys and dxgkrnl.sys (verified using bluescreenview).

saukeuchiuchi

10-26-2016, 07:51 AM #5

Spiegelmeister
Member

10-28-2016, 08:08 AM

I've seen many suggestions about removing and reinstalling graphics card drivers, then restarting, especially after similar issues. Updating Direct X also seemed to trigger problems before. Those steps might be the right place to begin. It popped up while I was browsing around.

Spiegelmeister

10-28-2016, 08:08 AM #6

Shardgale
Senior Member

547

10-28-2016, 01:15 PM

I've already tested that solution and the 14.4 drivers (non-beta), but I haven't updated DX yet. I'm still puzzled about why Afterburner triggers this issue.

Shardgale

10-28-2016, 01:15 PM #7

I've already tested that solution and the 14.4 drivers (non-beta), but I haven't updated DX yet. I'm still puzzled about why Afterburner triggers this issue.

tal1234b
Member

10-28-2016, 01:47 PM

tal1234b

10-28-2016, 01:47 PM #8

Lasersoft120
Member

156

10-28-2016, 03:29 PM

It began only recently, which makes it seem like a Windows problem.

Lasersoft120

10-28-2016, 03:29 PM #9

It began only recently, which makes it seem like a Windows problem.