|MSI mboards are known to be more likely to have this problem...|
If your mboard is not new (usually the mboard is at least 2 years old when this happens)......
Some mboards develop this problem - electrolytic capacitors were installed on them that were not properly made, and they fail eventually - the mboard manufacturer didn't know they were improperly made at the time the mboard was made.
Open up your case and examine the mboard to see if you have bad capacitors, and/or other findable signs of mboard damage .
What to look for, mboard symptoms, example pictures:
Home page that site
- what the problem is caused by
- he says there are STILL bad capacitors on more recent mboards.
Pictures of blown capacitors, other components, power supplies, fried Athlon cpus, etc.:
"The beep code says a parity check error."
If there's nothing wrong with the capacitors on your mboard,
that message = your ram is producing memory errors.
It is extremely RARE for the same ram that worked fine previously in the same mboard to go "Bad".
- A common thing that can happen with ram, even ram that worked fine previously, is the ram has, or has developed, a poor connection in it's slot(s).
This usually happens a long time after the ram was installed, but it can happen with new ram, or after moving the computer case from one place to another, and I've had even new modules that needed to have their contacts cleaned.
See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:
- if you have CHANGED which ram you have installed in the mboard since the mboard last worked properly....
Ram that works in another mboard , or any ram you buy or have lying around, may not work properly, or sometimes, not at all - even if it physically fits and is the right overall type (e.g. SDram, DDR, DDR2, etc.; PCxxxx, xxx mhz) for your mboard. In the worst cases of incompatibilty your mboard WILL NOT BOOT all the way with it installed, and the mboard may not even beep - the ram has to be compatible with the mboard's main chipset, or in the case of recent mboards, compatible with the memory controller built into the cpu.
If you still have the ram that was installed when the system worked fine, try installing just that ram.
It is easy to test for incompatible ram that has caused your mboard to fail to boot.
Make sure you have a speaker or speakers or the equivalent connected to the mboard so you can hear mboard beeps (see your mboard manual if you need to).
Remove the AC power to the case/power supply.
Remove all the ram.
Restore AC power.
Try to boot.
If nothing else is wrong, you will get no video but you will hear a pattern of beeps that indicate no ram is installed, or a ram problem.
E.g. for an Award bios or a bios based on one, that's often a beep of about a half second, silence for a half second, a beep of about a half second, silence for a half second, continuously.
If your ram passes a ram test, it's working fine, even if you can't determine whether it's listed for your mboard or system model anywhere
If you do a ram test, do that AFTER having tried cleaning the contacts and making sure the ram is seated properly - otherwise any errors found may be FALSE.
If the ram is incompatible with the chipset, or on more recent computers, incompatible with the memory controller built into the cpu, it will likely FAIL a ram test - that is NOT a true indication of the ram being faulty - there is probably nothing wrong with it, and it will pass the test if installed in a mboard it is compatible with.
NOTE: Sometimes incompatible modules (or matched pairs) won't work properly when more than one is installed, but will pass when by itself.
If you want to try a memory diagnostic utility that takes a lot less time to run a full pass than memtest86 does, this one is pretty good - Microsoft's
Windows Memory Diagnostic:
Windows Memory Diagnostic is limited to testing only the first 4 gigabytes (GB) of RAM.
It can be toggled (press T) to do a standard or a more comprehensive set of tests - use the default 6 test one first - if it passes one pass of that, use the latter one. A few of the tests in the latter set are intentionally slower.
If you don't have a floppy drive, see the Quick Start Information at that Microsoft link for how to make a bootable CD of the Windows Memory Diagnostic (you need Windiag.iso - you don't necessarily need to use the program they mention to add it to the CD).