E6600 Overclocking project - Experianced eye required!

[moogle]

30 min STs are fine as long as thats how long you use your PC for in any 1 sitting

I used to do the same until I started getting crashes after prolonged gaming sessions.....then found the benefit of making sure I am as close to 100% stable as i am going to get.

i use the pc alot longer and i've had no crashes yet.

[Clunk]

i usually stress for 30 min's, then if it stays stable then i leave it as that. i've tried 6 hours but the temp never increased so I always do 30 min's. plus i find its a waste of electricity running it for 12 hours at full load.

Thats fine if you dont require it to be stable.

If you DO want to see if it is stable, run it overnight for at least 12 hours.

If it fails the test, it just stops and flashes red, sometimes the pc will freeze, sometimes you can get a bsod, but usually, it flashes red and says STOPPED.

[rss1979]

My PC is used for well over 12 hours daily.....although it is rare that I stress the components to this degree.....perhaps 1 or 2% of the time MAX.

Still, I want a stable overclock for longevity more than anything!! I would rather back off on the OC and have the PC last an extra 6 months.........

[rss1979]

.....If it fails the test, it just stops and flashes red, sometimes the pc will freeze, sometimes you can get a bsod, but usually, it flashes red and says STOPPED.

ok, so this does more than just stress the CPU? It actually runs a test......?? I don't really understand.........can it tell if the processor is overstretched?

[moogle]

ok, so this does more than just stress the CPU? It actually runs a test......?? I don't really understand.........can it tell if the processor is overstretched?

it runs a set mathematical functions, knowing its values which will be output, and see's how accurate your cpu is outputting them to be. if your cpu is unstable, ie it read the voltage level as a 0 instead of a 1 the number will be off and it will detect it. thats all, that tells you that you either need to up the volts or lower the fsb. at the same time this calculation makes the cpu heat up because it is very stressful on the cpu.

for testing your memory run memtest, it's best to run the dos floppy version because it tests all the ram as running the windows memtest it cant get access to the memory windows is using.

[Clunk]

It stresses the cpu and ram. If it detects any errors, it will stop and tell you. If it stops, you need to go into the bios and lower the fsb, or up the vcore, but I wouldnt recommend upping the vcore while you are using the stock cooler.

[moogle]

Thats fine if you dont require it to be stable.

i use the pc alot longer and i've had no crashes yet.

stable and running.

[Clunk]

^^yet.

Exactly my point, you dont know that it is stable.

[rss1979]

ok, I understand now!! Right so it's a case of trial and error.......stepping the FSB/Voltage etc. up each time.....until I am happy with the result or it starts to get unstable??

Do we know what is an acceptable high temp for the E6600 yet? I found the tech spec sheet on the intel site and that refered to Thermal Specification of 60.1C........but I don't understand the explaination of Thermal Specification....

Thermal Specification: The thermal specification shown is the maximum case temperature at the maximum Thermal Design Power (TDP) value for that processor. It is measured at the geometric center on the topside of the processor integrated heat spreader. For processors without integrated heat spreaders such as mobile processors, the thermal specification is referred to as the junction temperature (Tj). The maximum junction temperature is defined by an activation of the processor Intel® Thermal Monitor. The Intel Thermal Monitor’s automatic mode is used to indicate that the maximum TJ has been reached.

WTF???

[moogle]

^^yet.

Exactly my point, you dont know that it is stable.

i use the pc alot longer

alot longer = more than 12 hours i should have said, ie sometimes in the summer holidays i'd play lots of online games like aa and stuff like that.

WTF???

http://en.wikipedia.org/wiki/Thermal_Design_Power

[rss1979]

ok, well seeing as i am topping out at around 60C and the TDP is 60C its all good in the hood??

[moogle]

ok, well seeing as i am topping out at around 60C and the TDP is 60C its all good in the hood??

it should be, 60c is not that good but it isn't life threatning, if you start getting probs where the pc shutsdown then the temp may be too high, which is usually around the 90c mark.
what i do is use the stock heatsink and run orthos, find the max temp it goes to. then i use my desired performance heatsink and keep it below/near that max temp.

[rss1979]

ok, that is kind of my plan, in a couple of weeks i will be fitting a watercooling kit........I want to find how far I can push it with stock HSF then use those settings with the watercooling..

[rss1979]

Just to recap, my spec is below.....

ASUS P5B Deluxe WiFi AP
Intel C2D E6600
Corsair TwinX XMS2-8500C5D (5-5-5-15)
MSI NX7600GT T2D256E
WD Raptor 74GB
WD Caviar 200GB (x2)
Tagan 500W PSU

I adjusted the BIOS settings as advised.....new settings below.....

CPU Config

• Manufacturer: Intel
• Brand String: Intel (R) Core (TM) 2 CPU 6600 @ 2.4GHz
• Frequency: 3.27GHz
• FSB Speed: 1448MHz
• Cache L1: 32KB
• Cache L2: 4096KB
• Ratio Status: Unlocked (Max:09, Min:06)
• Ratio Actual Value: 9
• CPUID: 6F6
  
• Modify Ratio Support: Disabled
• Ratio CMOS Setting: 9
• C1E Support: Disabled
• Max CPUID Value Limit: Disabled
• Vanderpool Technology: Disabled
• CPU TM Function: Disabled
• Execute Disable Bit: Disabled
• PECI: Disabled

------------------------------------------
Jumper Free Config

• CPU Frequency: 362
• DRAM Frequency: DDR2-1086MHz
• PCI Express Frequency: Auto
• PCI Clock Sync Mode: 33.3MHz
• Spread Spectrum: Disabled
• Memory Voltage: 2.45V
• FSB Termination Voltage: Auto
• NB VCore: Auto
• SB VCore (SATA, PCIE): Auto
• ICH Chipset Voltage: Auto

------------------------------------
North Bridge Chipset Config

• Memory Remap Feature: Disabled
• Config DRAM Timing by SPD: Disabled
• DRAM CAS# Latency: 5
• DRAM RAS# to CAS# Delay: 5 DRAM Clocks
• DRAM RAS# Precharge: 5 DRAM Clocks
• DRAM RAS# Activate to Prec: 15 DRAM Clocks
• DRAM Write Recovery Time: 5 DRAM Clocks
• DRAM TRFC: 42 DRAM Clocks
• DRAM TRRD: 10
• Rank Write to Read Delay: 10
• Read to Precharge Delay: 10
• Write to Precharge Delay: 10
• Static Read Control: Auto

---------------------------------------------------

I ran orthos for 12 Hours and the temperature reached a max of 64C.

The results of orthos are below......

----------------------------------------------------------
Type: Small FFTs - stress CPU Min: 8 Max: 8 InPlace: Yes Mem: 8 Time: 15
CPU: 2400MHz FSB: 266MHz [266MHz x 9.0 est.]
08/02/2007 16:17
Launching 2 threads...
1:Using CPU #0
2:Using CPU #1
1:Beginning a continuous self-test to check your computer.
1ress Stop to end this test.
2:Beginning a continuous self-test to check your computer.
2ress Stop to end this test.
1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
1:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
2:Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
1:Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
2:Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
1:Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
1:Torture Test ran 7 minutes 22 seconds - 0 errors, 0 warnings.
2:Torture Test ran 7 minutes 22 seconds - 0 errors, 0 warnings.
1:Execution halted.

2:Execution halted.

Type: Small FFTs - stress CPU Min: 8 Max: 8 InPlace: Yes Mem: 8 Time: 15
CPU: 3258MHz FSB: 362MHz [362MHz x 9.0 est.]
08/02/2007 21:13
Launching 2 threads...
1:Using CPU #0
2:Using CPU #1
1:Beginning a continuous self-test to check your computer.
1: Press Stop to end this test.
2:Beginning a continuous self-test to check your computer.
2: Press Stop to end this test.
1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
1:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
2:Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
1:Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
2:Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
1:Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
2:Test 6, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
1:Test 6, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
2:Test 7, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
1:Test 7, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
2:Test 8, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
1:Test 8, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
2:Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
1:Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
2:Test 10, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
1:Test 10, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
2:Test 11, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Test 11, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Test 12, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
1:Test 12, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2:Self-test 8K passed!
2:Test 1, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
1:Self-test 8K passed!

Missed a few to conserve space!!

2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Test 7, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
2:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
1:Test 8, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
2:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
1:Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
2:Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
1:Test 10, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
2:Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
1:Test 11, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Test 6, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
1:Test 12, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2:Test 7, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
1:Self-test 8K passed!
1:Test 1, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
2:Test 8, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
1:Test 2, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
2:Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
1:Test 3, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
2:Test 10, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
1:Test 4, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
2:Test 11, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Test 5, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
2:Test 12, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
1:Test 6, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
2:Self-test 8K passed!
2:Test 1, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
1:Test 7, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
2:Test 2, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
1:Test 8, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
2:Test 3, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
1:Test 9, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Test 4, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
1:Torture Test ran 12 hours, 0 minutes 1 seconds - 0 errors, 0 warnings.
2:Torture Test ran 12 hours, 0 minutes 1 seconds - 0 errors, 0 warnings.
1:Execution halted.

2:Execution halted.
--------------------------------------------------------

All seems ok after the test, my only concern is the difference in the speeds the cores were handling the calcs.....it seems that core one was crunching through them quicker than core two, is this normal??

[Clunk]

Looks good to me. What you can do now, is manually set the vcore and see if it will do the same test with low volts, and low volts will give you less heat.

Those results that you posted, was it one test that you did for 7 mins or so, and then another one for 12 hours?

[rss1979]

Those results that you posted, was it one test that you did for 7 mins or so, and then another one for 12 hours?

That was the start and end of a 12 hour test.......couldn't post all the results as it exceeded the maximum message size and I didn't want to span accross 2+ messages....That said, the results were comparable to those shown and I only listed them to illustrate the difference between the core's performance.