Problem with graphics card, pc crashing

Ronne

Commendable
Nov 14, 2016
3
0
1,510
http://pcpartpicker.com/list/pt8tQV

CPU: Intel Core i5-4690 3.5GHz Quad-Core Processor
CPU Cooler: Corsair H100i 77.0 CFM Liquid CPU Cooler
Motherboard: Asus Z97-A ATX LGA1150 Motherboard
Memory: Corsair Vengeance 8GB (1 x 8GB) DDR3-1866 Memory
Memory: Corsair Vengeance 8GB (1 x 8GB) DDR3-1866 Memory
Storage: Samsung 840 EVO 250GB 2.5" Solid State Drive
Storage: Western Digital WD Green 2TB 3.5" 5400RPM Internal Hard Drive
Video Card: MSI GeForce GTX 770 2GB TWIN FROZR Video Card
Power Supply: Corsair RM 850W 80+ Gold Certified Fully-Modular ATX Power Supply
Operating System: Microsoft Windows 10 Pro OEM 64-bit

Since I've been away all weekend I have not touched my pc, nor has anyone else. But when I tried to start WoW today, my pc went all slow. When I finally got in, it felt like the whole game was in 10 fps. After a few seconds my computer froze and restarted itself. This does happen mostly in games, but also whilst watching youtube, for example.

I have checked temperatures (CPU at 48 50 degrees celsius and GPU at 50 degrees celsius) aswell as load, and during my short playtime, load went up to 98%.
I have used DDU to uninstall drivers, as well as tried using old drivers and the newest one. I'm not sure what else to do since I have never had this problem before.
Thank you for any help you can give.

Edit: I recently had an error/blue screen that said "DRIVER IRQL NOT LESS OR EQUAL "What failed: nvlddmkm.sys"
Edit2: Another error/blue screen that said "Stop code: DPC WATCHDOG VIOLATION"
Edit3: Yet another blue screen saying "STOP THREAD EXCEPTION NOT HANDLED" What failed: nvlddmkm.sys"

I appreciate any help!
 
Solution
Try swapping cables, on the single monitor, that is currently working, just to rule out a bad cable. Sometimes a CMOS reset will fix odd problems, also.

Ronne

Commendable
Nov 14, 2016
3
0
1,510
System restore did not work, neither did checking the disk for corrupted files.

Could mention that the system restore point was 2016-11-10, so just 4 days ago, might have happened before that since I've been away all weekend.