news vbios updates and drivers available for radeon rx 5600 xt

vBIOS updates and drivers available for Radeon RX 5600 XT

We recently reported on the ryzing (anyone?) competition between AMD and Nvidia with the introduction of the Radeon RX 5600 XT. Nvidia dropped it’s GeForce RTX 2060 from $349 to $299 in anticipation of the new Radeon card’s launch at $279. AMD responded by pushing out a new vBIOS to boost the performance of the RX 5600 XT. The vBIOS increases the card’s maximum power draw from 150W to 160W, improving base and boost clocks, as well as rasing the memory from 12 Gbps to 14 Gbps.

However, the vBIOS didn’t quite make it out the door and onto cards before vendors started shipping them. Fortunately, the vendors were quick to release BIOS updaters, so those who have already received their cards can unlock the extra power waiting to be released. The vendors and cards are listed below with links to where you can find the updaters.

If you’re running an RX 5600 XT, you’ll also need the recently released Radeon Software Adrenalin 20.1.3 beta drivers, which add support for the new graphics card. The beta drivers also fix a number of issues, but are not issue free. You can pick them up here.

Fixed Issues
  • An intermittent black screen or loss of display may occur when performing parallel actions such as web browsing, gaming or watching video.
  • A limited number of games such as Nioh, Dragon Quest Builders 2, WWE2k20, Dead or Alive 6 and Atelier Ryza may crash or fail to launch.
  • Wolfenstein 2: The New Colossus is not detected in Radeon Software games manager.
  • Text overflow in some UI boxes or toast messages may be experienced in some language localizations.
  • Fan Tuning may change back to the default state when switching between available GPUs.
  • Copy text options are not available in the display specs table for Radeon Software.
  • An intermittent black screen or loss of display may occur when the system is left idle at desktop.
  • Factory Reset install may keep previously configured Radeon Software game profiles. This can cause mismatch between global graphics settings and per profile settings.
Known Issues
  • Grand Theft Auto 5 may experience a system hang or black screen at launch, when opening Radeon Overlay while in game, or after performing a task switch while in game.
  • Audio may intermittently be missing from Radeon ReLive recordings near the end of recorded clips.
  • Integer Scaling may cause some video content to show flicker when the display resolution is set to less than native resolution.
  • Multiple games may have very dark or very bright graphics in game when HDR is enabled in Windows.
  • Radeon Anti-Lag enable and disable beep notifications may be played in error when individually pressing keys assigned to the hotkey.
  • The Radeon Software Overlay hotkey notification may sometimes be displayed during video playback in web browsers or launching some video player applications.
  • Integer Scaling option is not showing up or available on some Windows7 system configurations.
  • Radeon Software may open with an inconsistent size or may not keep its previously set size when opened.
  • Some Vulkan gaming applications may crash when performing a task switch with Radeon Image Sharpening enabled.
  • Some Radeon RX 5700 series graphics users may intermittently experience a black screen while gaming or on desktop. A potential temporary workaround is disabling hardware acceleration in applications running in the background such as web browsers or Discord.

7 responses to “vBIOS updates and drivers available for Radeon RX 5600 XT

  1. The reason for memory/GPU utilization jumping from idle to load is because of hardware-accelerated apps and WDM. Driving extra screens and higher-refresh rates along with adaptive sync do come at a cost. The same thing happens on the Nvidia camp. GDDR6 is more power hungry than its GDDR5 predecessor (those extra cycles do come at a cost). Only the silent/low-power consumption crowd gives a hoot about this.

    Boost clocking has always been opportunistic since its implementation. The only difference now is that GPU manufacturers have been pushing their silicon much closer to the edge of stability and thermal envelope. There’s little to no overclocking headroom. It isn’t really shocking that boost on modern GPUs fall back after 30-minutes or 1 hour of load-time.

    DirectX9 is pretty much irrelevant for current and future software platforms. Windows 7’s death will accelerate its deprecation. We have seen this happened time and time again when the software ecology undergoes a paradigm shift.


    Multimonitor seems to have less problems on some HBM cards, but it also depends on which card you buy from what manufacturer, and what monitor. That said, there still is clockspeed jumping on GDDR cards at high refresh rates, monitor switching 1 to 2 for no reason, and display mix incompatibility that depends on what card and what monitor. It’s a TOTAL MESS, unless you are using hardware closely compatible. Just because YOU don’t have major problems, doesn’t mean it isn’t broken or other people aren’t having issues. AMD is shooting themselves in the foot by ignoring it.

    What you think about Dx9 is irrelevant. Both AMD and Microsoft are fully supporting it with no EOL date. There was a rumor that AMD was going to drop Dx9, but that was directly debunked by AMD themselves.
    There are a lot of developers still actively using it, and you can’t ever drop support or it would break games. It’s a really ignorant argument to make, especially when you are ignoring AMD’s own words on supporting Dx9. Dx9 today isn’t even using the same driver model of XP, as it was upgraded by Microsoft. There are a lot of indie developers who stick to it for various reasons, as they don’t need dx11, and this was pointed out during the now debunked controversy. This isn’t a question of Dx9 being “dead”, it’s a question of Nvidia beating the SNOT out of AMD in terms of having proper drivers, meaning more people will stop buying AMD.

    These edge case arguments aren’t even relevant to the other issues either. It’s a huge mess of everything not working how it should and being unstable, no optimizations / features being added like VRS, while AMD is instead putting work into revamping the UI in ways that break the drivers more than the old UI. Nobody asked for a new UI, we wanted better drivers and working features that AMD claims to support in hardware.

    This vBIOS thing just shows how stupid AMD is running their GPU dept. It’s going to be more problems for the manufacturer than the consumer, but it ultimately was AMD’s screwup that should never have happened in the first place. AMD is just winging it at this point.

  3. 5600XT debacle is just AMD’s version of Nvidia’s GTX 260 debacle back in the day. They both hastily re-spec the model at the last minute due to sudden competition. The launch units got screwed over completely. Honestly, AMD should have not bother with BIOS flashing “upgrade” and simply launch the first wave of units as is. They should have just re-spec future batches and re-branded the original 5600XT spec to “5600LE”.

    I got a multi-mointor setup with mixed panels they have adaptive sync capable and there are no driver related issues to it. It is just stupid Windows 10 DWM related bugs that only happen when waking-up from suspense/sleep (DPI scaling gets mess-up). Re-opening the applications addresses it.

    Directx 9 is dying my friend. It is almost 20 years old. The official EOL of Windows 7 is the final nail in the coffin. Developers are going to start dropping it hard if they haven’t done so already. Directx 6-8 faced the same music back when NT 5.x ecology finally sunseted. DX9 will be regressed to legacy status on future platforms.

  4. You need to watch GamersNexus, who has done multiple kid glove call outs of these problems. The latest one talks about how these vBIOS updates are untested, unsafe, out of spec, and will generally cause mass RMAs. This is NOT “working fine”, or acceptable practice. AMD pushed this update out during the Holidays, the factory workers are off, and users are going to get broken hardware with untested/unvalidated vBIOS.

    Dx9 still exists, AMD isn’t dropping it(debunked rumor), and there are plenty of really STUPID developers who are dead set on sticking with 32-bit/dx9, even though NOBODY is using the actual hardware/OS for it. Regardless, Dx9 support is a must for anyone still wanting to play older games like witcher 2. Either way, if linux developers can write a wrapper better than AMD’s native dx9, there’s a problem. Hell, it’s not even limited to dx9, since AMD still hasn’t updated their dx11 drivers to fully support hardware features like variable rate shading. There still is no compatibility mode for VRS 2.0 games.

    No, multimonitor isn’t fine. Maybe under certain niche conditions like dual same type AMD validated panels, but when you start mixing 1440p freesync using DP, and 1080p/60 with HDMI, everything F-ing breaks. This has NOTHING TO DO WITH OVERCLOCKING, and neither does any of the GPU throttling issues plaguing 5700 owners. AMD simply doesn’t have proper driver QC, nor are they using universal bug fixes. When AMD fixes one problem, it isn’t universally fixed across the board, and the ensuing chaos is unacceptable.

    I can give multimonitor gaming a pass, since it’s rare, but single monitor/factory settings are still broken. People are still getting BSODs, error messages installing updates, black screens, crashes, ReLive not working, GPU throttling issues, etc. The forums are CHOCK FULL of complaints. This is not standard procedure, even for AMD, since last years drivers were vastly superior. These problems started popping up with the VII/5700 cards, and got massively worse since 2020. It’s so bad, mainstream review outlets are pointing it out, since it affects their benchmarking. Take your head out of the sand, read the forums, and watch some reviews talking about it. It’s a total mess.

  5. Stupid, stupid issues have been going on since forever on both camps. Fanboys make mountains out of them and use it as fuel in their petty flamewars. Most users just don’t realize how complicate the hardware and software that drives modern GPUs. It is more of a surprise that aren’t more serious issues. Newcomers are just spoiled rotten. They never touch or used graphpical hardware/software that was truly broken (S3 Savage, NV40’s Purevideo, AMD Rage Maxx, Voodoo Rush etc)

    Multi-mointor works fine and power-saving works on both camps. Most of the reported issues are actually from inexperience/notice users who try to overclock their GPUs without fully understanding the consequences and cry foul when it burns in faces. It probably doesn’t help that factory overclock SKUs are effected by it. The whole 5600XT mess is going make it much worse for cards that were already made/distributed into channel.

    DirectX9 is being depreciated. The same thing is happening on Nvidia camp on newer hardware platforms. Nobody except a vocal minority gives a hoot about it. DX6-7 era stuff suffered the same fate back when XP finally sunseted. It is the nature of running legacy software on modern hardware platforms. That’s why remastering/VMs/wrappers exist. The problem will get worse with post-Navi and post-Ampere GPU designs.

  6. An intermittent black screen or loss of display may occur when the system is left idle at desktop.

    Just look at all these problems that didn’t exist until recently, and they’ve existed for months. The entire 19.9 series caused BSODs, then the 20 series broke ReLive and caused black screens. There is a severe lack of QC going on in the driver dept. AMD is releasing garbage, the community is beta testing, and AMD doesn’t admit problems until AFTER they’re fixed a month+ later. AMD is wasting resources reworking their control panel into something worse, when the real problem was drivers to begin with.

    Also, DX9 performance is so garbage that using a linux dxvk wrapper improves performance by 30+ FPS in DX9 games, not to mention certain driver features are not fully compatible depending on DX version. DX9 also severely mipmaps textures like a 256mb card, and still turns off bump mapping in old games unless you shine a light source directly, which is a decade old optimization cheat. (farcry/Halo/etc)

    Don’t even bother with multimonitor, since AMD gave up years ago, and you never know what will go wrong. Your GPU could be running full throttle at the desktop, power use might spike and short your PSU, Freesync might disable if 2nd monitor isn’t freesync, 1rst and 2nd monitor will randomly switch and you can’t easily fix it, etc.

    Who knows at this point what will go wrong. It seems like bugs are getting fixed, but the real problem is new bugs keep getting introduced and that shouldn’t be a thing. Drivers shouldn’t ever be this unstable and broken. It’s better if AMD would slowly introduce features after fully testing them, but then we’d be back to “fine wine” taking a year to get optimizations, although what does that matter when AMD isn’t implementing real optimizations anyway? DX9 performance sucks, Variable Rate Shading isn’t enabled for games that use it, and AMD is deliberately ignoring PTGI as a raytracing alternative.

    AMD cards support a LOT of good features *in hardware*, but none of them are being used, most likely because AMD is deliberately ignoring all of them in favor of 1:1 Nvidia compatibility in next gen hardware, screwing existing AMD users. It used to be worth buying AMD, but not at this point. Drivers are broken, and we’re not getting proper feature support. You can’t even get stable clockspeeds/fps, since AMD’s powersaving algorithms are both too aggressive and often literally broken via bugs. Instead of making clockspeeds more stable, AMD is constantly adding new powersaving features that introduce more bugs and unstable performance, which is totally unacceptable for people who want stable performance in games instead of powersaving.

    Even if you wanted to buy a 5700XT for “powersaving” desktop use, multimonitor is broken, video playback is severely pixelated/BLOCKY, and video recording codecs are buggy/broken. Not to mention who knows what else is broken, since the entire 5700 series is plagued by bad drivers, broken bios, improper coolers (msi), etc. Asus even had a problem where the cooler was too heavy for the spring tensioned screws, and over time increased thermals.

    AMD products are now a severe niche product where you can only use them under certain conditions where the drivers/hardware work (if you’re lucky). If you use AMD cards outside of these conditions, nothing will work properly, and some of these problems are due to poor 3rd party hardware flaws. At least with freesync 1.0, the monitor specs were published and you could avoid bad hardware, while the AMD cards themselves are a lottery of problems. That doesn’t even stop at video cards, since AMD motherboards are also plagued by poor bios and improper design even at the high end. BUYER BEWARE is pretty much the #1 issue for any AMD user.

  7. The early Radeon RX 5600XT cards that are using the same PCBs as Radeon RX 5700 may be more easily overclocked than the ones that have custom designs tailored for the lower power draw and lower clock speeds that Radeon RX 5600XT was originally supposed to have. Given that some 5700 cards can be overclocked to 5700XT levels, I wonder if the transitive property may apply to push some golden 5600XT cards up to 5700XT clock speeds.

Leave a Reply

Your email address will not be published.

Nathan Wasson

Inquiring mind, tech journalist, car enthusiast, gamer.