AMD drops Windows 7 and 8.1 and GPUs prior to Polaris

AMD has just released the Radeon Software Adrenalin 21.6.1 driver, with a series of new features including support for new GPUs and technologies such as upscaling FidelityFX Super Resolution (FSR) technology. There is also bad news such as the end of support for Windows 7-8.1 as well as GPUs prior to Polaris.

AMD has released a new version of its Radeon Software Adrenalin 21.6.1 graphics driver. The new software brings a lot of improvements and optimizations as well as a handful of new features, and support for new GPUs.

AMD is launching the upscaling FidelityFX Super Resolution (FSR) technology as promised by the founder. FSR technology first appeared in a limited number of games, including Godfall and six other titles. Ultimately, AMD is not opposed to making the device compatible with Nvidia cards.

AMD SAYS GOODBYE TO WINDOWS 7, 8 AND 8.1 WITH LATEST RADEON GRAPHICS CARD DRIVER

AMD optimized the execution of the Dungeons and Dragons: Dark Alliance game, and added support for the RX 6800M Laptop GPU. The list of changes is particularly broad in this iteration, but the main takeaway is that AMD has decided to end support for Windows 7, 8 and 8.1.

Older GPUs prior to Polaris are also no longer supported. Here is the full list of release notes:

Now supported

  • AMD Radeon™ RX 6800M Laptop Graphics Cards
  • Dungeons & Dragons: Dark Alliance™
  • upscaling AMD FidelityFX Super Resolution (FSR) in some titles.

PROBLEMS SOLVED

  • Radeon FreeSync™ may interlock intermittently on the desktop after performing a task switch between the extended and primary displays when closing a game, resulting in poor performance or stuttering.
  • Anno 1800™ may crash at launch when running DirectX®12.
  • The AMD Cleanup Utility can clean the folders/registers related to the system’s chipset/RAID installer.
  • Some Radeon Graphics products may perform below expectations in Destiny 2™ compared to previous versions of Radeon software.
  • By joining the AMD User Experience Program, the primary service of the AMD User Experience Program may have higher than expected processor usage.
  • Activation of Ray Tracing in Ring of Elysium™ with DirectX®12 may cause the game to crash.

KNOWN ISSUES

  • Resident Evil Village™ may encounter intermittent application blocking or TDR on AMD Radeon VII graphics products in the first mission of the game.
  • Enhanced gating can cause a black screen to appear when enabled on some games and system configurations. All users who may experience problems with enabling enhanced gating should disable it as a temporary workaround.
  • Connecting two screens with large differences in resolution/refresh rate can cause a flicker on the Radeon RX Vega series graphics products.
  • An Oculus service error can be received on Radeon RX 5000 & 6000 Series Graphics Products that prevent Oculus Link configuration software from running.
  • Radeon performance metrics and logging features can intermittently report extremely high and incorrect memory clock values.
  • If Ryzen Master is not detected in Adrenalin software after installation, a system restart may be required.
  • If a blue or black screen is observed on mobile systems, temporarily disable the enhanced connection
  • A driver mismatch error may occur when two versions of Radeon software (Windows Store and AMD Support versions) are installed on your system. As a temporary workaround, launch the Windows Store version of the Radeon software.
  • AMD is investigating a problem that may have a small impact on the battery life of the AMD Ryzen 5000 laptops.
  • A blue or black screen can be seen after updating to the latest version of Radeon software. A workaround is to disable the main isolation.
  • AMD is investigating an error code D3 that can be reported with some motherboards after the update to the latest version of Radeon software.
  • Below-expectations performance can be observed on some AMD Athlon™ mobile systems.

KNOWN ISSUES WITH AMD LINK ON WINDOWS

Intermittent corruption of the gray frame can be observed during streaming with HEVC on some configurations via an Internet connection. A workaround is to use the AVC encoding parameter instead.

Add Comment