Z87 Pro - Automatic reboot

jayjoethecocoa

Distinguished
Apr 19, 2008
3
0
18,510
Z87 Pro with latest bios (1205). When I shutdown Windows 7 Pro 64bit (patched, up to date), the computer will shutdown. After some seconds, the system will power back on. Any other Z87 Pro users having this issue?

Clearing CMOS had no effect. I'm currently trying the latest BIOS (1405) to see if it makes any difference.
 
Solution
Switch the board off (leave standby power on to the board from PSU) and then clear CMOS (Clear_RTC jumper). This will reset the ME (management engine). See if it still happens. If it does, check that non of the wake on lan settings are active in driver settings of the OS.

-Raja

raja@asus

Distinguished
Sep 28, 2011
891
2
19,360
Switch the board off (leave standby power on to the board from PSU) and then clear CMOS (Clear_RTC jumper). This will reset the ME (management engine). See if it still happens. If it does, check that non of the wake on lan settings are active in driver settings of the OS.

-Raja
 
Solution

smithchrism

Distinguished
Aug 2, 2013
46
2
18,535
Sorry to join this thread somewhat late but I am having the exact same problem as well. I have talked with Asus three times. We have tried various things which involve new PSU, I replaced the memory with other DDR3 to see if that helped, cleared CMOS, waved dead chickens over my head while hurling voodoo curses at the demons who have invaded my motherboard, etc.. Nothing has helped.

I have gotten to the point where I have obtained an RMA. Asus is going to ship me a replacement board. When I get the board, I'll swap the boards out and send them the one I have now. This will probably happen next weekend.

In the meantime, I would love to know if either of you resolved this.

Thanks.
 

smithchrism

Distinguished
Aug 2, 2013
46
2
18,535
Hi Bill,

First off, thanks for the response.

I've updated the BIOS since I purchased it. In fact, I've updated it twice, once to v1205 and the other time to the latest BIOS which is v1405 or whatever it is now.

I had WiFi Go installed at one point. At some point, I did suspect this and uninstalled it. However, that didn't appear to solve the problem. I have since wiped my system and reinstalled Windows from scratch at least twice. I have never installed the WiFI Go after my initial install as I really don't need it. However, that does make me wonder about something: do you have WiFI enabled on your system at all? I think I may go home and do some experimenting by disabling this in BIOS and such to see what happens with the newer BIOS levels.

The replacement path is already set in motion. I have sent my credit card information to Asus and am waiting authorization. I guess if I can find the problem prior to the board getting here that will at least be helpful as I will not have to perform the swap I suppose. Then again, I'd be a bit hesitant if I do anything to WiFi and my system suddenly seems fine. I have ran across times when I thought I had solved my issue only to see the problem reappear 3 or 4 days later.

Thanks again!
 

solomonshv

Distinguished
Sep 12, 2011
153
0
18,710
same issue with the Maximus VI Hero. Tried every single BIOS available. I really don't like this board. I'm thinking about just returning it and getting a Gigabyte board. my last 2 boards were from gigabyte, my brother's is from gigabyte, and we never had any issues.

with asus there is always a problem. i also have an Asus GTX 680, and that too had problems, the heatsink was not mounted properly, was causing BSODs. Many years ago i had an Asus P5ND2 Sli board, and that too had many problem.

sorry about the rant...
 

smithchrism

Distinguished
Aug 2, 2013
46
2
18,535
Raja,

I'm sorry I didn't respond to this sooner.

I originally had a Corsair GS800 PSU. According to their website, this PSU is compatible with Haswell so I think this angle was covered. I didn't know if there was anything wrong with it though. The PSU was only 1.5 years or so old so I doubt it was going bad. However, I was really itching to get a modular PSU unit. I used this as an excuse so I purchased a Seasonic 650W Modular unit which specifically stated it was Haswell compatible. I removed my Corsair unit and installed the new PSU; the problem did not go away.

I then began to wonder about the memory. I borrowed four sticks of DDR3 memory from work and swapped out my memory with the memory from work. The problem still did not go away.

After 6+ weeks of testing memory, testing PSU, updating all drivers and BIOS, following advice from tech support, waving dead chickens over my system, etc., I came to the conclusion I had a bad motherboard and Asus' tech support didn't argue against it.

Unfortunately, things went bad during the RMA process. Being a professional, I have a need for my system from time to time beyond gaming. I was told the route of sending my board in, letting them fix it, then Asus sending it back could result in at least 3 to 4 weeks downtime which wasn't acceptable.

I went the route of giving Asus my credit information and filling out some paperwork. I was supposed to get a replacement board in the mail, I would swap out my old board with the replacement unit, then I would ship my old board back to Asus.

Alas, after waiting a while (this process was supposed to be completed within 48 hours of receiving my faxed info which Asus tech support did confirm they received during a conversation...), I never got a replacement board. Repeated calls to Asus promised I would get status updates emailed to me and a replacement board would be shipped soon. I never got one. I got to the point I had to give up and ended up canceling the RMA process.

I wasn't a happy camper and decided to purchase a different board to replace mine. I went with a MSI z87-Pro MPower board and have been using it for about two weeks now. So far, my issues have disappeared and am confident they will stay gone.

Looking back at what I went through with the board which I'm not sure I documented here (I had some initial memory usage problems, the USB3 ports didnt' function properly, shut down issue developed about a month after system was running, etc.), I am inclined to believe I simply got a bad board from Asus.

I am concerned though about something. I haven't seen an outpouring of this issue on the Internet. However, I have seen this shutdown/reboot issue mentioned a fair amount and the culprit almost is always an Asus board. Not necessarily Haswell based units but newer ones. Asus may want to check some stuff out here.
 

smithchrism

Distinguished
Aug 2, 2013
46
2
18,535
Raja,

If you want to review my entire saga with Asus on this matter, my RMA # is USPC390845 if you have an ability to look it up.

After I cancelled the RMA option I chose, I was offered the second RMA option where I can still send in my board, Asus will fix it, then send it back to me. I guess I can use it as a backup board or put it up on Ebay which will basically be a waste of time. No one will buy a board that was just fixed and not used by me unless I give it away for less than $50.

I received a FedEx label for free shipping from Asus tech support. Being in a somewhat small town in Tennessee, we don't have a FedEx drop off that I'm aware of. However, we do have a UPS drop off but I will have to pay to ship it to Asus since I don't have a UPS shipping label. I'm not sure if I'm going to bother sending the board to Asus at this point. :(
 

smithchrism

Distinguished
Aug 2, 2013
46
2
18,535
I thought of those type of stuff and I reviewed everything. Not just the lan feature but wake on keyboard, mouse, power restore, etc.. All that stuff was disabled in the BIOS by default. For items I could disable within windows, such as going to device manager to go to the properties of the LAN card to disable Wake on Magic Packet or whatever that is, I did that as well. There were theories the new Haswell C power states were possibly causing a problem. I disabled those in the BIOS.

My initial thinking was when this started to happen windows was crashing or doing a quick BSOD on shutdown I couldn't see. I looked through the event logs within Windows; I never saw nothing wrong. As part of this thinking, I went into the 'Startup and Recovery' Section of Window's Advanced System Settings. I disabled Automatic Restart which is enabled by default; if the system was crashing or some other kind of issue then Windows was, in theory, restarting itself since that option is checked by default. This didn't help.

Between the fact the system ran without this issue for a month, all wake options were disabled by default, Windows was reviewed to make sure it wasn't doing anything, everything (such as BIOS firmware) was updated to latest revisions, etc.., I am 99.9% certain there was no wake up issues going on nor were there any software problems causing this issue.
 

solomonshv

Distinguished
Sep 12, 2011
153
0
18,710


my PSU is haswell certified.



but that's stupid! i want the wake on lan function! this was never a problem before. sometimes i need to turn on my computer remotely to access it and i don't it on 24/7

i had 3 gigabyte boards and before changing to Asus never had this problem.
 

jayjoethecocoa

Distinguished
Apr 19, 2008
3
0
18,510


Bill -
I have never gotten this resolved.
I cleared the CMOS - I have even updated to a newer bios.
I've uninstalled Intel's RST.

All to no avail.
 

Tomjreid

Honorable
Feb 1, 2014
2
0
10,510
In case you are still working on this one, I had the same problem with the Z87-PRO. Tried lots of the things that were suggested here. No joy. Looked for a physical cause to the problem. It turns out that the connections for the power LED were wrong and this is what caused the repetitive reboot on power down. Now that they're on the right way, the problems gone.
 

liolios2857

Distinguished
Feb 17, 2008
1
0
18,510


same problem. what did you do to fix it? plaese post a photo...
thank you.
 

Tomjreid

Honorable
Feb 1, 2014
2
0
10,510


The connector I've removed is the ASUS Q-Connector described in section 2.1.7 of the First Ed manual dated May 2013. The connections for the Front I/O Connectors are made directly to the correct pins on the board. And they all work fine with no rebooting.
 

Tom H

Reputable
Jun 23, 2014
1
0
4,510


In system, lan driver, disable wake on magic packet .
worked for me bios (1504)