Motherboard issue, or ?? Red light and two beeps. Bad RAM maybe?? ASUS P8Z68-V LE

soulweeper

Distinguished
Jan 26, 2012
148
0
18,680
My computer that I built about 4 1/2 years ago, just shut down today,and when I tried to power it back up, it does what you see in the video clip.

https://youtu.be/aOnKx-ivvOE

The red light coming on the motherboard might indicate something, not really sure. Right above that red light, and next to that little black button it says DRAM_LED, and above that black button above where the light is coming on, it says MemOK

One thing to note, that I never paid attention to....is that those two beeps you hear....well, for the longest time, after I built it, whenever it would sit idle for a bit (I leave it on all the time), the case fans would shut off, and when I touch any key, or the mouse, it would make those two beeps, the case fans (and fan lights) would come back on. It was as if it was "asleep", or something. I neve thought anything of it, not sure if that was normal, seemed like it. It stopped doing it for awhile, and then, after I cleaned out all my old temp files and whatnot the other day, it started doing the thing where it "shuts off" when idle, like I described. Just throwing that bit of info in, for whatever it's worth.

Thanks in advance!

 
The system is four years old.

The very first thing you should be checking at the start is the power supply unit of the system if it is also four years old.

If I were to be honest with you when it comes to power supply`s and a Pc is getting on in age it`s the very first thing to look at Soulweeper, at least test your system with another power supply if you have one, or borrow one for an hour or so from a good friend.

The next in the list is to remove all of the memory from the system.
Power the system up and see if you get a bios beep error code relating to no memory fitted to the motherboard.

Turn it off again if the correct bios beep error code is produced by the motherboard.
And then using a single stick of memory place it in the first memory slot of the motherboard.
And see if the motherboard posts or powers up correctly.

You should try each memory stick you have out of the amount you have one at a time placed in the first memory slot of the motherboard.

Where with each stick a powering of your system should be performed.
The sound I could hear.
Sounded to me like it was coming from the power supply of your system.
Or it sounded like a hard drive connected to your system had failed.
If it has broke or shorted out and, power is connected to the hard drive.
The motherboard will treat it as a short circuit, or the power supply unit of your system will also.

And will not power the system up correctly.
So depending on how many drives you have connected, including optical drives.

Remove power from all of the drives.
And see if the system powers up right.
Then connect the power back to one drive like the boot drive and again power the system up to see if it powers up right.
Do the same step each time you connect a drive.

If you connect power to a drive, and the system then fails to power on, it is a sign the drive has failed, and is causing the motherboard not to full power it`s self up right.
 

soulweeper

Distinguished
Jan 26, 2012
148
0
18,680
Thank you very much for that informative answer! I appreciate it!

Don't ask me why, but right now it is working, and I can access my backup drive. My boot drive is an Intel SSD, and my backup drive is a terabyte Western Digital HDD.

Yes, the entire system is a little over 4 years old. I built it. My first build.

I don't know what the BIOS beep error code is, hate to say. :)

Also, after I posted, it was in a "loop" you could say, of trying to boot up, pretty much like it was in that video clip. A few times it actually booted up, stayed on for 30 seconds, maybe a minute, and then went off, and immediately tried to boot again. After a few times of that, it stayed on for maybe 5 minutes, then shut down. The first time it did it, I got a window that listed some of my componenets, and it said that overclocking had failed, and to press F1 to go to setup, and re configure. I don't overclock, so that was weird. I went to setup, and hit discard changes and exit, and it started up. Didn't last long.

It did a few reboots, where it said windows had not shut down normally, and I had the option to start windows normally, or in safe mode. I started normally, and it booted right up. Shut down a few times, and then one time, it started up, and it told me windows couldn't start, and something about a repair came on the screen, so I told it yes. Why not,right? Then, during said "repair", it asked me if I'd like to restore the system, but not with any option as to when. Again, why not? I hadn't made any changes lately so didn't think restoring to anything fairly recent would do any good. So, it restored the system, came back up, and it's been on for a couple hours.

I have no idea why, if it "repaired" itself, system restore fixed it.....or whatever. Huge mystery as to what happened. Might just shut off in 5 minutes, I don't really know.

The weird part, to me, is how this seemed to come about right after I used this temp file cleaner tool. I've used it before though. A while back, right after I used it, and it could just be a coincidence, the computer would actually shut the fans off after it sat idle for a little bit, then when you touched the mouse, or a key, it would make those same two beeps, like you hear in the video clip, fans would some on, lights on the fans would come on, and away you go. It stopped doing that after a while, why, I don't know. Then the other day, it started doing that again, after I cleaned out my temp folders. Might just be a weird coincidence. The two beeps are the same beeps, that's why I mentioned it. May have no relation at all.

Anyway, right now it's cooperating, so I'm afraid to do any "testing." My suspicion is it didn't fix itself, and I'm just lucky, for now??

Really weird, to me.