Software Bug Lets You Overclock AMD's 5800X3D to Death In Seconds

AMD Ryzen 7 5800 X3D in motherboard socket
(Image credit: Tom's Hardware)

Igor's Lab has discovered a major glitch in the MSI Center Windows app that allows AMD's best CPU for gaming, the Ryzen 7 5800X3D, to be overvolted and overclocked beyond its limits. At first glance, this looks like a win for enthusiasts and overclockers. However, the application bypasses all artificial voltage and clock speed limitations altogether, turning this into a real danger for imprudent 5800X3D owners. To make matters worse, this issue was also discovered in Asus, Gigabyte, and ASRock software, marking this as a platform-wide issue.

Igor of Igor's Lab was able to demonstrate the danger of this bug with his own 5800X3D. After overvolting the chip to 1.3v and beyond with MSI Center, the 5800X3D reportedly died almost immediately. We don't know how the chip died specifically, but apparently Igor pushed the core voltage past 1.3v after two manual adjustments. The PC immediately shut down after the second voltage adjustment and never booted back up.

For the uninitiated, AMD's Ryzen 7 5800X3D is the first CPU to feature AMD's game-boosting 3D-VCache technology. The tech adds a 64MB slab of L3 cache right on top of the Zen 3 die, boosting the chip's L3 capacity to 96MB. However, this additional L3 cache severely affects the CPU's heat dissipation, forcing the chip to operate at lower frequencies.

The problem is significant enough that AMD previously blocked overclocking of the chip entirely and reduced the maximum core voltage from 1.5v down to 1.35v. AMD says the voltage restrictions are due to voltage limitations of the added cache, however,  our testing indicates that the limitations almost certainly have something to do with the chip's heat dissipation issues.

To verify Igor's discovery, I went into MSI Center on my personal rig — featuring an MSI B450 Pro Carbon AC and Ryzen 7 5800X3D, and found the same unlocked capabilities in the "User Scenario" sub-section. I found the manual core voltage can be increased as high as 1.55v, and the core multiplier is completely unlocked. I didn't find out what the multiplier limit was, but I was able to input a multiplier number of 80 (for 8GHz).

5800X3D Multiplier Set to 80 - or 8GHz (Image credit: Future)

Of course, I didn't apply any of these settings because I would like to keep using my CPU. However, based on the fact I can input these settings at all, without any limitations or greyed-out tabs does verify this is a big problem.

We have no deadline for a possible fix, but we are confident AMD will get to the bottom of this as soon as possible -- especially since YouTuber Der8aur killed a 7950X3D while fiddling with similar settings less than two weeks ago. 

Whether the fix will come in a new AGESA microcode update, chipset update, or software-side change is unclear. For now though, if you own a Ryzen 7 5800X3D, just be cautious when rummaging around your motherboard's overclocking software, and don't tweak any overclocking settings.

Aaron Klotz
Contributing Writer

Aaron Klotz is a contributing writer for Tom’s Hardware, covering news related to computer hardware such as CPUs, and graphics cards.

  • Makaveli
    this is a good PSA.
    Reply
  • TerryLaze
    Admin said:
    A glitch in seemingly all motherboard software has been found that allows AMD's locked Ryzen 7 5800X3D to be overclocked well beyond its capabilities.

    Software Bug Lets You Overclock AMD's 5800X3D to Death In Seconds : Read more
    Of course, I didn't apply any of these settings because I would like to keep using my CPU.

    Wus!
    Do it! Do it!

    You can write it off on your taxes as business expenses.
    #notLegalAccountantAdvice
    Reply
  • setx
    What you entered absurd multiplier into GUI without even applying means... exactly nothing! Even if you applied that it's not dangerous as multiplier can't kill the CPU. (And CPU likely would just ignore that.)

    Applying voltage/power/temperature beyond practical limits is a serious issue though.
    Reply
  • DingusDog
    Might want to proof read the very first sentence of your article. Maybe it was AMD's best CPU for gaming but is it still? Think about it for a minute.
    Reply
  • TechyInAZ
    setx said:
    What you entered absurd multiplier into GUI without even applying means... exactly nothing! Even if you applied that it's not dangerous as multiplier can't kill the CPU. (And CPU likely would just ignore that.)

    Applying voltage/power/temperature beyond practical limits is a serious issue though.

    Actually this is not always true. Most overclocking applications either grey out or lock out any voltage or multiplier inputs that are out of bounds from the CPU's requirements. Before you hit apply.
    Reply
  • rluker5
    Sounds like it could be handy to up the multiplier without increasing voltage.
    Reply
  • bjnmail
    Not at all surprising. This is why I never install any of the motherboard vendors' tuning software on my own or clients' systems, as they have all been prone to this for ages. The UEFI has limits imposed, but the software ignores them and sets the values directly, which can lead to exactly these chip-killing issues.

    Obviously some daring overclockers will have fun with this, assuming raising the multiplier actually takes effect like the voltage does, but regardless, it could lead to some slight improvements in performance if you're conservative with settings (or don't touch the voltage at all).
    Reply
  • razor512
    setx said:
    What you entered absurd multiplier into GUI without even applying means... exactly nothing! Even if you applied that it's not dangerous as multiplier can't kill the CPU. (And CPU likely would just ignore that.)

    Applying voltage/power/temperature beyond practical limits is a serious issue though.
    I think it may be fear of applying any change when the software is buggy. For example if someone's CPU died when the software was set to 1.3V even though the chip should handle 1.35V, there is a chance that what is being applied may not be what was specified in the GUI.
    Reply
  • Avro Arrow
    I don't understand what all the fuss is about. AMD has stated over and over that the R7-5800X3D is not supposed to be overclocked.

    So... someone overclocks a CPU that doesn't support overclocking and it dies.

    My response to that is "Ok...and?".
    Reply
  • TerryLaze
    Avro Arrow said:
    I don't understand what all the fuss is about. AMD has stated over and over that the R7-5800X3D is not supposed to be overclocked.

    So... someone overclocks a CPU that doesn't support overclocking and it dies.

    My response to that is "Ok...and?".
    The fuss is that any normal modern CPU, for many years now, has protections build into the chip itself so that even if you put the settings to something insane the CPU will still adjust itself and not burn out.
    At least not immediately as soon as you press the button.
    This isn't just a software bug, it's a bad CPU.

    This is how a modern CPU should react to stupidly high settings.
    jv3uZ5VlnngView: https://www.youtube.com/watch?v=jv3uZ5Vlnng
    Reply