Forum Home
Press F1
Thread ID: 35948	2003-07-26 08:07:00	BIOS ROM Checksum error	Stumped Badly (348)	Press F1

Post ID	Timestamp	Content	User
163020	2006-09-13 10:04:00	BIOS ROM Checksum error And the point of you raising a 3 year old thread from its grave is...?	godfather (25)
163021	2006-09-14 02:23:00	GF: Probably the point is that a new user has done the right thing: searched the archives for a problem occuring now, found a thread which describes the problem, but does not solve it, and hopes further wisdom might have accrued to the massed intellects of PressF1 in the interim. :D From your welcome, GF, perhaps not :( ;) Welcome to PressF1, satishrd. I might modestly suggest that my post in that thread could still be appropriate. :cool: Have you recently added any hardware which would increase the startup load on the power supply? Big hard disks are obvious candidates, but I suppose even a few big fans might also give a bit of a shock to the PSU at starting. A new CPU which pulls more current might also be a cause. But that's on the assumption that your problem is very similar to that described. A bit more (or any ;) ) information about your system and the frequency of the problem would help.	Graham L (2)
163022	2006-09-14 12:47:00	Nobody seems to be listening (?) Graham but just incase someone reviews this thread in another couple of years it has been my experience that this condition is almost without exception caused by a flat cmos battery. HTH JT	jinja_thom (4306)
163023	2006-09-14 23:07:00	Nobody seems to be listening (?) Graham but just incase someone reviews this thread in another couple of years it has been my experience that this condition is almost without exception caused by a flat cmos battery. HTH JT Highly unlikely. In this case it was a faulty board. Probably a dud bios, a replacement board fixed it and it has been running without a hitch ever since	bartsdadhomer (80)
163024	2006-09-15 01:45:00	jinja-thom: There are two different checksum error messages the BIOS can produce. The other one indicates a flat battery, which causes the BIOS data to be lost (and the clock to stop working). This particular one means a major problem in the BIOS executable code area which should not change by accident, nor be "lost". Modern ("flashable" for updates) BIOSs would have a section of unchangeable bootstrap code which does the checksum on the "flash" code. then starts the actual POST. If that went away, you wouldn't even get even this message. :D	Graham L (2)
163025	2006-09-15 06:02:00	Graham L thanks for that, just how do the two messages differ ? so I will recognise the difference in future. JT	jinja_thom (4306)
163026	2006-09-15 06:37:00	If it says something like "BIOS ROM Checksum error", it's serious. ROM= Read Only Memory ... that's the part which isn't changed by the setup routines, or by auto configuration. There is a checksum stored with it. (All BIOS extensions, like those in the ROMs in video cards etc use the same system). The BIOS configuration data are stored in battery backed "RAM" (read/write memory), and a new checksum is calculated and written into it when you use the Save and Exit option. Any error message when the checksum doesn't agree with the data will not mention "ROM".	Graham L (2)
163027	2007-12-20 15:14:00	Hey guys, so sorry about digging this topic up again.. I have the same problem as been above, the problem may be that the BIOS chip has gotten some damage... and needs specific BIOS for M/B but the thing is that my M/B does not take my Floppy drive and I cannot connect any FDD-s do it.... what should i do?	Lammutaja (4307)
163028	2007-12-20 17:59:00	are you able to boot from usb device if so 1. purchase a usb floppy and try that 2. put files on a usb pen stick and boot off that	beama (111)
163029	2007-12-22 13:43:00	I was given a PC with the same symptoms . After reading your posts, I pulled 3 pieces of RAM off, and found three different size, speeds . I put one piece of appropriate RAM in, and it started right up . I'm sure there are several issues that may cause these symptoms . But you might check the RAM . . .	pe1369 (4308)
1 2 3 4