First cause is possibly a hardware change. Reboot at least once to see if the message clears. The most likely cause is the CMOS battery getting weak or has lost its power. This can be changed according to your motherboard's manual. Other much less likely causes I've seen reported are new hardware being incompatible or faulty, or a motherboard faulty. These can cause you to panic but are not the likely cause, but should not be ruled out. Try the battery replacement first.
cmos ram might be corrupt. run bios setup and reset bios to default settings. if it occurs again try, flashing bios.
Generally, a "CMOS error" will occur if one of the following has happened:The configuration of the computer has significantly changed. Simply entering the BIOS and saving should remove the error message.The backup battery has gone dead. You can check for this by seeing if the time is incorrect in the BIOS. You would need to purchase a replacement battery.A checksum error can occur if the BIOS has been updated, or if some external program has modified the CMOS settings. Again, simply entering the BIOS and saving should fix the message.
you need to reset your cmos http://www.wikihow.com/Reset-Your-BIOS http://www.youtube.com/watch?v=Pdp_L5IxaNI
you need to reset your cmos http://www.wikihow.com/Reset-Your-BIOS http://www.youtube.com/watch?v=Pdp_L5IxaNI
the main reason this happens is when the CMOS battery needs replacing.if the problem isn't resolved by doing this then I would flash the motherboard bios
Trouble code P0602 means:Control module programming error
they all discard it because if checksum error error it mean data is sent byother user and it forget its rout due to fault of channel if reach thereso it is not need to notify the source about this error
Only TCP will automatically discard a packet with a bad checksum. UDP packets have a checksum field, but it is rarely used, and then only by the application (not UDP itself)
checksum
they all discard it because if checksum error error it mean data is sent by other user and it forget its rout due to fault of channel if reach there so it is not need to notify the source about this error (Waqas Qadeer)
You likely mean that it is going directly to the CMOS Setup. Every computer with a BIOS boots using the BIOS, but if the BIOS detects problems with the CMOS data, it goes to the CMOS setup so the user can fix it. What the BIOS does is verify to see if the calculated checksum of the stored data matches the recorded checksum. If they don't match, the CMOS settings are dumped and changed to the defaults, and the user is either prompted or taken to the CMOS settings.While the CMOS can be scrambled at random or due to misbehaving software, the main cause would likely be a bad CMOS battery. It could also mean the CMOS chip is failing (since some contain an integrated battery) or that there are other hardware errors -- such as a stuck keyboard or a bad hard drive. It generally should tell you why you are being sent there. In a rare situation, someone may have the CMOS jumper in the wrong place, perhaps because they bought a motherboard themselves and received it that way.
Every packet has a new set of error detection assigned to it, the Checksum is a part of this process. The error correction occurs in the transport layer where the ACK will fail and the receiving host will request the packet to be sent again.