First build but get C5 error on boot

Associate
Joined
8 Mar 2013
Posts
27
Hi all, I am getting an odd error (C5) when I turn the PC on. It seems to be a RAM issue and was wondering if anyone has stumbled upon this or knows how to resolve it?

Motherbard: ASUS B650E-E
RAM: Corsair Dominator CL30 6000
CPU: AMD 7800X3D

I tried different RAM slots but get the same. Going to try a BIOS update next.
 
A google of this error suggests you try:

1. Run with one stick in the correct slot for one stick (usually the second from CPU).
2. Clear cmos.
3. After it boots, shut down.
4. Put the second stick in.

Remove all devices from USB ports (maybe they had something in the flash port?).

Make sure the sticks are fully seated, apparently this is trickier than it seems and one side can be seated more easily than the other?

Wait for longer (someone mentioned it took an hour on first boot :confused: :o ).
 
Thanks all, I did a CMOS reset and waited for a while and the error code disappeared. It could have been that but I did take the RAM out and put them back in again. Successfully updated BIOS too. Now windows install.

Thanks again all :)
 
Hi
Just built my upgrade and got the ç5 error .my mobo is asrock x870e phantom gaming just reset CMOS and took a stick of ram out . See what happens
 
Hi
Just built my upgrade and got the ç5 error .my mobo is asrock x870e phantom gaming just reset CMOS and took a stick of ram out . See what happens
What model motherboard exactly do you have and what slots do you have the ram in?
 
Last edited:
Hi .
I have the asrock 870e phantom gaming and my ram is in slots 2 and 4 . I'm Having another go today . Just hope my components are all ok
 
Wow . Finally up and running got both sticks of ram working .
Solution Tetras was bang on the ram wasn't seated correctly. Thanks guys . Gonna get it all up and running proper tomorrow and smash some more witchfire .
Happy new year
 
Wow . Finally up and running got both sticks of ram working .
Solution Tetras was bang on the ram wasn't seated correctly. Thanks guys . Gonna get it all up and running proper tomorrow and smash some more witchfire .
Happy new year
unseated ram can cause wired issues.

I swapped over 16GB from my son's PC to my plex server and then moved the 32GB to his.

PC would boot directly to the bios every time, re seated the ram again and the same. For some reason doing this stopped the NVME drive from being detected so had to remove that and re seat it again.

Once done it booted fine but god knows why changing the ram caused this issue!
 
Back
Top Bottom