Solved

"AMD Display driver stopped responding and recovered successfully" Almost instant crashes on games and benchmarking

I've been having issues with my build and am wondering if anyone has any input regarding my problem,

I have been crashing on games and bench marking within seconds, for about 2 months, Occasionally it will black screen and lose display and i have to restart the system, but more often now I get the message "AMD driver stopped responding and recovered" and kicks me back to desktop. Usually starts with the screen freezing then a horizontal tear across the screen.
It has now more recently started crashing while simply watching films etc.

If i run games and graphical bench-marking using my cpu graphics I have no problem but as soon as I plug in my 390x the issue comes back.

I RMA'd my graphics card as i thought that was the obvious issue but the new one showed no signs of improvement.
I RMA'd my ram as it was showing 11 errors in 5 passes on memtest.

Tested new ram on memtest and found no issues in 5 passes.
Sadly this has not resolved my issue
.
I have tried multiple different drivers for my graphics card using DDU and AMD's driver clean up tool in between each attempt, tried this again after a clean install still no luck.

Checked gpu cables which seemed fine but swapped them out with spares I had just in case.

Heat doesn't seem to be an issue in this as it crashes before the card has a chance to heat up and my cpu is running quite cool with a hyper evo 212 and i think my air flow is adequate enough

build:
Win10 pro
i7 4970k
MSI 390x
MSI z97 mobo
EVGA GQ 750w
2x8 Corsair vengeance 1866mhz
250GB Samsung SSD
1TB WD
other various 2.5 drives

Nothing is overclocked other than factory overclocking.

Please any suggestions are welcome! been posting around all over the place and found nothing thats solved my issue so far :(
6 answers Last reply Best Answer
More about amd display driver stopped responding recovered successfully instant crashes games benchmarking
  1. Well I think you covered pretty much everything. If a clean install of the drivers did not work, I would move on to a clean install of the OS. If you don't want to do that I need more info, any error codes? Anything in event viewer corresponding to the driver crash?
  2. Can you find out any more information regarding driver crash? Event viewer?
    Have you tried uninstalling drivers with ddu and using the generic Windows driver?
    This will might give you a bit more insight to whether it's software or hardware related.
  3. Dunlop0078 said:
    Well I think you covered pretty much everything. If a clean install of the drivers did not work, I would move on to a clean install of the OS. If you don't want to do that I need more info, any error codes? Anything in event viewer corresponding to the driver crash?


    Honestly don't really know what I should be looking for but the obvious one to me is the display warning on administrator events but it doesn't seem to provide any useful information to me at least

    Display

    - EventID 4101

    [ Qualifiers] 0

    Level 3

    Task 0

    Keywords 0x80000000000000

    - TimeCreated

    [ SystemTime] 2016-08-06T00:07:44.819300100Z

    EventRecordID 463

    Channel System

    Computer DESKTOP-015DE1H

    Security


    - EventData

    amdkmdap


    Then there is device manager log for my GPU which has a few different events such as:

    - System

    - Provider

    [ Name] Microsoft-Windows-UserPnp
    [ Guid] {96F4A050-7E31-453C-88BE-9634F4E02139}

    EventID 20001

    Version 0

    Level 4

    Task 7005

    Opcode 0

    Keywords 0x8000000000000000

    - TimeCreated

    [ SystemTime] 2016-08-05T23:14:30.564997500Z

    EventRecordID 92

    Correlation

    - Execution

    [ ProcessID] 2936
    [ ThreadID] 2956

    Channel System

    Computer DESKTOP-015DE1H

    - Security

    [ UserID] S-1-5-18

    - Provider

    [ Name] Microsoft-Windows-UserPnp
    [ Guid] {96F4A050-7E31-453C-88BE-9634F4E02139}

    EventID 20001

    Version 0

    Level 4

    Task 7005

    Opcode 0

    Keywords 0x8000000000000000

    - TimeCreated

    [ SystemTime] 2016-08-05T23:14:30.564997500Z

    EventRecordID 92

    Correlation

    - Execution

    [ ProcessID] 2936
    [ ThreadID] 2956

    Channel System

    Computer DESKTOP-015DE1H

    - Security

    [ UserID] S-1-5-18


    - UserData

    - InstallDeviceID

    DriverName c0297237.inf_amd64_520b8b18f42653d5\c0297237.inf

    DriverVersion 15.300.1025.1001

    DriverProvider Advanced Micro Devices, Inc.

    DeviceInstanceID PCI\VEN_1002&DEV_67B0&SUBSYS_20151462&REV_80\4&B7B0A11&0&0008

    SetupClass {4D36E968-E325-11CE-BFC1-08002BE10318}

    RebootOption false

    UpgradeDevice false

    IsDriverOEM true

    InstallStatus 0x0

    DriverDescription AMD Radeon (TM) R9 390 Series


    Either of these useful or should I be looking for a specific event?
  4. Devildjinn said:
    Can you find out any more information regarding driver crash? Event viewer?
    Have you tried uninstalling drivers with ddu and using the generic Windows driver?
    This will might give you a bit more insight to whether it's software or hardware related.


    Using generic windows driver seems to work fine but obviously hard to test with intensive programs, and the cpu graphic drivers work fine if i install them and i can play older games like bf2, WoW etc with no problems
  5. Was a faulty mobo
  6. Best answer
    MERGED QUESTION
    Question from Farranuk : "How to test for a damaged/faulty mobo"

    Farranuk said:
    Hi there
    I am wondering how to test a motherboard for faults,

    I've been experiencing almost instant crashing when entering games(AMD display driver has stopped responding), after trying multiple different drivers and using DDU and with no success I believed this to be a fault with my graphics card which I RMA'd and then my ram because it showed errors on memtest but I'm still having the same issue.

    I ran a few short cpu tests and another memory test on my new ram and that seemed fine,
    I tried plugging in my graphics card to a separate psu (cx 750w) with everything else running off my case psu but still having the same issue.

    This has brought me to the conclusion that is my motherboard which is at fault but I don't know any way of testing for a dodgy PCI-E x16 slot etc and i cannot access my bios due to my screen being a 36 inch tv which screws up my bios resolution so I cant try it in the other x16 slot much to my annoyance

    I have no spares other than my other PSU as this was my first build so I cannot test it on another desktop setup but is there any other way of diagnosing faults with a mobo?

    ALSO I broke off the PCI-e x16 slot clip when removing my gpu the first time this error started occurring and am wondering if that would affect me RMA'ing my mobo with msi? ( iknow this isn't the fault because the problem occurred before this)

    Build:
    i7 4790k 4ghz
    msi z97 G5
    msi 390x
    evga GQ 750w
    corsair vengeance 1866mhz
    evo ssd
    wd hdd

    nothing overclocked over than factory overclocking


    BadActor said:
    Really, the only way to diagnose the motherboard is at fault is to eliminate everything else. Have your tried using the graphics card in the other PCie slot? I would also try another power supply. The 390x is a power hungry card (700 watt recommended) and may not work if the PSU is marginal. There's also a chance that the CPU could be at fault, but this is very rare. You really need to make sure the Bios is up to date, so I would borrow a monitor for this.


    Anonymous said:
    You will probably have a problem RMA'ing the mobo in a physically damaged condition but it might be worth a try as a last resort.

    Are you sure you have installed the latest BIOS updates? Check the MSI web site.


    Farranuk said:
    RMA was fine, asked them before i sent it off if it would be an issue but they didnt mention anything about it and the RMA went through without issue so maybe MSI are just kind or lazy who knows
Ask a new question

Read More

MSI-Microstar Crash Display Adapter Drivers Benchmark AMD Games Graphics Cards