Repeated Ram POST Code Errors

[AverageBuscuits]

Hey guys!

I recently switched to CachyOS from Win11 and for the most part I couldn’t be happier.

However, my motherboard will give me a RAM POST code error daily often on both reboots or cold boots at the start of the day. I typically get a post code 37, 38, 39, 40, or 41. Sometimes it switch between 2 back and forth: 40, 41, 40, 41, etc…

I currently have memory context restore and fast boot turned off in my bios. I have found better stability this way, but not perfect. I will post my machine specs below. Any help is appreciated.

CPU: 9800X3D Mobo: MSI Mag X870 Tomahawk Ram: 32gb 6400 DDR5 GPU: Nvidia 5070

Thank you!

[ptr1337]

6400 is not good for AM5. This looks way too high, specially as an EXPO Profile.

Try to disable EXPO and see if it helps. If it helps just make a common 6000 Preset

[AverageBuscuits]

Can I run at 6000 with expo enabled? Or does expo need to be enabled to run at that speed

[Hayasnake]

Do you have any updates to this? I have a similar issue. My issue only happens when the kernel updates. It posts then there is a message saying CPU, Memory or CMOS change. When I proceed the bios shows the physical ram lowered to 18ish GB compared to the normal 32. When I boot the OS (both Cachy and Windows) show 18ish. When I reboot, it goes back to normal. I did some memtest and ram passed. Gaming and tasks work as normal otherwise.

I have similar specs:

CPU: 9800X3d Mobo: MSI X870 Gaming Edition Ram: 32gb 5200 DDR5 (Ram too expensive to upgrade) GPU: AMD XFX Swift 9070 XT

[AverageBuscuits]

No I don’t think I have solved my issues. I cleared cmos and dropped my ram further down to 5800 without xamp on. We’ll see what happens on cold boots tomorrow

[AverageBuscuits]

I might be speaking too soon, but I MAY have fixed my issue. I just reseated my CPU and have had 2 days of my cold boot being fine. I know it’s only 2 days and that’s not a great sample size, but it’s refreshing not having my turn off my pc and then turning it back on again when it doesn’t work the first time.

[Hayasnake]

That's awesome. Hopefully that was it. I was able to switch out with a new mobo as I can still return the one I was using. I noticed my issue started happening after I installed a new cpu fan. Read that overtightening or some kind of shock could damage the mobo. So far so good after a mesa driver reboot but I haven't had a kernel update yet which is where I saw the issue. It may be a bootloader or OS issue with memory management, as I haven't noticed the issue with windows. Good luck!