dxgkrnl.sys causing random "black screens" and restart

Associate
Joined
17 Jan 2014
Posts
19
Location
The GRID
Hi all,

since few days I started to have random black screens followed by PC restarts (no BSOD).
I have this PC since December 2013, never had a problem before.
1-2 weeks ago I started to have few black screens and restarts, always the same errors in the dump linked (1-2 per day). In the last few days the amount of restarts increased a lot, during gaming, browsing any kind of activity (5-6 in less than 3-4 hours).

Checking Windows event Viewer, I found that the system was recording critical issues after all, and I started saving mini dump files, please find the most recent ones here:
Code:

http://speedy.sh/HmcUK/PC-issues-dump-files.rar

The error codes are always consistent:
0x00000116
Caused By Driver: dxgkrnl.sys

What I tried so far and didn't work:
- several uninstall and install of different Nvidia drivers versions
- updated directx
- cleaned windows registry
- Windows 8.1 "Refresh your PC" via Windows installation disc
- Updated BIOS Mobo
- Disabled "Internal graphics in BIOS"
- Selected in BIOS PCIE g3 for both GPUs
- Checked for GPUs BIOS updates (latest version available already applied)

My System:
2nd GPU ( SLI SYSTEM): MSI GeForce GTX 780 GAMING - 3GB - PCI-E
Processor CPU: Intel Core i7-4770K - 3.5GHz - Socket 1150 - Unlocked
Motherboard: ASUS Maximus VI Formula - Socket 1150 - ATX
SSD: Samsung 840 Pro Series 512GB
Bluray DVD: Asus BW-16D1HT 16x Blu Ray burner
CASE: CORSAIR Obsidian Series 550D PC Tower (CC-9011015-WW)
CPU WATERCOOLING: CORSAIR Hydro Series H100i watercooling system
RAM: CORSAIR 2 x 8 GB DDR3-1866 PC3-15000 CL9 Dominator Platinum PC Memory Modules (CMD16GX3M2A1866C9)
Powersupply: CORSAIR AX860i - Power supply ( internal )
H100i fan replacements: Prolimatech Ultra Sleek Vortex - 120mm x 2
Extra case fans and repl.: Corsair SP120 Performance Series High Pressure - Dual Pack (CO-9050008-WW) x 3 (6 fans in total)
FAN CONTROLLER : AeroCool V12XT 4-Channel LCD Touch Panel Fan Controller
SOUND CARD: Asus Xonar Essence STX Sound Card

NO OVERCLOCK

Please help me, because I really don't know what to do!
:confused::eek:

Thank you very much in advance!
 
I fear that we are dealing with an hardware issue, my main suspects are (in hierarchical order):

1) one of the GPU faulty ( I already had to RMA one of them because of a faulty FAN/dissipator issue), so I have 2 that are pretty much new (less than 2 months). One comes from OC.UK.

2) when cleaning the PC I dropped the SLI bridge, could be that?

3) The FAN Controller AeroCool V12XT 4-Channel LCD Touch Panel, works fine and I'm happy with it but when I installed I had to really squeeze in the power connector. Could be some faulty power issue that triggers restarts?

4) PSU faulty? I don't even want to consider this yet... because if true I'm very unlucky!!!

5) PSU not enough? Omg....

I'm going nuts! I hate when this kind of stuff happens... massive amount of time wasted in troubleshooting.

Thank you again for your help.
 
i may be wrong but also your PSU is cutting it close running all that, each of your GPU's can draw as much as 350W each under load, thats before you talk about wattage drawn from your CPU, MOBO etc then your cpu cooler, fans, fan controller, someone with better knowledge than myself will probably know better
 
Well after hours of hardware testing, me and a friend of mine realized that was a driver issue after all.
The latest nvidia drivers (334.89) don't like much SLI and Surround video systems.
A rollback attempt went very wrong and triggered all the issues described in this discussion.

How we solved:
simply uninstalling completely the 2 GPU in device manager (right click on the device and uninstall). After reboot Win 8.1 will install a default driver from where you can then update to more recent drivers version (I suggest 331.82, only recent drivers that supports properly SLI + surround video).

Don't ask me why but all the normal drivers uninstall process, tools and even a "Win 8.1 refresh" didn't help, only uninstalling the device itself worked.

Never seen such nasty issues with display drivers before...
 
Last edited:
Back
Top Bottom