Motherboard may be fried...

[leilei1]

So I was using my computer all nice and dandy and I was on youtube just browsing. Right when a video was about to start my screen froze and this giant screeching sound came from my speakers for about 10 seconds then stopped. My screen was still frozen and my CPU temp was at 33 deg C so it wasn't an overheating problem. I turned off my computer and then turned it back on, everything powered on but there was no display on my screen.

I ran through a basic check with the RAM modules switching them out and back with different ones but that made no difference. Then I noticed one of my CPU fans wasn't working and it was plugged directly into the motherboard which made no sense. It would only work of I gave it a slight flick with my finger. Also my motherboard has a small screen which is supposed to show boot codes and post codes in hexadecimals if there's anything wrong and afterwards it's supposed to show the temp of my CPU, now when I turn it on it shows nothing.

I currently have a beep code speaker connected and it makes no sound at all. I also tried resetting the BIOS but that didn't do anything. So at this point I believe that there's something wrong with my motherboard due to the freak out that happened. (or the processor?)

BTW is it possible that windows got infected with a virus that kills your hardware?

 

[hpdeskjet]

What are your system specifications?

 

[leilei1]

Biostar TA890FX
HD Radeon 5670
OCZ 2 Gb Ram(4 total)
Thermaltake Frio CPU cooler
Corsair HX 750
1055t processor

 

[jsc]

Then I noticed one of my CPU fans wasn't working and it was plugged directly into the motherboard which made no sense.

That's normal. Plus it used to work like that.
Silence from the case speaker when trying to boot generally means a bad power supply, motherboard, or CPU.

That is why we need to know what hardware you have in your system.

The following is an expansion of my troubleshooting tips in the breadboarding link in the "Cannot boot" thread.
http://www.tomshardware.com/forum/261145-31-read-posting-boot-problems

I have tested the following beep patterns on Gigabyte, eVGA, and ECS motherboards. Other BIOS' may be different, but they all use a single short beep for a successful POST.

Breadboard - that will help isolate any kind of case problem you might have.
http://www.tomshardware.com/forum/262730-31-breadboarding

Breadboard with just motherboard, CPU & HSF, case speaker, and PSU.

Make sure you plug the CPU power cable in. The system will not boot without it.

I always breadboard a new build. It takes only a few minutes, and you know you are putting good parts in the case once you are finished.

You can turn on the PC by momentarily shorting the two pins that the case power switch goes to. You should hear a series of long, single beeps indicating memory problems. Silence indicates a problem with (in most likely order) the PSU, motherboard, or CPU. Remember, at this time, you do not have a graphics card installed so the load on your PSU will be reduced.

If no beeps:

Check for line power at the PSU input. Extension cords, power strips, and power cords do fail.

If you have power and no beeps, suspect components in likely order are PSU, motherboard, and CPU.

Running fans and drives and motherboard LED's do not necessarily indicate a good PSU. In the absence of a single short beep, they also do not indicate that the system is booting.

At this point, you can sort of check the PSU. Try to borrow a known good PSU of around 550 - 600 watts. That will power just about any system with a single GPU. If you cannot do that, use a DMM to measure the voltages. Measure between the colored wires and either chassis ground or the black wires. Yellow wires should be 12 volts. Red wires: +5 volts, orange wires: +3.3 volts, blue wire : -12 volts, violet wire: 5 volts always on. Tolerances are +/- 5% except for the -12 volts which is +/- 10%.

The gray wire is really important. It should go from 0 to +5 volts when you turn the PSU on with the case switch. CPU needs this signal to boot.

You can turn on the PSU by completely disconnecting the PSU and using a paperclip or jumper wire to short the green wire to one of the neighboring black wires.
http://www.youtube.com/watch?v=5FWXgQSokF4&feature=youtube_gdata

A way that might be easier is to use the main power plug. Working from the back of the plug where the wires come out, use a bare paperclip to short between the green wire and one of the neighboring black wires. That will do the same thing with an installed PSU. It is also an easy way to bypass a questionable case power switch.

This checks the PSU under no load conditions, so it is not completely reliable. But if it can not pass this, it is dead. Then repeat the checks with the PSU plugged into the computer to put a load on the PSU.

If the system beeps:
If it looks like the PSU is good, install a memory stick. Boot. Beep pattern should change to one long and several short beeps indicating a missing graphics card.

Silence, long single beeps, or series of short beeps indicate a problem with the memory. If you get short beeps verify that the memory is in the appropriate motherboard slots.

Insert the video card and connect any necessary PCIe power connectors. Boot. At this point, the system should POST successfully (a single short beep). Notice that you do not need keyboard, mouse, monitor, or drives to successfully POST.
At this point, if the system doesn't work, it's either the video card or an inadequate PSU. Or rarely - the motherboard's PCIe interface.

Now start connecting the rest of the devices starting with the monitor, then keyboard and mouse, then the rest of the devices, testing after each step. It's possible that you can pass the POST with a defective video card. The POST routines can only check the video interface. It cannot check the internal parts of the video card.

 

[leilei1]

Okay so lets say I find the issue and replace it.

Did the crash happen because of a virus or because the hardware suddenly failed?
If it is a virus that means that the same thing will happen once I boot windows up, so how likely is it that a virus may have caused this issue.