cancel
Showing results for 
Search instead for 
Did you mean: 

Z790 boot issue after build Q Code 33

CmdrEvans
Level 7

Hi, built a new PC and looking for some advice, as I am having boot issues. 

Asus RoG Z790-E

Intel 14700K

Asus TuF 4070TI OC

Corsair Dominator Platinum DDR5 6400

Corsair MP600 Pro NH 1TB

Corsair MP600 Pro NH 4TB

 

Carefully assembled new machine over a couple of evenings. Added last elements today and went to boot the machine. 

Power in and PSU on, the ROG logo on the I/O panel lights up. Good start.

Power machine on and lights, fans, all encouraging. Cycles through an array of codes on the motherboard display, finishes on 33. No display at all, no other signs of life. 

Have double checked memory and CPU seating, all OK. Checked all connections to motherboard, all OK. 

Am stuck, and hoping for divine intervention or some guidance from here 🤞

1,044 Views
2 REPLIES 2

crazymouse69
Level 9

You are not alone. Read my story.... 3-4 days ago. I'm almost convinced that the problem is the rgb of ram whith aurasync or viceversa. At the moment i'm on stable system with 16gb of kingston fury no rgb lend by my friend. The strange thing is that for a week all was perfect and i'm not sure if the fault could be Armoury crate software or icue by corsair. Good luck and let me know what you think about. Ciao  

 

CmdrEvans
Level 7

For anyone else coming across this (I appreciate it could be an array of issues) it was caused, in my instance, by my Corsair MP600 Pro NH 4TB drive being in M.2 slot Slot 1. Upon removing this it booted fine. I have 2 x Corsair MP600 NH, 1 x 1TB and 1 x 4TB. 

Originally I had the 4TB in Slot 1 (processor) and the 1 TB in Slot 3 (chipset). Upon moving the 4TB from slot 1 to slot 2 (still processor) the machine boots fine*

 

* I will caveat fine by saying the 4TB does not appear to be detected in the BIOS or windows, and with my 4070ti installed I get Q Code D6, but without the 4070ti I could boot with onboard graphics and install windows. 

Suspect (and hoping) D6 is a not properly seated cable somewhere, and will continue trou reshooting the 4TB drive later.