Got my E6600, Gigabyte 965P-S3 and I'm clueless!

Wag

Diamond Member
Jul 21, 2000
8,288
8
81
OK, first Intel machine ever. Yes, I've either had Apples (long long time ago) or AMDs, so this is my first Intel. I'm all set up, got some spiffy Patriot DDR2 that's supposed to OC real well.

This board's bios has so many OC settings it's be wildering. I've got an Arctic Cooler sync on my chip and it's idleing at a nice 42F, with the case open, so there's a lot of headroom.

OK, multipliers, voltages, settings, blah! So much here! And I haven't even set up windows yet.
 

Polish3d

Diamond Member
Jul 6, 2005
5,500
0
0
I would start by wacking it up to about 2.7-3.0ghz on stock volts, and begin testing with prime and memtest. (make sure to use both to isolate problems). From there, you'll need to do more reading on OCing. Also, be sure to update the bios
 

myocardia

Diamond Member
Jun 21, 2003
9,291
30
91
Originally posted by: Frackal
I would start by wacking it up to about 2.7-3.0ghz on stock volts, and begin testing with prime and memtest. (make sure to use both to isolate problems). From there, you'll need to do more reading on OCing. Also, be sure to update the bios
Wrong. Never install your operating system (Windows) while overclocked. Start out by running MemTest. If it passes for 8-12 hours, then install Windows, and all of your drivers, and other important software, while still at stock speeds.

Now you're ready to overclock. First, do your research. There are hundreds, if not thousands of forum threads about overclocking C2D's, but pay the most attention to the ones that pertain to DS3's. The settings should be nearly identical to your S3.
 
Oct 4, 2004
10,515
6
81
42 degrees Fahrenheit is about 6 degrees celsius. That's impossible. Check temperatures using Core Temp. And just check out the dozens of threads in this forum.

(I wonder what's keeping n7, myocardia, RichUK, Frackal and the other gurus from creating a sticky-worthy Core 2 OC thread)
 

Polish3d

Diamond Member
Jul 6, 2005
5,500
0
0
Originally posted by: myocardia
Originally posted by: Frackal
I would start by wacking it up to about 2.7-3.0ghz on stock volts, and begin testing with prime and memtest. (make sure to use both to isolate problems). From there, you'll need to do more reading on OCing. Also, be sure to update the bios
Wrong. Never install your operating system (Windows) while overclocked. Start out by running MemTest. If it passes for 8-12 hours, then install Windows, and all of your drivers, and other important software, while still at stock speeds.

Now you're ready to overclock. First, do your research. There are hundreds, if not thousands of forum threads about overclocking C2D's, but pay the most attention to the ones that pertain to DS3's. The settings should be nearly identical to your S3.



Weird, I don't see myself telling the guy to install Windows while overclocked. I assumed he was posting from his newly built machine at stock, which would require him to have installed the OS and such
 

Polish3d

Diamond Member
Jul 6, 2005
5,500
0
0
Originally posted by: theprodigalrebel
42 degrees Fahrenheit is about 6 degrees celsius. That's impossible. Check temperatures using Core Temp. And just check out the dozens of threads in this forum.

(I wonder what's keeping n7, myocardia, RichUK, Frackal and the other gurus from creating a sticky-worthy Core 2 OC thread)

You know, I would at least give my own contributions to that thread. I've found OCing this board/mem/CPU combo to be a bit odd.

It seems to require me to move up incrementally, regardless of settings. What I mean by that is, if I were to reset all my settings to stock, I couldn't just go back into the bios and set them back to what I'm running stable in my sig below. I have to move up incrementally, using memtest to "coax"/burn-in my memory up through 2.7-2.9, than 3.0, than 3.2, than 3.4, than finally 3.6, and sometimes it'll work and sometimes not, but once it has, it kind of "settles" into it, and is finally stable. It's REALLY weird, I have no idea why this is the deal. It could be that I'm still running the F4 bios, which I will be updating this week. (F5 supposedly fixes some ram issues)