Struggling to find some help

My Rig:
DFI DK P35 TR2S
Q6600 Core 2 Quad G0 revision
4GB Mushkin Redline 2x2GB
Evga 9800GTX 512MB
Corsair 650TX
Zalman 9700

I am not new to overclocking I have OC’d AMD CPU for quite sometime but these Intel ships and the MB they run on just confuse me. Currently I can get the system to post and boot to vista at stock voltages @335 FBS (stable Prime95) and 362 (fails Prime95 but runs 3dmark). The overclock I am looking for is 3.4 which is a 380 FBS

(I have no clue how to change these voltages on my MB there is only special add but anytime I change this from auto I have to pull out the BAT on MB and reset cmos, I I have to leave the 2 speedstep option on cause if I turn them off the system wont even boot.) - Sorted this problem out (i think)

Here are some pics
http://onlyalad.net/stuff/335x9_Q6600.jpg
http://onlyalad.net/stuff/335x9_Q6600.jpg
http://onlyalad.net/stuff/335x9_Q6600_Memory.jpg
http://onlyalad.net/stuff/335x9_Q6600_Memory_SPD.jpg

I really need someone with a DFI DK P35 TR2S to walk me through the steps of pushing this board to the 380FSB, I have read quite a few things but they aren’t related to this board so there are some options not available to me.

Typical ram settings (volts, speed and how to change them correctly)
MB Voltage settings (seems to be 2 settings VID and CoreV not sure)
Typical temps on load and Idle
Anything you Pros think I should know.
Screenshots of Current Bios settings for my Board help me a lot, something i can base my changes on? So i can push the OC to 380-400 FBS


Additional Comment:

So i used prime95 25.6 to test they system @335 FSB and is has run for ~8hours no errors. After this i tried to push the FBS to 380, 390, 400 but i ran into 2 problems. Either BSOD on OS load or it would load the OS and run prime95 but would BOSD after ~10 minutes.

http://onlyalad.net/stuff/380fsb_crash.jpg
http://onlyalad.net/stuff/380fsb_crash1.jpg
http://onlyalad.net/stuff/380FSB@1.376vore.jpg - Crashed ~44minutes

Also are these temps kind of high?? It have a Zalman 9700 fan speed set to medium. - Updated
I noticed that my temps were high with the Zalman after looking at other posts so i went ahead and got a Thermalright Ultra-120 Extreme w/Scythe SFF21F http://www.crazypc.com/products/ultr...eme-50983.html

this is the best HSF for my setup right?

those temps are right for that poopy air cooler and yes,, its a turd cooler

its not a BAD cpu but not the best either... your voltages are somewhat out of MY liking for that Ghz you have set
up the vcore one more notch

NB SB and everything you shouldnt even have to touch for a while yet.
400mhz FSB is EASY for any board of any decent caliber and you wont need to adjust the voltages.


your also only running 1.9v on the ram,, up it to 2v see what it does
you should run memtest either in windows or dos and find out if the ram is failing instead of the cpu.

i dont know about the other guys but i see that vcore and i say your overvolting the cpu
and undervolting the ram..

get a new cooler

and those temps are spot on for that vcore running OCCT,,,

so i made the changes you suggested and tried a few other changes people suggested also, here are the results.

FSB @400
DRAM Ratio 333/666 @2.0v 5-5-5-15 (Mem86+ no error for the hour it was running) http://onlyalad.net/stuff/MemTest_10...-5-15@1005.jpg
Vcore added +.137mv put me at a 1.43 Vcore (from my reading this is really high) - if i dropped this down to .125mv BOSD on OS load. so im thinking that this is the problem but if i turn it up anymore it gets way too hot. i was reaching 67-70 celcius per core which is really bad for the chip
NB 1.33 (tried multiple settings booted from stock to 1.41)
VID 1.2 (tried multiple settings boost from stock to 1.3)

With those settings i can get it to post and load vista x64 but once i run Prime95 BOSD.

is there something im missing? i thought i bought a decent OC'ing MB/RAM/CPU

Should i be doing all this testing under vista? or should i move over to XP and test the system?

vista 64 is one of the biggest issues
you need to install windows x64 with 1 stick of ram
then do all the updates then stick in the other 2gb.

there is absolutely NO logical reason why anyone outside of a computer lab or 64bit programs need a 64bit OS. (crunches like it but that's their problem)

get back to adecent OS and do a FRESH install... XP doesnt care about 4 gigs of ram and neither does Vista 32bit,, but 64bit can have issues with 4gb of ram until you get it installed and do some updates.


i hate to say this but your cpu is choking.
you were at 3.4ghz and you were already at almost 1.4v
since you went to 400mhz you are going to need 1.5+v to get it to work.
kick the FSB back down to 333
set the vcore to auto just to see what it does.

the mobo is a great clocker but something isnt right here.

set all the voltages except vdimm to auto.
let vcore nb, sb FSB PLL. NB PLL etc etc etc all auto. just to test.

see what happens.

but vista 64 is a fools game my friend there is no reason in this world why you should be using it.

also make sure your running the latest bios.

Quote:

---

Originally Posted by Lestat

vista 64 is one of the biggest issues
you need to install windows x64 with 1 stick of ram
then do all the updates then stick in the other 2gb.

there is absolutely NO logical reason why anyone outside of a computer lab or 64bit programs need a 64bit OS. (crunches like it but that's their problem)

get back to adecent OS and do a FRESH install... XP doesnt care about 4 gigs of ram and neither does Vista 32bit,, but 64bit can have issues with 4gb of ram until you get it installed and do some updates.


i hate to say this but your cpu is choking.
you were at 3.4ghz and you were already at almost 1.4v
since you went to 400mhz you are going to need 1.5+v to get it to work.
kick the FSB back down to 333
set the vcore to auto just to see what it does.

the mobo is a great clocker but something isnt right here.

set all the voltages except vdimm to auto.
let vcore nb, sb FSB PLL. NB PLL etc etc etc all auto. just to test.

see what happens.

but vista 64 is a fools game my friend there is no reason in this world why you should be using it.

also make sure your running the latest bios.

---

currently i am at @335 everything else stock see screenshot
http://onlyalad.net/stuff/335x9_Q6600.jpg
i also ran Prime95 for 10 hours at these settings and had no problems

I run vista x64 for the 4gigs of ram. while this is my first vista experience i have not seen any problems related to speed but then again i have nothing to compare it to. as far as problems installing i had none it was quick and painless.

But if you think that vista x64 is my biggest problem i can go back to XP or Vista x32 (i kinda want to use Vista but it that is why im BOSD'ing then i dont mind going back to XP)

What do you mean by choking"? is this particular CPU a bad one?

Quote:

---

Originally Posted by on1yalad

Should i be doing all this testing under vista? or should i move over to XP and test the system?

---

use xp x64 to bench with and use the 64bit prime.
ftp://mersenne.org/gimps/p64v256.zip

and then go play with pista vista.

Quote:

---

Originally Posted by Lestat

vista 64 is one of the biggest issues
you need to install windows x64 with 1 stick of ram
then do all the updates then stick in the other 2gb.

get back to adecent OS and do a FRESH install... XP doesnt care about 4 gigs of ram and neither does Vista 32bit,, but 64bit can have issues with 4gb of ram until you get it installed and do some updates.

but vista 64 is a fools game my friend there is no reason in this world why you should be using it.

---

lol... you don't need to do all that with vista. if you grab vlite (vista's version of nlite) http://www.vlite.net/ you can slipstream sp1 into a vista disc( I've done it, but it takes a 120mins to do it) and install vista without having to pull any ram. I also used it to disable UAC out of the box.

Quote:

---

Originally Posted by safan80

use xp x64 to bench with and use the 64bit prime.
ftp://mersenne.org/gimps/p64v256.zip

and then go play with pista vista.




lol... you don't need to do all that with vista. if you grab vlite (vista's version of nlite) http://www.vlite.net/ you can slipstream sp1 into a vista disc( I've done it, but it takes a 120mins to do it) and install vista without having to pull any ram. I also used it to disable UAC out of the box.

---

why do i need to pull ram? it installed fine when i had both sticks in.

Quote:

---

Originally Posted by on1yalad

why do i need to pull ram? it installed fine when i had both sticks in.

---

I was refering to Lestat's statement. I've got no trouble in the past installing vista with 4GBs of ram, but some did.

Vista OC's fine... My abit in my sig was oc'ed on vista 64, and has been at 380x9 and 400x9 folding since oct in Vista 64...
I had no issues installing with 2x2gb...


I have 3 Q6600 G0's.
2 areas that catch my eye.

1. temps are too high... all 3 of mine like to be near 60c to be happy...

2. vcore is low. all 3 of mine need about 1.4v actual cpuz load vcore for 380x9, and 1.5v for 400x9....

IMO, you're gonna have to lower your oc expectation, or get a true120 with a fan on it and run it 100% under load. all mine are folders, so they run 100% 24/7.

Right now i'm running prime 380@9 1.360vcore...i upped the NB = 1.37 and the VTT = 1.235. before i really never messed with the VTT so that might have been my problem. (funny CPU-Z goes form 1.36 to 1.376 and even to 1.392 rarely)

Also since my Zalman is :banana::banana::banana::banana: i have to tun on all the fan max to stay at a 59-63 temps.

i didn't turn off either of the Speedstep options and im not seeing any issues so far...but who knows prim has only been up for ~1hour

UPDATE: BOSD after 3hrs...is there a reason why i get a BOSD rather than prime failing. it that a good indicator that there is not enough power going to one of the components?

Quote:

---

Originally Posted by on1yalad

UPDATE: BOSD after 3hrs...is there a reason why i get a BOSD rather than prime failing. it that a good indicator that there is not enough power going to one of the components?

---

bump the vcore up a notch and run it again... leave your fan on max, those temps are fine at 59-63c... you just need more vcore to stabilize it out. you're close if you're getting a 3 hr run... A bsod is just instability, same as any other instability error. just means you're not quite there. keep going up on vcore and run it again.. at 1.36v you're still a little low. compared to my 3. they range from 1.39-1.44, each chip is different.. but none of mine will do 380x9 long term 100% @ 1.36v... I've seen reports here of others that have chips that will, but don't assume you got lucky with a low vcore chip. I've bought 3 and the best one will do it at 1.39v constant, the worst at 1.44v...

oh, and turn off EIST and C1E, it's counter productive to have them on while stability testing...

since no one has really simplified this yet...

go back to basics and don't jack with anything except vcore and fsb.. isolate them to get a vcore/fsb stability.

1. turn off = C1E, EIST, Spread spectrum..
2. set your target fsb, in this case 380x9.
3. set your ram diver to run at or below stock settings, ram voltage and timings on auto.
4. leave all your other mobo voltages on default.
5. now just start going up on vcore one notch at a time until you can boot and pass occt or prime.

once you can pass overnight stress without bsod or error, THEN and only then go back and mess with ocing the ram, ram voltage, and timings.
you need to isolate your fsb and vcore first, without stability there, everything else is mute... that's where it looks like you're failing from the thread data.

Quote:

---

Originally Posted by MikeB12

since no one has really simplified this yet...

go back to basics and don't jack with anything except vcore and fsb.. isolate them to get a vcore/fsb stability.

1. turn off = C1E, EIST, Spread spectrum..
2. set your target fsb, in this case 380x9.
3. set your ram diver to run at or below stock settings, ram voltage and timings on auto.
4. leave all your other mobo voltages on default.
5. now just start going up on vcore one notch at a time until you can boot and pass occt or prime.

once you can pass overnight stress without bsod or error, THEN and only then go back and mess with ocing the ram, ram voltage, and timings.
you need to isolate your fsb and vcore first, without stability there, everything else is mute... that's where it looks like you're failing from the thread data.

---

1. Done
2. Done
3. Stock setting 5-5-5-15 @475 (under stock settings)
4. Done
5. Special add .150mv in cpu-z 1.392-1.404vcore (didn't do the vdroop mod)

My temps are pretty high when Prime uses a 8k FFT these guy's go to 67-69c fans are maxed and my room temp 68c

did that vcore increase enable you to pass stress?

yeah, those are high for my tastes... I like to stay around 60c...
you can drop the oc to 370x9 and see how low you can get the stable voltage, that'll remove a little heat for now, until the true120 gets there...

also, you made sure you got a good spread on the thermal paste?


you are within intels' specs at least http://processorfinder.intel.com/det...px?sSpec=SLACR , just a little too high for my comfort zone. (but mine stay on at 100% all the time folding, so I like a big cushion)... my fan has fallen off before and it folded all night long passive, when I caught it was at 75c for about 8 hrs and was fine, but thermal throttling at 50%... and I put the fan back on immediately.

those temps probably are about right for a 9700 cooler...
this is ocpulse's showdown at stock 2.4ghz...
notice the true is about 6c cooler...
http://www.ocpulse.com/hsf_showdown/load_avg_chart.png


anyway, you understand the basics now, so it's up to you to play around...
once the true gets installed, you'll have better temps... and if you're not going to fold or run full load all the time then it's probably fine like it is now, some here would say 68-70c is perfectly normal all the time. it's just my opinion that 55-62c is the safe temp I'm comfortable with. but you know what to do if you want to remove some heat until the true is installed, lower the oc and vcore...

then restress and adjust vcore until stable...

What do you mean good spread? i followed the directions i put a medium strip east-west in the middle of the chip, i did use a latex glove and my ringer to spread it out a bit so it would cover all the cores, is that good? (i don't plan on lapping either my HSF or the CPU, will i be okay?)

Also i ran prime last night and i work up this morning it was still going but right as i popped out of the shower BOSD and a reboot :( the voltages were 1.44 and i not comfortable going anything higher especially with a board where the only way i can control the vcore is by "special add" only. -i keep kicking my self fro not getting the LT.

i dropped the FBS to 360 with a 1.28+.125= sitting at 1.36-1.376 maybe ill have luck with this setup.

that's good. just asking to make sure you used paste... I've seen people not use it before...

good luck, you're on the right track.. just keep stressing and making small changes until it's stable and you're happy with temps..
you'll probably have more luck with 360 or 370... as said before chips are different, so you kinda have to play to find the sweet spots..

Yea, i really want to run 3.4 but if 3.2 is all i can get that is fine too.

One questions about Prime95...it seems that one core is slower than the others, is that due to me using the computer while prime is running? (surfing the web and what not)

Hopefully it will go through the rest of the night without a problem.../crosses fingers

so Im stable, although not sure if my vcore is too high...thoughts?

Screenshot:
http://onlyalad.net/stuff/3.2oc_17hr%20stable_15k.jpg
My setup waiting on wall mount
http://onlyalad.net/stuff/DSCN3678.JPG

wow, nice monitor...

temps look great... vcore may be fine, some chips need it, some don't.. the only way to know is lower it and restress overnight and see if it will pass...
once you find your min vcore allowable for a stable overnight run, then you can move on to stage 2 and change your ram divider and ram voltage and oc it if you want...

Thanks for all the help Mike!