Have you flashed the bios and noticed a difference whether that be with FSB or cpu and what have the out comes been

I'm only asking because i just flashed mine and the sound, well sounds like shiat!
i might have to switch to the onboard again

I have to be the odd guy out here - I dont flash shat. I dont OC and as long as something works I dont FOK with it. I have flashed BIOS in previous motherboards before but only when having a problem with the current BIOS, My new board has been rock steady and gives me no problems so I havent touched it, I dont plan to either. If it aint broke dont fix it........

ive got very bad bad news after f;ashing the mobo the first time it cranked the ddr up to 266 from 133
then i went to flash an old bios and now all i get is checksum error

so basically the mobo is fuxored, i won't be on for many more days unless someone wants to donate a AMD mobo DDR ram slots? im on my 433 with 128 mb sdr ram and 1 1 gb hdd

**** never should have flashed the damn bios! (stars put in by me)

Didn't have a choice, need my 2500+ to be recognized and a flash was needed. Other than that, I'm old school and don't flash unless I have to.

I bet your probably flashed wrong. Try it again.

post 2 i found an asus board now after taking an 11'' kinfe and rebending all the pins headers on the ide ,channels it worksas i know that there is power going to the mobo ,but now there is no display and by the looks of the mobo i have to change some jumpers

here is what it is
ASUS A7V8X with the funny blue pci slot!

Where you running either your FSB or your multi higher than stock when you flashed?

As far as the checksum errors, I get those everytime I change out my proc. I just jump into the bios before the error, load failsafes, reboot and it works fine. Although I gotta go change all that crap back in bios which, but it works.
Also, its usually said that after a flash you should clear the cmos as well. Sometimes I do, sometimes I don't just depends on the changes the bios has.

Also, did you flash from Dos or does Asus have a windows util?

The nforce 2 boards have had a history of bios problems, but I have flashed my nf7-2 hundreds of times with both abit and hacked bioses (what the heck is the plural of bios??) and they have all worked like a charm for me.

Quote: Originally Posted by Caspertg The nforce 2 boards have had a history of bios problems, but I have flashed my nf7-2 hundreds of times with both abit and hacked bioses (what the heck is the plural of bios??) and they have all worked like a charm for me.

Same here, from about Abit 21 and up. and I have left the CPU oc'ed as well...

I had to flash the bios on my mobo.
Currently running the top processor it can handle.
As well as, this is the only bios release where the 133 IDE chain is stable.

It's a very old board, the first board that had 133 for hd's.

i completely destroyed the bios on my NF7-S 2.0, and all i had to do was order a new bios ($15 from eXcaliburPC), install the new bios (CAREFULLY), boot up to windows and while the computer is ON, take the old bios out, put the new one in, and reflash it using a windows based flashing utility, now i have two perfect working bioses, one with the latest official build, and the other with pr3ach3rs bios....

a dead bios does NOT mean a dead motherboard...

EDIT: your poll needs to include "Yes, and it fixed one or more issues." since thats the whole reason for flashing in essence...

Quote: Originally Posted by Fu3lman a dead bios does NOT mean a dead motherboard...

Well, I sure as hell hope not! I don't really care to flash BIOS, but when my BIOS crashed, I had no choice. It gave me the bad checksum error, and I tried flashing it to original and new BIOS during the "Recovery" process, but it would just go back to where it started after flashing. So I sent it to ASUS, and for $5 they reprogrammed it. Popped it into the P4C800-E Deluxe yesterday, same checksum error. Well, I think I'm screwed. I'm starting to worry it's the actual motherboard now, and that would be very very horrible. I told ASUS about my reoccuring problem, hopefully they'll be as prompt and kind to respond a.s.a.p.

Quote: Originally Posted by Fu3lman i completely destroyed the bios on my NF7-S 2.0, and all i had to do was order a new bios ($15 from eXcaliburPC), install the new bios (CAREFULLY), boot up to windows and while the computer is ON, take the old bios out, put the new one in, and reflash it using a windows based flashing utility, now i have two perfect working bioses, one with the latest official build, and the other with pr3ach3rs bios.... a dead bios does NOT mean a dead motherboard...

I know you can do that with the NF7s but not sure if they sell bios chips for the asus boards. I am doing some research right now. I know a few boards have a system where you can send your bios chip to someone who will flash it for ya.

A pimp on here that has his board could even do it for him. Not to sure about trying to do that cross platform. (as in trying to flash his in an Abit board)

Edit: You could give this a shot, but like I said before I get that error all the time after changing components and all I do is go into the bios, load failsafes and reboot. May take a few reboots but it always works and i never get the error again untill I start playing with things again.
http://www.sysopt.com/articles/recoverbios/


Edit #2: Didn't want to double post, but I found a nice explanation:
After upgrading the BIOS on a motherboard, the new BIOS will likely take up more bytes of ROM than the replaced BIOS. The difference in the BIOS image file byte count is detected by the system as a checksum error. CMOS checksum errors require that you enter Setup, check and save your settings, and exit Setup a second time.

Also, it could be the cmos battery. You can try replacing that.

I flashed mine a few tiems when i was having some issues with installation. I also had to clear the CMOS a half a dozen times. Other than that If I dont have any issues with my system I will leave it alone.

I had a problem with my MSI board when i pulled it off of the box. i set it up and when i woudl leave my BIOS, the screen would go screwy. also it would shutdown all the way, so i flashed it, and it ran like a dream.

The stock DFI lan Party Bios was horrible!

Was not stable, and I had problems getting the FSB above 400.

After grabbing a Beta Bios, it went 520+ FSB easy!!!

I think i may have flashed my FIC once or twice.. can't remember... Never had any problems even out of the box.. I just wanted to stay updated..