Asus A7V133 Boot Problem

mkaltner

Junior Member
Mar 13, 2001
5
0
0
I built a computer consisting of:

Asus A7V133
AMD T-Bird 1.2GHz (200MHz FSB)
Crucial 256MB CAS2 PC133 DIMM
ATi Radeon 64MB (Retail)

And other various parts, but these are what could possible be related to the problem.

Last night, I set up the machine.
The jumpers are all default (JumperFree mode)
In the BIOS, the only thing I adjusted was drives and setting the DIMM speed to 133. The CPU is at 100x12.

It worked perfectly fine for the evening, no problems. I even put the case back together. The highest temp I saw with the AsusProbe was 53C. That was with the box all closed up and it still ran perfect.

I shut it down for the night...

This morning, all I did was unplug the drive cables and make them nicer for airflow from the lower case fan I put on.

Booted up fine, played a little Blade of Darkness, Quake3, ran like a dream.

After that, I thought about flashing the BIOS to the newest version. Downloaded the AWD file and flash.exe. The executable downloaded a little sketchy (bad isp) so I checked it by executing it, prompted to hit ESC to exit, I did... It worked fine... But I did NOT run the program in any way beyond that.

After that, I surfed a little and then let the computer alone to get ready for work.

That's when I heard the monitor re-sync. Thought it a little strange I sat back down and it did it a couple more times. Figured it best to power down and boot again.

After reboot it didn't take it very long to flicker again, this time locking up the machine. Rebooting provided the same results.

Rebooting again however got me nowhere.

I do not get a video signal, I cannot access the BIOS, all it does is sit there and beep.

The beep starts low for about .5 second then high for the same and loops. Kind of like a crappy digitized foghorn looping over and over.

What I've done:

Checked the CPU. The shim is still very well in place, the Arctic Silver II is making good contact with the HS, but not too much. Can see through the layer after removing HS.
Put two different AGP video cards in.
Put a different DIMM in.

None of this fixed the problem.

And from what I can tell, this particular beep code is not described in the manual.

Why don't I think it's temp?
Well, the computer ran fine, at higher temps and was perfectly stable. And the ambient temp this morning was much lower as well.

Well, I'm pretty lost as to what it is, hope this is enough info and that someone can help... As of now, I'm losing faith and I think I'm about to have a very expensive paper weight...

- Mike
 

nealh

Diamond Member
Nov 21, 1999
7,078
1
0
Can you put another cpu in the mobo??

That is the only thing you have not rechecked...does the system post....i had a bad cpu ....i know yours worked but i talked with a local computer store and they have had a few 1.2GHZ ...die after use...

A few obvious suggestions...make sure you reseat the videocard, check all the cable and insure they are corrected with correct orientation...make sure all power plugs are in place...I was helping a friend over the phone install a cdrw and we forgot to connect a power plug and this caused his system not to boot...

 

mkaltner

Junior Member
Mar 13, 2001
5
0
0
Correct me if I'm wrong, but if the CPU was bad, I the BIOS wouldn't even be beeping, would it? I mean, doesn't the CPU have to be functioning to even get to that point? Man, that would suck if the CPU died because I broke the first 1.2 I put in there... =( So far though, my plan is:

Test all components in another machine making sure that they work. I'm mostly worried about video and ram. If those work in another machine then Im going to completely take the machine apart and bread-board the MB,PS,Memory and Video. If at that point I can't get to the BIOS, it's either the CPU or motherboard.

Here's why I don't think it's the CPU.

I have a friend that used to be a tech and he feels the same that I do.

1) The CPU had consistantly run at a decent temperature. Between 42-52C depending on load.

2) The CPU nor the BIOS settings changed prior to the problem.

3) With no other cards installed, different video and memory do not change the situation.

But then again, as you said, it may have just died...

I'll narrow it down tonight but I'm pretty sure I'll end up narrowing it to either motherboard or CPU at which point I'm not sure what I'll do.

Thanks,
- Mike
 

Rick25

Member
Jul 10, 2000
104
0
0
Long beeps in endless loop in bad SDRAM. Make sure you didn't dislodge one while you were in working in the case.
 

SCSIfreek

Diamond Member
Mar 3, 2000
3,216
0
0
Yes the manual does mention the signs of problems with different beep sequences


--SCSI
 

maustin20

Junior Member
Mar 8, 2001
1
0
0
After that, I thought about flashing the BIOS to the newest version. Downloaded the AWD file and flash.exe. The executable downloaded a little sketchy (bad isp) so I checked it by executing it, prompted to hit ESC to exit, I did... It worked fine... But I did NOT run the program in any way beyond that

I don't know if you meant to say "AFLASH.EXE". I belive you need to use the aflash program on this motherboard. I don't know if "FLASH.EXE" could mess anything up or not.....
 

Regalk

Golden Member
Feb 7, 2000
1,137
0
0
If the beep sounds like a Uh Oh (dull beep as opposed to the normal sharp beeps) it means CPU problems bro.
 

djchemistry

Senior member
Mar 9, 2000
856
0
0
I had the same beeps for a little while. Make sure you set the voltage jumpers manually to whatever you want it at and reset the bios. That should do the trick.
 

mkaltner

Junior Member
Mar 13, 2001
5
0
0
Assuming it is the CPU, what would cause it? It was running around 45C the whole time really and was quite stable. I even checked the temp shortly before it crashed and it was 47C. It doesn't make any sense. I do have a copper shim in there (cracked my first one) but I don't think that's the problem either.

1) Copper is non-conductive
2) If it weren't placed properly, it would have overheated long ago.

I'm going to find out today, getting a new MB. If the chip does not work on the new MB, I'm going to return it and RMA the chip getting a retail one this time. This is rediculous...

Thanks,
- Mike
 

nealh

Diamond Member
Nov 21, 1999
7,078
1
0
I had a bad cpu that was pretested and did not work on 2 mobo...K7TA and A7V133...both gave beeps...so I thought as you did it was a video card , ram or mobo that is why I bought the mobo...after the second mobo and nothing took the setup to local shop they threw in a 700 tbird and boom...no problems.....

So I will not bet the cpu is bad but sometimes things go bad....this shop indicated they personally had several die after short use...

Good Luck...
 

jamesbond007

Diamond Member
Dec 21, 2000
5,280
0
71
Man, tough luck! If I were you, try resetting the CMOS. If you do get it to boot, there should be a program called AFLASH.EXE on your CDROM. Reflash your BIOS and be sure you're using AFLASH.EXE, not some other program. Hope this helps. Good luck man!
 

mkaltner

Junior Member
Mar 13, 2001
5
0
0
I FIXED IT!!! Okay, here's what happened...

As I found out on the Arctic Silver site, thier grease is slightly conductive. Since I was being overly careful by installing the shim, some of the grease came into contact with the Lx leads. After being on for a while, they shorted out...

What I did was took some slightly moistened cotton swabs and cleaned the L5-L7 section then went over it with some dry ones. After replacing the HSF, IT BOOTED!!!! It's reinstalling as I type this!!!! Man, simple-stupid mistake that was very easily overlooked. I'm sure glad I found it. I was about to RMA the sucker!

Well, thanks for all the help guys, but it's time to play! See ya!
- Mike
 

mkaltner

Junior Member
Mar 13, 2001
5
0
0
Well, it worked for a little while before it started the same old symptoms again.
Is it safe to assume that it's the CPU at this point?

I mean, it had these problems.
As soon as I cleaned it off, it started working.
Then it started acting up again.

Seems to me that it's the chip but is there any chance the MB could be acting up?

Thanks,
- Mike

 

Regalk

Golden Member
Feb 7, 2000
1,137
0
0
Its not the CPU HSink at all. It is a problem with the newest BIOS 1004! I just flashed it on a friend's computer and sheesh went through hell when I shut down and tried to restart. It would power up and shut down. After that it refused to power up. Turn off the PS switch and then back on and hit power switch - came on and off again over and over again.
At first reset using JEN, battery - still no go. Disconnected all PS (CD Roms, case Fans etc)everything and pulled all cards still no go. Tried (1 hour later) and tried until finally it powered on and so far so good. Tried a few shut downs and on again to make sure it works. #$@%## Bios from ASUS is real crap. Looks like a repeat of the A7V all over again.
 

jamesbond007

Diamond Member
Dec 21, 2000
5,280
0
71
Try runnning the machine for a while without the copper shim in there. I just wanna see what it does. Sometimes those things can actually defeat optimum cooling because it keeps the heat too bundled up into the ceramic that holds the pins. Just take it off and leave it off for a while and see if the machine works without it.

Also, maybe since the jumpers were connected, maybe permanent damage was done???