You are not logged in.
Hello,
I'm trying to track down a Hardware Error which seems to appear only once a Year (lol).
I wouldn't care too much but i had it happen on my old CPU 5600x over a year ago and a few months ago i also had it happen on new CPU (5800x3d) so i assume the CPU isn't the issue.
Ram has been tested a lot with all sorts of Memtest, Testmem, Prime, Y-Cruncher (pretty much all the stuff). And so far i wasn't able to reproduce the issue. I even investigated if it might be related to "too low idle voltage" but even when undervolting my CPU (setting CO to -20) i can't provoke that error. It seems to be a so called "silent machine check" since the Error both times was "Correctable" and i wouldn't have noticed the error if i wouldn't check out my Journal regularly.
However since i want to know what might be the cause of that issue and to be able to collect more information on this i installed Rasdaemon (as the arch wiki suggests)
Though what kinda confuses me after the Installation is that it doesn't seem to do much more than the Journal itself? I asked chat-GPT to show me how a detailed information with rasdaemon would look like after a MCE occured and it seems to contain pretty much the same as the Journal. So i wonder is there actually any reason to have it installed? And how helpful can it actually be to track this down? And how would you approach this to get some more information in case it happens again? I'll post the Error below (just in case it is helpful). Keep in mind pretty much the same Error already occured on a different CPU so i doubt that the CPU might be the Issue here.
[Hardware Error]: Corrected error, no action required.
[Hardware Error]: CPU:1 (19:21:2) MC16_STATUS[Over|CE|MiscV|-|PCC|SyndV|-|Poison|Scrub]: 0xca770d037f8097eb
[Hardware Error]: IPID: 0x0000000000000000, Syndrome: 0x0000000000000000
[Hardware Error]: Bank 16 is reserved.
[Hardware Error]: cache level: L3/GEN, tx: GEN
Last edited by Oddwierdo (2024-09-02 12:49:49)
Offline
I have a 5700X CPU and these "Bank X is reserved" has happened 6 times in 13 months, all on CPU:1 and three of them were about bank 21. It seems to be an AMD-only thing.
Offline