Jump to content

390x Screen Freeze

Hello all. since updating my gpu drivers, my sapphire 390x tri-x gives me screen freezes especially when watching videos using HPC-HC, but also tried quicktime and same issue.

- with drivers 17.4.4 and 17.6.2 the screen freezes, then it shows black screen and sometimes the screen shuts down, the system then recovers only to repeat the issue few minutes later

- with drivers 17.2.1 the screen freezes but it doesn't show black screen and it doesn't shut down, the system recovers and shows this in the event viewer : amdkmdap stopped responding (event 4101 display driver)

- drivers 16.5.2.1 are the ones i was using and function properly i tried uninstalling using control panel and DDU from safe mode. and the results are the same with the the three drivers i also tried disabling Pci express link state power management and same problem.

also the 390x is listed as 390 series in windows device manager.

 

GPU: sapphire 390x tri-x non overclocked.

CPU: I5 4690k non overclocked.

Motherboard: Asus maximus VII Ranger

RAM: 2 x 4g 1600 gskill ripjaws and 2 x 8g adata xpg 1866. (xmp 1600)

PSU: cooler master v1200

Windows 10 anniversary update

Thanks in advance.

Link to comment
Share on other sites

Link to post
Share on other sites

At this point you might want to consider reinstalling windows...

Record holder for Firestrike, Firestrike Extreme and Firestrike Ultra for his hardware

Top 100 for TimeSpy and Top 25 for Timespy Extreme

 

Intel i7 10700 || 64GB Kingston Predator RGB || Asus H470i Strix || MSI RX 6700XT Merc X2 OC || Corsair MP600 500GB ||  WD Blue SN550 1TB || 500GB Samsung 860 EVO || EVGA 550 GM || EK-Classic 115X aRGB CPU block - Corsair XR5 240mm RAD - Alphacool GPU Block - DarkSide 240mm external rad || Lian Li Q58 || 2x Cooler Master ARGB 120MM + 2x Noctua  Redux 1700RPM 120MM 

Link to comment
Share on other sites

Link to post
Share on other sites

thanks for the reply.

do you mean doing a clean install, format the HDD or reinstalling from windows.

note that reverting to the 16.5.2.1 fixes the issues.

Link to comment
Share on other sites

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

×