No operating system. Hadn't been able to get that far yet.
- Att
| Wayfarers of Veeshan http://www.wayfarersofveeshan.com/forum/ |
|
| BIOS ROM checksum error http://www.wayfarersofveeshan.com/forum/viewtopic.php?f=36&t=2825 |
Page 1 of 1 |
| Author: | Attrael [ Mon Jan 19, 2004 1:01 pm ] |
| Post subject: | BIOS ROM checksum error |
| Author: | Irodanis [ Mon Jan 19, 2004 1:22 pm ] |
| Post subject: | |
| Author: | Tanliel [ Mon Jan 19, 2004 2:54 pm ] |
| Post subject: | Re: BIOS ROM checksum error |
| Author: | Attrael [ Mon Jan 19, 2004 4:28 pm ] |
| Post subject: | |
| Author: | Kraznir [ Mon Jan 19, 2004 4:57 pm ] |
| Post subject: | |
| Author: | Tanliel [ Mon Jan 19, 2004 6:44 pm ] |
| Post subject: | |
There's the ZIP from : P4SPA+/P4SPE 4SPAC223.ZIP / 4SPAC223.exe ** R1.0C P4 478 800MHZ,DUAL DDR 4GB MAX, 5 PCI, 8 USB 2.0, Gb LAN CHP-052-SST |
|
| Author: | Attrael [ Tue Jan 20, 2004 7:45 am ] |
| Post subject: | |
That's the same exact bios that came with the board so the manufacturer is no help. On a side note, I ran a flash bios read/write test. It passed 3 of 4 read tests, and failed all 4 write tests... leading me to believe I have a mortally wounded bios chip... Another chip is being sent to me so when it arrives I'll try socketing the new one and see what happens. - Att |
|
| Author: | Shogi [ Tue Jan 20, 2004 8:49 am ] |
| Post subject: | |
your operating system is??? Remember also that if your using the dual DDR memory mode to put 1 stick in one dual bank & the other stick in the other set of bank/banks. |
|
| Author: | Attrael [ Tue Jan 20, 2004 10:04 am ] |
| Post subject: | |
No operating system. Hadn't been able to get that far yet.
- Att |
|
| Author: | Shogi [ Tue Jan 20, 2004 1:09 pm ] |
| Post subject: | |
OK...thought if usin 9x..its too much memory...if usin XP doesnt like the new hardware |
|
| Author: | Attrael [ Tue Jan 20, 2004 1:54 pm ] |
| Post subject: | |
Actually, what I think I'll do is take the mother board outside near my car, pop the hood, hook some jumper cables to my car battery, attach the other ends' positive terminal to one of those soldered chip nubs on the underside of one corner of the board, attach the other end's negative terminal to one of those soldered chip nubs on the underside of the other corner of the board, and get in the car and turn on the ignition. I wonder how many gigahertz I'll get out of it then... 
- Att |
|
| Author: | Shogi [ Wed Jan 21, 2004 10:22 am ] |
| Post subject: | |
| Author: | Attrael [ Wed Jan 21, 2004 7:20 pm ] |
| Post subject: | |
Well, I got the replacement bios chip today, installed it, powered up my computer, and bam, it still doesn't work. The system is still flakier than blonde in a blizzard and I still get the BIOS ROM checksum errors... So, with that in mind I'm packing the mother board back up and am going to see if I can return it... Anybody have any suggestions on what they think would be a good 800 Mhz FSB mother board for a P4 3.2 Ghz processor? I had picked SuperMicro because I've had good luck with them in the past, but this is my first 'bad' motherboard I've ever encountered so I'm both a little disenchanted and spooked by the whole thing.... Granted, it was only $140 for the board, but that's assuming that the processor made it through the ordeal ok and will sit happily in another board someday... (sigh) - Att |
|
| Author: | Shogi [ Wed Jan 21, 2004 9:40 pm ] |
| Post subject: | |
Internal BIOS checksum or code verification errors Explanation: The system has detected an error within the BIOS ROM. The read-only memory (ROM) containing the BIOS program (which is what is running when you turn on the PC and what generates this error) uses a checksum value as a double-check that the ROM code is correct. This checksum is compared against the values in the ROM each time the PC is booted and if there is a mismatch, this code is generated. Note: This error is not the same as a CMOS Checksum Error, which refers to corrupted values of the CMOS settings, the ones you set through the BIOS setup program. This error means the contents of the BIOS code itself are damaged. Diagnosis: The BIOS ROM chip on the motherboard is probably faulty. It could also be another component on the motherboard. Recommendation: Troubleshoot the motherboard. It is possible to replace just the BIOS ROM chip but often replacing the motherboard will make more sense for cost and simplicity reasons.There is an apparent failure of the motherboard or a system device on the motherboard Explanation: There is suspicion of a possible failure related to the motherboard. This can be a result of a specific message strongly implicating the motherboard in some sort of erratic system behavior. It may also be the case that the motherboard probably isn't the problem, but that we want to rule it out as a possible cause. Since the motherboard is where all the other components meet and connect, a bad motherboard can affect virtually any other part of the PC. For this reason the motherboard must often be checked to ensure it is working properly, even if it is unlikely to be the cause of whatever is happening. Diagnosis: Outright motherboard failure is fairly rare in a new system, and extremely rare in a system that is already up and running. Usually, the problem is that the motherboard has been misconfigured or there is a failure with one or more of the components that connect to it. Getting a system in the mail that has a loose component or disconnected cable is very common. In fact, though, there are a surprisingly large possible causes for what may appear to be a motherboard failure. Recommendation: Follow the suggestions below to diagnose the possible failure of the motherboard. You will find a lot of possible causes listed below, since there are so many problems that can make it look like the motherboard is at fault. This part of the Troubleshooting Expert is referenced by a large number of other sections. For this reason, you may want to skip some of the steps below if you have already tried them elsewhere. Also, try to avoid the very difficult diagnostic steps--especially replacing the motherboard--until you have exhausted the other possibilities both here and elsewhere on the site: First of all, if you have just recently installed this motherboard, or performed upgrades or additions to the PC of any sort, read this section, which contains items to check that may cause problems after working on the system unit. If the PC isn't booting at all, make sure you have at least the minimums in the machine required to make it work: processor, a full bank of memory, video card, and a drive. Make sure that all of these are inserted correctly into the motherboard, especially the memory. Partially inserted memory modules can cause all sorts of bizarre behavior. Remove all optional devices from the motherboard, including expansion cards, external peripherals, etc. and see if the problem can be resolved. Double-check all the motherboard jumper settings, carefully. Make sure they are all correct. In particular, check the processor type, bus speed, clock multiplier and voltage jumpers. Also make sure the CMOS clear and flash BIOS jumpers are in their normal, default operating positions. Reset all BIOS settings to default, conservative values to make sure an overly aggressive BIOS setting isn't causing the problem. Set all cache, memory and hard disk timing as slow as possible. Turn off BIOS shadowing and see if the problem goes away. Double-check all connections to the motherboard. Check the inside of the case to see if any components seem to be overheating. Inspect the motherboard physically. Check to make sure the board itself isn't cracked; if it is look here. Make sure there are no broken pins or components on the board; if there are, you will have problems with whatever component of the PC uses that connection. Check for any socketed components that may be loose in their sockets, and push them gently but firmly back into the socket if this has happened. Make sure the keyboard is inserted correctly into the motherboard. A failed cache module or using the wrong type can cause motherboard problems. If you suspect it, troubleshoot the secondary cache. An overheated processor can cause system problems. Try troubleshooting the processor. Troubleshoot the system memory. Memory problems are often mistaken for motherboard faults, especially on systems that don't have the protection of using memory error detection. Try troubleshooting the video card or replacing it with another one, preferably a simple straight VGA card that is known to work from being in another system that functioned properly. If the power supply is older, or this is a cheap case, or you have added many new drives to a system with a weaker power supply (especially one that is less than 200W) then you may have a power supply problem. You may want to try replacing it. You may have a BIOS bug or other problem. Check your manufacturer's technical support resources for any known problems with your motherboard. Check on USEnet as well. Contact the technical support department of your system or motherboard manufacturer for additional troubleshooting information. If this is a new motherboard, you may want to consider returning it for an exchange if you have exhausted all other troubleshooting avenues. Some newer viruses, when activated, overwrite part of the BIOS code in systems that employ a flash BIOS. If the BIOS is corrupted, the system won't boot. See here for ideas on recovering from this. Try swapping the motherboard with another one and see if the problem resolves itself. If it does then the original motherboard is probably faulty, but it could just have been misconfigured or installed incorrectly. Troubleshooting BIOS Beep Codes - Award BIOS Award is the other major BIOS provider today, along with AMI. Award uses by far the fewest beep codes of any of the BIOS manufacturers. In fact, they have only one beep code that I can find any reliable documentation on, and two others that I have had a couple of people report. (They prefer to use written error messages on screen, and only beep if they cannot access the video subsystem.) If there are others please let me know and I will add information on them. Next: 1 Long Beep: Memory problem 1 Long Beep: Memory problem Explanation: There is a failure of some sort related to the system memory. Diagnosis: The first bank of memory probably has a failure of some sort; this is usually just a physical problem such as an incorrectly inserted module, but may also mean a bad memory chip in a module. It is possible that there is a failure related to the motherboard or a system device as well. http://www.pcguide.com/ts/x/comp/ram/fail.htm Hope this Helps Attreal |
|
| Author: | Tanliel [ Thu Jan 22, 2004 7:44 am ] |
| Post subject: | |
If there are a few other features that you're looking for, I can certainly add that into my search (if you're interested in more assistance.)
|
|
| Page 1 of 1 | All times are UTC - 8 hours [ DST ] |
| Powered by phpBB® Forum Software © phpBB Group https://www.phpbb.com/ |
|