DFI NFII Ultra LanParty - problem

[sykopath79]

For the sake of laziness I'll paste the e-mail I just sent to DFI's tech support. I was wondering if any of you might have any ideas:

I recently purchased a LanParty NFII Ultra board and it worked like a dream with my 1.33 GHz Athlon "Thunderbird" & 2x256 MB PC2100 DDR in dual channel mode. Today I upgraded to an Athlon XP 2500+ "Barton" with 2x512 MB PC3500 DDR, and now I have a problem. When I make any changes to CPU clock speed or clock ratio in the BIOS and then select "save & exit", it starts to reboot but does not come back to the POST screen. I checked the diagnostic LEDs on the mainboard and they read as follows:
LED 1: off
LED 2: off
LED 3: off
LED 4: on
According to the manual this LED reading means "checking CMOS checksum and battery". It will not boot past this point unless I push the Reset button. I do not experience this problem when making any other BIOS changes, only with changes to CPU clock speed. Also, the Genie BIOS tool will show the settings I had previously selected, yet it still reports the default clock speed for the CPU (for example, I set the FSB at 200 MHz and the multiplier at 11, so it should report as 2200 MHz yet the BIOS still reports it at the stock speed of 1833 MHz). CPU clock speed changes never take effect.
I would greatly appreciate any help you could lend in this matter.

 

[DAPUNISHER]

Start out simple and clear the CMOS if you haven't already. If that dosen't work I'd flash the latest bios, or if the board came with the latest reflash it.

 

[AngryGames]

sykopath, please tell me which BIOS you have.

Also if this problem persists after the latest BIOS, and clearing of CMOS without no battery for at least 30 seconds (and no power to the board at all), then we will send you a replacement BIOS chip.

One question also: when you replaced the CPU, did you first clear the CMOS without hte battery before booting up to the new cpu? If not, you have most likely corrupted the BIOS.

Please let me know!

Travis

 

[sykopath79]

No longer a problem... I used Set Optimized Defaults in the BIOS and that fixed the problem, didn't even need to do a hard CMOS clear. Thanks for the response though.