Overclock.net banner

[AMD] Crimson ReLive 17.1.1, enabling support for ResidentEvil7

7K views 107 replies 51 participants last post by  ZealotKi11er 
#1 ·
Download link (Win10 64):

http://support.amd.com/en-us/download/desktop?os=Windows+10+-+64

Fixed Issues
Dishonored™2 may experience an application crash or hang on some Radeon R9 380 configurations.
Radeon ReLive may show an improper warning popup message when using Windows®7 basic themes.
AMD XConnect™ Technology configurations may experience a blue screen system hang when audio drivers load.
Solidworks™ will no longer terminate on unplug using AMD XConnect™ Technology configurations.
Some system configurations may experience a black screen after installing Radeon Software Crimson ReLive Editions 16.12.1 and later.
Display corruption or TDR may be experienced after applications wake up from a display timeout.
Paragon™ may experience flickering in Multi GPU with DirectX®11.
Radeon ReLive may crash or become unresponsive when toggling Multi GPU with Desktop Recording and/or Instant Replay enabled.

Release notes:
Article Number: RN-WIN-RADEONCRIMSONRELIVE-17.1.1
Radeon Software Crimson ReLive Edition is AMD's advanced graphics software for enabling high-performance gaming and engaging VR experiences. Create, capture, and share your remarkable moments. Effortlessly boost performance and efficiency. Experience Radeon Software with industry-leading user satisfaction, rigorously-tested stability, comprehensive certification, and more.
Radeon Software Crimson ReLive Edition 17.1.1 Highlights
Support For
Resident Evil™ 7: Biohazard
Fixed Issues
Dishonored™2 may experience an application crash or hang on some Radeon R9 380 configurations.
Radeon ReLive may show an improper warning popup message when using Windows®7 basic themes.
AMD XConnect™ Technology configurations may experience a blue screen system hang when audio drivers load.
Solidworks™ will no longer terminate on unplug using AMD XConnect™ Technology configurations.
Some system configurations may experience a black screen after installing Radeon Software Crimson ReLive Editions 16.12.1 and later.
Display corruption or TDR may be experienced after applications wake up from a display timeout.
Paragon™ may experience flickering in Multi GPU with DirectX®11.
Radeon ReLive may crash or become unresponsive when toggling Multi GPU with Desktop Recording and/or Instant Replay enabled.
Known Issues
A small amount of apps may still experience issues with Borderless Fullscreen mode and AMD FreeSync™ technology if other applications or game launchers are running on the primary screen in the background.
Counter-Strike™: Global Offensive and World of Warcraft™ may experience flickering or performance issues the first time the game is launched on a system boot with AMD FreeSync™ technology enabled. Workarounds include exiting and restarting the application or task switching (alt+tab) in and out of the game to fix the issue.
Shadow Warrior 2™ may experience an application hang when launched with Multi GPU enabled.
Radeon RX 400 series products may experience scaling issues for some applications when using the display scaling feature.
Deus Ex: Mankind Divided™ may experience an application hang when running in Multi GPU with DirectX®12 and performing a task switch.
AMD Multi GPU configurations may experience a system hang or reboot during install when using tiled MST 4K or 5K displays.
Mouse cursor corruption may be intermittently experienced on Radeon RX 480.
Known Issues for Radeon ReLive
The XBOX™ DVR application may cause conflicts with Radeon ReLive, users are suggested to disable XBOX™ DVR if Radeon ReLive is experiencing issues.
Radeon ReLive may fail to install on AMD APU Family products or experience a system hang or failure to record when using the recording feature on AMD APU Family products.
Radeon ReLive may stop working after hot unplugging of a secondary display.
Battlefield™1 may experience UI flickering and/or performance drops when recording gameplay with Radeon ReLive on graphics products with 4GB or less of VRAM.
Radeon ReLive recordings or overlay may experience flicker when creating a single recording for many hours.
Radeon ReLive may experience minor graphical corruption for the first few recorded frames when launching UWP applications.
Radeon ReLive will not allow recording settings to change with Instant Replay enabled. A workaround is to disable Instant Replay and change settings then enable Instant Replay.
Vulkan™ applications may experience a game hang when using Radeon ReLive to record.
Radeon ReLive will not notify an end user of low disk space during recording.
Package Contents
The Radeon Software Crimson ReLive Edition 17.1.1 installation package contains the following:
Radeon Software Crimson ReLive Edition 17.1.1 Driver Version 16.50.2611
 
See less See more
#4 ·
Quote:
Originally Posted by Zen00 View Post

Updates updates everywhere, but not a fix in sight.

150 Mhz bug still affecting us.
What is that
 
#6 ·
Quote:
Originally Posted by ZealotKi11er View Post

What is that
Sometimes the memory will get stuck on 150hz. Happened to me earlier, was playing Titanfall 2 and noticed that my fps was just really awful, couldn't figure out why, then noticed that my memory was at 150 while core was at 1100. Only restarting the computer seems to fix it for me. It's especially annoying when playing CSGO for me, as then I always tend to miss a round while restarting.
 
#7 ·
Actually, you don't have to reboot, only restart the driver. I've used the two .exe's that come with CRU, and it worked for me
smile.gif
 
#8 ·
How does this jive with Afterburner?
Quote:
Originally Posted by Hattifnatten View Post

Actually, you don't have to reboot, only restart the driver. I've used the two .exe's that come with CRU, and it worked for me
smile.gif
CRU
 
#9 ·
Custom Resulution Utility. In the .zip you'll find two executables (86 and 64) that will restart the display-driver. Pretty nifty sometimes
thumb.gif
 
#10 ·
So about the 150mhz bug on my 290:
-I uninstalled all 3d party oc software, i do not get this bug anymore, i run wattman vccd auto + vrmtool only.
-The only few times i still get this is when i patch the drivers with CRU or pixelclk aka ToasterX tools that we like and bless.
-Like when i force 75Hz on my monitor, i can't anymore change the ram clock in wattman, slider stuck; either if the driver crash, i get stuck to the 150mhz bug. Never happen, pc crash since i'm too far, drivers can't even recover!
rolleyes.gif


For me the problem now it is when the pc reboot from an oc crash, blank screen when windows should pop up!
Safe mode and reboot, is quite boring when you have a raid!
redface.gif


Hope it help.
smile.gif
 
#11 ·
Would it not be better for AMD for fix all those in the list and then releasing the driver?
 
#14 ·
Quote:
Originally Posted by ZealotKi11er View Post

Would it not be better for AMD for fix all those in the list and then releasing the driver?
Software developers(especially teams) tend to have a release cadence. Instead of waiting a long time for a fix that might take a while, they release what they already have fixed as not to disrupt the flow. OR have some customers wait for one of those already fixed because someone else had a problem on the known list that's taking longer.
 
#16 ·
I bought an RX 470 on release. I've had issued the entire time I owned it except for a blissful period on 16.11.5 and 16.12.1 (i think... whatever the first ReLive was)

Drivers were so bad for the first 3 months I nearly returned it. Would randomly get black screen and would have to restart entire pc to get display back

Then I'd get some weird permanent tear line in the middle of my screen. Then sparkly static on the left of my screen.

16.12.1 seemed fine, but I'm currently on 16.12.2 and getting occasional black artifacting on Titanfall 2. Haven't yet pinpointed the issue (maybe it's another compenent causing the issue, or maybe my actual card is failing and it's not a driver issue)

Never quite understood why everyone praises AMD drivers. They do look like they're working hard though and will eventually fix all the issues over time

Loving my RX 470 when everything's working though. Pretty badass card for the money
 
#17 ·
Quote:
Originally Posted by mejobloggs View Post

I bought an RX 470 on release. I've had issued the entire time I owned it except for a blissful period on 16.11.5 and 16.12.1 (i think... whatever the first ReLive was)

Drivers were so bad for the first 3 months I nearly returned it. Would randomly get black screen and would have to restart entire pc to get display back

Then I'd get some weird permanent tear line in the middle of my screen. Then sparkly static on the left of my screen.

16.12.1 seemed fine, but I'm currently on 16.12.2 and getting occasional black artifacting on Titanfall 2. Haven't yet pinpointed the issue (maybe it's another compenent causing the issue, or maybe my actual card is failing and it's not a driver issue)

Never quite understood why everyone praises AMD drivers. They do look like they're working hard though and will eventually fix all the issues over time

Loving my RX 470 when everything's working though. Pretty badass card for the money
Something else going on with your card. I have 6 AMD cards from GCN 1, GCN 2, GCN 3 and no problems at all.
 
#19 ·
Quote:
Originally Posted by dagget3450 View Post

So forgive me but what does enabling support for a game mean? I know its not crossfire right? Shouldn't the game work without a driver enabling support?

I know i am nit-picking here but if we need new game day drivers for a single gpu then what is the reason?
Not really. Games have to be tested to make sure no major problems occur with GPUs. These are Game Ready drivers.
 
#20 ·
Quote:
Originally Posted by dagget3450 View Post

So forgive me but what does enabling support for a game mean? I know its not crossfire right? Shouldn't the game work without a driver enabling support?

I know i am nit-picking here but if we need new game day drivers for a single gpu then what is the reason?
Should be the case.. You also don't need a game-ready driver per se, but some developers release garbage games, so Nvidia and AMD go in and optimize/fix all the problems.

You'd be amazed just how much work AMD and Nvidia put into their drivers.
 
#21 ·
Quote:
Originally Posted by ZealotKi11er View Post

Something else going on with your card. I have 6 AMD cards from GCN 1, GCN 2, GCN 3 and no problems at all.
Nah the main ones ended up being legit issues that AMD fixed in the three months after 470 release. People where even making 3rd party apps (ClockBlocker one was called I think) to fix some of the issues.

Glad it got better eventually though. As I said, once it's all going smoothly I love the card I have. Will most likely buy Vega too
 
#22 ·
These new batch of drivers seem to be bios locked so any form of oc is highly unstable.
 
#25 ·
Quote:
Originally Posted by Wimpzilla View Post

So about the 150mhz bug on my 290:
-I uninstalled all 3d party oc software, i do not get this bug anymore, i run wattman vccd auto + vrmtool only.
-The only few times i still get this is when i patch the drivers with CRU or pixelclk aka ToasterX tools that we like and bless.
-Like when i force 75Hz on my monitor, i can't anymore change the ram clock in wattman, slider stuck; either if the driver crash, i get stuck to the 150mhz bug. Never happen, pc crash since i'm too far, drivers can't even recover!
rolleyes.gif


For me the problem now it is when the pc reboot from an oc crash, blank screen when windows should pop up!
Safe mode and reboot, is quite boring when you have a raid!
redface.gif


Hope it help.
smile.gif
For the record, I've never had this bug and I don't have any 3rd party overclocking tools installed.
 
#26 ·
Quote:
Originally Posted by Newbie2009 View Post

For the record, I've never had this bug and I don't have any 3rd party overclocking tools installed.
So we find the problem imo, this bug happen when the driver get modified, it could be in some install/OS/config, 3rd party software do not impact.
On some other maybe yes, that's why even I, think that the 3rd party software are not the cause themselves.
It is rather the patching driver or modifying it that cause this bug on memory, aka when i modify the refresh rate with CRU.

So either the modified driver bug itself on ram, either the RCC (i like Relive Control Center
biggrin.gif
) badly recognize the ram clock, either it is the OS that fail into manage the ram speed correctly.

I tested all this stuff, and myself had sometimes this bug, this sometimes come out from patching my driver with CRU to apply 75Hz on my panel.
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top