Unsolved
This post is more than 5 years old
14 Posts
0
4106
January 25th, 2004 23:00
System CMOS checksum bad
I know this is a Dell Site but I have both a Dell and an older Hewlitt Packard. The HP is the one I am stating the problem with I have an older computer which uses windows 98SE a few months back I took it to a computer tech here in which they were suppose to have fixed it charged me 80.00 (to optimize, install AVG anti-virus protection, AD Aware, critical updates checked inventory for operation/Operationally checked for internet connectivity) in which it already had an antivirus program on it. Well after 3 months it started the same ol thing up again when you turn it on it boots but gives you this:
Phoenix Bios 4.0 Release 6.0.0
Copyright 1985-2000 Phoenix Technologies LTD.
Copyright 2000 by Hewlitt Packard, Inc.
Rev 1.15
P.U. Intel (R) Celeron (TM) Processor 600MHZ
40K sys. Ram Passed
2 M extended Ram Passed
128K Cache SRAM Passed
System Bios Shadowed
Video Bios Shadowed
something....MB upper limit segment address :E89D
Mouse initialized
fixed disk 0:WDC WD205AA-00BAA0
ATAPI CD-ROM : CRD 8483B
Error
251:System CMOS Checksum Bad-Default Config. used
Press (F1) to set-up (F2) to resume
if you press F2 it will take you to the windows screen I am taking a computer tech course but am not far enough into my studies to know exactly how to fix this problem..I know that this isn't good to run your computer in this kind of state so if anyone knows how to fix the problem PLEASE PLEASE give me step by step instructions on how to correct this problem. I do not want to take it to another tech for them to do the same thing charge me then it goes back to doing this in 3 months time.......Or if you know of anyone who can help me please let me know.....
Thank You Scooter


jwatt
4.4K Posts
0
January 25th, 2004 23:00
Jim
scooter1963
14 Posts
0
January 26th, 2004 00:00
jwatt
4.4K Posts
0
January 26th, 2004 00:00
The documentation you will need is the service manual for the motherboard installed in your computer. Without that I could only guess. You may be able to find the information somewhere on the HP Web site.
(edit)
this is what the box said that the computer came in
Was there an HP model number on the box?
Jim
Message Edited by jimw on 01-25-2004 06:19 PM
scooter1963
14 Posts
0
January 26th, 2004 00:00
What documentation do you need?
this is what the box said that the computer came in
20GB hard drive
64MB SDRAM memory
48X max speed CD-ROM
56K modem Celeron Intel 600MHZ Processor
upgradeable
scooter1963
14 Posts
0
January 26th, 2004 13:00
jwatt
4.4K Posts
0
January 26th, 2004 15:00
Thanks for the model number. By searching HP's support site, I found this article describing replacement of the battery. As the article says, you can likely purchase a replacement battery at a local computer parts store.
Jim
scooter1963
14 Posts
0
January 28th, 2004 14:00
jwatt
4.4K Posts
0
January 28th, 2004 19:00
You're welcome! Did replacing the battery resolve the problem?
Jim
scooter1963
14 Posts
0
January 29th, 2004 15:00
scooter1963
14 Posts
0
February 4th, 2004 01:00
ok got the battery changed on Sunday Feb 1st then today Feb 3rd it starting doing the same thing with the 2 beeps then what I've said above
I was told that if I unstall all peripherals then install them one by one that this would tell me what the problem is will it? IF not do you have any other suggestions on why this computer would be doing this?
Thanks Shelly
scooter1963
14 Posts
0
February 4th, 2004 01:00
scooter1963
14 Posts
0
February 4th, 2004 02:00
chuket
1.4K Posts
0
February 4th, 2004 02:00
scooter 1963
Most checksum errors are caused by the battery as referenced below:
http://www.pcguide.com/ts/x/sys/booterrGBER08-c.html
And this
Q. Can you tell me what causes CMOS checksum errors?
From:
http://www.duxcw.com/faq/cmos/cmos.htm
To rule out a virus, do an online virus scan at:
http://housecall.trendmicro.com/
Select housecall
If you want to try an experiment, leave the comp on 24/7 (with a new battery). Then shut down for ~ 5 minutes and immediatley restart. Do this for a week (or until the same thing reoccurs) and see if it keeps running with no problems. If it runs with no checksum errors then it should point to something draining the battery with the system shutdown.