Jump to content

Display Driver Has Crashed and Recovered

Go to solution Solved by JWMutant,

This is not uncommon for AMD and Nvidea alike.

 

For AMD it is normally due to a process called atikmdag not responding.

 

For Nvidea it is normally due to a process called nvlddmkm not responding as well.

 

Normally the best fix for it is to completely uninstall the driver. Then use your fav driver removal tool. Then Install the latest driver.

 

Worse case scenario if it still continues after doing that, back dating to a driver version that didnt create that issue in the first place helps as well. 

This happens occasionally to me (once a week or so) where the screen goes black for a couple seconds and then this appears in the bottom right with a red X. Should I be worried? I'm running Windows 10.

Guide to GTX 900 Series: http://linustechtips.com/main/topic/457526-nvidia-900-series-basic-performance-guide/

Performance expert, building noob. 

There is no such thing as excess in hardware. 

Link to comment
https://linustechtips.com/topic/461538-display-driver-has-crashed-and-recovered/
Share on other sites

Link to post
Share on other sites

AMD or nvidia?

 

what version

I have a 980 Ti. The most recent drivers.

Guide to GTX 900 Series: http://linustechtips.com/main/topic/457526-nvidia-900-series-basic-performance-guide/

Performance expert, building noob. 

There is no such thing as excess in hardware. 

Link to post
Share on other sites

Do you have anything overclocked?

Computer specs?

Nothing is OCed

EVGA 980 Ti SC ACX 2.0+

Intel i7 3770k

16 GB (2x8) Crucial DDR3

Guide to GTX 900 Series: http://linustechtips.com/main/topic/457526-nvidia-900-series-basic-performance-guide/

Performance expert, building noob. 

There is no such thing as excess in hardware. 

Link to post
Share on other sites

This is not uncommon for AMD and Nvidea alike.

 

For AMD it is normally due to a process called atikmdag not responding.

 

For Nvidea it is normally due to a process called nvlddmkm not responding as well.

 

Normally the best fix for it is to completely uninstall the driver. Then use your fav driver removal tool. Then Install the latest driver.

 

Worse case scenario if it still continues after doing that, back dating to a driver version that didnt create that issue in the first place helps as well. 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×