Jump to content
Corsair Community

OC with Corsair Twin 8500 CL5


Recommended Posts

Hi Community,


my problem is i can only overclock with my ram to an FSB from 350 stable.

when i push to 355 i got an error in orthos. cpu test i got no errors only when i test the ram or both.


settings in the bios:

default strap (think it is 266) - 443MHZ at 2,2 volt (10:8) divider - 4-4-4-12

same prob at 5-5-5-12

I also testet on 1:1 with 250MHZ on 333strap same prob failure or reboot


Temp (ram) read out with everest 4.2 is idle 38°C full load 45°C


ty pushook:[pouts:

Link to comment
Share on other sites

  • Replies 89
  • Created
  • Last Reply

In order to disable the Failsafe Watchdog you need to change the maintenance jumper on the motherboard and boot into setup. You will enter the maintenance BIOS menu. Just check your motherboard manual for the location of the jumper. It's near the IDE port and has a tab. You've probably done this already though if you are at 3.1Ghz.


Isolate your RAM from the overclock. Set it to a low divider, and then find your maximum FSB with that board. Remember that the Bad Axe (i975) is not a high FSB clocking boards like the i965. Once you have your maximum FSB, then you can ramp the DRAM up. Most people have to modify the motherboard to get higher clocks.


CPU Voltage: 1.40V - 1.45

Enhanced Power Slope: Enabled

MCH/ICH Volt Override: 1.525

Host Clock Frequency: 355

Failsafe Watchdog: Disabled




Reference Frequency: Default

Memory Frequency: 710mhz

tCL: 4

tRCD: 4

tRP: 4

tRAS: 15

Memory Voltage: 2.20




PCI Express Burn-In Mode Percentage: Default

PCI Latency Timer: 32

HPET: Disabled


Don't exceed 1.45V on air, or 60c during load. This is my advice. Others go higher but I am one that doesn't think these chips need that high a voltage to make 3.2 - 3.4Ghz and that is more than enough on a Dual Core Conroe. Any more and then you end up with bandwidth not being used.


I advise you to read the below thread thoroughly.



Link to comment
Share on other sites

speed brakes are all off in the bios^^

I have now 350FSB with this board at 437,5mhz/4:5 read out with cpu-z 1.41

2,2 volts


when I go on to 355fsb i got errors even when i set frequenzy from 667in the bios to 533mhz strange for me fsb for the board i think is no problem to go higher temps are under 60° under full load. memtestx86 reports no errors after 2 hours testing

Link to comment
Share on other sites

1,3875 vcore in the moment I changed to 1,4 to 1,5 same errors on ram


raised a little bit fsb and mch no luck


just for fun i raised the ram voltage to 2,4 for a short time and i got errors not after 10sec still after 30min


msn is uninstalled

Link to comment
Share on other sites

this was only a test with the 2,4 volt on dram because i tried so many things and i^m unhappy. i can go with my air cooling to 360fsb max.


i know 1,8 volt is enough for 800mhz and 2,2 is for 1066 or even more


memtest reports no errors


orthos run since 40min no errors with 350fsb!!


also i tested the cpu with my voltage listed above with no errors in orthos so it is not a must to raise the vcore or anything. i got the stop in orthos only when i stress the ram.


tested the ram with the oc settings got no errors!

Link to comment
Share on other sites

OK. What you need to do is separate your overclock into two events. First you find your maximum FSB of the CPU. You do this by setting your DRAM bandwidth divider low to isolate it as a possible variable to the overclock. With that DRAM it is not a good idea to set the Vdimm low though. Leave it at 2.2V.


Once your DRAM is isolated, then you begin to raise your FSB until it errors. Rather than use Orthos for this, you would do better to use OCCT as it will allow you a good begin testing of 30 minutes.


Download OCCT Perestroika Here


You have no problems with a load less than 65C so you have some Voltage playing room. However, if you raise by 5Mhz and your Core Voltage is at 1.3875 then if a voltage move to 1.45 does not allow you to find stability, it is not the core voltage that is holding you back. Look to the FSB Voltage and raise it a bit but I would not go higher than 1.4V.


What FPO/Batch number is your CPU? You will find that on the box.

Link to comment
Share on other sites

ok i will test with this program you linked. i would have 360fsb and it is still possible orthos shows without raising a lot vcore on the cpu.


cpuz is showing 1,188 vcore everest shows 1,14-1,18 under load it raise to 1,3, eist is off in the bios but it is still on may be an bios issue still present.


when i stress the cpu with 360fsb my max temp under load is about 63°C.


batch number is:L627B042

Link to comment
Share on other sites

You do NOT need a lot of Vcore with this CPU. You have a very good CPU there and with the right board and cooling you will very likely make a 3.4 - 3.6Ghz. This chip does run warm and water cooling is best to get 3.6+ Ghz from but they can do it. The L627B042 is a low VID processor. Download Core Temp Here

and tell me your VID (Voltage IDentification). Average E6600's have a VID of 1.35 but the "B" version of yours has a lower VID. The VID is the voltage necessary to start the system running stably. I have an L629B330 and have no problems with 1.38 (Windows) and 3.4GHz with a Thermalright Ultra Xtreme Cooler. What cooler are you using?

Link to comment
Share on other sites

air cooling with:scythe infinity / 120 Papst @1200 /up to 2400

watercooling i ordered yesterday for my new system.


ok lets start settings are:

vcore: 1,3875

fsb: 1,4000

mch: 1,550


ram on 360mhz / 1:1 - 5-5-5-15


ok will test with the program yet


ok failure after one minute with occt/ is there a log file?


core temp vid: 1.300

Link to comment
Share on other sites

Are you using windows programs to change settings or are you using the BIOS?


Set to 1.45V and retest. Let's see if we can figure this out. Sometimes there are points in the overclock that will not work and are considered a wall. For example, 357 is fine 360 walls, 365 is fine....

Link to comment
Share on other sites

350FSB at stock voltage^^ at 355 I get reboots. hmmm very strange for me.:confused:


and its not a ram fault? dividers or volt? because orthos reports only a failure when i test the ram


If you memtest the DRAM at 1066 with the cpu at stock and get no failure, then the issue is not the DRAM. You said the DRAM tests fine. Set your CPU at 266 (QDR = 1066) and set your DRAM at 1066. Test with Memtest for at least 2 Full Passes.



Link to comment
Share on other sites

i will test it later when i go out. so at 350fsb it is run all fine so you are right thats not the dram. i^m very confused thats the board. i have read so many posts in diffrent forums and nothing helped me. thanks a lot for your time and advice derek^^


next week i will have an other system /board and cpu:cool:

Link to comment
Share on other sites



ok last night i tested the ram again with memtestx86 -- 7 passes no errors^^


maybe i figured out with 360fsb


vcore: 1,3875

fsbv: 1,4500

mch: 1,6500

ram: 1:1 @ 360mhz - 2,08v


OCCT test no errors after 30min^^


maybe this board needs much voltage mch/fsbv from 350 to 360fsb


I test now with orthos 2004:laughing:

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...