Radeon Software Crimson ReLive Edition 17.5.1

bill dennison

Well-known member
Rage3D Subscriber
Radeon Software Crimson ReLive Edition 17.5.1 Release Notes


Support For
    • Prey®
      • Up to 4.7% performance improvement measured on Radeon RX 580 8GB graphics when compared to Radeon Software Crimson ReLive edition 17.4.4(1)
      • Multi GPU profile support
Fixed Issues
    • Fixed an issue that may sometimes cause the error message "1603" during uninstall.
    • Radeon Settings may sometimes fail to update through the auto Radeon Software update feature.
    • Forza Horizon 3™ may experience minor graphics corruption in some game maps
    • Sid Meier's Civilization™ VI may experience an application crash when using Hybrid Graphics system configurations and windowed game mode
    • Radeon WattMan may fail to apply settings on some Radeon R9 390 series graphics products.
    • Added switchable graphics support for Unigine™ Superposition for XConnect and Hybrid Graphics.
http://support.amd.com/en-us/kb-art...mson-ReLive-Edition-17.5.1-Release-Notes.aspx
 
◦ Radeon WattMan may fail to apply settings on some Radeon R9 390 series graphics products will make some happy. 'bout time! :p
 
◦ Radeon WattMan may fail to apply settings on some Radeon R9 390 series graphics products will make some happy. 'bout time! :p

i was happy too about the news until i tried the driver .. nop it's still broken for me.( always stuck at idle speed)

the last working driver for me is 17.2.1.
 
Try to select "Clean Install" during driver installation.

Since 17.3.x overclocking on my R9 290 was broken. With 17.5.1 it's finally working again. I haven't tried under/over volting the card though. I also don't use any third-party tools.
 
These drivers at least seem stable if still a tad slower than the 16.x.x series on my Fury's. All previous 17.x.x brought back the dreaded monitor signal out of bounds with 17.4.4 being the worst.
 
i tried everything believe me , Clean install , DDU .. etc ....all driver version higher than 17.2.1. make my R9 390 useless.

So the problem you see is that the GPU clocks are stuck at idle. Right? Does it only happen when you overclock the GPU? Also, are you using any third party tools (Afterburner etc.) ?

I remember in Wattman's early days, on R9 290, if you changed GPU voltage on any of the GPU states, the clocks would not go higher than the one state below. So basically, if there were seven clock states, and you changed the voltage of the fifth one (whether overvolt or undervolt), the GPU will raise its clock only up to the fourth state. That bug may still be there. I haven't experimented with changing the voltage.

If you are not under/over volting and if you are not using third-party tools, then overclocking 290/390 within Wattman should work.
 
By the way, my experience is with single display only. It could be that there are some problems with overclocking when you have two or more displays attached.

Also, if you overclock your monitor (for higher than officially supported refresh rates) using tools like CRU, then selecting a very small blanking interval can sometimes interfere with the GPU memory clock transitions. Though the GPU core clocks should still transition normally.
 
No , im not using any third party software , single 1080p monitor via DVI
i don't overclock anything , i just want to use my card as is.

if i use any driver version higher than 17.2.1 my GPU is always stuck at 300Mhz .. whatever i do .. the card won't clock higher than that or maybe displaying some weird numbers like 380 .. 350 ... 318 mhz....in gpuz , in short the card never change state . All my games i try , play like a powerpoint slideshow .. i get 18 FPS at best. If i revert back to driver 17.2.1 or lower my card work again as before.

this is my card model
http://www.xfxforce.com/en-us/produ...double-dissipation-black-edition-r9-390p-d28m

it has a custom clock of 1050mhz .. maybe the drivers higher 17.2.1 simply dont recognize my card anymore.
 
Once again VSR is broken in these drivers as well, wtf AMD :mad:

VSR doesn't work for me in any of the 17.x.x drivers, I have to go back as far as 16.11.5. What the hell changed?
 
Last edited:
Once again VSR is broken in these drivers as well, wtf AMD :mad:

VSR doesn't work for me in any of the 17.x.x drivers, I have to go back as far as 16.11.5. What the hell changed?

Ryzen that's what changed. AMD have moved almost all their remaining engineers over to the CPU side and basically aren't really interested in the graphics side ATM. :bleh:
 
VSR works fine on both of my setup (4K via HDMI, and 2560x1440 via DVI-D). I get higher resolutions on both, that is higher than 4K for HDMI, and 4K for the 1440p setup.
 
if i use any driver version higher than 17.2.1 my GPU is always stuck at 300Mhz .. whatever i do .. the card won't clock higher than that or maybe displaying some weird numbers like 380 .. 350 ... 318 mhz....in gpuz , in short the card never change state . All my games i try , play like a powerpoint slideshow .. i get 18 FPS at best. If i revert back to driver 17.2.1 or lower my card work again as before.

this is my card model
http://www.xfxforce.com/en-us/produ...double-dissipation-black-edition-r9-390p-d28m

it has a custom clock of 1050mhz .. maybe the drivers higher 17.2.1 simply dont recognize my card anymore.

I think you should contact XFX then. This is highly abnormal. The basic functionality of your graphic card going through various GPU clock states is broken for whatever reason.
 
I think you should contact XFX then. This is highly abnormal. The basic functionality of your graphic card going through various GPU clock states is broken for whatever reason.

i think the only thing i can ask XFX is if there is a newer BIOS than the one i have ... but clearly , something is broken in all driver version above 17.2.1.
 
it may very well be a defect in your graphic card only getting exposed on latest drivers. If the card is under warranty, it's XFX's responsibility to fix the broken functionality. There's absolutely no way that all of these particular XFX R9 390s can't go above idle clock rates on any driver coming out for past three months.

I'd not ask for new BIOS, rather explain to them the problem and they should provide you a solution.

For a long time, I had a 7950 that would blackscreen past the windows logo on startup in recent drivers, but would work fine on six month old (or older) drivers. Before throwing the card out, I contacted Sapphire, and they processed the RMA, shipped me another 7950 (of the same model) which worked great with latest drivers.
 
i think the only thing i can ask XFX is if there is a newer BIOS than the one i have ... but clearly , something is broken in all driver version above 17.2.1.

I have an XFX R9 390 and have no problems with the newer drivers. I just ran the SuperPosition benchmark along with the AMD System Monitor, and my card will run at 1015 MHz while the benchmark is running. I haven't tried to overclock the card because it performs quite well for me without having to go down that road.

I have dealt with XFX customer service in the past and was pleased with the response I got from them. I've had at least 5 different XFX cards over the years.

BTW, how long has it been since you checked for a BIOS update for the motherboard? My son got a new card this past week and his system would NOT recognize it until I flashed the board with a new BIOS.

Good luck!
 
BTW, how long has it been since you checked for a BIOS update for the motherboard? My son got a new card this past week and his system would NOT recognize it until I flashed the board with a new BIOS.

Good luck!

Omg .. it was it . i'm very surprised. I flashed this motherboard at least 3 times to update the Bios since i own it. I had the Bios 3103 dated 2016/04/15 so it was not that '' old '' i think ? but hey .. i followed your suggestion and i admit , i was a bit skeptical :) I could not believe that a video card could stop functioning normally and refuse newer driver updates because of a motherboard bios. Soooo i effectively found a newer Bios 3201 2017/03/03 and updated the motherboard.

Soon as i booted in Win10 i installed 17.5.1 , rebooted and tried Unigine2 Superposition benchmark on 1080p extreme settings .. Boom! a solid 1050 Mhz ..i tried a couple of other games to confirm that it work just like before ... and yes .. i'm back in business.

the change logs of the last five Bios updates ( 2015-17 ) for my motherboard contains only a small comment : Improve system stability. So nobody knows what magic happened this time.

happy ending ! I Thank you, Mr. Dire Straits.
 
But, AMD has terrible drivers!
- The Internet

:bleh2:




Glad everything is working for you. These cards are actually aging fairly strong even now with the stuff I play, which is the only reason I'm able to wait and see what Vega is like... if it couldn't cut it, then it'd be in a box in the closet as soon as the one from some e-tailer arrived. :D
 
Back
Top