hmmmmmmm. Got a little prob here and have to head off to work, so I don't have time to mess with it right now.
It's my kidz/wife's PC ( 1 gig Duron, not OCed, Iwill XP333R). Here's the msg I get at boot.....
Award BootBlock BIOS v1.0
BIOS ROM checksum error
Detecting floppy drive A media...
INSERT SYSTEM DISK AND PRESS ENTER
I've tried clearing the CMOS etc but will have to wait til later to go thru the box and reseat everything. Any ideas in the meantime.
Thanks in advance,
Todd
Anybody ever seen this msg @ boot up? WTF?
Anybody ever seen this msg @ boot up? WTF?
AMD Ph II X4 955 BE 3.2 @ 3.8 GHz | Scythe SCSMZ-2000 | ASRock 880GMH/USB3 | 8 GB G.Skill DDR3 1600 | Radeon HD5670 | Kingston 128GB SSD
-
NascarFool
- Posts: 3263
- Joined: Thu Nov 23, 2000 1:21 pm
yea I have seen it before but I donmt remember what Idid to fix it.
Greg
Greg
<a href="http://www.pcabusers.org" target="_new"> <img src="http://www.pcabusers.org/images1/banner.jpg" border="0"></a>
<a target=NEW href="http://setiathome.ssl.berkeley.edu/stats/team/team_87793.html">JOIN the PCA Seti Team!</a>
<a target=NEW href="http://setiathome.ssl.berkeley.edu/stats/team/team_87793.html">JOIN the PCA Seti Team!</a>
From here
http://www.pcguide.com/ts/x/sys/booterrGBER03-c.html
Diagnosis: The BIOS ROM chip on the motherboard is probably faulty. It could also be another component on the motherboard.
Some interesting tips here also
http://mall.eyo.com.au/tech-forum/posts/415877.html
<i>"The message means that your CMOS Settings were different when you started to boot up than they were the last time you saved CMOS settings. Most likely is the CMOS battery is getting weak (does the PC Clock lose time when your PC is OFF?). You should be able to get going if you enter CMOS Setup and perform a new save; you may need to do this every time you boot up if the battery is weak."</i>
And from Iwill
http://support.iwill.net/Q&A/AnsBIOS.htm
What is ROM checksum error?
Answer:
ROM checksum error mean the BIOS has been re-programming or orrupt on some area. Please to re-programming or replacement the EPROM by your local dealer.
http://www.pcguide.com/ts/x/sys/booterrGBER03-c.html
Diagnosis: The BIOS ROM chip on the motherboard is probably faulty. It could also be another component on the motherboard.
Some interesting tips here also
http://mall.eyo.com.au/tech-forum/posts/415877.html
<i>"The message means that your CMOS Settings were different when you started to boot up than they were the last time you saved CMOS settings. Most likely is the CMOS battery is getting weak (does the PC Clock lose time when your PC is OFF?). You should be able to get going if you enter CMOS Setup and perform a new save; you may need to do this every time you boot up if the battery is weak."</i>
And from Iwill
http://support.iwill.net/Q&A/AnsBIOS.htm
What is ROM checksum error?
Answer:
ROM checksum error mean the BIOS has been re-programming or orrupt on some area. Please to re-programming or replacement the EPROM by your local dealer.
[align=center]<img src="http://www.statgfx.com/statgfx/folding/?&username=blade&border=0,0,64&custom=21,138,255&label=79,79,255&header=149,202,255&stats=0,255,255&bgcolor=0,0,181&trans=no&template=fah_original&.jpg" alt="www.Statgfx.com" />
<img src="http://www.pcabusers.org/funnies/monkey2.gif">
<i><small>"Too much monkee business"</i></small>[/align]
<img src="http://www.pcabusers.org/funnies/monkey2.gif">
<i><small>"Too much monkee business"</i></small>[/align]
- FlyingPenguin
- Flightless Bird
- Posts: 33162
- Joined: Wed Nov 22, 2000 11:13 am
- Location: Central Florida
- Contact:
XP333's sometimes scramble the BIOS if overclocked and it's a bit tricky to clear them.
I found is mentioned in the IWill forum at AMDmb and saved it for future reference:
"Eventually I found what worked the best most of the time was shutting off the power, holding the insert key and power back up. When it got stubborn, isolating from the AC line, waiting five or ten minutes, using the jumper to clear CMOS and then powering up worked."
I found is mentioned in the IWill forum at AMDmb and saved it for future reference:
"Eventually I found what worked the best most of the time was shutting off the power, holding the insert key and power back up. When it got stubborn, isolating from the AC line, waiting five or ten minutes, using the jumper to clear CMOS and then powering up worked."
---
“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez

“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez

haha, don't I know it from OCing the stink out of these mobos!Originally posted by FlyingPenguin
XP333's sometimes scramble the BIOS if overclocked and it's a bit tricky to clear them.
Thanks for the input fellas. Appreciate it.
AMD Ph II X4 955 BE 3.2 @ 3.8 GHz | Scythe SCSMZ-2000 | ASRock 880GMH/USB3 | 8 GB G.Skill DDR3 1600 | Radeon HD5670 | Kingston 128GB SSD
- CaterpillarAssassin
- Almighty Member
- Posts: 2252
- Joined: Wed Nov 22, 2000 11:29 am
- Location: somewhere in N.E

