AMD EPYC 7002 Rome: CC6 Hang After About 1,044 Days

Confirmed erratum and scope

AMD’s Revision Guide for Family 17h Models 30h–3Fh, publication 56323 revision 1.03 (February 2026), includes erratum 1474 for the relevant EPYC 7002 (Rome) processors. After about 1,044 days since the last system reset, a core can fail to leave the CC6 idle state and hang. Spread-spectrum settings and REFCLK frequency can change the timing; this is not an exact uptime deadline for every server.

Workarounds

AMD documents rebooting before the projected failure time or disabling CC6. Dell’s matching advisory describes either a warm or cold reboot, and a BIOS C-state setting for its affected platforms. Use the server vendor’s matching BIOS/service instructions and an appropriate maintenance window. Disabling a power-saving state can affect power consumption.

The revision guide lists no planned fix for this erratum. That is the status of this specific erratum in the checked guide, not a statement that all firmware maintenance is unnecessary.

Corrections to the stored note

The source also repeats a social-media calculation of 1,042 days and 12 hours from a supposed 54-bit signed counter ticking every 10 ns. The checked AMD erratum does not establish that internal-counter explanation. Do not use the social calculation in place of the vendor’s approximate timing. The source’s claim that only a physical power cycle can reset the condition is also too strong: the documented preventive workaround permits rebooting.

The source’s broad affected-model list includes EPYC 7001 Naples (7551P/7601), Threadripper 1000/2000 (1950X/2990WX), first-generation Ryzen (1800X), EPYC 7002 Rome (7742), Threadripper 3000 (3970X) and second-generation Ryzen (2700X). This list has not been substantiated for erratum 1474 and must not be used as an affected-product list. Rome is Zen 2, not Zen+. Confirm the processor family, revision and vendor advisory rather than extending this Rome erratum to all Zen/Zen+ products released in 2017–2019.

Original case/reference: stored source.

Can't find an answer?

Upload a log for AI diagnosis, or ask the AI assistant directly in the console.