Black screen lockups

[Kei]

I've had this issue randomly since I upgraded from 7 to 10 last year. Basically one second all is fine playing a game or browsing and the next, the content on screen freezes for a second before all goes black. Sound continues to play for a few seconds before it freezes and the sound loops. It will then restart a few seconds later. (It's a TDR problem related to dxgkrnl.sys and nvlddmkm.sys) It's been very random and I could go for over a month without a problem then oddly I'd have a couple a day. It definitely got progressively more common from roughly October where the 1607 update occurred.

So far I've tried the following:

1 - Underclock the GPU
2 - Reset CPU overclock back to standard
3 - Swap my quad channel ram out for a dual channel set
4 - Swap my PSU out for another
5 - Safe mode DDU and reinstall of nvidia drivers
6 - Tried older and the most up to date nvidia drivers
7 - Updating all motherboard drivers
8 - TDR registry tweaks (which just made it stay with a black screen even longer or never reboot at all)
9 - Change PCIe Gen mode from 3.0 to 2.0 and 1.0
10 - Removed all add in cards
11 - Disabled all non essential integrated motherboard devices
12 - Reinstall windows

Thus far nothing has worked at all. I'm stuck to running chrome with hardware acceleration disabled and not playing any games. It seems that older games like UT99 don't cause it to lock up, or at least not during the amount of time I've played it for.

My spec:

OS:Win 10 Pro v1607 Build 14393.953
GPU:MSI GTX 780 3GB - 378.78
CPU:i7 4820K (stock)
MBD:Asus P9X79
PSU:Corsair TX650 V2
RAM:Kingston 16GB DDR3 1600Mhz (running at SPD 1333)
SPU:Asus Xonar Essence ST DLX (PCI)
AIB:AJA Kona LSe (PCIe)
HDD1:Crucial M500 240GB SSD
HDD2:WD Black 1TB
HDD3:WD Se 1TB
HDD4:WD Se 4TB
HDD5:Seagate Constellation SE 750GB
ODD:LG BH12LS38 Bluray writer


Anyone got any bright ideas on wtf is up with this as I'm at the end of my tether with it now.

 

[Kei]

Last part that I can test is the GPU so I've pulled my pc apart, stripped the gpu of it's water block and moved it to the spare AMD 8320/990FX pc which it is now working in. So far no problems running heaven and valley for a few hours. It's a bit toasty at 78-80 degrees but working fine.

I'm putting the gpu from the AMD system into mine, which is quite a step down from a GTX 780 to an HD 6850.

 

[ubersonic]

Are you certain you had the exact same issue before 1607? Because what your describing sounds exactly like the design flaw/bug introduced in 1607 (which is most prominent on ASUS X79 boards with Nvidia GPUs), the fix is usually to install 1511 and block 1607 but if you were getting the issue before it can't be that then :S

May be worth checking this thread anyway: https://forums.geforce.com/default/...uild-1607-randomly-black-screens-nvlddmkm-/1/

 

[Kei]

Sadly yes it has always done this since moving to windows 10. It was a lot less frequent prior to 1607 but it still occurred. I'm already a member on there and have posted in that very thread regarding this problem. No solutions have come of it yet.

So far the 780 has been working flat out playing fallout 4 all day in the amd system without a single problem. (fallout 4 being one of the worst for crashing the intel system) I've literally just got my intel pc back up and running with the HD 6850 in it so no idea yet if it behaves itself yet.

 

[Kei]

Well a month down the road and both systems worked perfectly with the gpus swapped around. Creators update applied and a suggestion that intel virtualisation might cause the problem, I put the 780 back into the x79 machine and managed to get about 5 hours or so out of it before it was back to it's usual tricks.

Not sure what to do with it now as I'm really tired of it. A new gpu looks like it'll have to be amd only and they are dragging their heels bringing vega out. A new cpu will be expensive due to the need for a new motherboard, ram and block bracket. Cheap solution looks like I'll have to swap my 4820K/x79 guts out for the spare 8320/990FX parts.

 

[Kei]

Scratch that, I found out that there are two flags for virtualization in the bios on my asus board. I'm guessing VT-x and VT-d, but one is in one sub section and the other in a different one, hence why I missed it. Since disabling both flags, I've not had an issue. It's not had enough time for me to say it's fixed yet but its the longest I've managed to get out of it in ages.

 

[Kei]

Just to keep this up to date, it seems that the problem is down to intel VT-d. I've not had a single TDR issue since disabling it.