topic Re: bluescreen video_tdr_failure igdkmd64.sys after update from windows 8.1 to windows 10 on intel hd graphics 4600 in Graphics

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

BEhrl — Sat, 08 Aug 2015 15:03:12 GMT

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

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

APalm4 — Sat, 08 Aug 2015 15:07:51 GMT

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

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

idata — Mon, 10 Aug 2015 20:18:12 GMT

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.

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

Allan_J_Intel1 — Thu, 13 Aug 2015 16:33:14 GMT

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.

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

idata — Mon, 14 Sep 2015 16:13:16 GMT

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

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

gbhj — Mon, 14 Sep 2015 23:01:19 GMT

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

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

idata — Fri, 25 Sep 2015 17:22:35 GMT

I'm back to win7

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

TLund2 — Fri, 25 Sep 2015 17:43:32 GMT

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

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

TLund2 — Fri, 25 Sep 2015 17:44:01 GMT

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

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

JHeym1 — Fri, 06 Nov 2015 17:00:58 GMT

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) Location

Deferred 1.SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols http://msdl.microsoft.com/download/symbols

0: 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 ***