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

124 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2015-09-02T20:21:29+00:00

    I just spoke to MS about this issue since I was not able to use the MS Display Adapter after updating to the newest driver.  They had me roll back to the one that is causing the BSOD errors and did acknowledge that the new driver has issue with wireless display that the older one did not have.  They said that I could either go to the new driver and not use my wireless display or roll back to the 4248 version and live with the BSOD issues until it can be resolved by Intel.

    No really the answer I was looking for!

    Regards,

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2015-09-02T19:58:56+00:00

    This same error occurs on an I5-4300 4GB Surface Pro 3 system. Rolling back to the 6/29/2015 (v10.18.15.4248) driver solves it for me. My trouble comes from a random reboot that takes out my system and my VMWare session. System flickers a few times, then cold starts to BSOD with above-named error. I am using the docking station and an external monitor.

    ...and it would be Really Nice if I could tell Windows 10 to NOT UPDATE THE DRIVER UNTIL I SAY IT'S OK TO DO SO!

    This new "Nanny" update is a Real Pain! Some of us actually *DO* know what we are doing and can handle the update process quite nicely. Now, with this imposed system, I have to roll it back every time I start the machine because of the "automatic" update!

    Intel/Microsoft *REALLY* needs to fix this!

    And I could wish that MS would fix the docking station keyboard/mouse disconnect problem as well (first start up keyboard and mouse do not connect - must cold start machine a second time to connect).

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-09-02T09:40:03+00:00

    I am also experiencing this random 'full system crash' error after upgrading to Windows 10 Pro  using a Surface Pro3 i7-4650U with the Intel HD Graphics 5000, and a single monitor attached via a Surface Pro3 docking station.  Resolution of the external monitor is set at the default recommended 2560x1440 resolution.

    Unfortunately there is no other Intel HD Graphics 5000 driver to roll-back (option greyed out) , as  the Intel driver version 10.18.15.4248 is that which came installed with Windows 10.

    This is a nasty error for Microsoft customers to encounter several times each day.

    Exactly the same issue here!

    IS ANYONE AT MICROSOFT READING THIS?

    It has to be fixed asap, we are using a Microsoft software on a Microsoft hardware!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-09-01T11:23:01+00:00

    We have 2 Surface Pro 3 machines and 1 Surface  Pro. None have external monitors attached. The Pro 3 machines are in docking stations. All were upgraded to Windows 10 from 8.1. All have the latest updates applied.

    The problem only happens on one of the Pro 3 machines. On that machine it happens about once a day.

    Please fix this.

    Thanks!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2015-08-31T23:29:22+00:00

    there have been a lot of issues with recent NVIDIA drivers, new one out again today

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments