After I Removed and Reinstalled the GPU I Got a few Driver Stopped Responding Error in a Row

feelingtheblanks

Honorable
Jan 3, 2014
412
0
10,960
Hello everyone.

Got a very weird issue tonight.

Before diving into the details here are my specs

Intel i7-4770K @ stock freq. for now + hyper evo 212
MSI z87-gd65 motherboard
4x4 g.skill ripjawsx 1866 mhz ram
sapphire radeon 7870 oc edition
samsung 840 evo ssd + 1gb wd black + 1gb samsung spinpoint hdd
Thermaltake Toughpower 750w modular psu
Windows 8.1 pro (with the recent updates)
couple of case fans

So recently my gpu fans has started making some weird noises at certain rpm. So I decided to clean it up tonight. I removed the gpu which was a bit hard for some reason. The pci-ex lock was very tough and it didn't release the gpu easily. So I had to use some force to remove it.

Anyways, then I cleaned and reinstalled it carefully.

After that I started playing some Divinity: Original Sin. Everything was OK. The weird noise was gone, gpu temperatures was around 65C (and cpu around 50C). I played the game for like 30 minutes. Then Steam servers downed for some reason, since I was playing with a friend we stopped and I alt-tabbed to check e-mails.

After a minute or two I got an error prompt coming from bottom right of the screen saying that:

"Display driver amdkmdap stopped responding and has successfully recovered"

Then I got a black screen. Then again that error and again a black screen ended up with a BSOD.

I restarted PC, and after 30 secs or so I got the same error few times again with black screens, monitor loses signal to hdmi ended up with a freeze and a reboot.

Then the same story after the reboot. And one more time. It was all happened in 8-10 minutes.

I thought I couldn't reseat the gpu properly so I double checked but it was fine.

After that I restarted the PC again. Steam servers was up again. So we continue playing and it's been 2 hours now without any error.

So what was just happaned? I actually thought I damaged the motherboard or the gpu since I had to use some unusual force to remove that damn lock. But if that's the case I would keep getting those error right? Or at least some stability issues...

Any ideas? What would be the cause?