DFI NF2 Lan Party Issues

[privatebreyer]

I've got a the NF 2 Lan Party board and a XP 2700. However WinXP Pro only sees a XP 2100 running at 1.7 GHz.

Does the board underclock it right out of the box? How do I fix it?

 

[will889]

Try here. Travis at AMDMB is official DFI tech support,and is in the forums eveyday. Im not really aware of specific DFI issues. AKA Angry_Games - AMDMB/Forums/DFI

 

[will889]

By the way. make sure your chip is running @ 166 Mhz (333DDR). Make sure you set optimized defaults in the bios, that may do it for ya. Sounds like it's running 133 Mhz.

 

[DerwenArtos12]

Yeah it isn't uncommon for any board to run 166's at 133 for some reason. It is just in the Bios that way.

 

[will889]

yeah, seems like a read across that at amdmb while in the DFI forum there, should be able to just set optimized and away you go @ 166.

 

[BudAshes]

Yeah just hit delete as you boot your computer go into the bios and change the fsb to 166. The athlons default to 133 for some reason.

 

[privatebreyer]

ah yeah. I just did and it beeped at me rudely and refused to boot. Is the RAM and the CPU suppose to be set at 166mhz as well?

And just for future referance, after you reset the CMOS its auto set to 100mhz.

 

[privatebreyer]

There it goes. I set the Ram bus to auto and the CPU to 166. It now reports properly. Thanks everyone.

By the way, I've got DDR400 Ram in it, but of course the CPU is intended for 333. Will it blow up if I set it to 200 (400)?

 

[will889]

No, it wont blow. Nforce2's run async pretty well. However, if you run sync 166/166 you'll get better scores. You can easily, and Imean easily run that XP2700 @ 200, then just use expert in the settings, and manually sync your ram @ 200 along with your fsb. You may have to raise vcore a tad to 1.75 - but it should work fine. If you want a poor mans overclock, you could just raise the muliplier to 12.5 - for that, voltage jump would probably not be necessary. If you just built the system, I would bun in @ 166/166 for a while (1 week) then jump it to 200x11, and raise vcore one notch, you "might" need to loosen your ram timings, depending on the rating your ram has.

 

[will889]

Originally posted by: privatebreyer
ah yeah.
And just for future referance, after you reset the CMOS its auto set to 100mhz.

Just so you know, yes it defaults to 100 Mhz after cmos reset. Seems after browsing some DFI threads elswhere it is common to have to manually assign the 166 in the bios, as "Auto" does not always work on that board. No matter though - looks like you got it. Manual is fine The DFI board apparently does not "always" do this - only on some AMD chips. Mine works fine @ 166 with setting on Auto, but of course, I like manual better Im OC'ed anyway --

Regards
Hoot

 

[AngryGames]

hola gentlemen =) I apologize for taking so long to find this. I have been doing 'real life' stuff lately...if there is such a thing hehe.

Glad to see you got it running up. Hoot is very correct in saying that your cpu will do 200FSB. Running in synch is the best, unless you are trying for a massive overclock like P4 owners do that dont have PC4000 ram . My Barton does 220x11 @ 1:1 and some extra voltages, so I would say give it a shot and I am sure you will find the same thing. It doesn't hurt the cpu much to crank up the bus to 200 from 166 either, and even 133 cpu's will do 200 (XP1700's anyone? heh).

And it will definitely reset to 100Mhz after a bad checksum/failed post. This is only to assure that upon reboot, the cpu will be guaranteed to work at the lowest common denominator (Durons).

If you have ANY other questions, please don't hesitate to ask!

Travis