Asus Maximus VI Gene kills processor in Standy-by mode (Error 00)

FKTky

Honorable
Nov 14, 2013
2
0
10,510
Hello there,

I've been reading this forum for a while and also found a similar problem to mine, but mine is a bit more extreme, so I thought maybe you guys have some idea or input on how to solve the problem.

3 days after setting up the new computer with Maximus VI Gene and i4770K processor, the computer went in Stand-by/hibernate (probably by windows default) and since then wouldn't fire back up. The coolers start spinning for a second with Error "00" displaing on the mainboard. and then everything goes black again. exchanging RAM, graphics etc didn't work.
I found other people having a similar problem, but their computers fire back up after letting it sit with the CMOS battery and PSU unplugged for a while. Mine doesn't.
To make things worse: I had both the mainboard AND the CPU replaced by the vendors (unfortunately two companies).
System worked perfectly fine for 4 days, yesterday my girlfriend puts it in stand-by when she goes out for shopping and believe it or not, the same thing happens again. PC doesn't fire up, 00 error message.
I tried flashing the BIOS (to the latest BIOS version 1002, from two days ago!!) with USB flash, it worked, but didn't help.

The guy from the processor vendor told me that the last processor had apparently shortened out. He suggested that the motherboard might have power surges after switch off.

When I take out the CPU it actually at least stays on, but apparently the graphics card won't work without CPU, so I couldn't check any settings. But this also shows that the CPU might be done for (again).

I will receive a second replacement for both this week, I don't want this to happen again, especially since the vendor of the processor is probably not too happy about the second replacement already (they'll kindly run a 24 hr test on the processor before sending it out though).

Do you guys maybe have any idea what is causing this and how I could prevent this from happening again?
(Besides flashing the BIOS right away, and turning off auto-hybernate in Windows.)
Is there maybe a possibility to turn off the function to go into hibernate in BIOS or Windows for good?
Also does anybody know where to find a changelist for the BIOS updates form ASUS? (on the download page it just says: stability fixes, but that can be anything.)

My system is:
ASUS Maximus VI Gene
Intel Core i4770k
Elixir DDR3 PC-3 12800 8GBx4
Geforce Galaxy GTX770 4GB
 

FKTky

Honorable
Nov 14, 2013
2
0
10,510
Thanks for the quick reply. Unfortunately I'm in Japan. (or maybe not unfortunately, because the shops have been really forthcoming so far, awesome service in the country). Also I already request a second replacement from the shops.

But anyway, this is the second board that this happened to, so I want to prevent it from happening to the third.
Could you tell me if there are any known issues regarding this and/or if this has been addressed in the latest firmware update?

Also who will pay for the processor if the motherboard fries it and the shops refuses to exchange it?
 

raja@asus

Distinguished
Sep 28, 2011
891
2
19,360
There have been no other cases of this reported, so this is very much a mystery. What I suggest is that you contact ASUS Japan and tell them what has happened and take it from there. They may need to speak to HQ.

Send me a private message with your email address and I will forward it.
 

mmouse698

Reputable
Mar 31, 2014
1
0
4,510
Hi,

First off, here is my system:

Asus Maximus V Gene
Intel i73770K
G.Skill Sniper series 8GBx2 @ 1866mhz
XFX HD 6750
Samsung EVO 840 SSD

I had the same issue with mine when I first got it as well, but with some tinkering with the power (flipped switch off on PSU for couple seconds 30+) that seemed to keep this from happening again. However it became an annoyance having to do it all the time until I found out what was the issue. From what I've read in other forums, and as much as I love this board, there's an issue with the BIOS on these boards that has to do with it going into sleep/stand by mode and causing this and other issues upon trying to wake. In my case, it was more likely when it was powered down for long periods of time through standby/sleep.

What worked for me without looking into the forums was I took it off auto sleep/standby (just found out today it's what worked for others as a work around). I also disabled Hibernate just to be safe. I have an MSI board running the same hardware just different board and it doesnt have this problem which supports what I've read so far on other forums. Luckily the others went through all the trouble shooting and still no solution. According to what I've read in the forums there's supposed to be an update or fix for it. But yeah, I'd either shut it down or leave the comp on with hibernate and sleep/standby disabled. Also, I found that leaving the power switch on the UPS/surge protector makes a difference as well. Doing otherwise will cause the same issue. It's too bad because I really like this board and this would be one of the only things I don't like about it.

Hope this helps.