Motherboard Error Or CPU?

[l0lapple]

I have two kits of the same RAM in my rig both 2x4gb and my motherboard's manual says its compatible in all DIMM slots yet it no longer lets me boot up in 16Gigs. Could my SSD cause this also, because I formatted it without knowing that I should have afterwards. My SSD has super high disk usage and the response time now is too high could this be the cause for everything?

Specs:
Windows 8.1 64-bit
ASUS Z97-PRO
i5-4670K
G.SKILL F3-14900CL9D-8GBSR
HX750 Corsair

 

[compprob237]

It freezes up on code 00 and maybe other codes. I would hit the power button on the case or on the mobo and neither would boot up after many attempts of spamming it and only after that it boots.

That still sounds like the motherboard to me. If it had a bad capacitor it would exhibit erratic behavior like that. I mean, there is a chance that the PSU could be feeding it erratic power but I've never had one do that ever. I've dealt with a lot of PSUs, and repair them, and never came across a single one that did that. Not even the cheap Aspire PSU with a bowed circuit board.

I tested 1 kit of RAM on another PC with the PSU which booted it up. This is the same kit of RAM I used to boot my PC. I might test the other kit but I doubt anything is wrong with it.

Any idea why I cannot flashback the bios? Most of my peripherals don't work now when I boot the PC, would that be caused by a CPU error or a board? Also I tried booting my board without a CPU not sure if it would boot without it because its a new board generally speaking, but I got the same code 00, now when I try it just gives me a 63 q-code I know what it means the manual doesn't tell me how to fix it.

Aside from testing your CPU in another known-working system I think it's safe to say the CPU or motherboard is toast. The only way to know for sure is to test the CPU in a working system. I'm afraid to suggest purchasing a used motherboard since the CPU could possibly be bad and you'd effectively burn money. The Q-code makes me think it's the motherboard but the CPU could still be the problem.

What it boils down to is that you need to take your CPU and test it in a working computer. If it works fine then you need a new motherboard. If it has problems like before then you need a new CPU.

 

[l0lapple]

It freezes up on code 00 and maybe other codes. I would hit the power button on the case or on the mobo and neither would boot up after many attempts of spamming it and only after that it boots.

That still sounds like the motherboard to me. If it had a bad capacitor it would exhibit erratic behavior like that. I mean, there is a chance that the PSU could be feeding it erratic power but I've never had one do that ever. I've dealt with a lot of PSUs, and repair them, and never came across a single one that did that. Not even the cheap Aspire PSU with a bowed circuit board.

I tested 1 kit of RAM on another PC with the PSU which booted it up. This is the same kit of RAM I used to boot my PC. I might test the other kit but I doubt anything is wrong with it.

Any idea why I cannot flashback the bios? Most of my peripherals don't work now when I boot the PC, would that be caused by a CPU error or a board? Also I tried booting my board without a CPU not sure if it would boot without it because its a new board generally speaking, but I got the same code 00, now when I try it just gives me a 63 q-code I know what it means the manual doesn't tell me how to fix it.

Aside from testing your CPU in another known-working system I think it's safe to say the CPU or motherboard is toast. The only way to know for sure is to test the CPU in a working system. I'm afraid to suggest purchasing a used motherboard since the CPU could possibly be bad and you'd effectively burn money. The Q-code makes me think it's the motherboard but the CPU could still be the problem.

What it boils down to is that you need to take your CPU and test it in a working computer. If it works fine then you need a new motherboard. If it has problems like before then you need a new CPU.

I can't do a BIOS flashback...so I guess that narrows it down to the board.

 

[compprob237]

I just watched that video you linked in PM and did some more digging on the hang with Q-code 63. It looks like it's related to RAM. Many posts saying dying/bad stick or bad seating (one had bent pins in the slot!) was the cause. After that it was the motherboard.

Pull all sticks of RAM and see if it hangs at the same Q-code. Either outcome will give you some more detail. Same Q-code means it isn't the RAM. Different Q-code means the RAM's involved somehow. If you get a different Q-code then try one stick of RAM at a time in DIMM_A2, as per the manual, and see if you get a stick that makes it hang on that original Q-code it hang on. If none match the Q-code hang then try DIMM_A1, DIMM_B2, and finally DIMM_B1 all individually and with each stick one at a time. It may be tedious but it's the last option you have. I'd suggest a visual inspection of the DIMM slots but you'd need to know what to look for and probably need a magnifying glass. Lastly, try removing the CMOS battery for at least a minute to make sure the BIOS configuration is reset and see if that solves it.

 

[l0lapple]

I just watched that video you linked in PM and did some more digging on the hang with Q-code 63. It looks like it's related to RAM. Many posts saying dying/bad stick or bad seating (one had bent pins in the slot!) was the cause. After that it was the motherboard.

Pull all sticks of RAM and see if it hangs at the same Q-code. Either outcome will give you some more detail. Same Q-code means it isn't the RAM. Different Q-code means the RAM's involved somehow. If you get a different Q-code then try one stick of RAM at a time in DIMM_A2, as per the manual, and see if you get a stick that makes it hang on that original Q-code it hang on. If none match the Q-code hang then try DIMM_A1, DIMM_B2, and finally DIMM_B1 all individually and with each stick one at a time. It may be tedious but it's the last option you have. I'd suggest a visual inspection of the DIMM slots but you'd need to know what to look for and probably need a magnifying glass. Lastly, try removing the CMOS battery for at least a minute to make sure the BIOS configuration is reset and see if that solves it.

No luck.

 

[compprob237]

No luck.

Same Q-code regardless of RAM stick location or no RAM at all?
If that's the case: Motherboard or CPU. I can't say for certain if it's either. The memory controller is a part of the CPU so if there's a problem with the CPU it will not behave. If there's a problem with the motherboard then it will act basically the same. I'm leaning more toward the motherboard because I've never had a CPU die on me but have had plenty of motherboards die.

 

[l0lapple]

No luck.

Same Q-code regardless of RAM stick location or no RAM at all?
If that's the case: Motherboard or CPU. I can't say for certain if it's either. The memory controller is a part of the CPU so if there's a problem with the CPU it will not behave. If there's a problem with the motherboard then it will act basically the same. I'm leaning more toward the motherboard because I've never had a CPU die on me but have had plenty of motherboards die.

I managed to flash bk my mobo twice with different bios versions and I keep getting the same error code.

Also I have a new ASrock board on the way, I'll update later.

 

[l0lapple]

No luck.

Same Q-code regardless of RAM stick location or no RAM at all?
If that's the case: Motherboard or CPU. I can't say for certain if it's either. The memory controller is a part of the CPU so if there's a problem with the CPU it will not behave. If there's a problem with the motherboard then it will act basically the same. I'm leaning more toward the motherboard because I've never had a CPU die on me but have had plenty of motherboards die.

I installed the new MOBO and the PC works again. It cannot install anything (drivers, mobo included software) though I don't know why.

 

[compprob237]

I installed the new MOBO and the PC works again. It cannot install anything (drivers, mobo included software) though I don't know why.

Hey good to hear it's working again!

Did you do a fresh OS install with the motherboard?

 

[l0lapple]

I installed the new MOBO and the PC works again. It cannot install anything (drivers, mobo included software) though I don't know why.

Hey good to hear it's working again!

Did you do a fresh OS install with the motherboard?

I reinstalled the OS, fixed the lag or whatever you wanna call it.

 

[compprob237]

I installed the new MOBO and the PC works again. It cannot install anything (drivers, mobo included software) though I don't know why.

Hey good to hear it's working again!

Did you do a fresh OS install with the motherboard?

I reinstalled the OS, fixed the lag or whatever you wanna call it.

Right on.