• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

3.0C Overclocking

M

mayakindaguy

Gawd
Joined
Jan 28, 2004
Messages
538
Just wanted to make sure, but if my overclock starts bluescreening at 245 FSB and I am on a 3:2 divider, that should eliminate the RAM as the culprit for the limiting the overclock right?
I know that 3.0Cs top out generally at 240 FSB, but I was able to run windows just not stable at 245 6 months ago.

I also bought 2x512 corsair XMS 3500 Cas 2 revision 1.1 and the strange thing is if I try to overclock it 1:1 by auto or manually setting the DRAM frequency to 400mha and AGP/PCI to 80/40 I actually get some type of short I think. Because what happens is the mobo will suddenly not be able to read my 36 gb raptor (which is my boot drive) so it's not in the BIOS and instead it's switching to my IDE drive which is just storage. So i get the please select correct boot device and reboot. I know that there is a shielding issue with SATA cables, but why in the world would this happen when I try to overclock the RAM at 1:1? Especially since 3500 revision 1s are supposed to be bh-5 (but regardless).
Everything runs fine at stock and the RAM does 2-2-2-5 just fine. And this is with all different types of voltage.

Thanks
 
sata drives don`t like to overclocked (something about the pci bus being overclocked) lock your agp/pci at 66mhz/33mhz and try again. i ran a 2.4c @ 3.2 Ghz with no problems like this with 2 raptors in raid 0. Hope this helps!
 
lol. thanks fatboy32. That really helped. The odd thing is that this RAM now wont run over specs. At 1:1 220mhz I get a bluescreen w/2.85vdimm. Kind of odd for winbound bh-5. However, it ran through memtest fine. I guess I will have to get to the bottom of this somehow.
 
glad it worked for you! about the ram you might be on your own. i think i have the same ram (2x 256mb) i couldn`t get the ram to run above spec either, even with relaxed timings and/or with increased voltage. the best results for me 2.75v more than that seemed to hurt results.
 
You must log in or register to reply here.
Back
Top