Frequent Display Driver Crash/Recover (win10)

Discussion in 'PC Hardware' started by doubtfire, Feb 8, 2017.

  1. doubtfire

    doubtfire MDL Junior Member

    May 26, 2015
    91
    8
    0
    #1 doubtfire, Feb 8, 2017
    Last edited by a moderator: Apr 20, 2017
    My graphics card will have these little hiccups and the screen freezes and my event viewer shows:


    Code:
    Log Name:      SystemSource:        DisplayDate:          2/7/2017 7:18:21 PMEvent ID:      4101Task Category: NoneLevel:         WarningKeywords:      ClassicUser:          N/AComputer:      EricCrateDescription:Display driver amdkmdap stopped responding and has successfully recovered.Event Xml <System>    <Provider Name="Display" />    <EventID Qualifiers="0">4101</EventID>    <Level>3</Level>    <Task>0</Task>    <Keywords>0x80000000000000</Keywords>    <TimeCreated SystemTime="2017-02-08T01:18:21.000000000Z" />    <EventRecordID>23187</EventRecordID>    <Channel>System</Channel>    <Computer>EricCrate</Computer>    <Security />  </System>  <EventData>    <Data>amdkmdap</Data>    <Data>    </Data>  </EventData></Event>
    Hopefully the hardware is not at fault. What troubleshooting steps should I take?
     
  2. Katzenfreund

    Katzenfreund MDL Expert

    Jul 15, 2016
    1,373
    831
    60
    First of all, have you tried updating the driver thru Device Manager?
    If there's no new version there, there might be at the graphic cards's manufacturer site to install manually.
    If no new version is available at all, you can try going back to the previous version, again thru Device Management.

    And you lose nothing by also trying Command Prompt (as Admin) > sfc /scannow
     
  3. doubtfire

    doubtfire MDL Junior Member

    May 26, 2015
    91
    8
    0
    And if the problem persists after that?

    I'm going to run HWiNFO with a high scanning frequency and try to catch any clues in the graph.
     
  4. Katzenfreund

    Katzenfreund MDL Expert

    Jul 15, 2016
    1,373
    831
    60
    Are you asking hypothetically, or you've tried the above without result.

    Try also uninstalling and reinstalling the driver.
    Check your disk and RAM.
     
  5. doubtfire

    doubtfire MDL Junior Member

    May 26, 2015
    91
    8
    0
    chkdsk and memtest86 completed without error (along with your first two suggestions, yes, the latter, tried the above without result)
     
  6. Joe C

    Joe C MDL Guru

    Jan 12, 2012
    3,522
    2,093
    120
    #6 Joe C, Feb 10, 2017
    Last edited: Feb 10, 2017
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. Katzenfreund

    Katzenfreund MDL Expert

    Jul 15, 2016
    1,373
    831
    60
    Yes, if you have indeed done all suggested so far, I'm afraid you seem to have tried the easy fixes and you'll have to go into deeper waters, like uninstalling and reinstallling the driver, and finally reinstalling Windows.

    There's one more easy fix, if you have an old system backup which you can restore. If you don't, now that you've seen their value, start making such backups from time to time. The easiest way is by means of a system drive image.
     
  8. LatinMcG

    LatinMcG Bios Borker

    Feb 27, 2011
    5,711
    1,606
    180
  9. doubtfire

    doubtfire MDL Junior Member

    May 26, 2015
    91
    8
    0
    I'll consider it. Now on a completely unrelated note, does anyone want to buy a perfectly good Radeon 280X for $150? :D

    Yes the next step I will take is to try a clean install of the anniversary update win10 (currently on build 10240) and see if it persists there. If it still does, then it's hardware, and if it's hardware then it could be be the PSU or GPU. The PSU is 6 years old at this point.