BSOD TDR_VIDEO_FAILURE (0x00000116 ffffe000`6aadd350)

Turtle · 28 Aug 2015

Hi,

Recently after upgrading to Windows 10, my Intel HD 4600 randomly decides to freak out due to the mentioned error.

The driver is the latest from Intel.
I have tried numerous other versions (base one from Toshiba from Windows 8, a driver from 2014, and currently the "Windows 10" driver from Intel which all have BSOD'd)
I switched to Balanced mode for my laptop in case High Performance was causing it for whatever reason (that clearly wasn't it either)

BlueScreenView Info:

Code:

The problem seems to be caused by the following file: dxgkrnl.sys

Technical Information:

*** STOP: 0x00000116 (0xffffe0006aadd350, 0xfffff80191186550, 0x0000000000000000, 
0x000000000000000d)

*** dxgkrnl.sys - Address 0xfffff8018cff2a8c base at 0xfffff8018ceb0000 DateStamp 
0x55bebfed

This first occurred while I was using Open Broadcaster Source streaming games and the like, which this has never happened before during this either under Windows 8(.1). I'm just so confused as to how to fix this as nothing I've looked at on Google has helped me. I hope you guys can help.

essenbe · 28 Aug 2015

Hello, Turtle. Welcome to the forums. I will try to help you. These errors particularly with a Laptop with switchable graphics are difficult. So, there will be a lot of trial and error to see if we can determine exactly what is happening. You are getting 3 types of errors. The most common one is

Code:

BugCheck 116, {ffffe0006aadd350, fffff80191186550, 0, d}
Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+16550 )

A stop code 116 is always a graphics driver/card error.


	Code:
	Use !analyze -v to get detailed debugging information.
BugCheck 119, {1, 135a45, 135a47, ffffe0015be86010}
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrCompletedPacket+7abb )
Followup: MachineOwner

Is a Video scheduler Internal error and


	Code:
	Use !analyze -v to get detailed debugging information.
BugCheck 9F, {4, 12c, ffffe000d3b9a800, ffffd0014c2869b0}
Implicit thread is now ffffe000`d3b9a800
Probably caused by : BTHUSB.sys
Followup: MachineOwner

Is a Driver power state Failure.  BTHUSB is the Bluetooth miniport Driver. 
Followup: MachineOwner

If you would please remove any Bluetooth devices and see if that is where some of your problems are coming from.

Next please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.

Turtle · 28 Aug 2015

I will try disconnecting my bluetooth mouse when I get home but I've also already run sfc /scannow and it returned no integrity violations.

essenbe · 28 Aug 2015

Ok, in the same elevated command prompt, please see if you can run this command. Dism /Online /Cleanup-Image /RestoreHealth It can take from 20 minutes to a couple of hours, depending on your machine and what it finds. It will start at 20% and act like it is stuck for a while. Just let it run. It will complete or give you an error message. For some strange reason, not everyone can run it.

Turtle · 28 Aug 2015

Essenbe,

I ran the above prompt in admin and got an all-clear complete.

Attachment 34422

essenbe · 28 Aug 2015

Good job. Not everyone can successfully run that. How often do you get a BSOD? Do you want to wait and see if that fixed the problem or would you like to try something different?

Turtle · 28 Aug 2015

Essenbe,

I get this BSOD randomly. I have no control as to when it occurs. The last one was watching my friend on Twitch playing some games. The ones around the weekend of August 21st were while I streamed game development. If you would like to try something just in case that didn't affect anything, we could. If you could also explain what that command I performed does, that would be great.

essenbe · 28 Aug 2015

What you did was basically a more in depth sfc /scannow. As I understand it, the command scans your system files against the ISO of the system and is supposed to repair/replace any missing/damaged/corrupted system files. It has helped me a couple of times.

The problem we have with Laptops with switchable graphics is usually, they do not switch in time so the system assumes a graphics failure and crashes. We have only found one solution which will, in most cases, solve it. It is not a very desirable solution. So, I was trying to make sure there were no corrupted system files, causing it. The next thing is to check drivers using Driver Verifier. There is the possibility that a clean install would be necessary, if it does not go right. I feel obligated to tell you that. However, we take every precaution to see to it that does not happen and it has never happened to me. What Driver Verifier does is put stress on all 3rd party drivers in order to make them crash, in hopes that the dump file will catch the offending driver. If you decide you want to do that, please let me know and I will give you some instructions on exactly how to do it and what to do beforehand in case it does not go as planned. If you have any questions, please feel free to ask.

Turtle · 28 Aug 2015

Essenbe,

I have heard of the Driver Verification tool and I suppose it would work. In regards to the bluetooth driver, I think that one's from station-drivers.com and is probably 3rd party. I've tried finding the first party driver with no luck which means I'm stuck on the base Windows 8 driver. I also have thought of doing a clean Windows 10 install but if you feel Driver Verifier would be a better idea to try first, I'm all in. I'll be back around 11:30pm EST to read your reply.

essenbe · 28 Aug 2015

Warning

Be sure to create a System Restore point before proceeding further https://www.tenforums.com/tutorials/4...dows-10-a.html

DRIVER VERIFIER
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. See if this might help some. Also, if you want to be extra safe, create a system image before you begin.