What's new

Msi h61m mobo error code

SyPh3R

New Member
Joined
Apr 26, 2018
Messages
33
Likes
0
Points
6
Age
26
#1
Hi guys

So I have a msi h61m-p3/w8 mobo and it keeps on hanging on a black screen with the error code 99 in the bottom right corner, internet is not much use says either i/o error or stuffed mobo, anyone come across the same problem with aa fix except getting a new mobo?
 

SyPh3R

New Member
Joined
Apr 26, 2018
Messages
33
Likes
0
Points
6
Age
26
#4
I did clear the cmos, still does not work. The only thing it does is shows a 99 in the bottom right corner, nothing else at all
 

Gurshick

Lurker
VIP Supporter
Joined
Dec 14, 2015
Messages
594
Likes
113
Points
43
Location
Jhb South
#5
Look if you maybe have bent pins or try a previous gen cpu

Sent from my Redmi Note 3 using Tapatalk
 
Joined
Jun 8, 2018
Messages
330
Likes
115
Points
43
Age
27
#7
It's an error with the BIOS. They call it a i/o error although I'm not sure why though, because its basically a corrupted BIOS in most instances. What you need to do is completely remove the old bios and replace it with a new bios. With the Asus boards its easy, you can just pull the Bios out and find a someone with the same motherboard then pull that one's bios out and replace it with yours (not sure how your friend will feel about this).

Unfortunately flashing the bios is not going to work in this case because when you flash a bios you are just restoring it to the original settings but if the BIOS becomes corrupted you have to completely reprogram the BIOS to the chip. There are ways of also removing the bios from the motherboard by soldering it off and then putting it on a USB kind of tool which you then plug into your PC and it reprograms the BIOS to the chip.

ScorpioMan86 might be able to give you some pointers on what to do as I had a similar problem with a motherboard and he was able to repair it.

Generally these motherboards are not worth it though. Chuck it and see if you can track down a H77 or a z77. Saw one floating around here on Carbonite recently.
 

SILTECH786

Forum Addict
Reseller
Joined
Feb 26, 2011
Messages
4,412
Likes
564
Points
113
Age
35
Website
www.sweetsnchocs.co.za
#8
It's an error with the BIOS. They call it a i/o error although I'm not sure why though, because its basically a corrupted BIOS in most instances. What you need to do is completely remove the old bios and replace it with a new bios. With the Asus boards its easy, you can just pull the Bios out and find a someone with the same motherboard then pull that one's bios out and replace it with yours (not sure how your friend will feel about this).

Unfortunately flashing the bios is not going to work in this case because when you flash a bios you are just restoring it to the original settings but if the BIOS becomes corrupted you have to completely reprogram the BIOS to the chip. There are ways of also removing the bios from the motherboard by soldering it off and then putting it on a USB kind of tool which you then plug into your PC and it reprograms the BIOS to the chip.

ScorpioMan86 might be able to give you some pointers on what to do as I had a similar problem with a motherboard and he was able to repair it.

Generally these motherboards are not worth it though. Chuck it and see if you can track down a H77 or a z77. Saw one floating around here on Carbonite recently.
Sound advice right here ....
 

Shamz

Fresh Spawn
Joined
Sep 27, 2016
Messages
18
Likes
0
Points
1
#9
MSI error 99 is usually a I/O error.

1. The mobo is fried, throw away.

or

2. Error 99 is an input error through either the back panel or mobo headers.

What to do to check #2 is disconect your front usb, sound and SD card wires on the mobo. Remove all PCI and PCI-E cards. You know what? Unplug your harddrives as well. Go to the back of the machine and unplug everything except your keyboard and power cable. Now fire her up. If you still get the 99 error, I think #1 happened. If you get the "no boot device found" error, you need to start reconnecting wires and cards, one by one and rebooting each time until you figure out where the error is.
 
Top