I have just started overclocking. I have read the guides and post and jumped in and found a good OC. (I think)
E6850 @ 3.51 (390x9) 1.3625 vcore, temps 34c/55c
AC Freezer 7 Pro
8 GB (4x2) g skils DDR6400 @ 936mhz 2.1v 4-4-4-12
PNY 9800 GT 1 GB DDR3 675/975/1575 temps 48c/76c (crysis high 2x AA (1920x1080)
I love this system. I built it about 2 years ago, but was wanting to get some more out of it. I have definitely noticed a jump in performance. Boots slightly faster, renders quicker. I can't quite afford a quad core just yet, but I've got my good eye on the Q9550. But unless Santa hits the lottery, it will still be after the first of the year before I get one. My main question is Vcore. I know the specs say I can go up to 1.5, but geez that seems like alot. I have seen screen shots of 1,44 and such, but it's not my aim to run this 'til it drops. I would like a couple more years out of it. So if any of you more experienced guys could reassure me, or mock me, I would appreciate it.
I've had an older rig for family (E6600 @ 3.5Ghz on GIGABYTE GA-P35-DSL) at around similar vcore maybe even tad higher for 24/7 stable and it's been solid for round two years now .
That's a pretty good overclock for your voltage , just a thought though you've obv stressed your system with rendering software etc have you tried a couple hours running Orthos or the like on small fft's? Tiz just to make sure you don't get surprised with blue screen occasionally.
Also with your low temps you could push for more and after seeing a quick review of your mobo it can reach a FSB of 540 with minor NB voltage increases, though your 8GB of ram may hold you back a tad 3.6-3.8 is there to be reached . As long as your cooling can keep up with the voltage increase taking her up to 1.5v isn't going to hurt, though i'd personally go to 1.45 if i were to keep the CPU for another couple of years.
Thanks for the reassurance closed_deal. I have run prime 95 small fft for about 8 hrs while I was sleeping with no errors. I thought I could get more out of it, but I'm new at this and I would crylke a baby, if I broke it. Maybe after I get a quad for the MB I will push this one to it's limit.
No problems fella, but no need for crying lol. You've probably already encountered the BSOD screen on a failed overclock so don't be afraid to push the limits and then back it down a few Mhz. Honestly as long as you don't over volt the mobo or RAM and stick with your cpu's cooling restraints you won't damage her .
Just keep on tinkering, you've gone past the first barrier of physically overclocking now get some practice in and play with your RAM timings etc.. when you see the BSOD screen think of it as challenge to overcome not 'oh feck i've broken something' .
The E6850 is a G0 processor, just as the Q6600 G0 is a pair of E6850's. Both are excellent 65 nanometer overclockers. VID is a good indication of overclock potential, which can be seen in CPU-Z or Real Temp. The G0 processors range from 1.200 to 1.325. A lower value is better. Since the E6850 has a 9x multiplier, it's natural sweet spot is 3.6 Ghz @ 9 x 400.
You haven't mentioned if your Vcore is BIOS, or load from CPU-Z, however, you'll typically need 50 millivolts per 100 Mhz. You can expect your CPU temperature and Core temperatures to increase ~ 4c per 50 millivolts. Since you're stable at 3.5 Ghz with 1.3625 Vcore, then it's likely that your processor will also be stable at 3.6 Ghz with 1.4125 Vcore. It's also likely that it would top out at 3.8 Ghz with 1.5125 Vcore. Regardless, you can safely run 3.6 Ghz, which would allow you to run the memory at 800 Mhz with less voltage. Another option is 3.6 Ghz @ 8 x 450.
thanx for the advice. After reading zipzoomflyhighs reply, I set the DDR mulitiplier to 2.0 for 800 mhz. current bios setting modifications
DDR muliplier 2.0
ddr voltage +.3
FSB voltage +.1
Vcore voltage 1.40
cpu-Z reporting vcore 1.344
Realtemp reporting temp 57c, distance to tjmax 43, 34c/57c min/max temp
running prime 95 small FFT for 10:09 at time of screen shot.
CPU ID HW Monitor
cpu vcore 1.33/1.38 min/max
DDR 1.97/2.0 min/max
I couldn't find the VID in cpuz, could you bird dog it for me. I have a screen shot of the hardware monitors, but haven't uploaded them to provide a link. if you have time could you take a look at the info I have provided. thanks again for the reply.
I have set the FSB voltage to normal, and dropped the CPU voltage to 1.39875 in BIOS and started the test again.
I opened the settings in Realtemp, and found the VID. I have read quite a few of your post, and am aware of your occupation. Could you explain to me what this information telling me? I will be more that happy to find it myself, but I would appreciate your summary.
It's not adjustable, however, BIOS settings can affect VID, which Real Temp reads. Since the E6850 is "high bin" it's typically a good overclocker, and as you're stable at 3.6 with less than 1.4 Vcore, this indicates that you have a very good sample.
The temperature I can't read on Hardware Monitor is "CPU". What is that value, please?
(1) If your motherboard has Line/Load Calibration (LLC) then enable it. Your Vdroop is massive at 56 millivolts, and LLC is designed to minimize it as much as possible. If you observe the Vcore signature in SpeedFan's "Charts" while running Prime95 "Blend", which is a cyclic workload, then you'll see just how much Vcore is fluctuating. Each downward spike is a potential BSOD. The objective is to maintain steady Vcore during load fluctuations. My Asus board typically fluctuates just 8 millivolts due to better voltage regulation.
(2) Your CPU temperature is improperly calibrated in the BIOS algorithms, which is all too common. In your screen shot, it should be 6c higher at 53c, which would be 5c below the Core temperatures, which is the proper thermal gradient between CPU temperature and Core temperatures. Since SpeedFan allows claibrations for CPU temperature and Core temperatures, it's the utility I recommend for inquiring minds who need to know as much information as possible. If you're only interested in Core temperatures, then use Real Temp.
I can't thank you enough. It is fantastic that you are willing to share your knowledge. I will continue to research and learn. You have saved me countless hours and shielded me from pitfall that could have cost me my system. I will check for the line/load Calibration in my bios and user guide, and also give speed fan a shot. I have used it before, but Vista's UAC was iritating me, and I had no luck in setting special permission for it. As I reply, Prime 95, small FFT at 1 hour 36 min, no errors, no warnings.
SpeedFan isn't for the squeamish, and can initially be a bit intimidating to the novice, but once you understand how to configure it properly, it's an outstanding freeware monitoring utility! As for Vista, you can tame the beast with the Ultimate Windows Tweaker - http://www.winvistaclub.com/Ultimate_Windows_Tweaker.ht...
With a little patience, you can make Vista settle down and run just as smoothly as XP does with "Tweak UI".