long continuous ringing BEEP error, no boot, no monitor!! HELP!

tarib

Honorable
May 9, 2013
4
0
10,510
Hello guys, I am having problems booting up my computer. I tried numerous troubleshooting methods mentioned in various websites and forums. I also followed the sticky regarding this problem. However, nothing worked out for me.
My computer is almost 2.5 years old. I was using 5770 crossfire and everything was working perfectly fine. Then, I wanted to upgrade it to a Sapphire 7870 XT. I figured this would be a good time to reapply thermal paste on my cpu as well, and get rid off any dusts inside the case. After installing the new 7870, my monitor receives no signal anymore. My build is:
Biostar TA890FXE
AMD II Phenom X6 1050T
Corsair XMS3 2x2 gb 1600mhz RAM
XFX Black edition 750 PSU
Tuniq 120 Extreme CPU FAN
My case doesn't have a speaker, so i used an external case speaker to hear the beep code errors. There is a long continuous (ringing) tone which stops only after I force shutdown or turn PSU off. According to AMI BIOS post beep code error, that specific error is related to
1)Memory failure
2)Graphic card failure
3)Motherboard failure
http://www.pcguide.com/ts/x/sys/beep/ami.htm
My motherboard comes with a BIOS POST indicator which says '60' or '09' depending on the angle(not sure which is correct). According to the manual,
60 = Initializes NUM-LOCK status and programs the KBD typematic rate. ( I did not understand what that meant)
but if 60 was decimal, its Hexadecimal value would be 3C, which means Mid POST initialization of chipset registers.
Here is what I tried so far:
1)I have verified my PSU is working with paperclip method.
2)I checked if every connectors were attached properly.
3)I have tried using my old 5770s, individually and on crossfire to see if the new 7870 XT was faulty.
4)I have tried using single stick of ram, and reseating them.
5)I have tried reseating CPU
6)I tried clearing CMOS via jumper setting, and also tried to reset BIOS by taking out the CMOS battery.
7)This was my last attempt:
I unplugged everything CPU, RAM, Graphic card, HDD, CD ROM,keyboard and mouse. and powered ON my motherboard. The LEDs were ON, fans were running but there were NO BEEP CODE ERRORS(neither visual nor on the speaker). Since I know my PSU should be able to power enough juice to at least boot my motherboard, and it did pass the paper clip test, I believe that there should be at least some beep error relating to empty CPU, there were none. Despite that, I installed my CPU with HSF, and again turned the MB on. This time I heard the beep error, an infinitely long continuous ringing tone. I installed my RAM(single stick, double stick, triple stick, almost every possible combinations, different slots) and still same beep error. I installed my graphic card and same error. After installing all the components back, I thought of removing CMOS battery and powering my MB on. There was no boot and no error message either. However, the same POST error occurred once I powered on with CMOS battery .
I would appreciate any suggestions regarding my problem. Please, do try to keep the suggestions at a simpler level for I only have an average knowledge regarding this area. I would provide any further information that will required to help you guys further analyze this situation.
I have warranty for all my components for at least 2-3 more months but the total cost of shipping my MB, and CPU would be at least 60$. but if i knew what component is messed up, I could actually buy a new one with some extra funding.
Thank you,
Birat
P.S. the fan headers(cpu fan1, and sys fan 2) on MB do not seem to work either, my cpu fan runs only and only if plugged into sys fan1 header.
 

tarib

Honorable
May 9, 2013
4
0
10,510


I tried that as well. Apparently, the cpufan1 and sysfan2 header seem dead.
 

tarib

Honorable
May 9, 2013
4
0
10,510


I cannot access the BIOS since there is no signal in my Monitor. I tried clearing CMOS and also took out the CMOS battery, still the same long ringing beep code error.
 

tarib

Honorable
May 9, 2013
4
0
10,510
hello guys, thank you for quick response. So, it is the motherboard then? okay. It couldn't be the CPU, could it?
thank you again for such a speedy help!