Windows 10 - VIDEO_TDR_FAILURE igdkmd64.sys

Anonymous
2015-08-05T13:25:39+00:00

Ever since i have upgraded to Windows 10 these failures happen at random times throughout the day. Mostly when i am playing a game but also has happened when watching Netflix. I have checked and updated all of my drivers and everything is up to date. 

Sometimes it says VIDEO_SCHEDULER_INTERNAL_ERROR, this one is not as often. I have looked online and tried almost everything people have said are solutions and nothing works, and there and almost no solved posts for this problem on windows 10 only for 8.1 and 7. The only way I can recreate the problem is by opening Hearthstone, other than that it is completely random and really annoying. 

PLEASE HELP

Windows for home | Windows 10 | Gaming

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

124 answers

Sort by: Oldest
  1. Anonymous
    2015-11-13T22:52:26+00:00

    Uninstall the driver files completely off of your computer. Restart, wait for windows to install the right drivers, and everything should work. (It did for me)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-12-02T09:29:08+00:00

    I have the same problem on a Microsoft Surface Pro 3 i7 running Windows 10 (and an external monitor).

    I've tried all the suggested solutions and still the computer crashes once a day on average.

    I spoke to Microsoft who firstly claim not to know of the problem, then when I point out that over there are 600 people reporting the same problem (on this thread alone), and it's been a known problem since July, the guy admits there is no known fix and sends me the instructions to return to Windows 8.1.

    As another poster has reported, this is Microsoft supplied software running on Microsoft supplied hardware.  If they can't get that to work, what hope for anyone else.....

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-12-02T11:44:22+00:00

    Dear Microsoft,

    I also have a Surface Pro 3 / i5 / 256k / most of the time on a docking station and external Dell 32" monitor set as "second screen only."

    Windows 10 has been running just fine since August 1st.  Today, August 25 - for first time - I got the BSOD with the same error message.  It ran BSOD diagnostics and then rebooted.

    I just checked windows update and there are no new updates available.  So I assume the SP3 is running all the latest drivers while this failure happened.

    Please fix this.  I'm running a pure Microsoft stack - hardware & software.  Please fix this.

    Thanks.

    The hardware is largely made my Intel with a smattering of other parts from other vendors. The CPU is more a system on a chip.

    I have been battling Windows 10 on my tablet and finally yesterday I found a better driver. Still the camera was not working, so I installed a BIOS update, and finally the camera works.

    I am using a HP Stream 7 which uses an Atom CPU but its generally the same as all the other tablets out there.

    I found with HP a large chipset, CPU, GPU and camera driver in on large driver package. Might be an idea to scour Intel's site for a more generic package.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-12-10T02:49:52+00:00

    So any solution? I still with this error, on my acer aspire M5 481PT. clean install of windows 10 pro, everything works fine with disable windows update, but suddenly a error message pops, saying the windows 8 driver has failed (the graphics card is a intel hd 4000),  I didn't give more importance to it, but it keeps poping and after a while it give me a BSOD, with the message in this post.

    after that, the system stars for a little and then give another bsod, now it doesn't even start de system, the mouse shows up and then BSOD with this message.

    I have try everything so far, star in safe mode and go back to older driver, same error. update everything and same error, format completly the C disc and clean install windows 10 pro again, same as first time when it runs good, but now when the driver is installed, the BSOD came back again.

    the only kind of solution is to A) do not install the driver at all, but the pc runs very slow and also cannot sleep, just hibernate. or B) install it, go to safe mode and disable the driver, and the results are the same, not fully functional pc.

    when it works good it was on this driver :VGA_Intel_10.18.10.3304_W81x64_A, download from the acer webpage, but now when I install that one on a clean installation of windows 10 it crashes no matter what.

    when i try to update it goes to the last version and its the same, screen goes black, just the mouse shows up, the sound of a new hardware added sounds a few times and then BSOD.

    I dont think it is a hardware issue because the pc works normally without install the driver, just runs slow.

    Any solution? is my laptop broken? help please :( 

    PD: Sorry for probably really really bad english, im from Chile and im not using any traslator.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-12-10T21:01:34+00:00

    Count me in as one with this problem on a Surface Pro 3 i5/256GB and Windows 10 upgrade from 8.1. One key difference is that I did a clean install of 8.1, then upgraded to 10 to make it as clean as possible.

    Also, I had no problems until I started to play a couple of older games from the mid 2000's. Nothing exciting (KOTOR2, Supreme Commander, etc). But I think there is a definite correlation between the CPU/GPU temp and this BSOD.

    I've also noticed "smaller" issues when doing less graphic's intensive tasks like maximizing/minimizing windows. For example, the screen will freeze and I will get the "your display adapter stopped responding" message. The driver restarts and everything goes back to normal.

    To re-iterate, NONE of these problems happened with 8.1. It's only 10. I'm running the latest update (build 10586) and it's happened twice today alone.

    Was this answer helpful?

    0 comments No comments