Asus A7M266 Issue: Won't boot up and unstable at FSB of 266 :(

[Toddmann]

First off, the first time i tried to boot, it defaulted my proccessor to a 750mhz and system speed of 100mhz. Unhappy about that, so i forced it to go to 1ghz, 133mhz system, and it hangs on just about every other reboot....

I do have a 1ghz t.b. with a 266 FSB btw.

Second, after POSTing in the 750mhz/100mhz configuration, it runs through all test flawlessly, even the PCI configuration listing....then just when im about to get the C:\ ...

Screen flashes, and 3 short beeps. This does this continuesly until i reset or powerdown.

I look in the manual, says that a long beep followed by a 3 short beeps (only one that was close to my scenerio) indicated a bad video card. So i swap out my video card for another....

Same thing

please help

 

[DaddyG]

Todd, I have not played with 'C' code TBIRDS but I'm pretty sure that they will not auto-detect on ANY mobo. Most have a 100/133 jumper or you have to select the cpu speed in the BIOS. This type of error that you are seeing is frequently caused by the power supply.

 

[Toddmann]

DaddyG,

I have tried forcing 1ghz/133mhz configuration (through jumpers and bios) and it hangs just about everyother time...

My power supply is brand new (300watts from addtronics). That cant be the issue can it?

There must be someone else out there that knows about this.....please?!

 

[clockhar]

are u sure u have a 1 GHZ processor? Not just an O/C one someone sent ya?

 

[Toddmann]

i paid $217 for it, it better be a 1ghz or i got ripped!!!

I bought it from Spartan Technologies....pretty reputable i believe.

 

[Toddmann]

Ok, here is some more detail

System
CPU 1GHz Thunderbird REV C (266FSB)
Heatsink Chrome Orb
Motherboard Asus A7M
Case Addtronics 6890A +3 fans
Memory (1 stick) 128 DDR Corsair (PC 2100 [266mhz])
Keyboard Microsoft Internet Keyboard PS
Mouse Intellimouse PS2
Harddrive Maxtor 30G
Monitor Trinitron 19"
Video Visiontek Geforce 2 Ultra 64 DDR
ROM CDR 4x4x32
Modem 56k
Speakers Altec ACS54X

First off, this is a brand new system - from scratch. 100% new components. Nothing on the hard drive at all.

The first time i tried to boot, it defaulted my proccessor to a 750mhz and system speed of 100mhz. Unhappy about that, so I forced it to go to 1ghz, 133mhz system (tried both ways: BIOS and JUMPER), and it hangs on just about every other reboot....

So I left it back to 750mhz/100mhz config. I am POSITIVE I do have a 1ghz t.b. with a 266 FSB btw.

Second, after POSTing in the 750mhz/100mhz configuration, it runs through all test flawlessly, and just AFTER the PCI configuration listing.... just when you would expect windows to boot up or in my case the A:\ ...(bootable floppy)

Screen flashes, and 3 short beeps. This does this continuesly until i reset or powerdown.

I should note that if I wait long enough it does boot off this floppy but it continues to flash and beep and is impossible to see what im doing.

This does this weather I have a disk in the floppy drive or not. So this is not as simple as a bad floppy

I look in the manual, says that a long beep followed by a 3 short beeps (only one that was close to my scenerio - because mine was just 3 short beeps) indicated a bad video card. So i swap out my video card for another....

Same thing.

Keep in mind that I am able to navigate through the BIOS screens with no problem and ive now tested 2 video cards, so ive basically eliminated the video as a suspect.

I have NO other cards in the system (other then video), only 1 stick of memory, and a BIG chrome cooler heatink.

I can monitor the temperature of everything through the BIOS and I am running cool.

help

 

[Geocross]

I think you should examine the processor, just to be sure. Getting a 1ghz Thunderbird "c" with the 266fsb for only $217 seems like a really good price, considering they are so scarce even now. Does the processor say "C" on it? also, what do the bridges look like? And lastly, where did you buy it?

 

[Geocross]

sorry, didn't see the part about buying from Spartan... still, just check to make sure. I've had similar probelms in the past (actually just once), and the culprit was an overclocked processor.

 

[neil]

here's a stupid question. It your ddr ram PC1600 (100mhz) or PC2100 (133mhz).
I know you need to have PC2100 to be able to run you processer at 133(266).
If you are running PC1600(100mhz) it is get overclocked when you force you Processer to run at 133(266).

My 2 cents.

-neil

 

[Toddmann]

Im sorry neil, i forgot to add that it is PC2100 (266mhz) memory....i edited my above post to state that

thanks for pointing that out for anyone else that was wondering...

 

[Toddmann]

ITS FIXED!!!

here is link to solutionfixed!