Solved My computer doesn't boot 2 long beeps MSI K8MM-V

Msi (motherboard) K8mm-v
March 22, 2012 at 04:00:14
Specs: Windows XP sp2, AMD Sempron 2800+ 1.6GHz Ram: DDR2 200MHz 512MB
Please help me I'm a novice in all these matters.
My computer is 5 years old and it used to run quite fine since I bought it. Recently from the last 10 months or so it has gone mad. One day when I booted it up, the screen was all blank, all fans running and anything that I could notice was 2 long beeps. I sent it to a repairing firm from MSI. When I got it back it worked fine for a few days and then again the same problem. I have had it repaired 4 times since then and now again the same problem has shown up. I tried booting it out of chassis and it booted just once and never again.
Please help me.

See More: My computer doesnt boot 2 long beeps MSI K8MM-V

Report •

✔ Best Answer
March 22, 2012 at 13:51:22
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:
http://www.badcaps.net/pages.php?vid=5
Home page that site
- what the problem is caused by
- he says there are STILL bad capacitors on more recent mboards.
http://www.badcaps.net/

Pictures of blown capacitors, other components, power supplies, fried Athlon cpus, etc.:
http://www.halfdone.com/Personal/Jo...
.........

"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".

However....

- 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:
http://www.computing.net/hardware/w...

- 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:
http://oca.microsoft.com/en/windiag...
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).



#1
March 22, 2012 at 04:40:44
Look up your beep code in your manual or here:
http://www.computerhope.com/beep.htm
Post back what it says plus include the make and model of your computer or a list of all components including makes and model numbers.

You have to be a little bit crazy to keep you from going insane.


Report •

#2
March 22, 2012 at 05:14:22
The beep code says a parity check error.

And well my computer never boots into a screen to say anything!!

Configuration:
AMD Sempron 2800+ 1.6GHz Socket 754
Memory Power 512MB DDR2@200MHz
Mobo: MSI K8MM-V MS:7142 Ver:1
Chipset: VIA K8M800
Integrated Graphics
Sony CD-RW/DVD Combo Drive
Samsung 1.44MB Floppy Drive
4Mb Award BIOS with PnP, ACPI, SMBIOS 2.3, Green and Boot Block
SATA-II support upto 1.5GBps


Report •

#3
March 22, 2012 at 13:09:35
The beep code says a parity check error.
And well my computer never boots into a screen to say anything!!
Configuration:
AMD Sempron 2800+ 1.6GHz Socket 754
Memory Power 512MB DDR2@200MHz
Mobo: MSI K8MM-V MS:7142 Ver:1
Chipset: VIA K8M800
Integrated Graphics
Sony CD-RW/DVD Combo Drive
Samsung 1.44MB Floppy Drive
4Mb Award BIOS with PnP, ACPI, SMBIOS 2.3, Green and Boot Block
SATA-II support upto 1.5GBps

Report •

Related Solutions

#4
March 22, 2012 at 13:51:22
✔ Best Answer
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:
http://www.badcaps.net/pages.php?vid=5
Home page that site
- what the problem is caused by
- he says there are STILL bad capacitors on more recent mboards.
http://www.badcaps.net/

Pictures of blown capacitors, other components, power supplies, fried Athlon cpus, etc.:
http://www.halfdone.com/Personal/Jo...
.........

"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".

However....

- 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:
http://www.computing.net/hardware/w...

- 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:
http://oca.microsoft.com/en/windiag...
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).


Report •

#5
March 22, 2012 at 14:13:55
"Specs: Windows XP sp2, AMD Sempron 2800+ 1.6GHz Ram: DDR2 200MHz 512MB"

'Memory Power 512MB DDR2@200MHz"

Is DDR2 a typo in those lines ?

Any typos in this ?
"MSI K8MM-V MS:7142 Ver:1"
If NO....

Your MSI K8MM-V (MS-7142 Ver. 1.0) mboard cannot use DDR2 ram !!
It must use DDR ram !

E.g.

http://www.crucial.com/store/listpa...


Report •

#6
March 22, 2012 at 15:21:50
Sorry I looked at the RAM stick it said DDR Ram PC3200.

The RAM Stick is the one that came installed with my system and it is still fine.

Can this also happen due to drained CMOS battery?


Report •

#7
March 22, 2012 at 18:03:26
Try cleaning the contacts on the ram module and re-seating it. See above.

By the way, you would be better off if you installed more ram.

"Can this also happen due to drained CMOS battery?>

NO.
If nothing else is wrong, the mboard will still boot fine when the battery is dead or too weak , but you'd get an error message "Cmos Checksum Error" or similar while booting because the bios would have reverted to default settings - at the very miinimum the time and date would be defaults..
If the hard drive is IDE, is connected to the primary IDE header, and is jumpered Master, or is jumpered Cable Select and is connected to the end connector of a 3 connector data cable, Windows would still load fine, except that some programs don't like the time and date being too far out.

Button cell batteries usually last at least 5 years - your mboard may be older than that.


Report •

Ask Question