Computing.Net > Forums > Windows 95/98 > CMOS/GPNV checksum bad

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

CMOS/GPNV checksum bad

Reply to Message Icon

Name: goingoutofmymind
Date: November 2, 2006 at 12:00:17 Pacific
OS: W98 SE
CPU/Ram: Intel 486 / 256MB ram
Product: Dell / Dimension 4100
Comment:

Need a CMOS expert, PLEASE!
CPU cannot boot up in normal mode, hangs with the W98 background screen. If reboot in safe mode, I get access, but can't seem to print, get internet, etc.

Today, message came up "CMOS/GPNV check sum bad", forcing me to go to BIOS screen. Didn't know what to do?

I've read a couple of threads that "battery" could be an issue. Don't know where to find or check this. Also, if battery not working, why is my computer clock and date bang on?

I'm in a little bit of a panic. Can anyone help?

EPL



Sponsored Link
Ads by Google

Response Number 1
Name: jboy
Date: November 2, 2006 at 14:49:43 Pacific
Reply:

A 486 with 256Mb or RAM?? Right.

Panic? (CMOS 'expert'?)

You might want to clear the CMOS data (in case of corruption) by either temporarily removing the battery or, if present, using the 'clear CMOS' jumper

Diplomacy is the art of saying 'Nice doggie!'... till you can find a rock


0

Response Number 2
Name: Rimfire
Date: November 2, 2006 at 14:52:46 Pacific
Reply:

Sounds like quite a glitch. The CMOS checksum error means something has changed in the CMOS settings since they were last saved. Go into the settings and load the defaults. Check that your drives are correctly recognised. If not, there may be an auto detect function. Once this is done save the changes and exit.

The inability to boot into Windows might be a result of the CMOS corruption. Windows might be trying to configure a phantom device. However I think it is more likely that this is a separate problem.

Let us know how you get on.


0

Response Number 3
Name: OtheHill
Date: November 2, 2006 at 14:54:57 Pacific
Reply:

Try booting to the BIOS screens and resetting values there to correct settings. The battery could still be an issue. With a 486 vintage computer the battery has to be old. Hopefully the battery is the removable type. If removable, the battery looks like an oversized watch battery. About the size of a quarter and about 1/4 inch thick. Take care not to bend the contacts when removing. You should be able to find a replacement at most any computer shop or Radio Shack. If you don't see a battery as described then it may be the older style barrel type that is soldered in.


0

Response Number 4
Name: goingoutofmymind
Date: November 2, 2006 at 15:47:40 Pacific
Reply:

Thank you to all 3 responses. Maybe some more light to shed on the information, based on your advice:

jboy: You're right, it's not a 486 processor, properties on my computer had X86 family, but I think it's the pentium III. I purchased it in 2000. My old profile has the following: Intel 82801 / 256 MB It's definately 256.

Rimfire: Installing a phantom device is not way out there. I've had modem problems for the better part of a year. Also, more importantly, I installed a new game for my son a couple of weeks ago. It's a 3-D game, not sure if my CPU can handle it, seems to be quite taxing on resources. Not sure if this is having an adverse affect on my box. Chip is an ATI Radeon 7200 AGP version 4.00

OthHill: My apologies, chip is not a 486.

OK, if I'm reading everyone correctly, if I change the battery, then I need to restore CMOS to factory settings. But If I change CMOS settings to this now, and it doesn't work, then would a new battery make a difference? My date and time seem to work fine, or does "boot up" require a significantly higher output from the battery, therefore, clock could be working OK, but not enough juice for boot?

What do you suggest I try first? New Battery or reset CMOS? Thanks.

EPL


0

Response Number 5
Name: jboy
Date: November 2, 2006 at 16:02:37 Pacific
Reply:

Sure - it'd have to be one very unique 486 to support that much RAM - I'd posted a link to the factory specs, so those appear to be reasonably acdurate.

CMOS isn't so complicated that it requires its own 'experts' - at least, for basic user interaction.

If time & date are ok, then a new battery does not seem indicated - although just by taking the battery out, that'd likely reset it to default values (unplug it though)

On a modern machine, the battery should be the 'standard' removeable type

Diplomacy is the art of saying 'Nice doggie!'... till you can find a rock


0

Related Posts

See More



Response Number 6
Name: OtheHill
Date: November 2, 2006 at 16:09:53 Pacific
Reply:

I didn't notice the RAM size. Clear the CMOS and reset to optimal settings. Check onboard hardware to enable or disable as needed, or set to AUTO. The following may not apply. Set first boot device and first graphics device to look for. You may need to change front side bus speed, memory speed, etc.


0

Response Number 7
Name: goingoutofmymind
Date: November 2, 2006 at 16:32:22 Pacific
Reply:

OK, so we're going to re-configurethe CMOS.

1) How do I set to "optimal" setting? I can load setup defaults or custom defaults?

2) The only reference to "onboard hardware" is in the 'advanced' tab. Peripheral Configuration has Serial & Parallel Ports set to AUTO, and USB support "enabled"
There is also and IDE and Diskette Configuration

3) Boot Configuration:

a) Quite Boot is enabled
b) Quick Boot is disabled
c) 1st Boot device is floppy
d) 2nd boot device is ARMD-FDD
e) 3rd boot device is IDE-HDD
f) 4th is ATAPI DCROM
g) 5th is disabled

there doesn't seem to be a "look for" choice for these boot devices.

4) I am clueless as to how to change front side bus speed, memory speed, etc

EPL


0

Response Number 8
Name: OtheHill
Date: November 2, 2006 at 16:42:40 Pacific
Reply:

As stated, being a Dell, you may not have any options to set FSB, etc. I am clueless as to what ARMD-FDD is. Try setup defaults. I suggest setting to boot to CDROM before IDE-HDD. Just don't keep a disk in the drive. The look for refers to the type of graphics device installed (AGP or PCI). Again, being a Dell means that setting may or may not be available.


0

Response Number 9
Name: jboy
Date: November 2, 2006 at 16:48:12 Pacific
Reply:

"therefore, clock could be working OK, but not enough juice for boot?"

Your computer is not 'powered by' the CMOS battery - all that does is power a tiny memory circuit that retains various hardware settings when the machine is shut off or unplugged.

It seems these values have been corrupted, which may be corrected by resetting to default values

Diplomacy is the art of saying 'Nice doggie!'... till you can find a rock


0

Response Number 10
Name: dave01
Date: November 2, 2006 at 20:00:38 Pacific
Reply:

ARMD-FDD
Advanced Removable Media Device (zip drive or LS120)


0

Response Number 11
Name: Rimfire
Date: November 3, 2006 at 04:04:19 Pacific
Reply:

The BIOS settings vary in every different motherboard and sometimes even different revisions of the motherboard. That is why you will never find a concise guide to CMOS settings.

You have the choice of "setup defaults" or "custom defaults". Of the two I would choose setup defaults. This is the safe choice. Custom defaults should work better, but until you have sorted out the problem, stick with the safer choice.

CMOS RULE OF THUMB: If you don't know what it does, leave it alone!

Since you have had some trouble with your modem, it is to be considered a prime suspect with the inability to boot windows. Safe Mode will not attempt to load modem drivers. If you still can't boot into windows after resolving the CMOS glitch, it might be worth removing the modem. Both physically and its drivers. You can remove the drivers by deleting the entry in device manager (Right click 'my computer' and click on properties)


0

Response Number 12
Name: goingoutofmymind
Date: November 3, 2006 at 08:08:30 Pacific
Reply:

Hi Everyone. Latest update...

The GOOD news, is that I've successfuly booted in Normal mode, seem's like I'm back to getting my time sensitive work completed. Thanks to everyone for their advice.

The BAD news, is that I'm not sure why it worked. I reset the CMOS to factory defaults, and everything went reasonably fine. Took a while to get from the W98 screen to my desktop? I didn't think is was going to work. I took a quick peek at the CMOS prior to exiting, but I didn't see any changes. Nor, do I recall in the past several years, ever having to go in there. So I'm not sure why it worked?

I will be back in touch in the next few days to provide follow up after a more rigorous look at CMOS. In the meantime, GREAT JOB, thx again to everyone for all your help.

EPL


0

Response Number 13
Name: jboy
Date: November 3, 2006 at 15:48:32 Pacific
Reply:

Glad to hear that things are working

Familiarity with one's own machine (including the CMOS setup) is an asset - they are all different, but more or less the same too

"I'm not sure why it worked. I reset the CMOS to factory defaults,"

Well... that was the advice given, and was explained somewhat at least once before - that data was corrupted (didn't "make sense" to the computer) and resetting likely replaced the 'bad' data with 'good'

Diplomacy is the art of saying 'Nice doggie!'... till you can find a rock


0

Response Number 14
Name: goingoutofmymind
Date: November 7, 2006 at 17:07:08 Pacific
Reply:

Hi Everyone,
I've been able to reboot my computer several times, all of which has been successful. I would consider this particular issue now solved. Thx to jboy for the followup, as well as everyone else for thier kind advice. Until next time...

EPL


0

Response Number 15
Name: TP
Date: February 17, 2007 at 07:59:46 Pacific
Reply:

I've had the same issue and addtional problems. My continuing issue is that when I change the battery the first boot says "CMOS battery low". The next boot it goes bact to "CMOS/GPNV checksum error". I don't know where to go from here. I've used three new batteries, 1 CR2032 and 2 DL2032s. Help!

TP


0

Response Number 16
Name: OtheHill
Date: February 17, 2007 at 08:27:31 Pacific
Reply:

Tim

Start a new thread for your problem. Give complete system specs and description of your problem.


0

Response Number 17
Name: TP
Date: February 18, 2007 at 07:18:58 Pacific
Reply:

Dell Dimension 4100 Pentium III. I purchased it in 2000. My old profile OS was Millenium 2000. I have 384 MB RAM & 1GZ


0

Response Number 18
Name: OtheHill
Date: February 18, 2007 at 08:35:22 Pacific
Reply:

dWhen I said to start a new thread that meant to go to the home page of this forum and enter a post there. This thread is old. You will get better support by having your own thread.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 95/98 Forum Home


Sponsored links

Ads by Google


Results for: CMOS/GPNV checksum bad

Cmos/gpnv checksum bad www.computing.net/answers/windows-95/cmosgpnv-checksum-bad/132560.html

CMOS Checksum Bad www.computing.net/answers/windows-95/cmos-checksum-bad/104853.html

CMOS Checksum Bad www.computing.net/answers/windows-95/cmos-checksum-bad/73328.html