R4E not posting after shutdown, an xperience -- but WHY?

[estrulian]

Hi,

I've read many threads on this same issue. I thought I would create a new one nevertheless to describe what happened and what I did mostly because I want to know WHY??? while I explore what I want to do with this build.

I am if anything an amateur learning as I go along :cool:

The essentials,

build date: February 2013
CPU Intel i7 3820
Mobo Asus Rampage IV Extreme
RAM Corsair Vengence DDR3 1600 4x4GB
CPU Cooler Corsair H100i
GPU Asus GTX 660Ti
PSU Corsair AX1200
Boot HDD Crucial M4 256GB SSD
OS Windows 8 Pro x64

Did not try OC features or mess with the BIOS. Everything stock except for updating drivers on GPU. Stays on 24/7.

Been using it since build. Light loads. No glitches except one where it didn't power up after two days of shutdown. I removed the plug to the PSU re-inserted and it switched it on. Didn't even think of it until now when the R4E just refused to POST.

June 4 - normal shutdown from OS as I was traveling for a few days. Switched off power from the mains as well.
June 8 - system would not POST.

Here is where the fun begins.

On standby ONLY the START, reset, BIOS led, GPU power leds remained lit when the PSU is turned on. Apart from that nothing, not even a fan. It just would not POST.

First I tried the RAM. Nothing. Removed all the sticks. Re-inserted. Nothing. Single stick. Nothing.

Then I started looking for fixes. Tried a myriad of different configurations with my RAM after stripping down to to just CPU and RAM. Tried one stick of RAM, one stick of RAM in different DIMM sockets, 2 sticks of RAM, checking the pins and re-seating the CPU, checking all connections, unplugging everything from PSU, switching BIOS chips, clearing CMOS.... removing battery.. leaving battery out for sometime.

Also, flashed BIOS1 with most recent update 4102 via USB. Had to convert .CAP. Was happy to see the BIOS led flash, atleast something was working!! But still refused to Power on.

Tried outside the case with only CPU and RAM in different configurations. Clearing CMOS, switching BIOS, Slow Mode Switch, Nothing. Nothing. Nothing. Absolutely no response on the START button or reset Button. Only the BIOS switch button and GO but would respond. GO button when pressed for a few seconds lit up and stayed lit until PSU was powered off.

After a week of mucking about I put everything back in the case. Starred at it for sometime long trying to decide what to do next. What should I replace??? I didn't have immediate access to a CPU, PSU or DIMMS to swap and see if they worked. I know the H100i worked because i tried it by shorting the PSU (without the PSU being connected to the Board).

So I left it on standby. With one DIMM in C1 socket, furthest from CPU and closest to the START button. I thought maybe my R4E would turn on by itself after it figured it has a consistent source of power. It was kinda a last hope and the only thing I had not tried, i.e. leave it plugged in. The R4E is known to have a life of its own right?? So no harm.

At 0258hrs about 4 hours since I left it on standby and just as I was falling asleep, the R4E literally roared to life!! I had hooked up just the monitor after reassembly for one last push on the START button. I turned on the monitor and there I was starring at the ASUS BIOS UEFI!!!!!

I reset it to see if it would turn on and it did! I started powering it off and putting in 1 DIMM at a time and starting it up. It worked. Next the HDD OS and I booted right up to the OS. Switched BIOS and it still booted into the OS. Stable for the past 7hrs. Debug LEDS read AA.

Interesting OBSERVATION: System date and time was the date it was shutdown last and probably exact time it was shutdown. 4 June 2013, 1808

So now the big question WHY?? and If its turned off for a long period will it not power up again?? Could the BIOS setting to stay shutdown in the event of power failure be the cause. Does ASUS know why? So many people seem to have had this exact same problem.

After all the reading I've done I am inclined to think that it is not a hardware issue. Many people have had the boards tested and returned back to them.

Any ideas? Any suggestions on where I can find out more?

[estrulian]

Been reading much of what has happened to you Izzyreb02. Looks like R4F is the way to go.

izzyreb02 wrote:
Woah, Seems like a lot of people having the posting issue going on here, just like what happened to my R4E.

Both of my R4E boards came across the same issue before but for some odd reason it just wont turn on until 11am and if I decide to turn it on before hand and waited till 11am it just turn itself on. But of course HiVizMan know where I've been through...

(this is before I decided to get R4F to take its place, but of course I did come across shut down issue in windows but wouldn't say much other than Event 6008 and the incident happened like 18th and 17th of this month)

[Rampage_Freak]

Thats why its a good idea to just have a backup M/B in cases of emergency. Its a really good idea! Ive seen more people on youtube getting this problem. Seems you have to drain out all the remaining power in the capacitors or something and leave it for 12 hours. Of course while you sleep... Then plug the power into the wall socket and power it on. It should work like a charm but will be frustrating as your doing that every single night.

[Halfdead]

I've had the same thing happen to me countless times, it always needs to have the power drained from the board for it to boot up again when it's having one of these episodes.

Not sure why this happens, it has happened to me with two brand new boards so far. Sometimes when it happens it won't completely post either, when this kept happening amazon.com replaced the board with a brand new one. Hopefully I won't see this again.

[Rampage_Freak]

Just to let you know. If you got it brand new you should RMA it through amazon or directly from asus. What are your specs? I might be able to help you out.

[estrulian]

Update: Shut it down finally for a few hours and then ofcourse as expected it would not power on or post. I removed the RAM and just left a single stick in and left it. Came back on by itself about 12 hours later with the time and date stamp of when I shut it down.

Wonder if it is RAM issue. Plan to replace them anyways since I've got corsair vengeance.

Any suggestions on a mobo to replace this? Thanks in advance for any suggestions.

[Domenick]

I just replaced mine with a formula. Was a risk but so far so good! I am using the same ram and don't get the issues, I have the corsair vengence LP. I am not on tight timings though. Anyway, see how it goes, I'm getting a brand new board replacement for my Rampage IV Extreme, but I think I will just leave the Formula IV in if it works 😉

[estrulian]

Forgot to mention that when it comes out of this "sleep" state by itself. There is a message saying BIOS settings have changed and to press F1. I go into the BIOS and just exit without any changes and it boots.

[estrulian]

Thanks Domenick. I am also leaning towards replacing with IV Formula. I did read elsewhere on many forums issues with vengeance series RAM and X79, on other boards like Gigabyte. Hence the thought to replace RAM.

Domenick wrote:
I just replaced mine with a formula. Was a risk but so far so good! I am using the same ram and don't get the issues, I have the corsair vengence LP. I am not on tight timings though. Anyway, see how it goes, I'm getting a brand new board replacement for my Rampage IV Extreme, but I think I will just leave the Formula IV in if it works 😉

[lowdog]

Hey guys I had this EXACT same issue.......just replace the cmos battery and you will fix the problem. My old cmos battery read 2.8v with multi metre so I replaced it with a new one that read 3.33v and no issues so far.

Hope this helps.

[estrulian]

Low dog, I am about to try that. CMOS battery is something I've never had to replace on a board. It does explain the time and date being off. I've only had my system up and running for 5 months.

lowdog wrote:
Hey guys I had this EXACT same issue.......just replace the cmos battery and you will fix the problem. My old cmos battery read 2.8v with multi metre so I replaced it with a new one that read 3.33v and no issues so far.

Hope this helps.