• 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.

SP35P2 Pro OC Help

E

Escher

Limp Gawd
Joined
Mar 9, 2000
Messages
496
Maybe this belongs in the OC forum, but I didn't see any posts there on this SFF box, so I thought it more proper to post here. My apologies if I made a mistake.

My problem concerns the memory speeds listed in the BIOS for the SP35P2 Pro. I have a Q6600 G0 and I'm pretty sure it'll hit 3.2 GHz, but it keeps crapping out and I think it's due to the memory being grossly overclocked. My ram is G.Skill F2-6400CL5D-4GBPQ, so it's rated max is a 400 MHz bus. If I could figure out how to get a 1:1 divider I'd be sitting pretty I believe, but it seems to never be an option.

The one time I was able to boot into Windows, I had the memory set at the 667 setting which seems to yield a 5:4 divider giving me a bus speed of 500 for the RAM. Unfortunately, the system wasn't very stable and ended up with a lovely BSOD. Neither the SPD, 800, or 1066 settings yielded a system that would even boot, so I'm theorizing it was trying to set the RAM on an even faster bus.

Am I totally dorking something up here, or is there no way to take the Q6600 to a 400 FSB and keep the RAM running at 400 as well?
 
Sounds like your using the latest BIOS (which adds the 1066 memory clock speed).

You could try going back to BIOS "N" which seems to overclock much easier. Also look over on the Shuttle forums at Sudhian.org for other Q6600 owners because its a little different from overclocking a 1333MHz FSB processor like my E6750. So my method, which is to set the memory clock speed to 667MHz and the FSB to 400, might be different to yours. Another thing you need to keep in mind is your memory and the timings and voltages it is getting. It won't boot if the timings are too tight and the voltage is too low. At 500 it probably needs at least 2.1V, and the BIOS is likely only giving it 1.8. But at 500 it might also need relaxed timings.

I'm not sure whether it is possible to get a 1:1 divider with Q6600's even with the latest BIOS -- you may need to run the memory at 500MHz to run the FSB at 400 if you're stuck with a 5:4 divider. But I do know that the latest BIOS made it impossible for me to achieve my usual overclock (3.2GHz @ 400FSB). I suspect it changed some obscure timings or voltages that my components aren't happy with... So try an earlier BIOS ("N" is what I use).

With 1333MHz processors getting a 1:1 divider is as simple as setting the memory clock speed in the BIOS to 667. With 1066MHz processors I don't think there is a way to get a 1:1 divider.

According to this post, the new 1066MHz memory clock speed setting yields a 2:1 divider, which I doubt would boot with any currently available DDR-800 and probably not even 1066.
 
That's interesting. I am using the newer Q bios, but seem to have a problem with Awdflash. I keep getting an "unknown bios type" error message when using it. I made a bootable USB key and attempted to flash and it won't do it. I even tried the /F option to force the flash to occur and all it does it sit there blinking "Please Wait".

Any ideas?
 
I think I got something like that, I took one of the switches out of the command line and it worked. I forgot which one it was though... lol

I'll see if I can figure it out. In the meantime what is the command line you're using?
 
I tried /PY/CC/CD/CP, optionally putting in /E, /F, /R, and /SN. The /E was to exit back to DOS, /R to reboot, /F to force the flash and I forget what /SN was supposed to do. I found the switches searching for people flashing their BIOS on this machine so I figured it worked for them.
 
before flashing make sure to load optimal defaults and be sure the BIOS flash protection is disabled.

otherwise I think it might have been either /cd or /cp that I removed and it worked. be sure to shut down and manually reset CMOS though so that stuff isn't carried over when you reboot. I think the first time I flashed without /cd or /cp I had some startup issues, but a CMOS reset cleared it up.
 
Excellent, I'll try that in the next day or so and let you know how it goes.
 
No joy. Even got a different AWDFLASH version (older) from Shuttle Tech Support than what was posted on Shuttle's site. No joy.

This sucks. I was able to get WinFlash to "succeed" in putting the "O" bios back once Shuttle pulled the "Q" bios. Still can't get AWDFLASH to work no matter what switches I try. I see there's a new "R" bios, but at this point I'm afraid of trying it out as it only seems to add support for 45 nm CPUs.
 
You must log in or register to reply here.
Back
Top