p5wdh stuck at 360

[catscit]

My p5w dh seems to be stuck at fsb360.
I have a week 27 e6700 and i'm running the following bios settings:

ai overclocking to manual
cpu freq 360

performance mode standard
pci express freq to 101
pci clock synch mode to 33.3mhz
mem voltage to 2.20v
cpu core voltage 1.55 or 1.53
fsb term voltage 1.5v
mch chipset voltage 1.65v
ich voltage 1.20

on cpu config page
disable all except microcode updation

on chipset page
config dram timing by spd set to manual, running 4-4-4-12 as per spec of the ram
dram ecc to disabled
hyper3 disable
dram throttling disabled
leave other stuff on auto

ram is running 1:1 but at 266fsb i can run it at 800mhz without probs so the ram is not holding me back.

i've bumper vcore to 1.6 but i can never get a decent boot on 370fsb.
it's 100% stable on 360 (4+ hours bf2)

my p5w dh is a very early one.
I followed the sticky and took all caps of the heatsinks, removed all thermal paste and replaced with as, heatsinks have good contact.
I have fans on the mem and nb, case has very good cooling with additional top fans (2x120)

what can i do to get a higher fsb?
I'd like to run 4GHz (fsb 400)

running bios 1101

[SLi_dog]

See here:
http://www.xtremesystems.org/forums/...d.php?t=111400

[^don.k's^]

Set performance mode Auto. Bump Vddr @2,4v, it wont hurt.

Are you using those 4 gigs ? Try with 2 gigs. Also see how much vcore needs that 6700 to get stable @3600, there seems to be a wall, not for the cpu id say.

Regards!

[catscit]

See here:
http://www.xtremesystems.org/forums/...d.php?t=111400

damn, how could i have missed that:

Summary:
1. FSB Wall at 380FSB with manual Ram settings in Bios
2. FSB Wall at 400FSB with SPD ram settings in Bios
3. FSB Wall at 440FSB with manual Ram settings in Bios but changed to match SPD in windows with memset.

I'll try spd setting in bios, i'm running manual

Set performance mode Auto. Bump Vddr @2,4v, it wont hurt.

Are you using those 4 gigs ? Try with 2 gigs. Also see how much vcore needs that 6700 to get stable @3600, there seems to be a wall, not for the cpu id say.

Regards!

I'm using those 4 gigs and need them (vmware).
my e6700 is 100% stable at 1.53 vcore 360fsb. 100% stable = i can play the whole day with the machine without reboots, play bf2 for several hours etc, no problem at all. Because that 1.53 is quite low in my opinion, i'm actually running at 1.55 to be safe.

what is vdimm 2.4 going to help? my mem is already 100% stable running 800mhz at 2.2 (using 4:5 divider), with fsb370 it's running at 740 so 2.2 ought to be enough?
I'll try 2.4 anyway but i'd like to learn from this!

thanx guys

[^don.k's^]

I'm using those 4 gigs and need them (vmware).
my e6700 is 100% stable at 1.53 vcore 360fsb. 100% stable = i can play the whole day with the machine without reboots, play bf2 for several hours etc, no problem at all. Because that 1.53 is quite low in my opinion, i'm actually running at 1.55 to be safe.

what is vdimm 2.4 going to help? my mem is already 100% stable running 800mhz at 2.2 (using 4:5 divider), with fsb370 it's running at 740 so 2.2 ought to be enough?
I'll try 2.4 anyway but i'd like to learn from this!

thanx guys

I dunno if 2,4 will help, but you can try, its free! BTW, also, try with just 2 gigs, i know you wanna use those 4 gigs, but, if thats the problem, you have finished looking for the problem is holding you back. If 2gigs lets you go higher, then the problem is the chipset cannot manage 4 gigs @more than 360 FSB, do i explain good ?

[politenessman]

i noticed that you are using the bios settings i posted on my "3700" thread. the automatic spd enabled is pretty important. also, bump up your pcie clock to 110mhz. i dont know why that works, but it works for me and the other guys who used those bios settings. i think i read about that here, at xs. dont worry about your ram timings being set loose by the spd. you will get more performance from a couple/few hundred axtra mhz than you would from tighter ram timings. also, like 1 or 2 of the above fellows mentioned, that 4gb ram could very well be holding you back.
good luck.

very truly yours,
politenessman

[Durzel]

4GB of RAM is really going to cripple your overclock. You would've been very lucky to get 4Ghz on air on an ES E6700 let alone a retail B2 stepping.

360x10 is a great overclock for the chip, 1Ghz overclock isn't to be sniffed at!

[catscit]

ok, using the 2 gigs just to find the "problem" is a good idea, i'll try that.

Yes indeed i'm using the settings from the 3700 thread as a starting point, i'll try the spd and the 110 pci-e setting as well, and post my results here.
I'm not too concerned about tighter ram timings, i'd rather have 4 ghz fully stable

[catscit]

ok, bios 1402 doesn't help my overclock and i tried everything but 370 was unreachable.

i put the mem timing on spd (auto setting) which helps cause then i can actually boot 370 but it crashes very quickly. without the auto settings for memtiming it crashes before reaching the windows load screen with the moving bar at the bottom

pci-e at 110 screws up my raid 0 dramatically, strange things happening like boot sector not found, files being read only and the 5th disk on the jmicron controller becomes unstable so i went back to 101 or 100 setting (running 100 at the moment)

haven't tried removing 2 sticks of ram yet.

however, bios 1402 has downward unlocked multis, changed from 10 to 8 and now 370 is no problem.
I'm running 2x GO-SP2004 as i type.

i'm a bit confused now, as apparently the board can do 370, the mem can do it (obviously, 400mhz mem running at 370 is not a problem) but the cpu just doesn't like 3.7GHz?

So my cpu is the bottleneck?

this would be a REAL

[catscit]

380x8 and still no problems.

I cannot use memset i think, i'm running XP64.
Any other program to retrieve the mem settings?

[catscit]

wow, 1.6 vcore is a killer, temps going trough the roof (didn't watch it for a moment and got instability and crashes).

I used cpu-z for the memset settings, the last setting in cpuz, bankcycletime (Trc) needs to be divided by 4 to be able to enter it in the p5w dh bios.

I've now set the bios mem timings to manual and then set them to the same timings i saw in cpu-z when set to spd in the bios.

fsb380 rock steady after increasing case fan speed to get out the heat.
vcore is 1.6, vdimm is 2.2, all other to max.

just letting dual go-orthos run for a while now to make sure i got a new stable baseline. then i'll either up the fsb, or up the multiplier to see if i can run 380x10.

overclocking is so much fun with this mobo.

and i tried pci-e 110 again a few times but i keep getting weird disk problems on both the raid 0 and the single jmicron attached disk so i've set it to 100 again.

[Durzel]

Are these results with 2GB or 4GB?

[catscit]

all with 4GB.

I'm now certain i have a temp problem.
8x380 is 100% stable with all fans @ 12V.
With the fans at 5 volts it fails pretty quickly in orthos go.

i took off the orignal heatsinks and put a thermalright hr-05 on the nb and zalman nb47 on the SB, strapped a 80mm zalman fan to both.

cpu temp is now 35DegC at full load, mb temp is 55-60degC (speedfan)

mb temp>65 = crash!

[^don.k's^]

You have temp problems, sure, put a fan over the DDR2 sticks, they should be getting insanely hot, touch em and you will see... Even 4x512mb sticks get insanely hot, it also push controller memory to its limits so you have such high mb temps, when you have some time, try with 2 sticks, it will fly

[catscit]

will try tonight!

tried booting at 370x10 ro 380x10 and both no go, i can get into windows but not even stable enough for a cpu-z suicide shot!

i have a 120mm on the mem.
I'll rearrange the fans tonight to get more air over the mobo between sb and nb and get more cooling on the sb.

cooling seems to be the main issue with 4GB ram, you're very right about that.

it's only a problem in orthos-go though, i can run superpi all day and mb temp never gets above 45degC, but ortho-go seems to be a good measure of overall stability

[catscit]

tried 2 gig of ram (2 sticks), doesn't help a thing (strange? i would have thought it would actually)
I still have only 2 gigs in there, i want to try more stuff.
i now have a 120mm fan directly over the mem and a 120mm fan and a 80mm fan blowing over the southbridge. the 120mm fan covers a big area of the board as well.
BTW, the NB gets PRETTY hot during go-orthos testing. the thermalright heatsink does its job pretty good though.

ok, so i'm baffled and stuck at 360x10 or 380x8.

would bumping the vcore a lot help?
I can do 350 at near standaard but need 1.6 for 360 and higer

[catscit]

ok, done a lot of testing.
I can boot at up to 380fsbx10 but need 1.65Vcore for that.
375x10 needs 1.625Vcore to boot
370x10 needs 1.6Vcore to boot
360x10 needs 1.55vcore to boot and 1.6 for pi stable
I can boot and do a 1M super pi at 380x8 a 1.6Vcore

I can never get even a post at 401fsb, not at 8mp, not at 1.65vcore. It will crash while saving the settings in the bios and never even post.

So i need a LOT of vcore.
Best settings are indeed mem timing set manualy at SPD settings from cpu-z
pci-e=101 (110 gives disk problems)
2.1vdimm, 2.2 REDUCES the max overclock!!!
all other voltages to max, auto reduces overclock.

I'd like to test another motherboard now.
P5W65, P5WDG WS Pro or Abit awd9 max

[^don.k's^]

That's weird for sure...