Tuesday, October 24, 2017

Radeon Software Crimson ReLive Edition 17.10.2

Listen up all you Radeon owners out there, AMD has released its Radeon Software Crimson ReLive Edition 17.10.2 driver. In addition to stability and performance improvements, these new drivers resolve the following issues:

Fixed Issues

  • Radeon Software may not appear in the uninstall options under "Apps and Features" on Windows® operating systems after a Radeon Software upgrade.
  • Minor corruption may appear in PLAYERUNKNOWN'S BATTLEGROUNDS™ in some game locations when using Ultra graphics settings in game.
  • Radeon Wattman may fail to apply user adjusted voltage values on certain configurations.
  • Hearts of Iron™ IV may experience a crash or system hang during some scenario gameplay.
  • Radeon Settings gaming tab may not automatically populate games detected on the users system.


Known Issues

  • A random system hang may be experienced after extended periods of use on system configurations using 12 GPU's for compute workloads.
  • Assassin's Creed™: Origins may experience an intermittent application or system hang when playing on Windows®7 system configurations.
  • The GPU Workload feature may cause a system hang when switching to Compute while AMD CrossFire is enabled. A workaround is to disable AMD CrossFire before switching the toggle to Compute workloads.
  • Resizing the Radeon Settings window may cause the user interface to stutter or exhibit corruption temporarily.
  • Corruption may be experienced in Forza Motorsport™ 7 on some HDR displays with HDR enabled in game. 
  • Radeon WattMan reset and restore factory default options may not reset graphics or memory clocks and unstable Radeon WattMan profiles may not be restored to default after a system hang.
  • OverWatch™ may experience a random or intermittent hang on some system configurations. Disabling Radeon ReLive as a temporary workaround may resolve the issue.
  • When recording with Radeon ReLive on Radeon RX Vega Series graphics products GPU usage and clocks may remain in high states. A workaround is to disable and then re-enable Radeon ReLive.