WORKING PIN MOD (bsel) for core 2 quad q9550

[CladInShadows]

Before we start, I have already seen this thread (http://www.overclockers.com/forums/showthread.php?t=729454) and it still doesn't give me an illustration of how to pinmod a Q9550 cpu (not an E2200!).

Please, no manual or software suggestions such as going through BIOS or using clockgen because guess what? I'm using a DELL computer! . I've had my q6600 overclocked ever since I got my Dell XPS 420 years ago, and I realize there are sites all over the internet that detail this working mod, but no WORKING mod for q9550 which I just got . The chip has been out since 2008 (I believe), so I figure there has to be somebody out there that has figured out a bsel I can use for this chip. (And no, the mod for the q9650 doesn't work, tried it) .

Anyone??

 

[||Console||]

Did you try this
http://www.xtremesystems.org/forums/showthread.php?232678-E8xxx-Q9xx0-FSB-1600-pin-mod

 

[Bobnova]

If the Dell motherboard doesn't support 400FSB, nothing will get you there.
Do you know if it supports it?
The BSEL mod for 333 to 400 is simple enough, this article (that you've already been linked to once) has the charts and pinmap to do it with: http://www.overclockers.com/intel-lga775-pad-modding/
Connect BSEL1 to VCC. Super easy (as these thing go, anyway). If it boots at 400 you're golden. If it doesn't boot your motherboard doesn't support 400FSB, and you're 100% out of luck.

BSEL is BSEL on 775, if you did the 333-400 BSEL mod on a q9650 and it didn't work it won't work on anything else, either.


EDIT:
Hey that article even has the 333-400 charted for you!

 

[CladInShadows]

Did you try this
http://www.xtremesystems.org/forums/showthread.php?232678-E8xxx-Q9xx0-FSB-1600-pin-mod

That's for a 9650. Tried it already, anyhow. Doesn't work.

 

[||Console||]

They are all the same

 

[RJARRRPCGP]

P43, G31 and G33 don't officially support 400 Mhz FSB. You're on your own.

 

[CladInShadows]

P43, G31 and G33 don't officially support 400 Mhz FSB. You're on your own.

I just find it strange that I was able to mod the Q6600 but not the Q9550 (using the same motherboard)...

 

[glussier]

The q6600 has a 266mhz base frequency, the q9650 has a 333mhz base frequency. So, nothing strange there.

 

[cw823]

The q6600 has a 266mhz base frequency, the q9650 has a 333mhz base frequency. So, nothing strange there.

QFT. You're out of luck here

 

[CladInShadows]

QFT. You're out of luck here

Well I got it to OC in setfsb from 2.83 to 3.40. It's just too bad I have to keep re-adjusting the settings after I shutdown PC. I think the updated ("donation") version of setfsb may fix this problem.

 

[freeagent]

Probably not..

 

[glussier]

Well I got it to OC in setfsb from 2.83 to 3.40. It's just too bad I have to keep re-adjusting the settings after I shutdown PC. I think the updated ("donation") version of setfsb may fix this problem.

The donation version won't solve your problem. However there are command line parameters to setfsb.

See this short thread: http://www.overclock.net/t/927882/setfsb-auto-startup

 

[CladInShadows]

The donation version won't solve your problem. However there are command line parameters to setfsb.

See this short thread: http://www.overclock.net/t/927882/setfsb-auto-startup

That solution works just fine when I reboot my computer, but not after starting it back up from shutdown. I assumed it was because I needed the latest version of setfsb, since I am running Windows 8?

 

[glussier]

I don't know if the problem is the setfsb version being used. The problem might be that you need to add a longer delay in the command line parameter when doing a cold boot.

 

[CladInShadows]

I don't know if the problem is the setfsb version being used. The problem might be that you need to add a longer delay in the command line parameter when doing a cold boot.

Okay. I only had it at 5 seconds, then tried ten. I'll try 15 and I'll see if that does anything...

 

[CladInShadows]

Well, that didn't work either, so I set the wait time back to "08". Now, I don't even touch the bottom slider of setfsb, as that seems to cause more instability than anything, so I figure I don't even need to include "i" in the target text field. I am referring to this article right here: http://www.ehow.com/how_12032951_keep-setfsb-settings-after-reboot.html

 

[glussier]

-s and -i essentially do the same thing. -s set the front side bus of your cpu at a specified mégahertz, -i is an offset from the stock base frequency of your cpu.

So, is it working now?

 

[CladInShadows]

-s and -i essentially do the same thing. -s set the front side bus of your cpu at a specified mégahertz, -i is an offset from the stock base frequency of your cpu.

So, is it working now?

After what? Do you think messing with the stock base frequency has anything to do with how the program saves after a cold boot?

 

[glussier]

I don't think so.