E6750 & Gigabyte P35C-DS3R Overclocking Thread

[MaDMvD]

At first, I thought I had a really good E6750. I am able to run at stock speed using a little over 1.0v through BIOS. However, I've found that when trying to reach higher clocks, it seems to be very voltage hungry. When I was testing 3.6GHz-3.8GHz, it needed ~1.48v or so to even boot into Windows, at which point it would instantly blue screen upon heavy load. You guys reaching higher clocks without breaking 1.4v have obviously been blessed by the Intel Gods. I think I'm going to find the lowest stable voltage for 3.2GHz and work my way back up. It's just that there are so many variables to play with, you can easily get lost in what works and what doesn't. One thing is certain, though, my processor is hungry for voltage.

 

[Vipeax]

Do you get auto-reboots/freezes/BSODs on lower voltages?

 

[MaDMvD]

Originally posted by: Vipeax
Do you get auto-reboots/freezes/BSODs on lower voltages?

Yes, usually a BSOD saying "uncorrectable hardware error detected", or simply "your computer is being shutdown to prevent damage to your hardware".

 

[Vipeax]

Originally posted by: fausto412
nice video clip...i can't see myself taking my board out to do that lol.
stock voltage is 1.325 as far as a i know...cpu-z shows 1.31 in the video. if it's orthos and prime stable at that voltage for 5+ hours each then your cpu should do 3.8 easy man. mine does 3.6ghz at 1.36 volts...mine is good, yours is bad ass

As more people requested some info on the mounting:
http://forums.anandtech.com/me...=2128999&enterthread=y

 

[mrfatboy]

Has anybody played around with the memory sub timings on this board? if so, was it worth it? What did it do?

 

[MaDMvD]

Ok, for anyone interested:

I spent a majority of the day seeing the minimum amount of voltage per 200MHz step. I only did 3.2GHz - 3.6GHz, but at least now I know what works and what doesn't - it's just a matter of me accepting the voltages.

3.2GHz - 1.3375v in BIOS
3.4GHz - 1.41875v in BIOS
3.6GHz - 1.5v in BIOS

Yes, I know many of you are at home saying "hahahaha, poor bastard". Well, shit, this is my first experience with overclocking and although it is not great, it's definitely enough for me to say I have learned a great bit more in computer science and that I've found my new fascination. For those of you who also have a seemingly voltage-hungry chip, I feel you. I'm probably going to stick with 3.2GHz and call it a day. The next thing I'm going to focus on is the RAM overclock.

@mrfatboy: Speaking of which, I did some playing around with the memory subtimings and I found the only value I've been able to change and retain stability is "Refresh to ACT Delay". I changed it from 42 to 35 and saw some improvement in Everest's RAM benchmark (latency, specifically). It dropped it from ~56.2ns to ~52.4ns at 42 and 35, respectfully.

I hope someone gets something useful out of this reply.

 

[VirtualLarry]

RAM errors are BAD. You should definately straighten that out. You may need to increase vdimm, or loosen your memory timings. Try 5-5-5-18, and 2.0v, to start with. Also set your RAM multiplier to 2.0.

 

[MaDMvD]

My RAM settings are in the sig - perfectly stable.

 

[Vipeax]

I found out why my memory gove an error with memtest, I was using the wrong version. PC6400/800MHz @ 1200 with 5-5-5-12 9 hours and 57 minutes stable.

 

[bajto219]

hi there
im new to this forum and i just have a quick question

is it normal that i reached 3.5Ghz without increasing the core and everything runs perfectly

here is my cpu z

http://imageshack.us]

[/URL]


thanks

 

[MaDMvD]

Originally posted by: bajto219
hi there
im new to this forum and i just have a quick question

is it normal that i reached 3.5Ghz without increasing the core and everything runs perfectly

here is my cpu z

http://imageshack.us]

[/URL]


thanks

The screenshot doesn't say much, but yes, it's relatively normal. I might as well ask - is it Orthos stable? If so, for how long?

 

[mrfatboy]

Originally posted by: bajto219
hi there
im new to this forum and i just have a quick question

is it normal that i reached 3.5Ghz without increasing the core and everything runs perfectly

here is my cpu z

http://imageshack.us]

[/URL]


thanks

i personally think you are one of the luckier ones than "normal"

 

[bajto219]

thanks fot the reply

i`ll try it now and let you know

 

[j0j081]

Is this board any good or only the C version?

http://www.newegg.com/product/...p?item=N82E16813128050

 

[bajto219]

i run at 3.5 it failed

pu the frequency to 3.4 it`s been runnin for 1 and half hours fine with a cpu temp @ 52

so i guess there is no need to increase the voltage

thanks

here are my spec

E6750 @ 3.4 stock voltage | Gigabyte P35C DS3R -F7 Bios |
2 X 1GB Corsair XMS DDR2 800@852 4-4-4-15 @ 2.13v (1:1)
HIS 3870 512 (803/1206) 7.11 |

 

[mrfatboy]

Originally posted by: bajto219
i run at 3.5 it failed

pu the frequency to 3.4 it`s been runnin for 1 and half hours fine with a cpu temp @ 52

so i guess there is no need to increase the voltage

thanks

here are my spec

E6750 @ 3.4 stock voltage | Gigabyte P35C DS3R -F7 Bios |
2 X 1GB Corsair XMS DDR2 800@852 4-4-4-15 @ 2.13v (1:1)
HIS 3870 512 (803/1206) 7.11 |

Now you seem normal

 

[MaDMvD]

Sounds like a decent overclock, but why 4-4-4-15? With XMS RAM, you should be able to do 4-4-4-12 easily, or even 4-4-4-10.

 

[bajto219]

here are the screenshot

http://img111.imageshack.us/img111/5236/arthosty3.jpg

 

[bajto219]

gonna try 4-4-4-12

 

[bajto219]

works fine at 4-4-4-12
gonna keep these settings and im quite happy with 3.4Ghz without increasing the voltage

thanks for you help guys


-------------------------
E6750 @ 3.4 stock voltage | Gigabyte P35C DS3R -F7 Bios |
2 X 1GB Corsair XMS DDR2 800@852 4-4-4-12 @ 2.13v (1:1)
HIS 3870 512 (803/1206) 7.11

 

[j0j081]

Originally posted by: j0j081
Is this board any good or only the C version?

http://www.newegg.com/product/...p?item=N82E16813128050

bump.

 

[JasperJ]

I just startedoverclocking on my DSR3 (using an E2160 until Penryn arrive) and a question on memory settings.

I was having random errors in Orthos until I made the memory settings manual and set to 5 /5 /5 /15 and the multiplier 2.0. However Refresh to ACT Delay showed 52 0 and there was no auto value. I changed it to 52 and since it's been stable (along with the other changes).

Looking through the thread I noticed that MrFatBoy has Refresh to ACT Delay set at 42 and ConjugalVisit has it set to 0. ???

Is this even something to care about?

 

[Conjugal Visit]

@JasperJ - I'm a little red-faced...I had mine set to 0 because of a combination of things. There was an overclocking guide at HardOCP that showed Refresh to ACT at 0. The bios seems to default to 0. Googling turns up almost nothing on the subject. I believe the motherboard manual lists 0 as well. Anyway, I've changed it to 42, which would be the SPD values - however these values correspond to looser timings. Haven't noticed a difference in stability one way or the other.

Regards,

 

[MaDMvD]

Originally posted by: JasperJ
I just startedoverclocking on my DSR3 (using an E2160 until Penryn arrive) and a question on memory settings.

I was having random errors in Orthos until I made the memory settings manual and set to 5 /5 /5 /15 and the multiplier 2.0. However Refresh to ACT Delay showed 52 0 and there was no auto value. I changed it to 52 and since it's been stable (along with the other changes).

Looking through the thread I noticed that MrFatBoy has Refresh to ACT Delay set at 42 and ConjugalVisit has it set to 0. ???

Is this even something to care about?

I would try 42, test its' stability, and move down from there. I was able to bring it down to 35 and remain stable. It also (arguably) has performance benefits to lower it...

 

[Conjugal Visit]

Originally posted by: MaDMvD

Originally posted by: JasperJ
I just startedoverclocking on my DSR3 (using an E2160 until Penryn arrive) and a question on memory settings.

I was having random errors in Orthos until I made the memory settings manual and set to 5 /5 /5 /15 and the multiplier 2.0. However Refresh to ACT Delay showed 52 0 and there was no auto value. I changed it to 52 and since it's been stable (along with the other changes).

Looking through the thread I noticed that MrFatBoy has Refresh to ACT Delay set at 42 and ConjugalVisit has it set to 0. ???

Is this even something to care about?

I would try 42, test its' stability, and move down from there. I was able to bring it down to 35 and remain stable. It also (arguably) has performance benefits to lower it...

Bizarre, tho - I'd had it set to 0 since I installed the board and manually set Ram options. I've memtested and Orthos'd more times than I can count. Never had any instability at all at 0. That's puzzling.