BSOD when gaming, mainly with GTAV errors include 0x000000d1

Adam16 · 02 Aug 2016

Hi,

Thank you in advance for any help that you might be able to offer.

Back in March I bought a bundle of a MB, CPU + cooler, and RAM from a reputable UK based online retailer. Alongside this I also bought a graphics card, an SSD for the OS and games, and an HD for general storage. The other components come from an old PC including case, 1000WPSU, Blu-ray, and screen. Details should presumably be in the uploaded file alongside this but if you need anything further please let me know. The bundle came overclocked but I have run it non-overclocked and am still having issues.

About a month after having set it up I started getting BSODs when gaming. This is mainly GTA V but numerous other games also suffer either complete BSODs or crash to desktop. I also got 2 red screen of deaths at this time.

Crash codes for this were mainly 0x000000d1 but also included a few 9Cs. I tried everything to fix this including checking the temperatures reached by GPU and CPU (maxing out at low 80s so while high shouldn't be the cause), driver reinstallation, reinstalling windows (hence why the dmp files from this period aren't captured) and memtest86.

memtest86 crashed on its first run an hour in and on its second run showed one error 8 hours into a 20 cycle test. I returned the bundle and gfx card to retailer for testing and they replaced the RAM.

Unfortunately this hasn't stopped the crashes and I am still getting BSODs when gaming. These are primarily d1s although there seems to be a bit more randomness in them this time round with 1e, 101, 7e, 139 also making an appearance.

BluescreenView and WhoCrashed aren't providing me with any obvious information to go on other than it being primarily an ntoskrnl.exe issue although FLTMGR.sys, e1d65x64.sys and HDAudBus.sys have also cropped up. Memtest86 passes with no errors.

Running driver verifier I consistently crash before the log-in screen due to atikmdag.sys and atikmpag.sys.

I have tried reinstalling the drivers repeatedly including using the AMD DUU for a complete clean uninstall but have had no improvement. I have the same issue whether I download drivers through the AMD website, use the various driver updater tools or use the driver that comes through devicemanager.

As such, I'm a bit stumped. I suspect its a faulty graphics card but before I go through the hassle of returning it I'm hoping someone might be able to confirm, or disprove, my suspicions.

Please let me know if there's anything else you need.

Ztruker · 02 Aug 2016

Definitely something to do with your AMD Radeon (TM) R9 390 Series video card or driver:

Code:

BugCheck C4, {2003, ffffe00081522ae8, fffff801e4b00240, ffffd000dc952520}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys

Could not read faulting driver name
Probably caused by : atikmpag.sys ( atikmpag+105c )

Did you try this one: Radeon Software 354 MB Crimson Edition 16.7.3 7/28/2016
Found here: Desktop

Adam16 · 03 Aug 2016

Thank you for your response. I think that's the only one I haven't tried so I'll give it a go today

Adam16 · 03 Aug 2016

Hi,

I've just installed them using the AMD minimal setup link on their website. I did a complete clean again before hand.

As soon as they were installed I ran driver verifier again and it's actually passed! It has never done that before!

I'm going to run GTA V and leave it running to see what happens but so far it appears that it might have actually worked - although why this time as opposed to the multiple other drivers versions I've used, god knows.

I'll keep you posted and will come back to this either way in a weeks time as if it hasn't crashed by then I'll be truly satisfied that it is fixed.

I suspect this might be like going to the doctors, ie that as soon as you go your cold disappears. But I'm exceptionally grateful for your time and help in any event - many thanks.

Ztruker · 03 Aug 2016

Good luck, thanks for letting me know how it's going.

Adam16 · 04 Aug 2016

Hello again,

Unfortunately it appears that my problem still persists. GTA V ran for 16 hours without a glitch, all the time with driver verifier running in the background. I then stopped verifier and was playing rise of the tomb raider when my system suffered a 0x0000009c, followed by 0x0000000a when I restarted and played again. I've re-run the data collection tool and have attached the results so hopefully the two new dmp files are contained within.

I have rerun driver verifier and it is still letting me get beyond windows login, which is good.

Once again, my sincere thanks for your help on this.

Adam

Ztruker · 04 Aug 2016

8/4 11:09 PM dump again points to the video card/driver.

Code:

fffff801`04a7a4f8  fffff801`ab573969Unable 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
 atikmdag+0x43969

I don't know what else to recommend. Dxdiag indicates you are using the DVI connection. Any chance you can switch to VGA just to test?

Also noticed your CPU is slightly over clocked.

Code:

0: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3504

Can you check your BIOS and see if you can set everything to nominal for speed and voltages?

Since Verifier is not showing any problems now, try FurMark.

===================================================
Follow this tutorials to stress test your GPU:
FurMark - GPU Stress Test - Windows 10 Forums

Also try removing and reinstalling the video card. Check any cable connections to it.

Adam16 · 05 Aug 2016

I can switch to the non-oc profile in the bios to see if it affects anything. Bit surprised the oc is that low so I'll have to see what's going on. I can't adjust the clock speeds and voltages myself outside of switching profiles without voiding the warranty so might be limited.

I'll try furmark and after that take the card out fully and use integrated graphics for a bit to see if that does anything.

Thanks once again