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.

[Nate152]

Hello Asandreoli

Welcome to the ROG forum.

Thank you for the detailed report and it seems you've done a lot of troubleshooting already. The motherboard giving off an electromagnetic noise raises red flags for me.

It sounds to me like it's either a power problem or mobo problem and since you tested with two psu's I'm leaning towards the motherboard.

Code 00 can be caused by a ground problem too have you installed the motherboard stand offs?

[Asandreoli]

Thanks for the prompt reply Nate.

The Hadron Air has standoffs coming from the case structure, so I screwed the MB directly to the case. Also, I don't remember of any standoffs bundled with the MB.

On the CPU cooler side, I have installed the Noctua NH-D9L plastic spacers but have not installed the adhesive plastic washers (bundled with the MB) on the backplate as I thought they were optional (i.e. only required if facing issues to install the CPU cooler). Is that correct?

When you say it may be a power problem, are you refering to the PSU specifically or could it be the lack of grounding, static or shorting?

[Nate152]

You're welcome

The motherboard doesn't come with stand offs. The stand offs come with the case, if your case has the motherboard stand offs already installed then you're good to go.

It could be psu specifically or a ground issue but testing with two psu's I wouldn't think it's the psu. You could install the adhesive plastic washers on the back of the motherboard to see if that helps (could possibly be a ground problem). An overtightened cpu cooler can cause code 00 too, you could try loosening the cpu cooler a touch.

If you're not 100% sure the bios update was completely successful you could try reflashing the bios again following this guide, rename the bios file to M7I.CAP

If you feel it was successful then you can skip it.

http://rog.asus.com/forum/showthread.php?1142-How-to-use-ASUS-ROG-USB-BIOS-Flashback

[Asandreoli]

I will try one last time outside of the case using the stock cooler and the Thermaltake 850W psu. I am considering four possible issues: (1) maybe the Noctua backplate - that is touching the socket backplate - is shorting the MB; (2) maybe the screws on the top part - that have contact with Impact Power II heatsink and the case - are shorting the MB; (3) maybe the power supply/outlets in my appartment are bad or finally, (4) my mobo Impact Power is deffective.

Do you think that a bad power source (outlets / unstable current) - NOT A MB PROBLEM - could cause the motherboard to give off electromagnetic noises? It is possible due to a bad power source, the MB freezes to protect the hardware? That came to my mind as the MB properly booted and faced the error on both PSUs and after being working in one power outlet and moved to another it freezed.

[Nate152]

I suppose it's possible, I never faced an issue like that but the four things you mention are worth taking a look at.

If you get it to post outside the case, run it like that for a while and see if code 00 pops back up. A 500w psu should be enough for the gtx 970 but try the 850w and see how it goes.

Is your electrical socket on a 15 amp breaker?

[Asandreoli]

I just tried outside the case using 850w psu, stock cooler, only cpu and MB booted with 14, 15, FE sequence. I manually restarted the system and cleared CMOS more than 10 times and boot happened in that sequence without 00 errors. After that I left it running on FE for about 5 to 10 min and when tried to mannualy restart it, boot error occurred (qcode 00 and cpu led on).

Let it rest with psu on for 5 min, tried again and boot was ok again. Not sure if the stock cooler was properly mounted though.

Changed to Noctua and boot continues to be ok after several tries. Left it running for 5 min, restarted and boot is ok with 14, 15, FE sequence. Moved from one outlet to other, including other room and boot continues ok on Noctua.

Related to the power socket, I noticed that it was working better (less errors) on a 20amp outlet and when moved to a 10Amp boot problem was more frequent. Today I changed all outlets to 20amp, which I am using for the tests above.

Until now, more than 30 tries, including some CMOS clearing, everything seems fine with Noctua's. I will try with Hadron's psu and later I will try to gradually add RAM and other hardware.

[wa3pnt]

A 850 Power Supply running flat out would only draw 8 Amps.

You are very lightly loaded, so probably drawing less than 3 Amps.

Therefore the circuit breaker on the circuits would not be a factor.

Defective (loose) wiring on a receptacle could be a factor. Can you measure the voltage on the receptacle while the computer is running?

RodeoGeorge

[Nate152]

Was it working with code FE?

Code FE from what I've read is memory error, I know you've removed and reinstalled the memory modules but double check they are fully seated.

If code 00 is still popping up randomly, that is a tough one to diagnose because the manual states code 00 is not used. In my experience with code 00 it's either the psu, cpu or motherboard and without other parts to test with, it's pretty much a guessing game as to which one it is. Sometimes a bios update can solve code 00.

If you have no other parts to test with and it's not too much of a hassle, you could rma the mobo and cpu to save time. I really don't know what else to tell you other than that.

This might sound like a silly question but do all your household appliances work ok?

[Asandreoli]

Unfortunately, I don't have the tools to measure the voltage here. Nonetheless, I inspected the wiring in the outlets as I changed them to 20amp sockets and everything is ok. Appliances run fine. The power supply is not that bad I think.

Still running only cpu and noctua with 850 W psu and no errors until now. I will change to Hadron's psu and later add RAMs. It is currently running on FE but w/o Ram. I guess it is right. I am betting that the random errors today were more related to an incorrect mount of Intel's stock cooler. After I changed to Noctua without screwing it all the way down, there were no more errors even when changing outlets.