1 2 Previous Next 16 Replies Latest reply on Dec 15, 2015 9:14 AM by allan_intel

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

    Portoa

      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

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

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

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

            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.

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

              All:

               

              This information is intended to all Windows 10 users that are experiencing issues with a supported Intel® Graphics Controller (supported graphics)

               

              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.

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

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

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

                  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

                  How to Analyze a BSOD Crash Dump

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

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

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

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

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

                        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
                        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                                     ***
                        ***                                                                   ***
                        *************************************************************************
                        *************************************************************************
                        ***                                                                   ***
                        ***                                                                   ***
                        ***    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.      ***
                        ***                                                                   ***
                        ***    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.      ***
                        ***                                                                   ***
                        ***    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.      ***
                        ***                                                                   ***
                        ***    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.      ***
                        ***                                                                   ***
                        ***    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!_KPCR                                      ***
                        ***                                                                   ***
                        *************************************************************************
                        *************************************************************************
                        ***                                                                   ***
                        ***                                                                   ***
                        ***    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!_KTHREAD                                   ***
                        ***                                                                   ***
                        *************************************************************************
                        *************************************************************************
                        ***                                                                   ***
                        ***                                                                   ***
                        ***    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                                     ***
                        ***                                                                   ***
                        *************************************************************************

                        SYSTEM_SKU:  Aspire SW5-171P_0930_1.04

                        SYSTEM_VERSION:  V1.04

                        BIOS_DATE:  11/7/2014

                        BASEBOARD_PRODUCT:  Longchamp_S

                        BASEBOARD_VERSION:  V1.04

                        ADDITIONAL_DEBUG_TEXT: 
                        You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

                        WRONG_SYMBOLS_TIMESTAMP: 560ca418

                        WRONG_SYMBOLS_SIZE: 852000

                        FAULTING_MODULE: fffff800a8e16000 nt

                        DEBUG_FLR_IMAGE_TIMESTAMP:  560ca418

                        BUGCHECK_P1: ffffe001a0801010

                        BUGCHECK_P2: fffff80053f06560

                        BUGCHECK_P3: 0

                        BUGCHECK_P4: d

                        FAULTING_IP:
                        igdkmd64+16560
                        fffff800`53f06560 4055            push    rbp

                        CPU_COUNT: 4

                        CPU_MHZ: 63c

                        CPU_VENDOR:  GenuineIntel

                        CPU_FAMILY: 6

                        CPU_MODEL: 45

                        CPU_STEPPING: 1

                        CURRENT_IRQL:  0

                        ANALYSIS_VERSION: 10.0.10240.9 x86fre

                        STACK_TEXT: 
                        ffffd000`203d27c8 fffff800`52d7160c : 00000000`00000116 ffffe001`a0801010 fffff800`53f06560 00000000`00000000 : nt!KeBugCheckEx
                        ffffd000`203d27d0 fffff800`52d70da3 : fffff800`53f06560 ffffe001`a0801010 ffffd000`203d28a9 00000000`000000b7 : dxgkrnl+0x14160c
                        ffffd000`203d2810 fffff800`555ae481 : ffffe001`a0801010 ffffd000`203d28a9 00000000`0032fa08 00000000`00000002 : dxgkrnl+0x140da3
                        ffffd000`203d2840 fffff800`555db13c : ffffe001`991ea000 00000000`00000002 ffffe001`991ea000 ffffe001`991ec000 : dxgmms2+0x1e481
                        ffffd000`203d2910 fffff800`555c7955 : 00000000`00000002 00000000`00dd6577 00000000`00000001 fffff800`00000000 : dxgmms2+0x4b13c
                        ffffd000`203d2950 fffff800`55595c9d : 00000000`00000000 ffffe001`991ec000 ffffd000`203d2b00 00000000`00000000 : dxgmms2+0x37955
                        ffffd000`203d2a00 fffff800`555d3463 : ffffe001`991ec000 ffffd000`203d2bc8 ffffe001`9942b2b0 ffffe001`00000000 : dxgmms2+0x5c9d
                        ffffd000`203d2b90 fffff800`555d3440 : ffffe001`991ec000 ffffe001`991ec000 ffffe001`948a5780 ffffd000`204f9bc0 : dxgmms2+0x43463
                        ffffd000`203d2bc0 fffff800`a8efc558 : ffffe001`948a5780 ffffd000`203d2c90 ffffd000`204ed180 fffff800`a8f692f0 : dxgmms2+0x43440
                        ffffd000`203d2c00 fffff800`a8f693c6 : ffffd000`204ed180 ffffe001`991f8800 ffffd000`204f9bc0 9ca07283`7b771d34 : nt!PsGetProcessSectionBaseAddress+0xe60
                        ffffd000`203d2c60 00000000`00000000 : ffffd000`203d3000 ffffd000`203cd000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x4496


                        STACK_COMMAND:  kb

                        FOLLOWUP_IP:
                        igdkmd64+16560
                        fffff800`53f06560 4055            push    rbp

                        FOLLOWUP_NAME:  MachineOwner

                        BUGCHECK_STR:  560CA418

                        EXCEPTION_CODE: (NTSTATUS) 0x560ca418 - <Unable to get error code text>

                        FAILURE_EXCEPTION_CODE:  560CA418

                        EXCEPTION_STR:  WRONG_SYMBOLS

                        IMAGE_NAME:  ntoskrnl.wrong.symbols.exe

                        MODULE_NAME: nt_wrong_symbols

                        SYMBOL_NAME:  nt_wrong_symbols!560CA418852000

                        BUCKET_ID:  WRONG_SYMBOLS_X64_10240.16545.amd64fre.th1.150930-1750_TIMESTAMP_151001-031016

                        DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X64_10240.16545.amd64fre.th1.150930-1750_TIMESTAMP_151001-031016

                        PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS

                        FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_10240.16545.amd64fre.th1.150930-1750_TIMESTAMP_151001-031016_560CA418_nt_wrong_symbols!560CA418852000

                        ANALYSIS_SOURCE:  KM

                        FAILURE_ID_HASH_STRING:  km:wrong_symbols_x64_10240.16545.amd64fre.th1.150930-1750_timestamp_151001-031016_560ca418_nt_wrong_symbols!560ca418852000

                        FAILURE_ID_HASH:  {4d14db82-2492-9436-0743-b8cea166c9c1}

                        Followup:     MachineOwner
                        ---------

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

                          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 Download Intel® Graphics Driver for Windows® 7/8.1/10* [15.40]

                           

                          Allan.

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

                            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!

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

                              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.

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

                                Hi Allan,

                                thank you for escalating the issue.

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

                                Lenovo System information.JPG

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

                                  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

                                  1 2 Previous Next