Videocards keep getting black screens

Emperor010

Commendable
Aug 25, 2016
7
0
1,510
Hello everyone,

I have a problem for a few weeks/months now, my gpu's keep getting black screens but the sound continue to play. I can't do anything then turn of my pc the hard way... :(

The first card that had this problem is a Sapphire R9 290 (reference model with accelero IV cooling). I had this card for over a year when the black screens begin. For a long time i thought it was driver related or in the gpu bios since i flashed a lot of them. I must have flashed over over 20 different bios versions but no succes. One day in bf4 it went on black and stayed that way, even when booting up. I ended up buying a new MSI GTX 980 Gaming 4G that actually worked pretty good for a few days, no problems at all even in heavy battlefield sessions 8 hours+

Since it worked so good i thought i overclock this beast and then actually the same symptons occured. Black screens every time while i was gaming and eventually it died. Not one signal of life. I returned the card to the store where i bought it and they said it worked ok :eek:
I was like wtf and explained the story to them, they tested some more and confirmed the card had a defect. Then i knew that that card maybe died because of my overclocking and decided to wont do it again (even if i did it with the last 5 gpu's but ok...)

So i had no gpu at this point and put back in the good old Sapphire R9 290 and it was alive again, i could actually play a few games and then the black screens came back. This time without being overclocked. I was done with the gpu and today i bought another GTX 980, this time an Asus Strix version. I put the card in (before this i ran driver sweeper ofc) and started up gta5, after 2 mins of play it crashes. Now im kinda pissed :D

Things i done so far:
- replace dual link dvi cable
- try older motherboard bios version
- try other monitor
- other pci-e slot
- underclock the r9 290 to 800/1000
- run prime95 26.6 for 8 hours+
- a lot of cursing after i got a cooldown from cs go again

Basicly my PSU is the prime suspect here in my eyes. It ran fine with a FX 8350 with OC and a R9 290 (also OC) for a long time. I think the problems really started when i switched to i7 6700k.
There is no option for me to borrow a psu or get help from anyone. They have 400-500 psu's. That's ok but before i gonna spend more money at this i want to make sure that my dying psu really is killing my gpu's :(

One last remark: after i reboot the pc after a black screen i sometimes see artifacts with the newest card. Purple things and stuff. I took it out now and hope it's still ok...

What do you guys think of this? Sorry for bad english btw.

SPECS:
CPU: Intel i7 6700K
GPU: Asus GTX980-STRIX 4GB OC
MOBO: Asus Z170 Pro Gaming
MEM: Kingston HyperX Fury 8GB DDR4 2400 C15
PSU: Seasonic Platinum Series 520W Fanless
SSD: Samsung 850 EVO 500GB

*edit* http://www.tomshardware.co.uk/forum/id-2547993/psu-tier-list.html
The psu is in tier 1
http://www.realhardtechx.com/index_archivos/Page362.htm
according to this 520watt should be ok

 
Solution
Is it still under warranty? many psus have surprising warranties on them, either way, sorry I couldn't be of much help, really really hope it works for you, if it does, reply here, might be worth a go, mine's still warrantied so it'd be a pain to do but not expensive.

Cheers and good luck.

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560
What OS and windows version you on (windows key + R, type winver hit enter)? I'm also having this issue (minus the artifacting), I'm thinking it could either be Vulkan, DX12 or the windows Anniversary update.
 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560
Can you run a program called "Who crashed"

It's returned me this error:
On Fri 26/08/2016 12:43:11 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: watchdog.sys (watchdog!WdLogEvent5_WdCriticalError+0xCE)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFCE00E4A9A960, 0xFFFFE30EE4994DA0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

It may reveal something for you or even confirm our troubles are indeed the same, perhaps a more technical individual can decipher that mess of warnings?
 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560


You should be able to simply scroll to the bottom of the report page after running analyze to get a report similar to mine there, no pro needed really.
 

Emperor010

Commendable
Aug 25, 2016
7
0
1,510
Ah yes, u are right.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 25-8-2016 22:29:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082616-4250-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x9BFEB8)
Bugcheck code: 0xD1 (0xFFFFF80998C2FEB8, 0x2, 0x8, 0xFFFFF80998C2FEB8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys .
Google query: nvlddmkm.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 25-8-2016 22:29:46 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x9BFEB8)
Bugcheck code: 0xD1 (0xFFFFF80998C2FEB8, 0x2, 0x8, 0xFFFFF80998C2FEB8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys .
Google query: nvlddmkm.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 24-8-2016 12:51:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082416-4046-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A060)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 24-8-2016 11:26:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082416-4046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A060)
Bugcheck code: 0xD1 (0x0, 0xD, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

*edit* please note, the problems started BEFORE the anniversary update with an AMD R9 290 card. Then two other cards of nvidia (both 980's) have the same symptons.
 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560
Not gonna lie, looks like our problems are different, but while I try some things to rectify whatever the hell mine is, I'll at least try a couple of google searches see if I can't find an answer for yours :) The whocrashed at least mentions for you that it looks like a typical driver issue and not a hardware one which, while not 100%, looks promising, but having read your post you've already been through the driver sweeper, fresh driver install stuff so I don't know what to recommend there...
 

Emperor010

Commendable
Aug 25, 2016
7
0
1,510
I gonna pick up a Corsair RM 750x now.

My theory: for a long time i run the psu at very high loads and i mean year in year out and it's basicly 24/7 on.
Long gaming sessions with a heavy overclocked config. Maybe the psu degraded somehow and now can't handle full loads anymore and driver crashes are the result. Since there is no fan in the psu it could have run sometimes hotter then it was supposed to be. The psu is 3,5 years old.

But i wouldn't be surprised at all if i install the new psu and the same problems occur. Then it has to be the motherboard :(

Thanks for your help anyway, much appriciated :)
 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560
Is it still under warranty? many psus have surprising warranties on them, either way, sorry I couldn't be of much help, really really hope it works for you, if it does, reply here, might be worth a go, mine's still warrantied so it'd be a pain to do but not expensive.

Cheers and good luck.
 
Solution

Emperor010

Commendable
Aug 25, 2016
7
0
1,510
Yes it is under warrenty. This evening i installed the new Corsair RM750X and all my problems were gone.
Both videocards work great again, tested them for hours in several games:)

gonna stick with my good old r9 290 untill i can score a nice gtx 1070 and sell the 980 for now.
 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560


Really great to hear, happy you managed to sort it, I'm gonna reinstall windows, failing that test gpu in a friend's machine, if that fails, RMA GPU I guess :/

 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560
Oh hey! You'll probably never see this but after seeing your success I caved, even though it was a huge pain, I ripped out my PSU to have a gander, lo and behold, the GPU power cable had melted into the PSU screwing with the power delivery! Quick change of cable and socket, I'm back playing with the best of them haha! :D *is chuffed*

A huge thank you, if I hadn't seen your solution, I'd have probably RMA'd the card and received a hefty 'waste of time' bill.

Reinstalled windows for nought, haha fml.
 

Emperor010

Commendable
Aug 25, 2016
7
0
1,510

Wow, that's amazing,.. We both got our shit fixed :D

Game on bro.