OEM E6600 + P5W DH Initial results (alittle help needed)(GREAT NEWS!!!)

[Ldawg]

arlight guys, specs are in the sig. right now im priming at 3.0Ghz...

cooling: scythe mine W/ silverstone fan = 70-80 cfm

FSB: 333 Mhz x4 = 1333mhz
Mem: 1:1 333mhz 5-6-6-18 (loose for now) x2 = 666mhz
vMCH: 1.6
vCore: 1.465 in bios
hyperpath 3: disabled
pci-e freq: 105
pci freq: 33.33

been priming for 20 min so far. had problem with sp2004 orthos erroring out with same settings except 1.45 vcore... havent figured out why since 1.45 seems high for only 3000mhz...

are there any major settings in the bios other than the ones i mentioned that i should be looking at?

as far as temp goes... core temp shows 58c after 20 min of sp2004, speedfan shows 41c... which should be trusted?

vCore... cpu-z shows vcore at 1.440 mostly, sometimes it drops down to 1.213!!!!! please tell me this is a glitch and vdroop isnt really THIS bad... also speedfan and pcprobe show vcore at a constant 1.44-1.45...

should i be adjusting any of the other voltages? vfsb? vICH?

[AndrewZorn]

orthos gives errors, prime does not?

youre using DUAL primes, right?
ive been using orthos lately, it could all be in my head, but it seems to give errors eratically.

if your vdroop was really THAT bad, itd be nowhere near stable at speeds that require the 1.45v you se it to...

[Ldawg]

i worded myself wrong, i used orthos both times... yea its running in "dual" mode which is what orthos does by default i assume.

so your saying if my vdroop was THAT bad i wouldnt be able to "orthse" for as long as ive been "orthosing"(lol)... AKA its a glitch, right?

[AndrewZorn]

ah ok

but what i meant is
well let me give an extreme example

i set it to 1.5v in BIOS
during orthos i see it drop to .6v
and it doesnt stop instantly
instead it just keeps going
and returns to 1.5vish soon after
obviously misreading
and if its not, then well, its still stable, so awesome

if you start seeing the megadroop and orthos failures colliding, then id start worrying. but either the low voltage is [somehow] still stable, or more likely, its not drooping near as much as it reports

[Ldawg]

ty very much for clearing that one up! now just gotta figure the rest out...

as5 hasnt really settled in, from my experience it takes 2 or 3 days of burn-in and ill see a slight temp drop...is this correct?

[AndrewZorn]

thats what everyone says, but ive never experienced it settling
or even hardening over time (more like a curse than feature, but everyone SAYS it happens...)

[Ldawg]

your the man. any input on my other questions? :)

[bobov]

FSB: 333 Mhz x4 = 1333mhz
Mem: 1:1 333mhz 5-6-6-18 (loose for now) x2 = 666mhz
vMCH: 1.6
vCore: 1.465 in bios
hyperpath 3: disabled
pci-e freq: 105
pci freq: 33.33



Do you really need 1.465v vCore to stable @ 3.0GHz? Seems too high for only 3.0G.

[Ldawg]

yea, seems high to me also. but orthos will error out with anything less than that after 30 min... with the settings above. theres gotta be something im missing and thats what im trying to find out.

i know its a lot to ask but if someone whose got similar (if not identical) hardware priming at much higher, could you take pictures of major bios screens? ie. jumperfree, chipset, and some of the others...

[Kantana]

yea, seems high to me also. but orthos will error out with anything less than that after 30 min... with the settings above. theres gotta be something im missing and thats what im trying to find out.

i know its a lot to ask but if someone whose got similar (if not identical) hardware priming at much higher, could you take pictures of major bios screens? ie. jumperfree, chipset, and some of the others...

Here's my E6600 on same motherboard and settings/temps, Assume all else is default unless stated otherwise etc:

Intel E6600 retail steping 6 B2
Corsair Cool water cooling
P5W DH bios 0903

FSB 400
Memory 800
Timing 5-5-5-12-5
Vmem 1.9 v
Vcore 1.5375 v
Vmch 1.6 v
Vich Auto
Vfsb Auto

Temp ambient 26 degrees c
Temp idle 41 degrees c
Temp load 60 degrees c

[bobov]

You may check http://www.xtremesystems.org/forums/showthread.php?t=110231

[Ldawg]

thanks for the responses guys!

@kantana - i tried those settings earlier when i first saw your thread. this baby wouldnt post. i had to clear cmos to get it to post. only difference i see is the bios version. myabe ill try updating to 0903... im currently on 0801.

@bobov - thanks for the link man! im gonna start reading through their while this baby is still priming.


...im thinkin maybe it needs a little burn in to really get going. i think im just gonna leave it overnight and assuming it passes ill increase fsb tomorrow and see what kind of results i get!

[Kantana]

thanks for the responses guys!

@kantana - i tried those settings earlier when i first saw your thread. this baby wouldnt post. i had to clear cmos to get it to post. only difference i see is the bios version. myabe ill try updating to 0903... im currently on 0801.

@bobov - thanks for the link man! im gonna start reading through their while this baby is still priming.


...im thinkin maybe it needs a little burn in to really get going. i think im just gonna leave it overnight and assuming it passes ill increase fsb tomorrow and see what kind of results i get!

I think we are seeing a wide variance on the quality (overclockability) of these retail step 6 conroes. The benchmarks set by the step 5 (ES) chips were really high compared to all the retails. I was disappointed by my E6600 compared to the ES samples which I believ may have been cherry picked by Intel for reviewers.
I have a E6400 (2Mb cache, 7x multiplier) chip that was stable at 438 FSB for 3.5G, I bought the E6600 as I wanted the larger cache and believed I would also be able to run 438 FSB stable. Due to the large variations in the quality of each chip sold at retail I no longer believe that a higher model chip will overclock better than a lower model one.
My E6600 is at the limits of performance given the Vcore/Temp. As an example it will fail dual prime after 50-60 mins if the Vcore is lowered to 1.525v
Your E6600 may have issues due to insufficient cooling as the core temps you posted before are bordering on critical. If the ambient temp goes upto 28 degrees c then my setup will also fail dual prime at 1.5375 Vcore. I am currently working on better cooling, will try to remount the water cooling on my cpu.
Try using a better heatsink/reapply the AS5. The conroe seems to perform best below 72 degrees c core temps, above that they tend to lose stability.

[Mikesta]

Disappointing to hear about the E6600's.

It's kinda funny that when the AMD fanboys and also objective members suggested that Intel where sending out Cherry Picked ES's and that retail might not be as good, the Intel fanboys heckled them.

It looks like Conroe isn't quite as good as we were led to believe, OC wise anyway. Conroe performance is still undeniable and even a dual core at only 3.0ghz is great.

[Ldawg]

even tho im a tad disappointed i have no doubt this chip has some more left in it. i feel like i ill be able to get it to 3.2-3.3... ill be lapping the cpu and hsf tomorrow and turn the AC on a bit stronger, i have a rather high ambient temp (75 F).

ill be honest a 3.0 ghz conroe is way more processing power than i need, i was hoping to get 3.6 for bragging rights :)

[Xefier]

Good luck Ldawg, keep us posted, im curious how far you can get it :)

[fornowagain]

After a bit of fiddling about I get, ambient 20C or so.

Prime 3.5Ghz@1.45v 43C from ProbeII

Prime 3.6Ghz@1.55v 50C from ProbeII, Tuniq starting to get kinda warm.

Pi 1M 3.7@1.55v it needs a bit more juice for prime but it benches ok. Dont fancy going to 1.6v on air.

There does seem to be some variability in E6600 results, but is it the chips or boards? Mine came with really crap TIM contact on the chipset, putting on some AS5 and fans made a lot of difference to clocks.

[Ldawg]

alright guys, heres the plan for this week...

i decided to let the machine burn-in overnigth last night at stock settings with memory @ DDR2-800. letting it settle down and maybe it needs to be warmed up before i can really push it...max temp after 8 hours of orthos was 47-48c in a closed case with all fans turned down quite a bit...

i will be lapping the cpu today, so that should be an extra few degrees as well...

im inclined to think that it is some sort of setting that is holding me back...i was priming for 4 hours at 333fsb, 3000mhz with 1.45 in bios (which seems high anyway) but no matter what voltages i tried, loose memory timings i could not get prime to last more than ~3 sec at 3100 mhz... i doubt my chip is at its limit at 3000mhz...

well, i guess we'll see after the lapping...

and just incase it is at its limits, i have another oem e6600 coming in tomorrow from clubit... so ill have mnay variables to test...

[Ldawg]

just purchased all the things i need for lapping, at around 5pm EST (in 4 hours) ill lap my cpu and heatsink... lots of pictures coming

[Xefier]

Just out of curiousity does anyone have any links to a good CPU lapping guide?

[Ldawg]

heres the one im following, looks excellent to me.

http://forum.overclock3d.net/showthread.php?t=4735

btw, i purchased the sandpaper at autozone, they had up to 2000 grit. the piece of glass was purchased at a hardware store...

[Ace-a-Rue]

I think we are seeing a wide variance on the quality (overclockability) of these retail step 6 conroes. The benchmarks set by the step 5 (ES) chips were really high compared to all the retails. I was disappointed by my E6600 compared to the ES samples which I believ may have been cherry picked by Intel for reviewers.


my take on the retail chips not having good overhead is that intel had to come out with B2 stepping to correct for the Raid 5 issues of cpu utilization...i would bet that has taken some of the overhead away!

[theteamaqua]

I think we are seeing a wide variance on the quality (overclockability) of these retail step 6 conroes. The benchmarks set by the step 5 (ES) chips were really high compared to all the retails. I was disappointed by my E6600 compared to the ES samples which I believ may have been cherry picked by Intel for reviewers.
.......

bingo ...
reason on my sig

intel release ES5 that are extremely overclockable to fool us consumers. the highest E6600 i have seen was andreyang's E6600 ES5, it was like 3.8 , 3.9GHz dual prime stable for 30 min on air tower 120

but do know that clock for clock, i am pretty sure that ES5 are the same as retail , but for overclocking, no ES5 > retail....

[Mr.X]

Good luck Ldawg! Hope you can reach at least 3.4Ghz prime stable.
Nice setup btw! :)

[Ldawg]

Good luck Ldawg! Hope you can reach at least 3.4Ghz prime stable.
Nice setup btw! :)

ty sir!

this build im taking the time to do everything right the first time around. usually im in such haste to get a system up and running but this time its all about the patience...:D

[Ldawg]

anybody think disabling virtualization might help pass this wall im hitting at 340?

[Mako88]

Ouch. Makes my 3.6 6400 and 3.75 6700 seem like cherries...these 4mb conroes are a whole different ballgame it seems, just that much more difficult to get a good one I guess.

[xpsentity]

I've seen it set as disabled on many 'settings lists' posted around here.

[Ldawg]

hmm, that could be it... what does it actually do? anything useful?

[Ldawg]

alright guys, just finished lapping and wanted to share some pics... havent gotten around to do the scythe mine, dont think i really need to to be honest...

well, here enjoy!

ps. - im going to try and disable virtualization and see if that helps anything... anybody know if it affects performance in any way?


http://i49.photobucket.com/albums/f263/nytrackstar/IMG_1894.jpg
http://i49.photobucket.com/albums/f263/nytrackstar/IMG_1902.jpg
http://i49.photobucket.com/albums/f263/nytrackstar/IMG_1906.jpg
http://i49.photobucket.com/albums/f263/nytrackstar/IMG_1914.jpg
http://i49.photobucket.com/albums/f263/nytrackstar/IMG_1918.jpg

[AndrewZorn]

i want to lap mine when i get it SO bad. but resale and warranty are gone when you do that.

[Ldawg]

ive been thinking, can it be that im running a RAID-0 as my os disk that my OCing is very limited??

[xpsentity]

ive been thinking, can it be that im running a RAID-0 as my os disk that my OCing is very limited??

I HIGHLY doubt it, a large number of people here run raid 0.

[syne_24]

ive been thinking, can it be that im running a RAID-0 as my os disk that my OCing is very limited??

That's interesting posibility. Is there a retail e6600 out there NOT running raid on P5W?

[xpsentity]

Tomorrow morning I will have my 6600 retail on P5W, no raid. Will report back.

They did do that whole Raid fix thing.. but I think that was for Raid 5 stuff only. Suppose something could have been borked just a bit, and thrown it off just enough.

Was the fix just for 4mb Cache models?

^^ Because it seems the 4m Cache models are the "meh" clockers atm.

[Ldawg]

well ive pretty much come to the conclusion that i am in posession of a dud...

the closest ive come to being remotely stable is where im at now...

fsb = 333
mem = 1:1 5-6-6-18
vcore = 1.465 in bios
basically the same settings as orignial post... its been "orthosing" for 45 min...

its wont even orthos at these temps at 1.45 vcore, so im assuming its the chip...

i have another e6600 coming in tomorrow, ill give that one a go... if that one works out better, ill sell this one really cheap...

[xpsentity]

Sucks =/

Your major stuff, (chip, mobo, gfx) is same as mine. If I can get a good OC I'll post/pm camera shots of the related bios sections.

Locked PCI @ 33.3?
Locked PCI-E @ 100/101?
Hyperpath Disabled?
All EIST and Thermal Throttling Disabled?
Ram thermal throttling disabled?
Correct ram voltages?

Should be stock NB/SB voltages @ those speeds also.

What is failing on the Orthos/SP runs? Run a CPU stress and a RAM stress seperately. Which fails?

Have you run Memtest for a few loops at stock settings? (read: 4+ hours)

Disable USB stuff, try without raid.. etc. I could go on. Disconnect all un-needed hardware (External drives, usb hubs, front usb port stuff). Etc, etc, etc, etc.

Don't give up, plenty of things left. It could be one stupid, small setting somewhere. Change one thing at a time and test, only combine things that make sense to combine at the same time.

Don't change too much at once, it will make it hard to nail down the problem. It could also create new problems, disabling one thing and enabling another could create a conflict somwhere.

Start as simple as possible with the OC and move from there. Hope this helps.

Edit: ALSO!

If your second 6600 exhibits the same behavior, don't depair. It could still be settings in the Bios. We need more reviews and testing of the retail 6600's before any "omg suck" conclusions can be drawn. Someone might nail something down in the coming weeks that is borking the OC's. Do try it without raid, something about the fix seems too coincidental to me. It's the only major change (I know of) between the ES and retail, provided the ES's weren't hand picked.

[Ldawg]

wow, i really appreciate the help man...im gonna go ahead and do all the things u mentioned... orthos has been goin for 2 hours now, temp is sitting right at 60c, case closed and fans on med/low (which is how itll be used most of the time)... temp is measured via core temp, speedfan says the temp is 43c...

[xpsentity]

wow, i really appreciate the help man...im gonna go ahead and do all the things u mentioned... orthos has been goin for 2 hours now, temp is sitting right at 60c, case closed and fans on med/low (which is how itll be used most of the time)... temp is measured via core temp, speedfan says the temp is 43c...

Oh! Disable the temp monitoring in Orthos. If you get a big spike when you first start (Which you should), it can bomb.

The logic is, a huge spike/delta/whatever, can mean a hardware failure of the worst kind, so Orthos/SP/Whatever immidiately backs off loading the cores and calls it to your attention. This, IMO, is exactly what it should do (to a point), to prevent you from having a magic smoke moment.

So head to an overclock barely over your current voltage, something you KNOW will fail in 3-5 seconds on Orthos/SP, and try it.

^^ The above is total heresay / secondhand. Someone please correct me if I am wrong and I will edit my post.

Also, I've had dual instances of Prime pass fine while Orthos totally failed at 3 seconds, every time. Provided you don't do anything in which a data loss would be totally catastrophic(In which case you should not be OC'ing anyway) - an overclock that is otherwise stable besides Prime/whatever can work just fine. Sure it's not "24h Prime WIN!" stable, but it can be plenty stable for daily usage.

You personally are the end all stability test. If it works for you day in and day out, it's your choice.

[Ldawg]

well, i just recieved the OEM E6600 from clubit and they more than made up for there incompetence!

they sent me the full version of GRAW with cd key and all and a 10pk of DVD-R's...very cool :)

[Ldawg]

alright heres the deal for later tonite:

ill be home earlier today (5pm) - so ill have 8 or so hours to work on this issue.

things il be doing:
1. replacing the mine with my ultra-120.
2. test without raid
3. update the bios from 0801 to 0903
4. try the second E6600
5. reinstall windows, i think my temps might be flaky to a degree because bios and pc-probe show the cpu idling at like 28-29c which seems too low to me...

we'll see how it plays out...

[Ldawg]

GREAT NEWS!!!!!


i put the new E6600 in and with everything default except vcore at 1.4, im orthosing at 350 FSB!!!


looks like the other chip was simply a dud!!! woohooo

thanks to everyone that gave some input!
...special thanks to xpsentity for all the IM's and advice and everything!! you inspire me!

[Ldawg]

ill be selling the old one for $250, its lapped so no warranty. good chance to get in on a cheap e6600 if your not oc'ing...

[davefr]

GREAT NEWS!!!!!


i put the new E6600 in and with everything default except vcore at 1.4, im orthosing at 350 FSB!!!


looks like the other chip was simply a dud!!! woohooo

Congrats, please post the date code on the one that only did 333 and the new one that does 350.

[BlazingArrow]

Please try to get to 400 FSB....i wanted a E6600 but would only get it if I could achieve this level of overclock

[Ldawg]

the one that did 333 at 1.465vcore was a week 25 chip, ill dig thru the pics to get the exact number, and the one that is doin well so far is a week 24

[Ldawg]

i will find out if this baby can do 400 by tonite, just goin little by little.

...i wanna know if itll do 400 as bad as you do ;)

[bobov]

GREAT NEWS!!!!!


i put the new E6600 in and with everything default except vcore at 1.4, im orthosing at 350 FSB!!!


looks like the other chip was simply a dud!!! woohooo

thanks to everyone that gave some input!
...special thanks to xpsentity for all the IM's and advice and everything!! you inspire me!

Congrats!

350X9=3.15GHz @ 1.4v, maybe you could lower vcore a little bit.

[Ldawg]

i probably could, but instead of lowering vcore im going to raise fsb by 10-15 every hour of orthos and see how far itll take it

[xpsentity]

Grats man. Mine is also a week 24, it's at 380FSB, 1.45V Bios. It was/is windows, game stable at 1.40V, bumped to 1.45 for Prime stability.

Once you get to 360~ you'll most likely hit a nasty spot of craptastic no post. Enable SPD and it should work fine. Quite a few people are needing to do this.

I'm hoping it's an issue that can be addressed in a Bios update :(

The amount of voltage needed to go from 3.2<-->3.4 is just wierd IMO, but I need a lot more testing ;)

It's odd, I went from 1.4-1.45, it doesn't feel right that it needs THAT much for Prime/SP stability.

Also, Ldawg - Try dual Sp2004, or dual Prime95 instead of Orthos if it's erroring. Orthos kills on me, but dual SP is fine.

[xpsentity]

Please try to get to 400 FSB....i wanted a E6600 but would only get it if I could achieve this level of overclock

Have you noticed the dividers on P5W being totally jacked up (besides 1:1, ofc). I've been seeing quite a few people saying so, I've also experienced it.

Did you need to enable SPD over 360~ FSB for boot?

If not 1:1, what are you running?

I'm@ stock voltages on everything except CPU @ 380 - you?

Sorry for all the questions, I'm really trying to absorb as many people's settings at high(er) FSB on the P5W to see if I can't come up with some reasoning and fixes for the boards wierdness.

[Ldawg]

alright heres what ive done and where im at now:

Cooling: Ultra-120 w/ Silverstone FM121 @ 12v (110cm+)
-highest load temp after 1 hr is 57c via CoreTemp, speed fan reads 42C...


1. 350x9 = 3150 @ 1.4v - orthos 1 hour(manually stopped), every other voltage @ stock

2. 360x9 = 3240 @ 1.435 - orthos 1 hour (manually stopped, every other voltage @ stock

3. 370x9 = 3330 @ 1.465 - failed orthos at 54 minutes, every other voltage @ stock


More info:

1. as far as mem goes, left it at "auto" in jumperfree area, and "set by spd" in chipset area. i will start playin with ram settings tonite.

2. i havent touched any other voltages other than vcore, so increasing some other might stabilize me at lower vCore...

3. other settings im using:
-hyperpath 3: disabled
-PCI-e @ 100 mhz
-PCI @ 33.33 mhz
-everything else is auto

4. im also running RAID-0 with 2x 150GB Raptors


...tonite i will try and get 370x9 stable for 2 hours or so, ill post back, i dont really wanna go over ~1.5vCore because this is all being housed in a Lian-li s80 with fans turned down, so airflow wont be "optimal"

@xpsentity

what vcore are you running thru the proc for 380x9? how stable is it? orthos time before fail? im lookin for at least 8-12hr orhtos stable oc :)

[Shrekogre]

where did u get your oem cpu?

[Ldawg]

clubit.com

[Brahmzy]

alright heres what ive done and where im at now:

Cooling: Ultra-120 w/ Silverstone FM121 @ 12v (110cm+)
-highest load temp after 1 hr is 57c via CoreTemp, speed fan reads 42C...


1. 350x9 = 3150 @ 1.4v - orthos 1 hour(manually stopped), every other voltage @ stock

2. 360x9 = 3240 @ 1.435 - orthos 1 hour (manually stopped, every other voltage @ stock

3. 370x9 = 3330 @ 1.465 - failed orthos at 54 minutes, every other voltage @ stock


More info:

1. as far as mem goes, left it at "auto" in jumperfree area, and "set by spd" in chipset area. i will start playin with ram settings tonite.

2. i havent touched any other voltages other than vcore, so increasing some other might stabilize me at lower vCore...

3. other settings im using:
-hyperpath 3: disabled
-PCI-e @ 100 mhz
-PCI @ 33.33 mhz
-everything else is auto

4. im also running RAID-0 with 2x 150GB Raptors


...tonite i will try and get 370x9 stable for 2 hours or so, ill post back, i dont really wanna go over ~1.5vCore because this is all being housed in a Lian-li s80 with fans turned down, so airflow wont be "optimal"

@xpsentity

what vcore are you running thru the proc for 380x9? how stable is it? orthos time before fail? im lookin for at least 8-12hr orhtos stable oc :)

Great info - thanks. I just ordered a P5W DH for my E6600 because my DS3 blew up.

What BIOS version are you running?

[alpha0ne]

Try using this form to list settings that will help ppl troubleshoot :)

ASUS P5WDH Dlx Overclock Settings

CPU :
DDR2 :
Bios :
VGA :
HDD :
PSU :
OS :
OVERCLOCK (MHz) =

BIOS SETTINGS

JumperFree Configuration

AI Overclocking set to MANUAL

CPU Frequency :
DRAMM Frequency :

Performance Mode :
PCI Express Frequency :
PCI Clock Sync Mode :

Memory Voltage :
CPU Vcore Voltage :
FSB Termination V :
MCH Chipset V :
ICH Chipset V :
--------------------------------------------------------

CPU Configuration

Microcode Update :
Max CPUID Value Limit :
Execute Disable Function :
CPU Internal Thermal Control :
Virtualization Technology :
Intel SpeedStep Technology :
--------------------------------------------------------

Advanced Chipset Settings (DDR2)

Configure DRAM Timing By SPD : Set to MANUAL
DRAM CAS Latency :
DRAM RAS Precharge :
DRAM RAS To CAS Delay :
DRAM RAS Activate to Precharge Delay :
DRAM Write Recovery Time :

Hyper Path 3 :
DRAM Throttling :

[conarth]

2. 360x9 = 3240 @ 1.435 - orthos 1 hour (manually stopped, every other voltage @ stock

Nice. I need 1.5 just to do this.

[Ldawg]

@ alphaone, im at work now, but when i get home ill fill that chart in for each stage of my OC.

@ brahmzy, im using bios 0801...i probably wont be updating to latest since i see no issues with this one... "dont fix something if it aint broke..."

advice for you is this, i would call asus and have them send you a bios chip with the latest revision on it, have it sent before your mobo arrives. when you get your mobo just pop it in and resent cmos... this way you dont have to deal with any bad flashes and you will have a spare bios chip incase anything happens...


...Conarth, WELCOME TO XS! :)

[Brahmzy]

@ alphaone, im at work now, but when i get home ill fill that chart in for each stage of my OC.

@ brahmzy, im using bios 0801...i probably wont be updating to latest since i see no issues with this one... "dont fix something if it aint broke..."

advice for you is this, i would call asus and have them send you a bios chip with the latest revision on it, have it sent before your mobo arrives. when you get your mobo just pop it in and resent cmos... this way you dont have to deal with any bad flashes and you will have a spare bios chip incase anything happens...


...Conarth, WELCOME TO XS! :)

Tahnks for the tip - I'll call 'em at lunch.

[Ldawg]

remember to make them send it for free, because the board is suppose to support c2d and all... a little pressure and they'll crack

[Ldawg]

alright guys, right now im priming at 370x9 @ 1.485vcore

mem @ spd, 1:1
vMCH @ 1.6 (dont even think this is needed)
all other voltages default

max temp so far is 57c via coretemp... ill stop it after an hour or so

[Ldawg]

aright above setting dual sp2004 for 2 hours, manually stopped.

kickin it up to 380 now same settings... failed after 2 seconds

...raising vcore to 1.5

[Ldawg]

well, i just finished a 3 hr sp2004 session at 380x9 @ 1.525vCore, proc got a bit too hot for my test...

i think ill be settling at 370x9 @ 1.475vCore 3330mhz... seems to offer the best performance per temp/quietness...not its time to tweak the memory a bit and prime her overnight

[xpsentity]

Good luck with mem timings.. I've spent the last 4 hours trying to get it off SPD setting @ 380.