P5WDH E6600 Stable Setting for 3.6 ghz

[Denun]

I have a problem to stabilize the system FSB @ 400/401
I read on OCZ forum that to gain some stability with RAM i have to go over 400 (like 401, 402.....)

here is my system:
MB: Asus P5W DH Deluxe
CPU: E6600 @ 3.600 ghz + Zalman 7700
RAM: 2 x 1gb OCZ PC6400 DDR2 Dual Channel Platinum XTC Revision 2 Edition (OCZ2P800R22GK)
HD: 3 x Segate SataII 320gb 7200 in modalita AHCI
VIDEO: EN7300GT Silent
PSU: OCZ Gamer Syst. 650W

some info about the system...
- i can boot at every speed even @ 425mhz, i didn't try to set my system to those speeds bcose i'm on air.
- Windows Crash on start after FSB >415
- from FSB=380 to 410 i can run PI32 MB without problem, i can run S&M "long full load" test without problem.

but Orthon and Prime give me arror after few seconds, WHAT CAN I DO? i really need an help.

http://img331.imageshack.us/img331/5259/fsb405ram405cpu3645vramxt4.th.jpg (http://img331.imageshack.us/my.php?image=fsb405ram405cpu3645vramxt4.jpg)

I'd like to stabilize the system for FSB=400/401, i'm running all day and i can do everything (watch movie, encoding), SuperPi 32M , S&M Test, but Orthon and Prime give me error after few second.

Here is my setting:
FSB = 401 ----> already tried from 400 to 420
DRAM = 802 ---> already tried from 800 to 840
V Memory = 1.90 ---> already tried from 1.9 to 2.2
V CPU = 1.50 ---> already tried from 1.50 to 1.55
V FSB = 1.5
V MCH = 1.75 ---> already tried from 1.75 to 1.85
V ICH = Auto ---> already tried from 1.05 to 1.2

Digital Home Mode = Disable
Modify Ratio Support = Disable
Microcode Updation = Enable
Max CPUID = Disable
Execute Disable Function = Disable
Enanched C1 = Disabled
CPU Internal Thermal Control = Disable (already tried in Auto)
Virtualization Techn = Enabled
Intel SpeedStep = Disabled

Configure DRAM by Speed = Disabled (already tried in enabled giving me this timings 5-6-6-15-23)
RAM Setting: 4-4-4-12-6 (already tried in Auto)
DRAMM ECC Mode = Auto
Hyper Path = Disabled
DRAM Throttling Threshold = Disabled (already tried auto)

PEG Buffer Lenght = Auto
Link Latency = Auto
PEG Root Control = Auto
PEG Link Mode = Auto
Slot Power = Auto

Bios Version 1407

http://img331.imageshack.us/img331/5259/fsb405ram405cpu3645vramxt4.th.jpg

http://img331.imageshack.us/my.php?image=fsb405ram405cpu3645vramxt4.jpg

[jkresh]

if your temps are ok the try upping the vcore a little, if prime isint running then you are not stable and a voltage increase is probably necessary. On my water setup at 1.6volts (1.58 actual) I seem to be stock at 378, if I got higher (even 383 or so) prime will run fine but at some point the pc will just restart itself (and prime never errors, the restarts happen anywere from after 5 minutes to 2-3 days but it happens and continues to happen randomly until I go back below 380). My temps under full folding at home load are 32c, and full prime they hit 40 (under asus probe, coretemp has about 5-8C higher.)

[Falkentyne]

jkresh,
disable automatic restart in control panel->system.

I can't believe how many people don't disable it.
You NEVER know what error you're getting if you don't do that, unless you use something like Debugging tools for Windows to open up the crash dump.....

[jkresh]

Falkentyne thanks but automatic restart is disabled and if I check the event viewer there is no event from the restart, it doest appear that windows is catching the error (it reacts as if someone just hit the restart button or quickly powered it down then right back up.) I have been overclocking for a while now and I havent seen anything like this before. Usualy if I am prime stable (24+ hours) then go up a few I get an error in prime, not this random restarting.

[Mykou]

here are my settings to be stable @3.6ghz

-fsb 400 x 9
-cpu settings=all disable but microcode
-Vcore=1.43v( stable orthos ,maybe you'll need more , have a good L628B121..:rolleyes: )

-vdimm=2.1v
-VMCH=1.65 ( my P5W DH early rev so it is set at max )
-Vfsb=1.40
-ICH=auto

ram manual settings 4-3-4-12
hyperpath 3=auto
ram throttling=auto


Vmch at 1.75 + may be very hot , don't forget to cool it enough

Regards :)

[Denun]

@@!!!@@@!!

i did a little step back, i started from FSB=370 and goign up only after 3 hours (minimum) of orthos.

i had a real bad notice, to make my system stable @ 380 i had to give 1.475 volts to the CPU. Is it the worst cpu around?
i can reach 1.50 but i don't think i can give more voltage then that to my conroe, bcose i can't handle the temps with my zalman 7700.

looking the chart, what's ur estimate? how much i need to reach 400FSB?

my only hope is that the bios is beta (downloaded from asus official site) perhaps using other bios i can reach the same FSB giving less voltage.


Do u know if there is a bios that permit to use less volt for the cpu?
Can i raise other params voltage instead the cpu? (don't know, fsb, mch, ...)

http://img67.imageshack.us/img67/9306/p5wdh1503ocstepfy2.th.jpg (http://img67.imageshack.us/my.php?image=p5wdh1503ocstepfy2.jpg)


Note:
in every step i can run Pi 32MB, windows works fine without crash, only orthos report me an error after few minuts (in black)

[unixadm]

Sounds like it may be your processor. You can always try to lower your multi and see if you can stabilize at those FSB settings. If you can, then you know your processor is the problem.

I just purchased an E6600 from Newegg and a P5W DH Deluxe. Here's what I've found interesting about my particular combo. I'm using the 1503 bios, the cpu I received has a default VID of only 1.225v. Once I passed 402FSB, my board would not post. I looked through the big thread of problems and solutions and found somethings that may help. After trying everything listed, nothing helped. My board would fail to post at anything above about 405fsb. I figured I got a board that was not a great overclocker.

Mind you at the 9 multi, I had my processor running at 3.3ghz using the default voltage, which was indicated at 1.2v in Windows. However once I started increasing the FSB and dropping the multi, I found that I had to increase my Vcore to 1.3 just to get the system to post. Mind you, Orthos was stable at 3.3ghz using a x9 multi, would not post at a lesser speed using the x8 multi above 405fsb. For some reason if I set the voltage in the bios to anything less than 1.3, it will not post no matter if the FSB is 410 or 425. I don't think my CPU needs the voltage, but it has something to do with the board. 1 FSB (405 -> 406) = .8v increase to post? Does not add up to me.

I'm running everything else at the default or auto settings. I do not have the MCH over-volted. I'm not using SPD settings with my memory (Corsair XMS2 PC6400PRO, 2gb), but running 5-5-5-15 set manually. Hyperpath3 is enabled as well. Nothing crazy and so far, so good on Orthos stability and 3dmark 2006, along with SuperPI.

As of today I'm at 425x8, 3.4ghz, 1.28v indicated, DDR 850. Lower that multi and start testing other things besides your processor. My board does not need crazy volts or cooling to be stable at higher FSBs.

[triggerc]

unixadm, do you have a B coded e6600 as well? man i'm jealous of all these super Bs, anyone wanna sell me one?

[moshpit]

@@!!!@@@!!

i did a little step back, i started from FSB=370 and goign up only after 3 hours (minimum) of orthos.

i had a real bad notice, to make my system stable @ 380 i had to give 1.475 volts to the CPU. Is it the worst cpu around?
i can reach 1.50 but i don't think i can give more voltage then that to my conroe, bcose i can't handle the temps with my zalman 7700.

looking the chart, what's ur estimate? how much i need to reach 400FSB?

my only hope is that the bios is beta (downloaded from asus official site) perhaps using other bios i can reach the same FSB giving less voltage.


Do u know if there is a bios that permit to use less volt for the cpu?
Can i raise other params voltage instead the cpu? (don't know, fsb, mch, ...)

http://img67.imageshack.us/img67/9306/p5wdh1503ocstepfy2.th.jpg (http://img67.imageshack.us/my.php?image=p5wdh1503ocstepfy2.jpg)


Note:
in every step i can run Pi 32MB, windows works fine without crash, only orthos report me an error after few minuts (in black)

Question for you. Is there a specific CPU clock your shooting for, or just looking to find your fsb ceiling? If the later, have you tried dropping your multiplier as yet? In order to see if I could do 400fsb, I dropped the multi to 8x on mine. Now running a smooth 3.2Ghz with 400fsb and 800 memory and still seem to have quite a bit of headroom above that.

I've Prime95'd and Ortho'd it to hell and back now and totally stable. Drop the multi, just to see if your really hitting a fsb wall or not.

[Denun]

Question for you. Is there a specific CPU clock your shooting for, or just looking to find your fsb ceiling? If the later, have you tried dropping your multiplier as yet? In order to see if I could do 400fsb, I dropped the multi to 8x on mine. Now running a smooth 3.2Ghz with 400fsb and 800 memory and still seem to have quite a bit of headroom above that.

I've Prime95'd and Ortho'd it to hell and back now and totally stable. Drop the multi, just to see if your really hitting a fsb wall or not.

my goal was to have a system stable @ 400 FSb so i could set RAM ratio 1:1, i tryed to set the multiplier @ 8x but i having problem just to boot the system.

in the afternoon i'll post other excel table to check how is doing.

What's ur setting? ar u liquid cooled or air?

[moshpit]

my goal was to have a system stable @ 400 FSb so i could set RAM ratio 1:1, i tryed to set the multiplier @ 8x but i having problem just to boot the system.

in the afternoon i'll post other excel table to check how is doing.

What's ur setting? ar u liquid cooled or air?

Using Air cooling. Gigabyte G-Power Pro and AS5. Temps are around 51C idle, about 60C load as told by Core Temp and iTAT. Motherboard sensors tell a completely different story tho, 37C idle, 47C to 50C load depending on what it is loading up the CPU to 100% and room air temps.

Settings are multi of 8 with bus speed 401 (I tried setting 400 flat, but it kept showing up as 399 and just under 3.2Ghz total, setting to 401 shows as 400 flat and gives me exact 3.2Ghz). Ram is on the 1:1 divider and vcore is at 1.375. I was completely Orthos and Prime stable at this speed with stock vcore, but something weird kept causing my TV Tuner to reboot the computer, bumping up to 1.375 eliminated that issue. Motherboard bios is the F5 version.

I gave my MCH a little +.1 voltage, fsb +.1 voltage, and ram +.1 also (tho this might have been unnecessary as 400fsb means stock speed of 800 for my ram, but I've read too much about problems with higher fsbs on this site and a tiny +.1 won't hurt anything). Just to be safe, I also dropped the PCI-E to 98mhz instead of the full 100mhz. SuperPi is in the mid 17's right now, perfect I think for this speed chip.

I couldn't be more satisfied I think. I've hated Intel for a long time, but that time is now over. They've proven themselves to be past the worst of thier problems as far as I'm concerned. I'm truley excited about this rig :D

Edit: I should add that I'm not a complete noob to overclocking, but I am a complete noob to Intel overclocking. My old X2 4400+ runs a smooth, stock air cooled 2.62Ghz and has done so for well over a year now, but that's still piddly compared to what this week 29B E6600 can do. But niether am I an expert like many of the guys here on these forums and am quite the noob compared to them. Regardless tho, I'm very proud of my choices in hardware and ability to get the most out of it as, in this case at least, I'm getting a 40% OC for free with minimal effort.

[Denun]

vcore is at 1.375
1.375 for 3.6ghz .....u'r killing me :D

even at 1.57 i can't have my 6600 stable @ 3.6

[moshpit]

I just had to double check what I said to be sure, but I didn't say anything about 3.6Ghz, I said I'm doing 3.2Ghz right now with plenty of headroom for more I think. 3.6Ghz is my eventual target tho, funny that you should mention that speed. If I can achieve 3.6Ghz on air with this chip, then I'll do a little dance of joy at seeing my first 50% overclock. I'm not putting my hopes on it too much tho, my current speed is insanely powerful as it is, and with having just tuned up my memory timings to what they're supposed to be instead of the crazy 5-6-6-20 that auto had me on, my SuperPi just broke into the 16's. Timings are now at 5-5-5-15 and just to be safe I gave the memory a little +.1 voltage nudge.

http://i12.tinypic.com/48zwkko.jpg

[my65bug]

I have a e6700 but I do have to pump alot of vcore into her to get her to post. I cannot go over 400 fsb without a post failure. Very interesting reading.

http://www.differentracing.com/john/7268.jpg

[ooztuncer]

Well, i dont have an asus board or a 6600 cpu, but I have the same ram. i wanted to say that I believe your problem is the cpu or the board but not the ram (just to eliminate one other factor)

i am using my ram @ 450mhz giving 2.1 voltages (4-4-4-15 for 3.6ghz vcore=1.45 - 24/7 run) and they are OK up to 475mhz using 5-5-5-15 @ 2.1 vdimm (see sig).

if I were you, to be on the safe side I would change the timings to 5-5-5-15 while finding your max cpu, then try tweaking the ram timings. Then run orthos or play games, whatever you prefer, to check stability. Good luck...

[my65bug]

Well, i dont have an asus board or a 6600 cpu, but I have the same ram. i wanted to say that I believe your problem is the cpu or the board but not the ram (just to eliminate one other factor)

i am using my ram @ 450mhz giving 2.1 voltages (4-4-4-15 for 3.6ghz vcore=1.45 - 24/7 run) and they are OK up to 475mhz using 5-5-5-15 @ 2.1 vdimm (see sig).

if I were you, to be on the safe side I would change the timings to 5-5-5-15 while finding your max cpu, then try tweaking the ram timings. Then run orthos or play games, whatever you prefer, to check stability. Good luck...

Who was this directed to?

[Denun]

i think he was referring to me.


the RAM is really good but i think there is some kind of incompatibility with this motherboard, bcose if i change the timing it's worse.

on this chart u can see some (i did a lot of try) examples:
http://img325.imageshack.us/img325/2020/p5wdh1407ocstep359401hm3.th.jpg (http://img325.imageshack.us/my.php?image=p5wdh1407ocstep359401hm3.jpg)

and another strange thing is that when cpu is undervolt the machine can run orthos only for few seconds, i understand that is undervolt but i'd expect at least 20/30 minutes.
I have to say again that i'm new on OC, but i have the feel that if i have other ram perhaps i can gain something in cpu volts.


i can't push futher to search the stability on 400 FSB, bcose i can't handle higher temps, so i have to work there on other params.. or find a motherboard that is more stable/permit less volt on cpu.

note:
Tomorrow i'll try P5W64 and i'll add another chart.

note2:
for sure there is no difference for me between Bios 1407 and 1503, on my system they needs the same volts (contrary to what other users found)

[unixadm]

unixadm, do you have a B coded e6600 as well? man i'm jealous of all these super Bs, anyone wanna sell me one?

What's a B coded processor?

My FTP/Batch#: L629B361, Pack Date 10/03/06.

[triggerc]

yep you have a B, the letter after the 629 is the processor code, and Bs are amazing overclockers.

[Denun]

the new P5W64 and Conroe 6400, really amazing result.

during the day i'll try the 6600

http://img85.imageshack.us/img85/9307/p5w64b303e6400266to440rg4.th.jpg (http://img85.imageshack.us/my.php?image=p5w64b303e6400266to440rg4.jpg)

[pancito]

Denun

You and me have the same board and memory combo.

I have notice that memory timings is what is :banana: :banana: :banana: :banana: my overclocks, my 6400 easily gets up to 3.6 with 1.525 vcore BUT with memory at 667(3:2 Divider?) if i try to change it back to 800 range it doesnt but up no matter what voltage i put on MCH or memory.

I hate that SPD changes the default timings at 6.5.5.18 if i put those timings at Bios it doesn't boot up.

I currently have my pc at FSB 410 x 8 = 3280 memory at 1025 (4:5 Divider), yesterday i could run Orthos for around 2 hours at 3.4 but after a reboot it failed in like 3 mins.

I hate taking all night to play with the damn settings. and getting to the same results.

[triggerc]

try using memset and loosen the tRCF to 42 and tRD to 7 or higher, see if that helps your stability.