- Sep 20, 2017
- 5
- 0
- 510
First i'll start this off with the fact that for a few months now i've been getting "Display driver has stopped responding and restarted" errors. In addition to that I blue screen if I run a site like Twitch or Youtube while gaming. I've checked the temperatures and i'm not overheating, so that's not the issue. Other less cpu (gpu?) intensive sites don't cause the blue screens, although running multiple programs does seem to increase the driver error occurrences. I've tried updating my drivers and reinstalling them but that didn't work. All of those problems aside I have an even bigger problem and i'm sure they're all related.
I was talking to a friend on Discord when all of a sudden the pc crashed, restarted, and brought me to the windows repair screen asking me to reinstall Windows. The first time this happened I figured no big deal and reinstalled Windows (i'm lazy). This time, however, I checked my bios and found that my hard drive priorities had changed. It was trying to boot from my HD rather than my SSD (the one with Windows on it). I switched the priorities and restarted and i'm up and running again. The display driver error still happens though, so I imagine that didn't fix the problem. So, any clues as to why this might be happening? Any information would be greatly appreciated, thanks for reading and sorry if the category is off.
Hardware:
MOBO - Gigabyte Motherboard ATX DDR3 2600 LGA 1151 GA-Z170-HD3 DDR3
GPU - AMD Radeon R390
CPU - Intel Core I5-6600K
I was talking to a friend on Discord when all of a sudden the pc crashed, restarted, and brought me to the windows repair screen asking me to reinstall Windows. The first time this happened I figured no big deal and reinstalled Windows (i'm lazy). This time, however, I checked my bios and found that my hard drive priorities had changed. It was trying to boot from my HD rather than my SSD (the one with Windows on it). I switched the priorities and restarted and i'm up and running again. The display driver error still happens though, so I imagine that didn't fix the problem. So, any clues as to why this might be happening? Any information would be greatly appreciated, thanks for reading and sorry if the category is off.
Hardware:
MOBO - Gigabyte Motherboard ATX DDR3 2600 LGA 1151 GA-Z170-HD3 DDR3
GPU - AMD Radeon R390
CPU - Intel Core I5-6600K
Facebook
Twitter
Instagram