Machine won't boot - at a loss for the cause

threazy

Reputable
Sep 18, 2015
12
0
4,510
I need some expert hardware help: my computer won’t boot and won’t even get to the Windows Startup graphics (i.e., no signal to the monitors at all - there’s not even an opportunity to enter the Bios). It starts to power up, then shuts down, and then restarts.

First, here’s my system: HP Pavilion HP-h8-1360t (http://support.hp.com/us-en/document/c03425388). Intel i7. Replaced main drive with 128G Samsung SSD and Windows 7 pro. Two optical drives, three HDDs. Factory video card. Started with factory Hynix 4G RAM cards; now have 4 4G Crucial Ballistic sport cards.

The timing of the shut-downs and restarts is consistent and seems to be a good clue – and I’m hoping someone here can what the clue might mean. There are two cycles, actually. The first short cycle is
Fan spin-up to shut down: ~5.8 seconds
Shut down to restart: ~4.8 seconds
The second, and currently most frequent cycle, is
Fan spin-up to shut down: ~33 seconds
Shut down to restart: ~4.8 seconds

In order to stop the cycling, I need to physically turn off the power supply with the on/off rocker switch on the back of the box. It will not boot from a CD boot disc, either.

The main question I would like answered is: What is the sequence of “hardware checks” the system does as it’s starting up? Is it, in fact, the RAM that is causing the restarts? Or is there something else in early in the power-up sequence that could be the problem and I’m barking up the wrong tree futzing with the RAM? Given the history of the problem, it seems like something (not the RAM) has been slowly going bad and the RAM-thing is just a fluke.


As I’m testing it tonight, a boot with a single card in the #1 slot starts with a short cycle and then repeats the long cycle. Cards in #1 and #3 repeats the short cycle. Cards in all four repeat the short cycle. (Though this does not seem to be consistent – earlier tonight I could swear it was repeating the long cycles with all four cards.)

Here’s the history, for more information. There have been two main “incidents” prior to today.

============ incident #1 around 6/15/15 ======================
Prior to June 15th, the machine seemed to have problems booting up, but after a couple tries it was successful. I don’t recall when this actually started happening. I can’t think of any changes I made to the machine since the initial physical changes made just after I bought the machine in 2013.

Around June 15th, there were a lot of Windows updates to install. (I usually keep the machine running 24/7.) So I shut down the machine and let them install. No problem. But, from there, the machine wouldn’t boot again – it would exhibit the startup-shutdown behavior described above. I talked to a tech friend who suggested the power was a problem; because of the three HDDs, I’d been concerned about the factory power, so this was a plausible cause.

I bought and installed a corsair 750 – plenty of power now. But the machine still wouldn’t boot up! I did more research and saw something about bad RAM, so I pulled the Hynix RAM card from slot three – and the machine booted!!! So I bought a new Crucial Ballistic card, put it in slot three and was able to boot and go. About a month later, I bought two more Crucial Ballistic RAM cards, put them in slots 2 and 4 and was able to boot up and go. Don’t remember if I had problems booting then. Everything was good until incident #2.

============ incident #2 around 9/9/15 ======================
On September 9th, we had some home network issues so shut down my machine. When I tried to restart, it wouldn’t boot – it went into the restart cycle described above. I started logically swapping RAM cards, testing Slot #1 only, #1+#3, and all four slot filled to see if my remain factory Hynix RAM card had gone bad. Inexplicably – truly inexplicably – after testing and retesting, it successfully rebooted with Crucial cards in #1+#3 on a the second restart of a test. So I was good to go until I had to shut down on 9/17 to clear some stuck browser processes that I couldn’t kill. (Which were weird, but I don’t think related – this really seems to be a hardware problem.)
 
Solution
It does sound like the motherboard is getting wonky.

Have you tried rotating one stick of RAM through the different slots and seeing if you get different results? If only one memory slot or one channel is going bad, you may still be able to use the others. Same if you have one bad stick of RAM and that happened to be the one you were testing with.

edit: no, there's not really a way of repairing it when a slot goes bad. And if it were possible, the cost would likely exceed that of a new board anyway, especially the cheapo ones they use in prebuilt systems.

threazy

Reputable
Sep 18, 2015
12
0
4,510
Thanks, Sapphire. I just followed the steps here: http://www.tomshardware.com/forum/261145-31-perform-steps-posting-post-boot-video-problems The specific relevant paragraph is

"If you get the long beeps, add a stick of RAM. Boot. The beep pattern should change to one long and two or three short beeps. Silence indicates that the RAM is shorting out the PSU (very rare). Long single beeps indicates that the BIOS does not recognize the presence of the RAM."

I get the long beeps with no RAM. I get silence and the restart cycle as soon as I insert a RAM card. Therefore, I conclude that my problem is most certainly the RAM slots. Now the question is: can I get those repaired or do I need a whole new motherboard. (I think I need the whole new motherboard. :-( )
 
It does sound like the motherboard is getting wonky.

Have you tried rotating one stick of RAM through the different slots and seeing if you get different results? If only one memory slot or one channel is going bad, you may still be able to use the others. Same if you have one bad stick of RAM and that happened to be the one you were testing with.

edit: no, there's not really a way of repairing it when a slot goes bad. And if it were possible, the cost would likely exceed that of a new board anyway, especially the cheapo ones they use in prebuilt systems.
 
Solution

threazy

Reputable
Sep 18, 2015
12
0
4,510
Thanks, Taco - Yes, I've tried both an original memory card and a brand new card (several, actually), in all the slots. Does seems weird, though, that none of the cards work in any of the slots. Can they all fail at once? Or is there something downstream that is failing?

Gonna order me a new board. :-(

Bill



 

threazy

Reputable
Sep 18, 2015
12
0
4,510
Final result: sent the machine back to HP for repair. They replaced the mobo - same partno, thankfully, and I was able to bring back my original environment by plugging in the original OS drive on an SSD. The only problem now is that Windows is asking for an activation key.

And fwiw, I want to give a shout-out to HP Customer/Repair Service. I don't know what has changed (I thought HP was notorious for bad service), but my customer service and repair experience was absolutely excellent.
 
Wow, that's pretty good that they were able to get it fixed for you like that and glad everything works.

Usually a pre-built machine will have a sticker on the back or side with the Windows registration key for that specific machine (OEMs like HP are required to do that by their license agreement with Microsoft, I believe). If you can't find one, call HP up again and they should be able to help you.
 

threazy

Reputable
Sep 18, 2015
12
0
4,510
2016-09-01: followup: the problem resurfaced about a week ago. This time, pulling the video card enabled the machine the boot, albeit with a few false starts. At the recommendation of a techie friend, he suggested updating the bios. I did - and it's a very different bios - and the machine has booted up smoothly each time since. Not sure if this is THE solution, but it certainly seems to have helped. (Got a new video card, too.)
Here's the bios update:
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-HPE-h8-Desktop-PC-series/5258496/model/5261720
 

nybigapple

Distinguished
Nov 13, 2011
1
0
18,510


I really think this is a bios issue. Somehow the bios gets corrupted. Maybe something to do with UEFI as that often causes boot problems, and is exactly what the bios you just updated to addresses. I just had the same exact issue as you come up a bit after upgrading to windows 10.

I found no solution and was never able to boot again. I had to buy another motherboard. I opted for the exact same motherboard again and will be sure to update the bios ASAP.