Maximus VII Impact won't post (QCode 00 CPU Led on)

[Asandreoli]

Hi, I need some help as I am facing random "QCODE 00" + "CPU Led On" errors and system won't post.

Parts List:

MB: Asus Maximus VII Impact (LN2 Disabled)
CPU: I7 4790K (stock)
COOLER: NOCTUA NH-D9L
RAM: KINGSTON HYPERX SAVAGE 16GB 2X8GB 1866MHZ DDR3 (HX318C9SRK216)
VGA: EVGA GTX970 4GB SSC ACX2.0+DDR5 04G-P4-3975
HD1: SSD KINGSTON HYPERX SAVAGE 240GB
HD2: WD VELOCIRAPTOR 150GB 10K RPM
CASE: EVGA HADRON AIR WITH 500W 80 PLUS GOLD PSU
CASE FANS: 2x NOCTUA NF-S12A PWM

Build everything without problems, first post seems OK, installed OS (Win7) and during updates' restarts some posts ended in Qcode 00 and CPU Led on. Clearing CMOS did not help. After a few tries the system booted and I updated BIOS from 0217 (Factory) to 2801 (latest) through DOS (USB drive renaming BIOS file toM7I.CAP). Update seemed ok, system posted on iROG1 update, reseted and ended with QCODE 00 + CPU Led On. Tried clearing CMOS, removing power cable, etc. Posted again after some time on iROG2. Same QCode error and after other tries, system posted on iROG3 update. After that I was not able to make the system post again, always receiving QCODE 00 + CPU Led.

So, I remove all parts and tested posting on every change, but no luck. Checked socket pins, cable conections, etc. Nothing seemed wrong or damaged. removed the MB from the case and let it rest for a while. Started building again and magically post returned to work with QCodes and Errors Led varying as expected (lack of RAM, lack of bootable device as I was adding parts). Tested the posting after each change (each cable, card, hd, etc.) and everything was working until VGA power cords were connected. So I thought that it could be the PSU.

Therefore, I tested the build with a spare Thermaltake 850W and error continues. Tested CPU, RAM and VGA in other MB and everything was working properly, so I focused on the MB. Tried to update BIOS again to 2801 via DOS and everything seemed to work on the fourth complete rebuilding try (this time iROG updates were completed in sequence without QCodes 00). Get excited that maybe it was a BIOS update failure (since iROGs were interrupted by QCodes 00 before as mentioned above). Tested one last time on my work table with only the power cord connected and everything posted ok, then tested clear CMOS and BIOS verified hardware briefly as expected, restarted and posted correctly. At that time, I thought that problems were solved. Then I closed the case, disconected the power cable and moved the PC to my room. Connected the power cord again in another power outlet, connected all cables (keyboard Logitech G15, mouse Logitech G5, Spdif audio cable, wifi antena, HDMI). Press the power button and..... QCODE 00 and CPU Led on.

I am desperate at this moment. I already spent 4 nights building, removing and building everything again to try to find the problem. After this last result, I started to think that maybe it could be my power outlet (i.e. grounding issues) or the Keyboard and mouse draining to much power from MB (as G15 has a LCD display). But I am not confident that it is not a Power Management problem on the MB as erros seems inconsistent (i.e. they appear in random momments, that is, after BIOS update, after connecting the VGA, after removing FAN and Coolhub, after moving the case from on table to another, etc). The error after moving it around could be a coincidence...

Additionally, what intrigues me most is that since the very first boot on BIOS 0217 and in the few successful posts after in 2801, the system presented a energy/eletromagnetic noise that was very audible and that got worse when moving mouse around BIOS or Win7 or when using the keyboard (noise seemed to come from Impact Power II). So I read in other posts that some people faced these strange noises (not only with Impact cards), which were solved by changing the CPU Power in BIOS to "Extreme" (Full Phase). Tried it and indeed solved my problem. Nonetheless, with all clearing CMOS required to get the sytem to boot in between post errors, I had to reconfigure the BIOS every time.

It is so confusing that the system booted correctly some times. In fact, one time after the first BIOS udpate to 2801 I was able to keep the PC turned ON for several hours (all drivers updated to last version from Asus support). At that time, I also able to perform some stress tests on CPU, RAM and VGA on win7 without any issues. Nonetheless, after a day working correctly, when the system was simply returning from Sleep it faced the same boot error.

Please mind that I was not overclocking the CPU. RAM was at 1600Mhz instead of 1866MHz as I was not confident to try any change to BIOS default settings due to the lack of stability. Tried one time to match XMP profile in BIOS and faced the same boot error on restart.

Can someone please help me on any thought or ideas? Should I RMA it or could the fault be on power (e.g. power outlets, lack of grounding, USB draining too much power, static or shorting in the case)? I am resisting to RMA as in my country I will have to wait several weeks to receive a replacement. I would not like to RMA until I am completely sure that it is a MB problem.

Sorry for the long post, but I tried everything and I am running out of options.

[Asandreoli]

Yes, yesterday I tested the cpu in another MB and it was ok.

i successfuly changed to Hadron's PSU and still no errors in boot after several tries. Lets add some RAM.

Edit 1: added one stick on far socket and booted fine, several qcodes, restarted by itself as it recognized the stick and booted just fine again going through several qcodes and ending on 99 for some seconds and later changed to d7. Tried reseting and boot continue to work fine. 🙂

Edit 2: same happened for the second stick. Try some resets with success and then added both sticks and still no errors. Qcode still d7. Getting confident. 😉

Edit 3: moved around rooms to test other power outlets and everything continues normal with both RAM sticks now. Qcode is d7 and bootable device led is on. Only noticed that the first boot in a new outlet led the board to a brief boot (like when hardware is changed) followed by a normal boot (similar to reset). Battery is new (bought today) and is in place.

Edit 4: added coolhub, sound card and wifi combo and everything continues to work just fine. Tested boot 3 times for each component and no errors so far (qcode always d7 - no console input devices). I will move to the GTX970...

Edit 5: added the vga and no errors after 5 tries and one Clear CMOS. Can I consider my mobo is fine or it is too soon? Now I would bet on cooler being too tight on past days? But how to explain the electromagnetic sound on Bios and Win7 coming from Impact Power II? I am so suspicious that I dont want to claim victory yet... Lets see what happens when mobo is attached to hadron. Maybe a shorting is coming from the case.

Edit 6: Success!!! Added SSD and Velociraptor without problems. Moved all the system (outside the case yet) to the pc room and booted into bios. Connecting my Logitech G5 mouse make the Impact Power give out some eletromagnetic noises (specially loud when moving the mouse aroung in BIOS). Also, connecting my Logitech G15 keyboard implies in more noise from Impact Power II. I noticed that changing ports won't help and will result in a B4 QCode. Nonetheless, there were no more errors in post, bios or even win7 loading.

BIOS version is as follows:

BIOS Version: 2801 x64
BIOS Build: 06/25/2015
iROG1 Version: RGE1-Z97-0135
iROG2 Version: RGE2-Z97-0206
iROG3 Version: MKEY-Z97-0138
ME Version: 9.1.25.1005
PCH Stepping: 00/A0

Changed CPU Power Phase Control to "Extreme" and Impact Power II noises are much lower. Also, I changed the DDR RAM frequency to 1866Mhz and it booted correctly, improving timing to factory numbers (CL9).

Now it only remains to install the MB in the Hadron Air case and connect the FANs.

[Nate152]

You say you tested the cpu in another motherboard and it was fine, I'm back to thinking it's the motherboard.

[Nate152]

That is sounding better Asandreoli, keep us updated as you add components.

[Asandreoli]

I would thank you all (specially Nate) for the great support!! Considering the system is stable until know (several hours later), it is safe to consider that the Mobo is alright :rolleyes:? I can't understand yet what really happened in the past four days. Maybe a cooler that was too tight, loose connections and poor power supply altogether, which confused me a lot...

Last thing, I would greatly appreciate if someone could give some advice on "must have" changes to BIOS default parameters and maybe some basic overclocking.

I will let you know if something goes wrong in the next days!

Tks! 😄

[Nate152]

That's awesome Asandreoli !

I don't know what was giving you code 00, ground or psu? But let's hope it's behind you now.

To set bios to defaults hit F5 while you're in the bios.

If you would like some help overclocking I can help you with that too. We can do it right here if you want, just say so when you get your mobo installed in your case.

Run it for a while and see how she goes, then we'll venture into overclocking if you like.