NF7-S rev 2.0 / Duron 1.8 / won't overclock!?!

[gserlenga]

Hello Anandtech Forums people, i just joined today :>
Today i built a new system from the ground up based on an Abit NF7-S 2.0 mobo, Duron 1.8GHz Applebred
CPU, and 2 sticks of BuffaloTech PC3200 cl 2.5 256MB DIMMS with Winbond CH-6 chips.
System runs beautifully with WD Raptor HDD under WinXP SP1a, BUT.......

I cannot overclock the system in any meaningful way, it won't boot with anything except:
-factory multiplier of 13.5, FSB:133MHz, core clock: 1.8GHz
I have read that many people using this same board have gotten overclocks with the 1.6 and 1.8GHz applebred-core Durons in the 2.0-2.2GHz range with 200MHz FSB. I have experimented with a number of settings in BIOS that i picked up scanning the forums here and at extremeoverclockers.com, but to no avail.
The system won't POST with any settings other than the defaults. Cooling is more than adequate, that's not the problem. The BIOS "User Define" function allows me to adjust the multiplier, CPU-FSB ratio, FSB speed, and all voltages. It does'nt appear that the CPU is multiplier-locked, and the Abit MaxFID feature is supposed to override that even if it is multi-locked, or so i have been led to believe.

Can anyone who has successfully overclocked this CPU on the same mobo please give me a hand?
My goal is: 10 or 11 multiplier X 200FSB, with minor overvolts if necessary on core, DIMMs, chipset, etc.
Specific assitance and not confusing generalities would be most appreciated.... :>

 

[Soulkeeper]

looks like you got a locked cpu
you might have to rely soley on fsb speeds for you overclock
i tryed a locked 1800+ in a board and the bios still let me select different multiplyers but it would only do the lower ones

so the default might be the highest you can get, from there it'll be chipset/memory overclocking
so work those voltages vdd helps
don't be afraid to pump the vdimm up to 2.8v

good luck

 

[gserlenga]

a few more questions... Since i'm using PC3200 memory, i should'nt need to play with my vdimm settting(currently at 2.6v) since my FSB/mem bus is only running at 133 now and even overclocking it to 200 is still within the rated specs of ddr400/pc-3200 memory, right?
i can't get the system to boot or POST at all at any multiplier other than 13.5(the default for a 1.8GHz duron). I tried a 134fsb at 13.5 and it booted....guess all i can do is keep pushing the fsb till i reach a limit. I don't think i should have to do any overvolts except for possibly pushing the vcore to 1.6v, but even this seems unneeded since i've read of many people who have overclocked unlocked applebred durons up to 2.2GHz at the stock 1.5v core voltage...damn! this CPU is turning out to be a real disappointment, i just read that all "post week 39" applebred durons are multi-locked, should've spent $45 more for an XP-M 2400+! i'll keep trying to o.c on the FSB alone though. Hopefully i can at least get to 166, if not i'm trashing this cpu ASAP.

 

[Soulkeeper]

you might need to bumb the vdimm to 2.8v just to get 200mhz if you have 2-3-2-11 timings or better
most people agree that vdimm under 3v is safe with most current ddr1 modules

will it let you run a 5:4 fsb/mem divider ?

 

[jagec]

dividers are bad on nforce2 though...

 

[gserlenga]

I just read that the post week 39 (around Dec. 2003) AMD CPUs are all superlocked (don't know if that includes the xp-m which is advertised as being multi-unlocked). Check out this ridiculously long thread at ocforums.com:
http://www.ocforums.com/showthread.php?s=bfffc0e6ba1497bb1f630c91f95fb745&threadid=244237&perpage=30&pagenumber=40
This means that they won't run at any multiplier but default, which has been my experience thus far.
I don't really want to run async., but what would a 5:4 divider do for me?
i'll just keep pushing the fsb and set the vdimm to 2.8, if i can get 13.5x166 or even 13.5x150, i'll have to be satisfied. Hopefully i can get it around this FSB with aggressive mem. timings

 

[jagec]

Originally posted by: gserlenga
I just read that the post week 39 (around Dec. 2003) AMD CPUs are all superlocked (don't know if that includes the xp-m which is advertised as being multi-unlocked).

you read that right, all of them except the XP-M. Which is why XP-Ms are becoming pretty popular these days...

I'm kind of surprised they started locking them that way...I didn't think rebadging of AMD processors was happening too much, and it really alienates the enthusiast community.

 

[Soulkeeper]

Originally posted by: jagec
dividers are bad on nforce2 though...

not really
with the dual channel memory you are already getting plenty more memory bandwidth than the fsb and agp/pci bus can saturate fully
this is why there was only a few % in many things

dividers let you get that extra few mhz
5:4 is great because once you get that fsb up the mem speed will pass it's default
good for slower mem like pc2100 and pc2700 too

 

[gserlenga]

Here's an update on my progress for all those interested...

Gear: Duron 1.8 (multi-locked with no L2 mod, AMD is cracking down!), NF7-S rev 2.0 with latest BIOS(23), two 256mb Winbond Ch-6 DDR400 modules from BufTech, 2500rpm cpufan, copperbase aluminum heatsink, arctic silver ceramique paste, 120mm rear exhaust.

Tested with Prime95 torture test (set to "inplace large FFTs", max heat generation/power consumption)

All results @ 2-2-2-6 timings / core:1.65v, all other voltages left at default /
- 13.5 x 150 = DDR300, Prime95 stable, 41idle/48load
- 13.5 x 155 = DDR310, Prime95 stable, 43idle/50load
- 13.5 x 166 = POST but freezes at WindowsXP boot

strangely as i sit here typing this with only my web browser and an explorer window open, almost 1/2 an hour after running Prime95 at DDR310, my cpu core temp is still pretty high. It remained at 50C for quite a while before dropping back to 46C as of now.

- I tried 13.5 x 166 at 1.75v core, it booted into windows but failed Prime95 in 30 seconds. I did not check the temps at that time since i cannot get AbitEQ or Winbond hardware monitor to run. AbitEQ gives error message when run "open file error", WHM gives error message "no driver exists". I am now using MBM5 to track temps/voltages.

-given the high temps only at DDR310, i imagine DDR333 is just too hot for the Duron 1.8, where its running at 2.25GHz. i'm not willing to install loud and elaborate cooling solutions just to get stable at DDR333 on a duron.

right now while still at 13.5 x 155, my CPU core temp is at 44C, almost 45 minutes after running Prime95 and being fairly idle after that....

 

[MDE]

2.25 isn't bad at all. That's about what I got on my 1.6 Duron at 1.65V.

 

[gserlenga]

actually, right now its only stable at 2.1GHz / DDR310

 

[MDE]

Originally posted by: gserlenga
actually, right now its only stable at 2.1GHz / DDR310

Sorry, I misread then. You still got an extra 300MHz out of it though :beer:.