Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

HP G6000 Not booting issue - only boots if CMOS is removed

Nov 1, 2009 11:30PM PST

A standard boot up will not happen. This laptop will only boot up if you take the cmos battery out for 20 minutes (and the mains power and the main battery) - ie BIOS memory cleared.

If I choose restart from Windows it will not boot - there is no Bios info or options - the power light comes on, the HDD LED flashes once and the fan spins for 0.5 seconds. Then it tries the above again.

I have loaded up new versions of the bios and tried all kinds of chk disk and googled for hours but seems all advice is just to replace the CMOS battery which I have done already....

I have re-seated the RAM, used one then the other, in both RAM ports, doesn't appear to be a RAM issue.

Any ideas? or is the mobo toasted?

Thanks

Rory.

PS running Windows Vista Home Premium which boots happily from a cleared Bios memory.
PPS Exact model number is HP G6065EA

Discussion is locked

- Collapse -
Tell me one more thing.
Nov 1, 2009 11:41PM PST

Using your Digital Volt Meter, what voltage is that CMOS battery reading?

The other clue is the trials of other BIOS versions. That's never a good sign. I think in 20 years that paid off 2 times. So go back to the ORIGINAL BIOS issue.

Sadly, as told it looks like a new mainboard is needed.
Bob

- Collapse -
CR2032 -3volt - I have tried the original one and 2 new ones
Nov 2, 2009 12:10AM PST

The BIOS was only updated to see if it would resolve the issue - it made no difference - so I am thinking it is a Mobo issue - except flushing the Bios memory causes it to start correctly... which leads me to think there is a Bios influence to the issue...

- Collapse -
I disagree
Nov 2, 2009 1:29AM PST

While there is likely something that could be coded (that is written NEW by a programmer) the story is consistent with a failed board. Here's how I demonstrated this to a customer (that paid for the demo!) years ago. We installed the new board and it worked. They paid for us to demo the old board and the reset same as the new board and the old board failed every time. Flip in the new board and it worked first time every time.

Still rare to find someone that would pay another 2 hundred to prove they were not being ripped off by a board change but it was interesting and a lesson they were willing to pay for.
Bob