Did I fry my BIOS?

[snidy1]

I flashed my bios (Abit IC7-G) and it worked fine for a half hour or so. When I rebooted it wouldn't post at all. Everything is powered up, just no post. I tried resetting with the jumper, I took out the battery for an hour. Still no go. I did get it to post ounce and it said cpu is unworkable or has changed. So I checked all the settings and it still says that. I reflashed the bios to the earlier, 7.18. And it still had the same message. I reset it again and now I'm back to no post at all. Any Ideas?
If it's the BIOS chip, will Abit send me a new chip, or will I have to send in the motherboard?

 

[snidy1]

Anyone?

 

[SpeedFreak03]

I would guess that something got screwed up. Did the flash go okay (like did it fully complete, and was there any errors)? I think you will have to send Abit the board back.

-Josh

 

[snidy1]

The flash seemed to go fine, no errors. I've done this many times and this is the first problem I've had.

 

[swank121]

Abit boards are picky about settings when you flash them. Try this: go into your BIOS and restore the default settings. Clear the CMOS using the jumper on the motherboard. Then flash the BIOS. After the flash, clear the settings in the BIOS again. That should fix it .. the same thing happened on my IC7-MAX3. As long as the PC still boots you shouldn't need to send the board back in.

 

[snidy1]

Originally posted by: swank121
Abit boards are picky about settings when you flash them. Try this: go into your BIOS and restore the default settings. Clear the CMOS using the jumper on the motherboard. Then flash the BIOS. After the flash, clear the settings in the BIOS again. That should fix it .. the same thing happened on my IC7-MAX3. As long as the PC still boots you shouldn't need to send the board back in.

Thank's for the reply, but I can't get it to post at all. I tried resetting it several times with no luck.

 

[Paperlantern]

Same thing happened when i installed a new processor on an ASUS board in an Alienware PC. It would hang then tell me processor changed, all it is is you have to match the cpu multiplier and bus frequency to match your processor speed, for example, a Athlon XP 2200+ is 1.8ghz. So on his board i had to set the bus speed to 133Mhz and the multiplier to 12.5, it comes to 1660 or something close. Since that was VERY NEAR the core speed of the computer it worked and recognized the processor as a 1.8ghz. the idea is to come as close as possible, once thats saved, it should, i emphasise SHOULD, cuz sometimes it doesnt, work everytime.

 

[snidy1]

I set all the CPU settings properly when I did have it up. I think it must be a dead BIOS chip.

 

[Bozo Galora]

dont know if this will help, but try......
clear cmos, boot up and disable HT, reflash, reboot to bios

 

[snidy1]

Originally posted by: Bozo Galora
dont know if this will help, but try......
clear cmos, boot up and disable HT, reflash, reboot to bios

It won't post anymore, even when I reset it.

 

[Intelman07]

If it worked for an half hour...the flash couldn't have screwed up. But thats my thinking.

 

[snidy1]

Originally posted by: Intelman07
If it worked for an half hour...the flash couldn't have screwed up. But thats my thinking.

That's my thinking also. I'm stumped

 

[Bozo Galora]

some 6-8 layered P4 boards dont do well under extreme pressure of heatsink cradle - try reseating CPU, then just hold a HSF on cpu with finger pressure - mobo out of case - see if it boots

 

[snidy1]

Originally posted by: Bozo Galora
some 6-8 layered P4 boards dont do well under extreme pressure of heatsink cradle - try reseating CPU, then just hold a HSF on cpu with finger pressure - mobo out of case - see if it boots

Thank's, but I tried that also.

 

[snidy1]

Anymore suggestions before I pack it up?

 

[1966]

Originally posted by: snidy1
Anymore suggestions before I pack it up?

http://www.badflash.com

 

[Ichinisan]

Look for a "Safe Mode" jumper in the instruction manual. It might be different than a BIOS bank-switching jumper. Most mobo's have a Safe Mode jumper for clock frequency issues.