[lukini]

So last night something failed in my computer during a game and I'm pretty sure it is the motherboard.

Currently the computer starts up, but the motherboard never makes it through POST. The POST code that is displayed is 2A. According to the manual:

2A Initializes different devices through DIM.
See DIM Code Checkpoints section of document for more information.

I'm not sure what DIM is, but the only other table is for bootblock initialization.

I had headphones on, so I don't know if there was a pop when it crashed or anything. The motherboard looks fine physically. When it crashed, the screen was a solid color and the sound looped the last 0.1 seconds or so. This is similar to what usually happened when my GPU was getting GSODs. Not quite the same, but enough for me to initially think it was the GPU.

So, any ideas on what might have failed? I feel like it has to be the motherboard, but for all I know, it could be the CPU. Any assistance in determining the definite cause is appreciated.

 

[makinu1der2]

Post the make/model of the PC. If custom built post the specs

Motherboard-CPU-Memory-Graphics card-Power Supply brand/wattage

Perform the following steps:
-Remove the power from the system and open the case
-Remove the graphics card from the PC
-Clear the CMOS settings (removing the battery from the motherboard for a few minutes will suffice)
-Attempt to boot the PC using the integrated graphics (if equipped)

If unsuccessful continue:
-Remove all RAM and test with one stick at a time
-Remove any PCI card installed (modem,nic,sound,etc)
-Disconnect drives (storage and optical)
-Inspect motherboard for damaged capacitors
-Test with another PSU

 

[Tyree]

PC Specs?
Pre- Built Brand & Model Number
Custom Built- Brand & Model of Mobo-CPU-RAM-Graphics-PSU.

 

[lukini]

To both: The specs are in my profile and under My System to the left, but I'll post it here I guess:

CPU: Intel Core i7 920 D0
Mainboard: ASRock X58 Extreme
Memory: OCZ Gold 6GB DDR3 1600 (running at stock 1066)
Hard Drive: Samsung Spinpoint F3 500GB
Video: XFX Radeon HD 5870
CD Rom: Samsung Black 22x DVD Burner
Power Supply: Corsair 750W
OS: Windows 7 x64
Nothing is overclocked.

Perform the following steps:
-Remove the power from the system and open the case
-Remove the graphics card from the PC
-Clear the CMOS settings (removing the battery from the motherboard for a few minutes will suffice)
-Attempt to boot the PC using the integrated graphics (if equipped)

I don't have integrated graphics, but should I still clear CMOS?

 

[ReviverSoft]

^ Yes, you still can.

 

[Tyree]

If no joy after the CMOS reset remove all the RAM. boot and listed for beep codes.
No RAM & No beeps indicates a Mobo issue.
If you get the correct beep code bench test
Remove EVERYTHING from the case.
Set the motherboard on a non conductive surface. The motherboard box is perfect for this. DO NOT PLACE THE MOTHERBOARD ON THE STATIC BAG! It can actually conduct electricity!
Install the CPU and heat sink.
Install 1 stick of RAM.
Install the video card and attach the power supply connection(s) to the card if your card needs it.
Connect the monitor to the video card.
Connect the power supply to the motherboard with both the 24pin main ATX Power connection and the separate 4 or 8 pin power connection.
Connect power to the power supply.
Do NOT connect ANYTHING else. Make sure you have the power connector on the CPU fan connected.
Use a small screwdriver to momentarily short the power switch connector on the motherboard. Consult your motherboard manual to find which two pins connect to your case's power switch. Then touch both pins with a screwdriver to complete the circuit and boot the system.

If all is well, it should power up and you should get a display. Then assemble the parts into the case and try again. If the system now fails to boot, you have a short in the case and need to recheck your motherboard standoffs.

If the system does not boot after this process, then you most likely have a faulty component. You'll need to swap parts, start with the power supply, until you determine what is defective.

 

[lukini]

I removed all the RAM and heard no beep code. The manufacturer's site mentions beep codes for their BIOS, but I wasn't sure if those applied to me. After some googling, it sounds like I should have the beep codes listed.

I'm guessing this pretty much means it is the motherboard like I thought, right? I'm contacting their support in regards to the motherboard, but it seems like it is probably the culprit.

 

[makinu1der2]

Do you have the motherboard speaker connected? If not then you won't here the beeps.

Are you able to test the graphics card in another PC or try another card in this PC?

If all else fails RMA the motherboard.

 

[lukini]

I feel stupid for forgetting that...thanks for the reminder. I get 3 beeps now which looks like it matches no RAM.

Asrock support just got back to me and said that the 2A code means I should try another GPU or another PCIe slot.

 

[makinu1der2]

Asrock support just got back to me and said that the 2A code means I should try another GPU or another PCIe slot.

Definitely worth trying.

 

[lukini]

The GPU is what malfunctioned. My friend's card works in the computer.

I actually recently RMA'd the GPU. The card needed to be underclocked to prevent a gray screen of death. XFX did a lot of testing on it and determined that the card worked just fine. This probably meant that it was something on my end, so they sent it back.

Now I'm kind of confused as to what was causing the problems with my GPU or if they were related to this complete failure. Could another piece of hardware have caused the issues with the GPU or is it more likely that the card just happened to have failed completely on its own?

 

[makinu1der2]

What make/model card did you try from your friend?

I would think that the card just failed.

 

[lukini]

XFX HD 6870. I had to completely reinstall the drivers before I tested it. I'm not sure if that is normal.

If the card just failed, that makes me really confused what caused the previous issues. They are very easy to reproduce. Maybe it had something to do with driver issues. I'm not sure