Asusa7v133 no post

Wilber31

Junior Member
Nov 14, 2000
3
0
0
If their is anyone that could give me a hand I would really apreciate it. I just finish putting my computer together using a asus A7v-133 /
Amd 1.2/266 , 128Mb/133 micon ram ,ati video. I power it up and it posted just fine. I went to the BIOS and set the fsb to 133 saved the settings and the screen went black and now it will not post.I have no idea what to do.
 

Boonesmi

Lifer
Feb 19, 2001
14,448
1
81
clear the cmos
(that will reset all the bios settings back to default, then it should post again)

the manual will tell you how, but basically on your board it means shorting two points on the board, a screwdrive tip will work
 

ThisIsMatt

Banned
Aug 4, 2000
11,820
1
0
Shouldn't it have been at 133 already? The only time I couldn't get into the bios was when the unlock job on my tbird failed and I had to reset the cmos and redo the bridges. Other times when it wouldn't post just from too high an OC, I just shut it down and powered back up and it would go into the bios immediately...
 

Wind

Diamond Member
Jul 22, 2001
3,034
0
0
Something is not right here. If u r using a 1.2/266 FSB. The mobo should post at 1200 Mhz...meaning there is no need to adjust the bios setting on FSB.

Anyway, clear the CMOS as Boonesmi said. The CMOS solder point is at the edge of the mobo next to the batt. Screw driver or paper clip will do. Short the 2 point bout 30 sec (I prefered). Boot up, & u should be fine.
 

bchalker

Golden Member
Feb 17, 2000
1,204
0
0
I had a similar problem...

1Ghz Locked AXIA read as 750Mhz (7.5x + 100mhz FSB). I bumped it to 133 to put it at 1000Mhz. It then would not boot, and I only got a long beep, before the computer shhut down, each time I tried to power up.

I shorted the CMOS, but still got the same thing. I called ASUS (big waste of time), and told them first about the 750Mhz thing, which they responded with "you have to set the FSB to 133 in the BIOS." I told them that I was not the only one with the 750Mhz problem, but they said it was not an issue with the board. He gave no explanation as to why the post did not read the CPU properly.

I then mentioned the non-posting problem. He told me to reset the CMOS (I told him I had already done that) :disgust: , and then told me my CPU was fried. He said the long beep means it is an "unrecognized " issue, and that my CPU was fried. Well I was a little disgusted, and thanked him for being so condescendingly helpful.

After an hour or so, I exchanged the board, and bought an unlocked 1.2Mhz AXIA. The problem is solved, and my AXIA still works. No damage whatsoever.

In short, I think this is a problem with a quirky reset "feature" on the board. Why they don't have the tried-and-true jumper reset, I do not know.

Hope this helps...