Radeon Software Crimson ReLive Edition 17.4.1 Download & Discussion

I always "clean" install it after a DDU removal, but I reinstalled a second time and it launched without incident. Weird.

 

Same here do you get THIS message???

directx function "findclosestmatchingmode" failed with e_fail

sry cant post pics atm


btw used ddu

 

The easiest way to trigger the UVD bug is to open a game while having a browser running in the background, at least on GCN 1.0 that's how it works.

Any DXVA video playback while there's an instance of Chrome running also triggers it 90% of the time.

The best practices to avoid this bug is to make up the habit of not running browsers and games/videos on media players at the same time.

 

Well I managed to turn off GPU acceleration in the launcher and no crashes running the game but ingame performance also seems wonky. Will be doing a full re-install of Windows with Creators update so will see how things turn out.

 

Thanks for the help.... much appreciated.

 

Edit: I was wrong, read my new reply here.

On my HD 7950, the 2D clock is 150/300, the UVD clock is 500/900, the 3D clock is 1000/1250. The clocks get stuck on the UVD values and do not go back to 2D clocks when the GPU is idle. If a 3D game or app is launched, the clocks do go up, but to values lower than the 3D clocks (I think to 900/1250 or something). I am using MSI Afterburner to control my clocks, but you CANNOT fix this issue with Afterburner. The easiest way to fix this is to use the "restart" executable provided in the CRU (Custom Resolution Utility) package to restart the driver without needing to reboot your machine.

 

Thanks for the specs, and the help..... I have clarity now. Very much appreciated. Thankyou.

 

The only "solution" to the issue , is to flash your bios so that the 3d clocks on UVD state are the same as your normal/overclocked state 3d clocks. Of course this partially fixes the issue because your idle clocks will remain higher but, for me at least, the main issue is the 3d clocks.

 

For some unknown reason, the ReLive part refuses to install.

I click on the install option, the installer informs me that everything went fine and I should restart, but there is no ReLive tab when I open Crimson.

Same thing happened with the 17.3.3s.

Followed the exact same steps I've been using for the past years when installing a new driver (DDU included).

 

Whatever was causing this jerky mouse movement just after updating to 17.4.1 has stopped, now back to butter smooth, before I felt the need to check DPS latency.

I've since updated Windows 10 to RS2 (or whatever the new major build is called) and no issues so far.

 

Thanks for that... I was on the verge of asking weather a bios mod to the card might sought the issue out..... something to be weighed up by the user i guess, ie risk of bricking card and needs/application of the card. Thankyou.

 

Basically if you want to fix UVD bug bios must look like this. There is no other way.

 

Yeah this fixed it entirely , but I am not sure if there are issues with video playback after that.

 

for some reason, all these latest "non-whql" drivers always show as whql for me, using creators update, go figure

 

Because AMD paid for M$ to sign 17.4.1 display drivers so it is WHQL. AMD have a bad history on mislabeling the drivers. They could use BETA instead.

 

Dude, for me all latest 17.x.x betas fail with Forza H3 with the exception of 17.3.1. 17.3.1 works flawlessly for me with Forza H3 (works tiptop with all my games, all current AAA titles)... 17.2.1 works great too (whql) but 17.3.1 outperforms it hands down...

I am running Creators Update 'Gaming mode' on, fully updated...

Funny thing is, I seem to get better gaming performance with 'Game mode' disabled... MS tech?, focused improvements in gaming? go figure

Just thought I would share my experience so far with this driver...

Peace peeps :thumbup:

 

I didn't get the chance to update my previous reply earlier but I spoke too soon. This driver is completely broken on my system. Trying to reboot/shutdown the machine or closing MSI Afterburner after it has been loaded results in a THREAD_STUCK_IN_DRIVER BSOD right away and is 100% reproducible; this driver certainly has issues with Afterburner on GCN v1.0 and I am pretty sure it is because GCN v1.0 has also been moved to Wattman now. Also every time after reboot due to BSOD, I get the "Default Radeon WattMan settings have been restored due to unexpected system failure" even though I never even enabled or used Wattman.

After uninstalling the driver I tried to install 17.3.3 but it completely refused to install on my machine. Then I tried to install 17.3.1 which I was using before and it seemed to install but after reboot, the OS gave me the repair screen regardless of how many times I shutdown or rebooted the machine. Eventually I was forced to do a system restore and reinstall 17.3.1 and go back to square one.

Props to AMD for this nice evening. :bang:

 

well the past few non-whql drivers, actually says nonwhql in the filename, have been fully whql for me, just thought it was weird when filename says they are not but in fact they are! 17.3.1, 17.3.2, 17.3.3 all whql here

 

I get those two when I undrevolt my gpu, and blue screen STUCK_IN_DRIVER when undervolted way too much. Maybe "stay calm and raise Vcore" ?
But better don't touch afterburner, it's broken since forever.

I actually thought they are dropping 2011 GCN 1.0. But no, it gets wattman, and async compute was restored.

 

I'm pretty sure I have the downclocking problem as well, the fan pretty much always stays at 20% and the card keeps downclocking to 711mhz which sucks, the only work around (kinda) I've found at the moment is using MSI Afterburner to use a custom fan curve and set the minimum at 50%.