e6300 Help

First off all I would like to say Hi to everyone on the forum, I have been reading and visting it daily since i bought my E6300.(about a month ago) and have been implying some things on my system slowly ( I have never overclocked before unless you count overclocking my Celeron 2.55GZ to 2.61GZ) Last night I hit the wall for the first time and I would appreciate any help I overclocked my system to 3.2GZ and otrhos failed after 17 Min 10 Sec on that Large test that stresses some memory I would like any suggestions you guys might have. My setup is below.

Mobo Gigabyte 965)-DS3
550W power Supply
2X512 DDR2 (PC6200 I think) its 800MHZ OCZ Platinum Edition
Closed Case with 3 80MM Fans, 2 pumping air in 1 pumping out
Im not sure of the Heatsink I have its huge with 6 Copper Pipelines and on it I have 2 120MM fans that fit exactly on the top surface of the heatsink.
E6300 overclocked to 3.2 at 1.375 V set in my bios
factory memory settings at 4-5-4-12 my setup 5-5-5-15 V+4
FSB V normal MCH voltageV+1
Virtualization and most Advanced Bios Settings for thermal monitoring etc Disabled
Factory settings runs at 34-35 Idle Full Load 45-47 at 3.2gz Idle at 44-45 Full Load 56-57
I can run at 3.03 stable for hours on stock V for my Vcore 1.325 it hink that would be and runs at 54 full Load
I have a Conroe I think since its B2, I appologize if my terminology is wrong I tried my best I dont think Im going to be going over the 3.2GHZ I was wondering if I can keep it stable. Hopefully I wont get that hooked on OCZ and do and overdose. Any input is very welcome and thnx for taking the time to read my info to everyone......

so, 3200/7=457. your fsb and ram are already at 457mhz, so your ram is already very oc'd. i am not familiar at all with gigabyte's bios (although many here are, someone can be more specific i'm sure), but have you tried increasing the voltage to the memory, ie the vdimm?

if raising the volts on the ram doesn't help, you may be maxed out there. it could also be that your mobo needs some extra juice to achieve the higher fsb speeds.

what settings are you totally orthos stable at?

Totaly stable at 3.03 GHZ 6HRS of orthos Stress Large Memory and CPU I increased the mem voltage that would be the DDRV + 4 im guessing maybe i increased something else i thought that was mem and im not sure the mem is giving out it could be this is the eror msg
CPU: 3199MHz FSB: 457MHz [457MHz x 7.0 est.]
4/15/2007 5:53 AM
Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length.
Test 8, 4000 Lucas-Lehmer iterations of M18274367 using 1024K FFT length.
Test 9, 4000 Lucas-Lehmer iterations of M18274369 using 1024K FFT length.
Test 10, 4000 Lucas-Lehmer iterations of M18074369 using 1024K FFT length.
Self-test 1024K passed!
Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length.
FATAL ERROR: Final result was 01FCE7B9, expected: 632CAD0B.
Hardware failure detected, consult stress.txt file.
Torture Test ran 17 minutes 19 seconds - 1 errors, 0 warnings.
Execution halted.
for core 1 its no errors
Using CPU #1
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length.
Test 8, 4000 Lucas-Lehmer iterations of M18274367 using 1024K FFT length.
Test 9, 4000 Lucas-Lehmer iterations of M18274369 using 1024K FFT length.
Test 10, 4000 Lucas-Lehmer iterations of M18074369 using 1024K FFT length.
Self-test 1024K passed!
Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length.
Test 2, 4500 Lucas-Lehmer iterations of M17432575 using 896K FFT length.
Torture Test ran 17 minutes 19 seconds - 0 errors, 0 warnings.
Execution halted.

I tend to hit a wall at about 3.2Ghz on my system (check sig). Interesting at that speed everything works fine except Orthos that runs into an error almost immediately. Although I was running that speed at 1.190v And my load temps were in the 40s.

What Bios version are you using? It's best to check the Motherboard forum, apparently the latest ones aren't the best for overclocking, perhaps F7s are the best but I can't remember for the moment.

Are these the correct settings you are using for the 3.2 gig attempt?

1.375v set in the BIOS
FSB V normal MCH voltage V+1
RAM settings: default settings 4-5-4-12, but you're using 5-5-5-15 V+4

Well, cooling is ok. Think you are getting close to the limit for normal overclocking. But, try bumping all the voltages up one more notch. FSB V+1, MCH V+2, memory V+5 (that should be 2.3v), and vcore 1.4v.

If that don't work, go back to what you were using and then try to find the highest stable O/C. For example, you might find 3.1 gig (443 FSB) or 3.15 gig (450 FSB) to be the sweet spot. Even your current 3 gig O/C is pretty darn good.

BIOS version can make a difference.

ok will do does anyone know what these error msgs mean or how i could find out? i just played around with it and if i put it up to 3.4 or 3.41 ghz Im still ok through windows and programs untill i hit orthos......

prpz said:

ok will do does anyone know what these error msgs mean or how i could find out? i just played around with it and if i put it up to 3.4 or 3.41 ghz Im still ok through windows and programs untill i hit orthos......

Click to expand...

I'd like to know too, never been able to find the stress.txt file if that's what you mean.

Bios Version is dec 2006 and im 474X7 3318ghz in windows now doing things everything is fine except orthos temp idle 47 load 58

I found the stress.txt but its more of support readme thing doesnt say anything about error msgs or definitions

Ah right, that sucks.