BSOD + three beeps.

[zPanic]

Hi!

 

I recently upgraded my GPU from an R9 280X to an RX 580.

Back then, when I tried booting my PC, it would simply leave my monitors on standby, with no lights coming on on my mouse and keyboard (which is what is supposed to happen if the PC boots, even without any display connections).

I fixed that by reseating my GPU properly (the clip wasn't properly opened when I first seated it).

My system has been working fine for the past week or so, since I upgraded.

Today, I got the dreadful "System thread exception not handled" BSOD, along with three beeps after my PC shut down.

Afterwards, it tried booting itself up again.

I got the same thing as described before; standby monitors, no lighting on mouse/keyboard, etc.

I forced my PC to shutdown (holding the power button), then rebooting it again.

Lo and behold, it booted. At first, my main monitor was completely blue (with me being able to move the mouse around freely), where the login screen should be.

After waiting patiently for 20-30 seconds, it showed me the login screen.

 

Now, my PC works again, but I'm afraid it'll happen again.

Could I do something to prevent this from happening again?

Thanks.

[iRileyx]

Was it one longish beep and 2 short ones?

 

Try reseating the ram.

[zPanic]

Just now, RKRiley said:

Was it one longish beep and 2 short ones?

 

Try reseating the ram.

I didn't pay attention to the length of the beeps, sorry.. 

I'll try that. 

It just crashed again and gave me a "kmode" error. 

What failed: win32kfull.sys. 

Same thing with it restarting to standby monitors and no lighting on my mouse/keyboard. 

[iRileyx]

Also "System thread exception not handled" is normally something to do with display drivers, so try updating them also. Use DDU to un install any current ones and then re-install from amd's website.

[zPanic]

Tried that. What happened:

 

As it was installing the new drivers, my screens lost signal, went on and off a few times (which is normal when installing gpu drivers). 

However, it then showed artifacts for a second or so, on  both my monitors, for a couple of times.

Then, my monitors went on standby, my keyboard lighting froze, and I was flicked out of the Discord call I was in. 

[zPanic]

This time e1d65x64.sys caused the crash. Seems to be the Intel gigabit adapter. Do you think it could be yesterday's Windows update that causes the crashes?

[zPanic]

It was the latest windows update, or so it seems. Been able to play for 20 minutes now; it used to crash before 10 minutes of playtime prior to uninstalling the latest update. This is the update that caused it: Windows 10 version 1607 (KB3150513) (May 2nd 2017)