bluescreen video_tdr_failure igdkmd64.sys after update from windows 8.1 to windows 10 on intel hd graphics 4600

[BEhrl]

Yesterday i updated my gaming notebook from windows 8.1 to windows 10. Overall it works fine but i got now 2 times a bluescreen telling me video_tdr_failure and igdkmd64.sys which as far as i knows means a problem with my intel hd graphics 4600.

Anyone has any idea how to solve this?

When i try to search for an update it tells me i have the knewest but the intel homepage says the newest is 15.xxxx which i cant download cause it tells me error:page not found and the driver is english while i have german drivers

[APalm4]

I am having the same problem. I made a post about it yesterday but so far nobody has answered.

[idata]

I also have the same problem. I've tried all the drivers from intel and solve this problem. Meanwhile comeback win at 7 before it tunes.

[Allan_J_Intel1]

All:

This information is intended to all Windows 10 users that are experiencing issues with a supported Intel® Graphics Controller (http://www.intel.com/support/graphics/sb/CS-034343.htm supported graphics)

/message/321854# 321854 Re: -NEW- Intel® Iris™, Iris™ Pro, and HD Graphics Production Driver for Windows* 10 64-bit 15.40.4.64.4256

See post # 93

Allan.

[TLund2]

I have full update my Intel HD 4600 to win 10 64 bit drivers and still get the problem

[idata]

Neither version of 4279 does not solve the problem. Only blue death does not occur, but a window appears that the driver was restarted.

[gbhj]

if you still have the memory dump (c:/windows/memory.dmp) you can use windbg to post more info about the cause of the crash

http://www.instructables.com/id/How-to-Analyze-a-BSOD-Crash-Dump/?ALLSTEPS How to Analyze a BSOD Crash Dump

[idata]

I'm back to win7

[JHeym1]

Since nobody has done a dump analysis, here is mine. Please let me know if this helps.

Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!560CA418852000 )

Followup: MachineOwner

---------************* Symbol Path validation summary **************Response Time (ms) LocationDeferred 1.SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols http://msdl.microsoft.com/download/symbols0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************

VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: ffffe001a0801010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff80053f06560, The pointer into responsible device driver module (e.g. owner tag).Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.Arg4: 000000000000000d, Optional internal context dependent data.

Debugging Details:

------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************

*** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Either you specified an unqualified symbol, or your debugger ****** doesn't have full symbol information. Unqualified symbol ****** resolution is turned off by default. Please either specify a ****** fully qualified symbol module!symbolname, or enable resolution ****** of unqualified symbols by typing ".symopt- 100". Note that ****** enabling unqualified symbol resolution with network symbol ****** server shares in the symbol path may cause the debugger to ****** appear to hang for long periods of time when an incorrect ****** symbol name is typed or the network symbol server is down. ****** ****** For some commands to work properly, your symbol path ****** must point to .pdb files that have full type information...

[Allan_J_Intel1]

I have been using Windows(R) 10 for a while on Intel® HD Graphics 4600, I have received this message couple of times so far, but nothing to worry about, I just ended up restarting the computer and the machine kept working properly. I am currently running the latest video drivers version 4300 https://downloadcenter.intel.com/download/25484/Intel-Graphics-Driver-for-Windows-7-8-1-10-15-40- Download Intel® Graphics Driver for Windows® 7/8.1/10* [15.40]

Allan.

[PSton2]

Hi Allan, a couple of Blue Screens might be OK with you but I get them at least 4 or 5 times a day. It is mostly when I am using graphics intensive programs like AutoCAD. This Windows 10 issue has remained unresolved for too long please please don't sweep it under the carpet - fix the problem!

[Allan_J_Intel1]

This driver crashing issue has been escalated to our engineering team, we are just waiting for any update on this matter. I still do not have an estimate time of resolution but I will come back as soon as possible.

Allan.

[PSton2]

Hi Allan,

thank you for escalating the issue.

here are the details of my system and graphics for your engineering team's reference;

[TLund2]

I have full update my Intel HD 4600 to win 10 64 bit drivers and still get the problem

[HIkhs]

i'm having the same problem here. my device is ASUS X450 JF

the problem begins when i'm playing a game and suddenly gray grains appears on the screen and then BSOD with video_tdr_failure.

After that i couldn't enter normal windows mode because the screen freezes and grainy, i tried entering safe mode via cmd from installation disk and uninstalled the driver from device manager and restarted it. now i can enter the normal mode, however after trying to install intel graphics driver the problem still persists until now. I tried to install driver from intel driver update app with newest driver , the same. tried to install driver that's given from their website ( total of 4 different driver ) still the problem persists, and now the BSOD occurs in the middle of installing the graphic driver. every single time. i wonder is this a hardware problem? because i tried using win 10 and win 8 , still the same problem existed.

BTW, i'll post my dump files later, still trying to crack this problem before taking it to service center\

thanks

[idata]

As I wrote earlier. When you quit the game World of tanks information window will pop up.

It will happen just by accident once in a while.

Even more information for you. In Windows 7, the problem is not. This problem is only after upgrading to Windows 10. If I return back to 7 problem again is not. This means that the problem is associated with win10.

/servlet/JiveServlet/showImage/2-359486-248954/intelproblem.jpg

Intel(R) HD Graphics 4600

Datum zprávy: 14. prosince 2015

Čas zprávy [hh:mm:ss]: 8:35:52

Verze ovladače: 20.19.15.4326

Operační systém: Windows* 10 Pro (10.0.10586)

Výchozí jazyk: Czech (Czech Republic)

Fyzická paměť: 8108 MB

ID dodavatele: 8086

ID zařízení: 0416

Revize zařízení: 06

BIOS grafického adaptéru: 1035.0

Aktuální rozlišení: 1920 x 1080

Procesor: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz

Rychlost procesoru: 2494 MHz

Používaná procesorová grafika: Intel(R) HD Graphics 4600

Verze shaderu: 5.0

Verze rozhraní OpenGL*: 4.3

Verze rozhraní OpenCL*: 1.2

* Microsoft DirectX* *

Verze modulu runtime: 12.0

Verze podporovaná hardwarem: 11.1

* Zařízení připojená ke grafickému akcelerátoru *

Aktivní displeje: 1

* Integrovaný displej *

Typ displeje: Digitální

Protokol DDC2: Podporováno

Gamma: 2,2

Typ konektoru: Integrované rozhraní DisplayPort

Typ zařízení: Integrovaný displej

Maximální velikost obrazu

Šířka: 13,39 palců

Výška: 7,48 palců

Podporované režimy

1920 x 1080 (60p Hz)

Nezpracovaná data EDID:

00 FF FF FF FF FF FF 00 0D AE C4 15 00 00 00 00

28 17 01 04 95 22 13 78 02 EF 05 90 54 52 93 29

25 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01

01 01 01 01 01 01 5E 35 80 96 70 38 14 40 2C 1C

24 00 58 C1 10 00 00 18 00 00 00 FE 00 4E 31 35

36 48 47 45 2D 45 41 42 0A 20 00 00 00 FE 00 43

<p style="font-size: 13px; font-family: intel-clear, arial, helvetica, 'helvetic...

[Allan_J_Intel1]

Intel is currently investigating the issue and the engineering team is working towards a resolution. I will update this thread when I get additional information.

Allan.