B550 Unify-X stuck at Debug code "22", but only sometimes??

[ProRules]

Hello, I have this persistant issue where after a restart or a pc power up, the PC might get stuck on this debug code 22, which means "OEM pre-memory initialization codes".

What's weird is that it happens sometimes, maybe like 1/3 of the boots. And well, after the boot, the PC works flawlessly and passes HCI memtest without any error.

 

My specs are:

SF750 Platinum PSU

3800X - 1900 IF stable.

G.Skill 4000C16D-32GVKA running at 3800 14-14-14 1.48V (stable HCI memtest), 2x16GB DR.

B550 Unify-X mobo.

 

Could it be my IMC just sometimes struggling to load the RAM settings? My previous B450 Tomahawk max 4 layer PCB worked well with 1900 IF and 2x8GB SR but the IMC couldn't even handle 1900 IF to boot with DR even on 2133 stock JDEC RAM settings for the RAM, which means that the move from SR to DR was enough stress on the IMC to not even be able to boot high IF.

 

What do you guys think is the culprit for the 22 debug code?

[Hairless Monkey Boy]

Probably something funky going on with memory training. Sometimes the board can just miss, especially when running very tight timings.

 

Have you messed with your timings beyond just the primaries? Locking everything down might help, so the motherboard doesn't set something absurd. You can also try changing the Memory Fast Boot setting.

[ProRules]

11 minutes ago, Hairless Monkey Boy said:

Probably something funky going on with memory training. Sometimes the board can just miss, especially when running very tight timings.

 

Have you messed with your timings beyond just the primaries? Locking everything down might help, so the motherboard doesn't set something absurd. You can also try changing the Memory Fast Boot setting.

I attached a file, those are all locked. I did change tRAS to 30 since then (looser), and tRDWR 8. All stable as in this image.

[ProRules]

On 12/27/2021 at 10:46 PM, Hairless Monkey Boy said:

Probably something funky going on with memory training. Sometimes the board can just miss, especially when running very tight timings.

 

Have you messed with your timings beyond just the primaries? Locking everything down might help, so the motherboard doesn't set something absurd. You can also try changing the Memory Fast Boot setting.

Hey I fixed my issue in case you're interested knowing - there is a BIOS setting on MSI boards called "Memory fast boot" which is enabled by default.

I disabled this setting and voilla.. Idk what's even the point of that setting, because it takes the exact same amount of time to boot with it, or without it enabled.

[Hairless Monkey Boy]

On 1/1/2022 at 12:57 PM, ProRules said:

Hey I fixed my issue in case you're interested knowing - there is a BIOS setting on MSI boards called "Memory fast boot" which is enabled by default.

I disabled this setting and voilla.. Idk what's even the point of that setting, because it takes the exact same amount of time to boot with it, or without it enabled.

Good, I thought toggling it might help. Glad I mentioned it.

[ProRules]

19 hours ago, Hairless Monkey Boy said:

Good, I thought toggling it might help. Glad I mentioned it.

Yup thank you kindly =)

Also, now lower tRAS and tRC are possible, because prior to that I had the training issues.