Radeon Software 19.4.1 splats bugs and stays the course

Amid all the excitement about upcoming products, it's easy to forget that the day-to-day business of supporting all that hardware must continue. On that note, AMD just released Radeon Software version 19.4.1. This is—as the version number indicates—the first Radeon driver release in April, and while there aren't any big-ticket items like game-specific support, there are still a few fixes to appreciate.

You can bet some multi-sampling was used in this WoW screenshot.

Most notably, Radeon VII and Radeon RX Vega cards should stop crashing or hanging when you hook up three or more displays. Using multi-sampling in World of Warcraft should no longer crash the game. Mouse cursors should stop vanishing on Ryzen Mobile chips with integrated graphics. Also on the mobile Ryzen chips, AMD's Vari-Bright dynamic screen brightness feature should correctly respond to configuration changes now. Radeon WattMan auto-overclock, as well as the game World of Tanks ought to work on RX Vega cards now.

Issues hanging around in this release include screen flickering on multi-display setups on Radeon VII cards and while watching videos on an HDR display in the Netflix app. Also on the Radeon VII, WattMan's performance monitors may not read the correct values. Finally, using the Radeon performance metrics overlay may cause flickering when playing back protected content.

New to AMD's download site is the note above. This warning is interesting given that Nvidia's drivers for its latest cards require the 1809 release of Windows 10 to install owing to older versions missing support for DXR. It's possible that AMD could soon release a driver that likewise requires certain Windows updates, but for now, the release notes don't make mention of any such requirement.

You can, as usual, head to AMD's download site to read the aforementioned release notes or simply download the drivers. Here's a handy link to both for the Windows 10 64-bit version.

Comments closed
    • brucek2
    • 8 months ago

    As someone with 3 monitors hooked up, and [used to] play a lot of WoW, does this mean those Radeon cards would have been useless to me all this time? Haven’t they been out for like months now?

    I never knew because my current card is nVidia, but holy smokes would I have been pissed off at AMD if I had gone the other way…

    I get that there are small bugs all the time, but to me at least those both sound like major card-is-useless / must return category bugs.

    • Zizy
    • 8 months ago

    Stop crashing on 3+ displays? WHAT???? That was one of the selling points of good old 5xxx cards. Now it took this current update to restore what was available for 10 years? Whoa.

      • DoomGuy64
      • 8 months ago

      Lol, yeah. I don’t even know if eyefinity works anymore since they hid the feature. So it either only shows up when you have 3 monitors, or AMD removed it. Bad idea AMD. People who don’t know whether or not you support the feature aren’t going to attempt it unless they already have 3 monitors. Not that AMD has any products capable of driving 3 monitors, aside from the radeon vii or crossfire which lacks support.

      I have a strong suspicion eyefinity has been dropped, or bare minimum AMD is de-emphasizing the feature. Either way, the new control panel still lacks functions compared to CCC, and annoyingly removes desktop features from mobile.

      Whatever. This just means AMD really is giving up the high end to Nvidia.

    • Zizy
    • 8 months ago

    Multipost…

    • Zizy
    • 8 months ago

    Multipost…

    • Zizy
    • 8 months ago

    Multipost…

    • tay
    • 8 months ago

    My Radeon wattman is still buggy. I have a 470 that I can’t undervolt or under clock because wattman detects something went wrong. Which it could,but this only happens on reboots. Annoying.

    Guess who’s getting nGreedia next time.

      • R-Type
      • 8 months ago

      You know, AMD designed and built the damn cards. It’s not like it should be so hard for them to figure out how to control the logic. Regardless, the base driver stack has improved significantly over the last year.

      • NTMBK
      • 8 months ago

      Have you considered that maybe your undervolt isn’t 100% stable? There is a reason why AMD chooses their stock voltage, and it’s not because they hate efficiency…

        • DoomGuy64
        • 8 months ago

        470s aren’t 480s for a reason, they are defective silicon, and Nvidia does the same. Throw in OEM redesigns and custom firmware changes, and you get all sorts of random issues, which is why it is important to only buy products that have been review verified to work how you plan on using it.

        Even if it was a bug, we still have MSI afterburner that works better with older cards, making complaints like these rather petty. Especially since it isn’t a game breaking issue.

        That said, I will say from past experience with a 390, AMD puts older cards power efficiency on low priority vs stability, as multi-monitor will disable several low power modes, and requires manual intervention to implement. Their official response to complaints was that is how the hardware works, but considering that you can still manually adjust it and it works, the official excuse was a lie to justify eliminating efficiency modes on the 390 for any scenario outside single monitor. Considering that very few users notice, fewer complain, and not a single tech site has written about it, I’d say AMD has easily gotten away with breaking features, and it even increases sales when knowledgeable users get fed up and buy new cards.

        Nvidia does the same, but with driver optimization and limiting hardware specs to obsolete faster. Like the 3GB 1060, and Kepler’s driver performance in newer games vs Maxwell. (960 beating the 780) The 470 will easily outlast the 1060 3GB for sure. You just have to ask yourself which trade off is less annoying, and I’d say AMD is far less troublesome for general use. Especially with MSI afterburner. Users can’t fix Nvidia’s methods of planned obsolescence.

        • tay
        • 8 months ago

        Haha fair enough, but even the smallest tweak will be fine when running games and FurMark, or even waking from sleep. A cold-boot and Wattman resets all the settings.

        Argh! Anyway, R-Type pointed out a possibility that I hadn’t considered.

        • ptsant
        • 8 months ago

        I don’t think this is the most likely explanation. Because that would happen DURING load, not at boot. If the poster can play long sessions with undervolted/clocked settings then the hardware probably tolerates.

        Wattman has a function that detects abnormal shutdown (crash) and in that case resets default settings. My hypothesis is that, for some reason, every time you boot Wattman thinks it did not shut down correctly.

        A test that you could try is to shutdown wattman normally before rebooting and see if you still get the same message. Alternatively, you can try overvolting (without changing clocks), which should not destabilize the hardware.

      • rechicero
      • 8 months ago

      Have you tested your undervolt properly? It might be something is actually wrong and wattman detects it when rebooting…

        • tay
        • 8 months ago

        Hi, I had not considered this! Thanks for the reply, but this sounds like the most plausible explanation along with NTMBK’s point.

      • DPete27
      • 8 months ago

      For over a year now, I’ve had to restart in order for WattMan settings to apply properly. Nothing is right on cold boot.

        • synthtel2
        • 8 months ago

        I haven’t had quite that experience, but do have to open up WattMan momentarily after boot or the settings will sometimes de-apply or worse once I’m gaming (on a worn out RX 480 that isn’t quite stable at any settings).

        Edit to clarify – I suspect this is fundamentally the 480’s fault, not the drivers. It wasn’t a problem with a 460, and this 480’s various jank shows up in both Linux (AMDGPU non-PRO) and Windows.

        • Krogoth
        • 8 months ago

        Since 18.4s and onward, I had no issues with Wattman with my RX Vega 64. It only reverts back to factory settings when my system had an unscheduled/unexpected restart.

      • nexxusty
      • 8 months ago

      You’re incredibly stupid.

      Just go with nVidia, yup. Lol….

      • Puiucs
      • 8 months ago

      try a clean install.

      • maxxcool
      • 8 months ago

      Your modified card is unstable.. WEIRD! O.o .. i don’t get how AMD could be sooooo rude as to build a card that doesn’t operate correctly outside of the defined normal operating parameters…

Pin It on Pinterest

Share This