Intel Display driver crash GRAPHICS_DRIVER_TDR_FAULT

Discussion in 'Windows 10 on Surface Pro 3' started by ptr727, Aug 17, 2015.

  1. ptr727

    ptr727 New Member

    Joined:
    Aug 4, 2015
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    SPro3
    Was working today, the screen turned black, mouse cursor disappeared, reappeared, then BSOD in the Intel graphic driver.

    Known problem, any solutions?

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: ffffe00101b26170, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8012e2165e0, 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:
    ------------------


    SYSTEM_SKU: Surface_Pro_3

    SYSTEM_VERSION: 1

    BIOS_DATE: 06/05/2015

    BASEBOARD_PRODUCT: Surface Pro 3

    BASEBOARD_VERSION: 1

    BUGCHECK_P1: ffffe00101b26170

    BUGCHECK_P2: fffff8012e2165e0

    BUGCHECK_P3: 0

    BUGCHECK_P4: d

    FAULTING_IP:
    igdkmd64+165e0
    fffff801`2e2165e0 4055 push rbp

    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

    CPU_COUNT: 4

    CPU_MHZ: 8f7

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 45

    CPU_STEPPING: 1

    BUGCHECK_STR: 0x116

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ANALYSIS_VERSION: 10.0.10240.9 amd64fre

    STACK_TEXT:
    ffffd000`b4776708 fffff801`2ba22a8c : 00000000`00000116 ffffe001`01b26170 fffff801`2e2165e0 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`b4776710 fffff801`2ba22223 : fffff801`2e2165e0 ffffe001`01b26170 ffffd000`b47767e9 00000000`000000f4 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    ffffd000`b4776750 fffff801`2c77e481 : ffffe001`01b26170 ffffd000`b47767e9 00000000`00725496 ffffd000`b4776960 : dxgkrnl!TdrIsRecoveryRequired+0x193
    ffffd000`b4776780 fffff801`2c7da0e1 : 00000000`00000000 ffffd000`b4776920 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiReportHwHang+0x3fd
    ffffd000`b4776850 fffff801`2c7d79ee : ffffe001`09124000 ffffd000`00000102 ffffd000`b4776b00 00000000`00000004 : dxgmms2!VidSchWaitForCompletionEvent+0x441
    ffffd000`b47768e0 fffff801`2c775fa7 : ffffe001`09126000 00000000`00000000 ffffe001`09126790 ffffe001`09124810 : dxgmms2!VidSchiWaitForCompletePreemption+0x7e
    ffffd000`b47769d0 fffff801`2c76cbf5 : ffffe001`09126000 ffffe001`09126000 00000000`00000004 ffffe001`0105fc40 : dxgmms2!VidSchiCompletePreemption+0x13
    ffffd000`b4776a00 fffff801`2c7a3403 : ffffe001`09126000 ffffd000`b4776bc8 ffffe001`0fbd10f0 ffffe001`00000000 : dxgmms2!VidSchiScheduleCommandToRun+0x7285
    ffffd000`b4776b90 fffff801`2c7a33e0 : ffffe001`09126000 ffffe001`09126000 ffffe000`fc5d2780 fffff803`3d462740 : dxgmms2!VidSchiRun_PriorityTable+0x1f
    ffffd000`b4776bc0 fffff803`3d16f948 : ffffe000`fc5d2780 ffffd000`b4776c90 fffff803`3d3ec180 fffff803`3d1dbd10 : dxgmms2!VidSchiWorkerThread+0x80
    ffffd000`b4776c00 fffff803`3d1dbde6 : fffff803`3d3ec180 ffffe001`090e4280 fffff803`3d462740 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`b4776c60 00000000`00000000 : ffffd000`b4777000 ffffd000`b4771000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    igdkmd64+165e0
    fffff801`2e2165e0 4055 push rbp

    SYMBOL_NAME: igdkmd64+165e0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: igdkmd64

    IMAGE_NAME: igdkmd64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5591ec5d

    FAILURE_BUCKET_ID: 0x116_IMAGE_igdkmd64.sys

    BUCKET_ID: 0x116_IMAGE_igdkmd64.sys

    PRIMARY_PROBLEM_CLASS: 0x116_IMAGE_igdkmd64.sys

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x116_image_igdkmd64.sys

    FAILURE_ID_HASH: {2dd455a7-a731-ffcb-c3fd-14ce7783fc02}

    Followup: MachineOwner
    ---------
     
  2. leeshor

    leeshor Well-Known Member

    Joined:
    Jun 19, 2012
    Messages:
    5,071
    Likes Received:
    877
    Trophy Points:
    113
    Location:
    Norcross, GA
    My Device:
    SPro4
    Did this only happen once?

    How long have you been using it since the last restart?
     
  3. ptr727

    ptr727 New Member

    Joined:
    Aug 4, 2015
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    SPro3
    Only BSOD that I know of.

    I never manually restart, just let it sleep, only time it restarts is when windows update restarts it or when I install software that insists on restarting, probably been on for a week or so. I did notice that after the BSOD it installed updates while rebooting.
     
  4. leeshor

    leeshor Well-Known Member

    Joined:
    Jun 19, 2012
    Messages:
    5,071
    Likes Received:
    877
    Trophy Points:
    113
    Location:
    Norcross, GA
    My Device:
    SPro4
    You should restart at least once a week. I'm guessing that was a fluke from not having been restarted.
     

Share This Page

Search tags for this page

5591ec5d

,

bugcheck 0x7e surface pro 4 herbanation

,

intel hd graphics driver causing video tdr failure

,

onenote 2016 disappear

,

surface pro 3 intel video crashes on windows 10

,

surface pro 4 graphics crash

,

surface pro 4 graphics driver crash

,

surface pro 4 video tdr crash

,

tdr crash surface pro

,

windows 10 surface pro 3 video tdr failure