Google Kind outcomes, collected by u/ofesad, who granted us permission to share his outcomes, present quite a few failures sharing the identical CPU batch/lot quantity. This highlights probably unhealthy batches from AMD, however we predict it’s extra seemingly a BIOS subject.
Different customers declare they “revived” their seemingly lifeless CPU by downgrading to a earlier BIOS, and ASRock despatched two customers a then-unreleased BIOS that resolved their points, however requested them to not share it.
If these points hold occurring and AMD and ASRock can’t resolve it, we’ll do first-party, hands-on testing with a number of the boards and CPUs that is perhaps affected. However we predict it appears like they’re attending to a solution so we’re going to watch the state of affairs as a result of it appears fairly near a decision. This seems to be a pair potential points. BIOS is unquestionably considered one of them. We’ll additionally discuss in regards to the batch factor, which appears a little bit shaky.
We’ll be capable of use this piece later if ASRock and AMD can’t resolve the state of affairs. This story gives a fast recap. We’ve compiled all the data we might discover on the market to date on the precise points and failures so that you just’ll have the entire proof. If this helps you analysis any points that you just’re operating into then we’ll additionally current a few options we discovered or we’ve thought up.
We’re making this as a result of we compiled the entire analysis for it however we haven’t performed a first-hand testing deep dive on it but as a result of we’re mainly at a stage the place we’re making an attempt to determine if that’s needed. It is a new method for us, the place we’re compiling all of our analysis and we’re simply going to place it on the market and hopefully it helps somebody. Likewise, hopefully a number of the people who find themselves operating into issues with this subject would possibly contact us with potential leads on the place to go subsequent.
That is additionally Tannen’s first analysis piece and he’s performed an important job compiling every part, digging by means of the boards, and placing collectively this report back to share with you all and to hopefully assist some people who find themselves operating into this. We plan on following up on this as we study extra. It might be contained to simply {hardware} information, but when lots of people inform us of potential leads then it could be potential that we revisit this with hands-on testing.
Defining the problems
Failures in any CPU line occur, however Intel’s latest points have been uniquely unhealthy. We don’t see that too typically.
The 9800X3D that famously exploded on Reddit a couple of months in the past can also be in latest reminiscence, however after performing some forensics on that one, all proof pointed towards crushing the socket at an angle and never being appropriately oriented when the clamp was closed. That CPU additionally died instantly and earlier than the consumer was ever capable of boot, additional reinforcing that 12V shorted to floor as a result of it simply died on boot.
These ASRock and 9800X3D failures are completely different: They’re occurring typically months into use, which means that the programs did work, however stopped spontaneously.
Typically, CPUs are among the many most secure parts, and so it’s simple for the story to run away with the social media cycle — however dozens of failures on one platform in a comparatively brief time span does trigger questions.
For perspective, although: Retailer Mindfactory alone has offered over 20,000 9800X3Ds, main us to estimate the worldwide items offered are within the a whole lot of 1000’s.
There’s a really small probability of experiencing these points your self, even when you’re utilizing a 9800X3D and ASRock motherboard. Each the variety of reported failures and ASRock’s seemingly greater incident price each stood out to us.
The Drawback
Right here’s what’s happening: Some consumer programs with a 9800X3D are capable of POST, or power-on self-test, and run as anticipated. The time till failure ranges from underneath an hour to three months. These with debug shows encounter a “00” error code, which generally signifies a CPU downside.
There appears to be two root causes: First is a potential unhealthy batch of CPUs from AMD; second seems to be ASRock BIOSes inflicting issues with system boots in addition to motherboard settings probably resulting in probably unstable CPUs.
One of many issues we got here throughout right here was a possible for voltage that was too low, which shouldn’t damage something. It simply wouldn’t be capable of boot. In order that’s truly excellent news as a result of meaning you don’t must, hopefully, fear in regards to the CPU exploding. That has occurred up to now.
One problem is that there are some lifeless CPUs on the market with burn marks. At the moment, the analysis we’ve been capable of do makes it unclear how related these points are. We simply wish to be very clear about that. Proper now, it’s unimaginable to distinguish with our present analysis between these potential failures with out some extra hands-on testing. We’ll hold monitoring to see if we have to extra aggressively herald parts for testing, however with the tempo ASRock has been engaged on this, we suspect they’ll hopefully have a repair earlier than we might root-cause it for the reason that lab workforce is bogged-down with different failure evaluation proper now.
Unusually, we additionally seen that many customers be aware their boards work high quality with different processors both previous to or after their reported 9800X3D failures.
Findings Between All Studies (Trigger Unclear)
Let’s get into the causes of failure we discovered throughout the posts.
All reported failures produce the identical preliminary signs of failure, making it difficult to determine the supply. Including to the complexity, not everybody utilizing a 9800X3D and ASRock motherboard experiences failures. We’ll begin with findings from all failure sorts earlier than protecting particular circumstances the place the origin is extra simply identifiable.
Within the pattern report of 42 9800X3D failures on the time of writing, the boards affected embrace: 34 ASRock, six ASUS, one Gigabyte, and one MSI. Chipsets embrace: 30 X870s, six B850s, 4 B650s, and two X670s. It seems to be distributed throughout a number of chipsets and a number of motherboards however the distribution appears to match what folks have a tendency to purchase proper now. Failures occurred on BIOS variations: 3.11, 3.15, 3.16 , 3.17 (beta), and 3.18 (beta), although it’s unclear if failures have been essentially attributable to these BIOSes. For the time earlier than failures: six weren’t specified, 15 occurred in every week or much less with 4 of these occurring in lower than a day, 14 happened within the vary of 1 week to 1 month, and 7 took over a month earlier than failing.
Additionally, 4 listings report the CPU displaying burns or markings, which is what caught our consideration.
Concern 1 (BIOS Boot points)
It’s exhausting to parse what is perhaps inflicting these particular burns versus every part else so we’ll begin with BIOS points.
Not less than 4 customers mounted their presumably lifeless 9800X3Ds by flashing again BIOS to a earlier model, which suggests the CPUs weren’t lifeless, and two remedied their points by updating to a “particular” BIOS despatched to them by ASRock.
u/Flaringup seen failure after updating to BIOS 3.16. u/Eldaroth skilled the problem after updating to BIOS 3.18. u/Fancy_Potato1476’s system malfunctioned shortly after putting in Home windows with the motherboard operating 3.15 out of the field – turning the pc into a really fancy potato. This was additionally the identical BIOS u/Kojac4323 was utilizing when he encountered failure.
These consumer experiences point out failures usually occur after a BIOS replace and recommend variations 3.15, 3.16, and three.18 could trigger boot points.
Three of these customers claimed a BIOS flashback to an older 3.10, 3.11, or different outdated variations resolved their subject.
Consumer u/Eldaroth defined {that a} 3.10 flashback didn’t instantly resolve the issue, however after a second try at a 3.05 flashback, Eldaroth was capable of “revive” the system. From there, the consumer flashed again to newer BIOSes and located 3.10 was the most recent possibility working for the construct.
This means that the problems is probably not killing the CPUs (apart from those with the scorched marks, however that’s a special story), however that it could be a boot subject. The hope could be {that a} botched BIOS is simply inflicting points booting and never inflicting any harm to the CPU itself. It’s uncommon for a BIOS to break a CPU, however it could possibly occur. We noticed that with ASUS beforehand on the 7800X3D, which is why everyone seems to be so delicate to this subject.
On the time of penning this, we haven’t noticed any 9800X3D boot points occurring on BIOS 3.10, probably establishing it as probably the most secure possibility at present. Customers who reverted to three.10 reported their programs being mounted.
As for the customers who acquired a BIOS from ASRock: Based on one, ASRock acknowledged, “Connected is the brand new BIOS. Please don’t unfold this but. It should most likely be launched quickly. This BIOS will not be associated to the dying CPUs. However it could possibly assist with another boot subject. In case you can strive it that will be nice. After the replace, please keep in mind to provide the system a couple of minutes to see if it boots.”
That’s seemingly a reminder that reminiscence coaching may also seem like a boot failure. Particularly in some configurations, reminiscence coaching can take 5-10 minutes in some conditions.
The opposite consumer with the brand new BIOS claimed: “ASRock confirmed to me that 3.18.MEM03 that they offered to me will increase the voltage to 1.2V for the 9800X3D and that enables it besides and repair the 00 debug code. The problem is that not sufficient voltage was utilized for some 9800X3D items and it was not secure.” Each customers reported this BIOS resolved their state of affairs.
This is able to be higher than the likelihood that it was overvolting the CPUs, which might be the one seemingly means the BIOS would truly inflict harm to the CPU. Too little voltage seemingly received’t damage, however it’d even be unstable. If so, then this could be one of many higher failures to have.
On February twenty fourth, ASRock launched a beta BIOS 3.20 with the outline stating, “Enhance minority proportion of AMD 9000 collection CPU boot subject.” We assume this was the identical BIOS beforehand despatched out to these choose customers.
To be clear, BIOS updates received’t “revive” a actually lifeless CPU, however they will probably resolve boot points inflicting your CPU to seem as lifeless. We expect some customers experiencing boot points and concluding it’s a lifeless CPU would possibly’ve partially contributed to ASRock’s disproportionate CPU failures, and truly what they may have been seeing as a substitute was simply that it wasn’t booting with out the CPU being lifeless, although we will’t fault the customers for believing that.
Concern 2 (CPU Batch Failures):
Transferring on to the failures probably attributable to a foul CPU batch.
As seen within the “9800X3D fails” Google Kind outcomes, out of the 9 customers who included their CPU’s batch/lot quantity of their response, seven are from batches CF 2443PGY or CF 2442PGY.
However keep in mind that this might be utterly coincidental and doesn’t essentially assure unhealthy batches. We at GN have CPUs from each of those batches and so they’re high quality. There may be numerous coincidence right here: AMD’s 9800X3Ds have been in excessive demand and so they haven’t been out too lengthy but. We don’t know what number of batches there are, however we wouldn’t assume it’s a loopy quantity. Likewise, folks experiencing any sort of failure, whether or not that’s attributable to the board or the CPU, could be seemingly on the same batch in the event that they’re all constructing and shopping for across the identical time.
We wouldn’t definitively state that there’s a unhealthy batch, however it’s nonetheless price exploring and contemplating in case this develops and extra folks report failures from these batches. CF 2443PGY and CF 2442PGY could be the two codes to concentrate to.
In these seven responses of the exploded CPUs, the motherboards embrace: three ASUS, two ASRock, 1 Gigabyte, and 1 MSI, illustrating an anticipated distribution of failures. ASUS is the most important vendor by market share.
Concern 2 – How one can determine the batch quantity / do some primary checking
If in case you have a positively lifeless CPU and also you wish to examine the batch quantity, right here’s the way to determine it. That is additionally helpful for guarantee claims.
The CPU batch quantity may be discovered within the picture above, outlined in purple. The batch quantity begins with two letters, which we consider to point CPU stepping.
As defined by u/rigred on Reddit, the letters are adopted by 4 digits specifying the 12 months and week the CPU was manufactured, and ends with three letters specifying ATMP and wafer manufacturing location.
Within the case of the “CF 2443PGY” batch, these have been produced in the direction of the tip of October 2024 and assembled in Penang, Malaysia.
ASRock Response
There’s been one thing of an ASRock response, although as of penning this, they’re nonetheless investigating.
Present boot points are addressed by the corporate’s most up-to-date 3.20 beta BIOS, although its efficacy has but to be decided on a big scale.
ASRock Japan’s publish on twitter, which has been machine translated, states points happen after updating BIOS on already secure programs.
If we soar again to u/Fancy_Potato1476, largely as a result of the title conveys a sure opulence that we recognize, the flamboyant potato didn’t replace BIOS and nonetheless skilled boot points, seemingly contradicting ASRock’s declare. The ASRock publish additional explains:
“The problem is attributable to some older DDR5 RAM and sure reminiscence controllers on X3D CPUs, in addition to the impression of Agesa.”
The primary a part of that wouldn’t actually make sense as a result of if the system is working after which it stops working, that doesn’t actually hyperlink as much as RAM that was secure after which simply all of a sudden wasn’t, however what would possibly join it’s the Agesa half, which is the binary that AMD distributes that’s a part of the BIOS and that will have an effect on reminiscence conduct. So if there’s any reality to that assertion, then it’s the Agesa half that’s key.
When requested if it’s AMD or ASRock who’s accountable, the corporate acknowledged by way of translation, “It’s attributable to a really particular mixture of parts.”
The publish ends by repeatedly expressing, “Do NOT replace the BIOS if it’s operating stably.”
Typically, we’d agree. Nowadays, new BIOSes can provide necessary safety patches; nonetheless, broadly talking, we want not messing with BIOS if every part is working properly and there’s no sturdy safety purpose to.
Conclusion
It appears like a mixture of points. There’s positively a BIOS downside. There’s probably an issue with the voltage being too low, which is inflicting inoperability at tried boot that shouldn’t hurt something bodily, in order that’s a great downside to have so far as issues go. There’s additionally a possible unhealthy batch subject. The BIOS subject might have a number of sub-issues, together with too excessive voltage. Some customers reported extreme VSOC by way of HWINFO, however these numbers aren’t all the time correct and ought to be double-checked with bodily measurements.
Some basic recommendation for anybody operating into issues like this: First, you’d wish to rule-out reminiscence coaching on preliminary boot. AMD programs, particularly, could require extra time to finish reminiscence coaching the place it’s primarily tuning your reminiscence timings. Reminiscence coaching usually solely occurs on the primary boot. This shouldn’t take over quarter-hour with a brand new configuration and will end a lot quicker for configured programs.
For these utilizing a 9800X3D on an ASRock board, we’d observe ASRock Japan’s suggestions of not updating BIOS until one thing seems unstable.
If one thing does seem off, we’d advise a flashback to model 3.10 or 3.11 if 3.10’s unavailable. These seem like probably the most secure variations of BIOSes in relation to the boot points. We’d briefly maintain off on updating to the most recent 3.20 beta BIOS (until you have got points already, wherein case you need to simply replace) primarily as a result of it’s extraordinarily latest, and beta BIOSes are usually much less secure.
Use Flash Again when you already are on an unstable BIOS. This enables a BIOS flash with out stability of the platform by way of a USB key.
In case your system’s failing to publish after beforehand working, we’d first suggest inspecting the CPU for any markings earlier than going ahead. We’d additionally advise checking your batch quantity at this level whereas your cooler’s uninstalled.
For the handful of customers with one other appropriate motherboard, we’d recommend utilizing it to check your CPU’s skill to publish. This is able to decide whether or not your processor’s lifeless or if there’s a boot subject. In case your CPU’s unable besides within the secondary motherboard or when you don’t have entry to 1, we’d advise flashing again to BIOS 3.10 first, then 3.20, and eventually 3.05, in that order. After every flashback, give your system a couple of minutes earlier than making an attempt besides. If any of those resolve your subject, we’d recommend staying on that model.
If these choices don’t go anyplace, you’re sadly left with returning the components to the retailer when you have a guaranty or going by means of an RMA with AMD. Fortunately, we haven’t discovered any claims rejected and have noticed RMAs accredited lower than 24 hours after submission.
In case you’ve skilled a failure with considered one of your parts and also you don’t assume it was one thing that we’ve already coated, you need to e-mail us at [email protected]. Conversely, if it’s one thing we’ve coated and we’re simply not performed but, like with this story, for instance, then tell us and we is perhaps concerned about shopping for parts. We’re additionally doing an RMA rescue collection on our GNCA channel, the place we’re mainly shopping for folks’s failed parts after which pursuing the RMA as a substitute of them having to undergo the method of getting to do it in order that we will take a look at a producer’s guarantee course of with an precise failed element from an finish consumer.
Transferring ahead, we’ll hold following this story if something develops additional.
