• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

SATA Raid 0 / 2.4C OC problem

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

ghost_shell

Registered
Joined
Aug 27, 2002
I was getting ready to OC my brand new 2.4 C P4 CPU when I ran into a problem.

For starters I am using 2 WD Raptors set in Raid 0 config with Corsair XMS PC3500 2 sticks X 512 MB each. I also have a WD Spec. ED 80 GB HDD with 8 MB cache hooked up to the IDE connector as a backup drive.

Everything is working smooth with the default settings. I was able to get the memory timings down to 2-5-3-2 in dual DDR mode and stable with the Vdimm set at 2.65 v ( although it will work fine at 2.6 v set in bios , I just decided to give the memory a little more juice b/c the winbond hardware doc. was reporting my memory to be actually using something between 2.65-2.67).

In any case, I started with a extremely conservative OC of just 5 mHz on the FSB I left the memory divider set to 1:1 and the computer will lock up at the point where the SATA RAID drivers are being loaded?

If I go back and change it to the default FSB speed no prob. .

I tried increasing the the memory voltage to 2.7 and I also changed the memory timings to the defaults and even tried a memory divider of 5:4.

No luck, still locks up at the point where the Intel SATA Raid drivers are loading.

I hope that there is some simple explanation, anyone have a similar setup or words of advice?.....I want to try a decent OC.



Thanx as always for all the help I have gotten so far and constructive criticism! :)
 
Be sure you are not overclocking the RAID chip or the PCI/AGP bus. Most new boards allow you to lock out the PCI/AGP to default 33/66mHz. if you did not lock them please do. Also ease your mem timing back to 2.5-5-3-2

Good Luck
 
PCI/AGP/SATA bus needs to be locked at 33/66/100 as in my experience, overclocking the SATA bus causes problems from not being able to detect the SATA drive to corruptions/BSOD's =)
 
Back