F5F Stay Refreshed Hardware Desktop Is there a way to fix the motherboard debug code 22 when using new hardware during the Windows 11 installation?

Is there a way to fix the motherboard debug code 22 when using new hardware during the Windows 11 installation?

Is there a way to fix the motherboard debug code 22 when using new hardware during the Windows 11 installation?

F
futurehero
Member
59
08-05-2021, 04:13 AM
#1
Hello everyone!
This week my system stopped working, so I received these new components yesterday:
Mobo: X870E Aorus Pro Ice
CPU: 9800X3d
RAM: 32GB Corsair Vengeance 6000MHz CL30 (listed on the compatibility list)
All other parts stayed the same.
Now regarding the issue:
I put everything together, turned it on, updated the BIOS, and installed an empty M.2 SSD. Everything was recognized in the BIOS. But when I began the Windows 11 setup from a USB drive, all steps went smoothly until it reached the hard drive search stage. At that moment, debug code 22 appeared on the mainboard and everything froze.
As long as I stayed in the BIOS or even in the installation tool before the hard drive section, everything functioned properly. However, once the process needed to interact with SSDs, Code 22 appeared instantly and nothing worked afterward. It’s worth noting this error code isn’t mentioned in the manual!
So far I’ve tried:
Swapping the RAM slots and testing one stick at a time (the other was always off)
Testing various PCI slots for the M2 SSD
Testing three different M.2 SSDs (all compatible with the motherboard)
Changing and reinserting the CMOS battery
Now I’m unsure if the problem comes from faulty hardware or another issue.
Is there any way to check if the motherboard, RAM, or CPU are defective? Unfortunately, I don’t have spare parts to test.
I also found a Reddit post describing the same problem, but no solution was offered there.
Thank you for your attention.
Best regards.
F
futurehero
08-05-2021, 04:13 AM #1

Hello everyone!
This week my system stopped working, so I received these new components yesterday:
Mobo: X870E Aorus Pro Ice
CPU: 9800X3d
RAM: 32GB Corsair Vengeance 6000MHz CL30 (listed on the compatibility list)
All other parts stayed the same.
Now regarding the issue:
I put everything together, turned it on, updated the BIOS, and installed an empty M.2 SSD. Everything was recognized in the BIOS. But when I began the Windows 11 setup from a USB drive, all steps went smoothly until it reached the hard drive search stage. At that moment, debug code 22 appeared on the mainboard and everything froze.
As long as I stayed in the BIOS or even in the installation tool before the hard drive section, everything functioned properly. However, once the process needed to interact with SSDs, Code 22 appeared instantly and nothing worked afterward. It’s worth noting this error code isn’t mentioned in the manual!
So far I’ve tried:
Swapping the RAM slots and testing one stick at a time (the other was always off)
Testing various PCI slots for the M2 SSD
Testing three different M.2 SSDs (all compatible with the motherboard)
Changing and reinserting the CMOS battery
Now I’m unsure if the problem comes from faulty hardware or another issue.
Is there any way to check if the motherboard, RAM, or CPU are defective? Unfortunately, I don’t have spare parts to test.
I also found a Reddit post describing the same problem, but no solution was offered there.
Thank you for your attention.
Best regards.

K
kickster54
Junior Member
18
08-11-2021, 12:04 AM
#2
Have you experimented with another USB drive and a new download from the official source?
K
kickster54
08-11-2021, 12:04 AM #2

Have you experimented with another USB drive and a new download from the official source?

M
MCasia
Junior Member
19
08-11-2021, 05:51 AM
#3
It seems like the text was copied directly from another source.
M
MCasia
08-11-2021, 05:51 AM #3

It seems like the text was copied directly from another source.

R
Roccoboy8
Member
162
08-11-2021, 06:52 AM
#4
It worked after switching to an Msi board, but the problem remained until I got a new CPU. Now everything is fine.
R
Roccoboy8
08-11-2021, 06:52 AM #4

It worked after switching to an Msi board, but the problem remained until I got a new CPU. Now everything is fine.