My brother was trying to copy a file from my computer via "hard disk -slave." But he forgot to take out the jumpers from the hard disk on my computer and his hard disk that was supposed to be slaved. Both hard disk jumpers were set on Primary while connected to the IDE cable. Then my computer crashed. i then formatted my cpu. But this time, when I turn on the system, a message error pops up which state "Cmos Bad Checksum." I tried to clear the RTC(Real Time Clock) RAM by removing the onboard battery and moving the jumper cap from pins 1-2(default) to pins 2-3. Kept the cap on pins 2-3 for about 5-10 seconds, then move the cap back to pin 1-2. Then I reinstalled the battery and turned on my computer. But still the "Cmos Bad Checksum" error still pops up. When I turn on my system, it keeps on rebooting.One time I managed to get through. I take a look at on the device manager and on the processor, there appears to be two processors, when in fact, I only got one. By the way, here's my computer specs
Bios Type: AMI
Bios Date: August 29, 2007
Bios OEM Date:Ver. 8.00.12-0807
Chipset: Via 82C314 rev 0
MotherBoard: ASUS P5VDC-MX
Maximum Memory: 2048MB
Reseat your ram modules and remove the 2nd hdd
If same thing , then reset the Bios to default ,save and exit
If same thing ? assuming you have more then 1 stick of ram,, try booting with 1 stick removed . to eliminate ram modules being bad
then switch ram untill you have verified ram chips are or aren't bad
Hope this helps
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
The most probable reason you are getting the bad checksum error is you have to set the date and time because you have cleared the CMOS and reset the BIOS. You should also get a message that says press F1 to load defaults or press a certain key to access setup. Access setup (BIOS) and set the date and time. That should take care of the bad checksum error. Another good idea is make sure the motherboard battery is not dead either.
I guess everyone working on a computer is familiar with the word BIOS and what exactly it is? Still let me tell that BIOS is intelligent software that enables the system to start. I need not to mention that system here refers to computer. Bios facilitate the booting of a system without human intervention. BIOS is a program that is installed in a hardware chip known as ROM chip.
This single word matters a lot to most of the users who face various problems when their system failed to start normally or make some unusual activities. Each time I visit any technical forum I see a lot many users posting their problem regarding BIOS. I researched on internet about BIOS errors and from my knowledge and experience I am posting this piece of help for those who find themselves helpless in getting a solution to BIOS problems.
Sometimes BIOS itself provide a troubleshooting to most of the problems. When you power ON your system it give beep sound. Checkout some beep codes 1 short Beep indicates System is OK (Acceptance Beep) Continue long Beep tells RAM Problem 1Long 3 Short Beep confirms RAM Problem 2/3/4 short Beep --its time to Check the RAM & Video Card
By now most of you have found some clue about the problems you are facing. Now learn about POST faults 1) K/B Error/ NO Keyboard present ·Check the loose cable connector ·Cable may be bad (Keyboard) ·K/B itself may be bad ·Check the physical condition of K/B connector on M/B ·If all these are ok & problem is still processed ·Than replace the keyboard port 2) Floppy disk drive Fail ·loose data & power connector of FDD ·Data cable may be bad (FDD) ·Load the CMOS defaults ·Floppy disk drive itself may be bad 3) CMOS Checksum error ·CMOS battery has gone bad replace it. (Weak) ·Check the CMOS jumper it may set on clear ·If the entire ok than check the CMOS battery jack, it may be bad
4) Invalid System Disk, Insert System Disk & Press enter when ready/ NTLDR is Missing ·Check the root directory; it may be formatted or missing bootable files. ·Repair the Windows or Reinstall the operating system.
5) Disk Boot failure, Insert System Disk & Press enter when ready ·Hard Disk check in POST Detected or not ·If not Detected Check the power cable ·Check the Master/Slave jumper setting. ·Also check BIOS setting 6) Computer gives message: Your computer has a serious problem Back up your data & replace your Hard Disk This error message is displayed due to the SMART option. This scans the HDD for errors, if it detect the errors than it show the above message. Follow the error message & back up your data on to another drive. I tried to explain most of the problems along with their solutions. There could be a lot more solutions for the problems. Make your own search and try to fix BIOS problems at your own home. Forward this to all those who need help!! SOVI
> Primary IDE Master: NONE
> Primary IDE Slave: SP0822N
Good. Your motherboard has detected ONE disk-drive.
Do you have just one connected disk-drive on your PRIMARY channel, or do you have two connected disk-drives (via the 2 connectors on the one ribbon-cable on the PRIMARY channel) ?
If you have two drives connected via one ribbon-cable, you MUST set the 'master/slave/cable-select' jumpers on BOTH disk-drives, to identify which of the two will be the 'master' and which will be the 'slave'.
Also, check that the 'second' disk-drive is getting electrical power.
> NTLDR MISSING
Like I said, you deleted 99% of the files, including the 'NTLDR' file.
Your computer is trying to "boot" from the 1% of the files that still exist on the disk-drive, but cannot find the now-deleted file.
Perfectly normal, given that you have formatted the disk.
Jumper off will set the drive to slave. If you can connect both drives to the same ribbon cable with the master on the end & the slave to the second connector. Look at your bios as win is booting up to see if shows the drive as slave, you will not be able to copy windows as a operating system off of the drive, but should be able to copy files.
Ofcourse you can, look at the top of the hard drive to find the jumper settings lable, change the jumper so the drive is slave.
Then connect it to your computer with a ide cable, if you have another hard drive on the same cable the other hard drive needs to be set as master, and be preferably on the end of the cable and slave on the center of the cable.
Then check your bios / cmos / cmos setup / computer setup, right when you turn on the computer to see if the hard drive is detected and properly installed.
if everything is okay it should show up in windows, if it doesn' then right click on my computer, select manage, then on left side select disk management, you may have to initialize and or partition the disk first before it shows up on my computer.
first be sure the drive is a vaible drive.....meaning it should be in it;s originbal PC it came out of and able to boot up on the installed OS. If it can then you are in luck..... install the drive you want to copy to as a slave and use a program like DriveCopy or Norton Ghost to copy the entire drive.....or if you are just after select files, you can use the copy/paste method to the drive. By trying yo use the drive in a different PC it will not boot since it has the other PC's drivers on it =( If the drive will not detect in it's native machine then most likely the drive is lost (unless you pay to clean room recover the contents....spendy!) Let mem know if you need more help!
BOOT BLOCK COMPATIBLE VERSION VER .005 BAD BIOS CHECKSUM CHECKING FOR CD ROM READING FILE "P5SD2VM.ROM" READING FILE "P5SD2VM.ROM" READING FILE "P5SD2VM.ROM" READING FILE "P5SD2VM.ROM" READING FILE "P5SD2VM.ROM" NO CD-ROM FOUND CHECKING FOR FLOPPY DISK READING FILE "P5SD2VM.ROM" READING FILE "P5SD2VM.ROM" READING FILE "P5SD2VM.ROM" READING FILE "P5SD2VM.ROM" READING FILE "P5SD2VM.ROM" NO FLOPPY DISK FOUND