video dxgkrnl fatal error

anchyka

Honorable
Jan 25, 2014
1
0
10,510
I recive this blue screen after i turn on the computer. and before i closed it the day before i played the game (tomb rider). It also started to happen after i installed tomb rider i guess and previously i had problems with sims 3 because it wouldn't work and i couldn't figure out why so i reinstalled it a couple of times as i found out i should only change compatibility settings. I also becaouse of that thought and upgraded some drivers that the dell site offered me (i have dell inspiron 5537, 8 gb ram and radeon hd 8850m-i have a laptop). Idk what to do please help:(
if you need aditional dettails i will add them
 

anchyka1

Honorable
Nov 8, 2013
2
0
10,510

actually i did...i did a system restore.. google it up it's not hard. The reason why it happend was probably because i don't know why i thought that directx was missing so i installed it. I guess it somehow ''argued with the original'' :) I suggest you not to install unecesary drivers though because maybe you did one too much and it screws up the computer:/
hope this helps:)
P.S:: i tried to find other ways to do it because i was afraid to lose my saved games but it doesn't affect anything maybe just unninstalls it but saves remain after you redownload:)
 

Traveljack2014

Reputable
Jul 5, 2014
1
0
4,510
I installed win 8.1 on a Acer Aspire E1-572G and got the screen after the most recent update. From Acer's download page I got the right VGA drivers and intalled those (got a warning that the ones installed were more recent and ignored it).
After this instalment, the laptop worked without any further problems.
 
Jul 18, 2014
2
0
4,510


 

kermdawg

Distinguished
Apr 16, 2013
48
0
18,530
***Scroll down for TL;DR version at end of post*****
Hi there. I've been posting this on a couple threads on a couple differant websites in an effort to help anyone who might have ran into this problem. I can't say it WILL work for you, but it DID work for me and I havn't seen it posted anywhere else.

Long story short-Computer started randomly rebooting and eventually would fail to post. I replaced my mainboard thinking I had a bad motherboard(which turned out not to be the case). Replaced PSU-which got me to boot. Finally changed out memory-turned out memtest would crash in less than 5 minutes with one particular module of a 2x8gb set. Memory RMA'd and backup memory from previous build(1x4gb DIMM of 1600mhz kingston with samsung memory chips) was installed.

This got me to where I could boot into windows and install my stuff. I ran prime 95 for 24hours on torture test to ensure CPU was good, along with a couple other benchmarks. Cpu is still good.

I would run boinc-seti at 95% gpu usage. Gpu check. Note I think this is a good test to try and locate HARDWARE issues-if the GPU is bad you'll notice it OUTSIDE of 3d programs as well as gaming.

GPU is a gigabyte GTX970-G1 gaming edition, approx 4 months old, at stock clock settings with latest nvidia drivers downloaded from nvidia website.

Anyway, upon trying to run World of Warcraft, or ANY other 3d program, my computer would blank screen and reboot, seemingly ALWAYS at the same time-approximately 5 minutes in, give or take a few seconds. I think this is clue number 1, as it allowed me to replicate the circumstances pretty consistantly.

I tried uninstalling, rebooting, and reinstalling my graphics drivers. No luck there. I flashed my bios to latest version on my ASUS p8z77-v LK motherboard(remember, this is a fresh board with stock settings) and installed intel chipset drivrers and ME. No luck.

I tried reinstalling windows 7 and reupdating all software. No luck. Ran the sfc /scannow, everything was fine. Redownloaded directx, and reinstalled. Everything was good on their end. Of course ran windows update 10 times(I've seen it asked before, but can we PLEASE get a SP2 release?) Still not working.

I was really pulling my hair out, I registered with gigabyte and prepared all my RMA information, and on one last ditch effort, I thought "Hmm, maybe the motherboard is defective". Stranger things have happened...i was reasonably sure the graphics card was good as I'd been playing with it for 4 months, but the motherboard was fresh out of the box, and could contain a manufacturing defect like a bad PCI-E socket, or even a bad trace somewhere.

I had a GTX 650 from a previous build laying around and decided to swap that in while I sent my GTX 970 back in for RMA. Then I thought I'd test the 650 to see if the same thing happened with a differant graphics card. Duh, right? Should have thought of this hours ago...

Sure enough I installed my 650, windows reverted to standard vga driver, and i reinstalled the geforce drivers. Ran furmark. Perfect. Ran WoW. Perfect.

I was really bummed cause I thought my GTX 970 was bad. But then I thought, hell let me swap it back in because that will confirm it.

I reinstalled my GTX 970, windows installed the standard driver again. Updated to GTX 970. Ran furmark and held my breath. It worked perfectly. Let it run all night. Ran WoW. Worked perfectly.

Problem solved.

I can't say this WILL work for you, but the problem definately appeared to be on the windows side of things.

TL;DR version-
Possible causes of the problem-
1)bad seat/motherboard(unlikely in my case as the GPU would run for hours at 95% utilization outside of 3d settings)
2)Something on window's end/direct x. Im not a tech guru but I have been working on computers for 20+ years. I have loved windows 7 and have never had a serious problem until the last month. Very possible one of the updates screwed something up.
3)Something on Nvidia's end. As I've read through dozens of forum posts with AMD users that had the same problem, I dont think this is the case.

Once again, the TL;DR solution for me-
Uninstall "bad" graphics card
install a known good graphics card
reboot windows and let it install default graphics driver, reinstall nvidia graphics card driver
(I tested here to see if there was any differance, and I'd advise you do the same to rule out the previous graphics card being defective)
uninstall known good graphics card and reinstall "bad" graphics card
reboot, reinstall nvidia graphics driver
play game/run benchmark to test

If you dont have a spare GPU laying around you might even consider buying a cheap one from a retailer, as you can get a cheap previous generation GPU for around 20 dollars, and it might be nice to have around for future diagnostice purposes. And yes I did try to just reseat the 970, but that won't cause windows to reinstall the drivers on it's side.

However, something I did not test is removing the GPU completely and booting into windows with the integrated graphics. You might try that if you do not have a spare GPU but I did not test it and cant comment on any results.

I hope this information helps somebody as this seems to be a problem without a very definitive solution. Windows is pretty good at fixing itself if we know how to manipulate it to do so from my experience. If all the other methods on this site and others fail you, I would try this as a last resort after confirming with sfc /scannow and dxdiag that your system files are all good and making sure you have the latest drivers from AMD/Nvidia, as well as running windows update and updating your bios/chipset drivers.

Above all, good luck guys!
 

T1B3R1US

Reputable
Apr 29, 2015
3
0
4,510


 

T1B3R1US

Reputable
Apr 29, 2015
3
0
4,510
ok i've had the same problem with my DELL Latitude 3540 wich has the same graphic card AMD Radeon HD 8850m
here is the solution:How to fix Windows 8.1 Blue Screen problem 'Your PC ran into a problem and needs to restart' having technical error code KMODE_EXCEPTION_NOT_HANDLED (dxgkrnl.sys) : Open 'Driver Verifier Manager' and see the existing settings. If you have enabled test type 'Randomized low resources simulation' to verify the driver 'dxgkrnl.sys', then you will get this blue screen problem 'Your PC ran into a problem' with technical code 'Kernel mode exception not handled'.
Solution: Delete the existing settings from the driver verifier manager and restart the computer.
Bugcheck Analysis:
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled.
Arg2: 8ae48097, The address that the exception occurred at
Faulting module: dxgkrnl.sys
 

xavierman232

Reputable
May 16, 2015
1
0
4,510
https://support.microsoft.com/kb/2990029/en-us

This solved my problem with the video dxgkrnl fatal error.

Hope it helps! :)
This also fixed my problem. I had a terrible experience when my intel display driver was updated by mistake. Even after 3 windows 8.1 reset, the computer would still use faulty drivers when booting. Also, to install the fixed mentionned above, the two graphic adapters must be connected and pilot installed. If not, the fix doesnt run. This problem caused my Radeon r9 m265x to disconnect and reconnect and also some kind of electrical malfunction that caused my bios to not boot 1/3 of the time. I opened the computer as much as I could without removing warranty, and I made sure that the gpu was still in good shape, ( just touched the gpu screws with my finger). And then I closed off the laptop and tested it. from there I was able to apply the fix and everything is fine. I was having dxmgrkrnl fatal error at boot and sometimes during windows restart. 0x113 error code.
Hope you can use this info to know if your problem is software or hardware. I was about to give up when I fixed it.