Motherboard stuck at random debug codes

[biascoblix]

TLDR; Bios A and B are stuck on CPU Initialization. Debug code 02. No idea whats wrong here

 

So full story,

 

I came home yesterday with the computer completely frozen. No display output. The mouse isn't lit. The power button was flashing quick and nothing was responding. The PC i think was a little louder than usual too.

 

I force closed it and tried to boot it up again but it just didn't. It got stuck at some debug code that don't remember. I think it was something resembling "Early south bridge initialization" 

 

So I unplugged everything, removed the gpu, removed all but one stick of RAM and it was still not booting, sometimes getting stuck at 00 which is not even described in the mobo manual and sometimes getting stuck at the early south bridge thinge.

 

I kept searching online and came into the multi bios thinge which i didn't even know about. So I switched to BIOS B and boom it booted up.

 

Seemed totally fine with absolutely no issues. BIOS B was working flawlessly, BIOS A was stuck at 00

 

So I decided to get around to fixing BIOS A now. Downloaded the recent BIOS from MSI, put it on a FAT32 flash drive. Booted up BIOS B, went to M flash and choose BIOS A as the destination. Flashing seemed to go fine. No errors or anything. It said it flashed succesfully.

 

And now both BIOS A and B aren't booting up. Both get stuck at 02 which is CPU Initialization but im pretty sure there's nothing wrong with the CPU since it was working fine literally minutes ago.

 

I tried removing the CMOS batter to clear the BIOS too. Didn't do anything.

 

Any ideas ? 

 

 

 

• CPU
  i7-5820K
• Motherboard
  MSI X99A GAMING 7
• RAM
  G.SKILL Ripjaws 4 Series 48GB
• GPU
  MSI GTX 980

[Noah0302]

Had something similar happen to my GFs pc when update her Asus Prime X470 Pro to support Ryzen 3000.

 

I knew the RAMs were faulty, we planned to RMA, but had not so far.

I started the EZflash, saw it was progressing and we went to grab something to eat.

After we returned the PC was on, fans spinning, LEDs RGBing but the keyboard, mouse and monitor were off.

Shutting it down by unplugging, the fans started to go full ham for abour 3 seconds, turned back down but the mouse and keyboard, aswell as the monitor did not turn on.

So I reset the CMOS - still no boot.

I pulled the one RAM stick out, which was defect and after resetting the CMOS a 2nd time, it booted.

BIOS update successful, but with the new one it would not boot with the defect RAM plugged in.

After the RMAed sticks arrived, everything worked perfectly.

 

Maybe try a whole new kit as well as hard resetting the CMOS.

[biascoblix]

5 minutes ago, Noah0302 said:

Had something similar happen to my GFs pc when update her Asus Prime X470 Pro to support Ryzen 3000.

 

I knew the RAMs were faulty, we planned to RMA, but had not so far.

I started the EZflash, saw it was progressing and we went to grab something to eat.

After we returned the PC was on, fans spinning, LEDs RGBing but the keyboard, mouse and monitor were off.

Shutting it down by unplugging, the fans started to go full ham for abour 3 seconds, turned back down but the mouse and keyboard, aswell as the monitor did not turn on.

So I reset the CMOS - still no boot.

I pulled the one RAM stick out, which was defect and after resetting the CMOS a 2nd time, it booted.

BIOS update successful, but with the new one it would not boot with the defect RAM plugged in.

After the RMAed sticks arrived, everything worked perfectly.

 

Maybe try a whole new kit as well as hard resetting the CMOS.

Literally tried it without any RAM. Still stuck at the error. Also sometimes it'd turn of like a second then turn off again and then it'd turn on and get stuck again at 02.

 

PSU ?

[Noah0302]

22 minutes ago, biascoblix said:

Literally tried it without any RAM. Still stuck at the error. Also sometimes it'd turn of like a second then turn off again and then it'd turn on and get stuck again at 02.

 

PSU ?

That sounds really weird.

 

Is it possible to try a different CPU as well?

It is REALLY unlikely, but the CPU could have gotten a sudden power surge, maybe from a bad PSU or something, and is now kinda fucked.

 

It is really difficult to troubleshoot something liek this.

[biascoblix]

2 minutes ago, Noah0302 said:

That sounds really weird.

 

Is it possible to try a different CPU as well?

It is REALLY unlikely, but the CPU could have gotten a sudden power surge, maybe from a bad PSU or something, and is now kinda fucked.

 

It is really difficult to troubleshoot something liek this.

The CPU worked fine and the GPU too when BIOS B was booting. Like the PC booted up. Everything was fine. I don't think it's faulty CPU. 

 

It's weird. I'll try to check if the PSU was faulty by connecting some kind of two pins together. I remember doing that before. 

[biascoblix]

Connected one of the green pins to the black ones. The power supply seems to be alright.

[biascoblix]

So somehow apparently the motherboard fucked up both BIOSes.. I found some guy here that fixed it for like 15 bucks or something. Saved me a shit ton.