qx960 cant run 1600fsb anymore :(

[supersyz]

I have a strange problem, i used to run my qx9659 @ 1600 linked with my 1600 DDR3 ram and everything was fine. Then i saw a bios update for my EVGA 790i to go from p06 to p07. I updated fine but as soon as i ran the FSB @ 1600 it would lock when i get into windows, i tried on a fresh XP but the same.
I can run the cpu @4Ghz with just changing the multiplier and i can also take the FSB upto 1550 but as soon as i hit 1600 it will lock just as it gets into xp.
I did up the voltage to the highest green setting and it did boot further into windows but still locked hard. Since i have also tried the p08 bios but just the same and i cant find the p06 online anywhere, would be very gratful if anybody has any ideas and please let me know if you need more information.

 

[Smirnoff]

Most likely a FSB hole, try going a little over or under 1600

 

[supersyz]

Most likely a FSB hole, try going a little over or under 1600

OK i never thought of going over 1600, i can take it just under 1600 and its stable but its just a shame how it ran fine before the bios update. I will drop to x8 and try 1650 thnx for advice

 

[Ben M]

try dropping your multi right down and seeing what fsb speeds your mobo will handle.

 

[supersyz]

try dropping your multi right down and seeing what fsb speeds your mobo will handle.

I dropped multi to 8 but couldnt go much over 1550 fsb without it locking hard but i used to run this at 4Ghz with linked ram/fsb @1600.

I can leave everything on auto and just up the multi and get stable 4Ghz but i just cant up the FSB since bios update below are my normal stable settings.

BIOS Version: P08
**System **
CPU Freq, 3000MHz: GHZ
FSB Reference Clock, MHz: 1333.3
CPU Multiplier: [9X]
PCle x16-1 & 16-2, MHz: [auto]
PCle x16-3, MHz: [auto]
SPPc->MCP Ref Clock, MHz: [auto]
nForce SPP --> nForce MCP: [5X]
nForce SPP c-- nForce MCP: [5X]
**Spread Spectrum**
CPU Spread Spectrum: [Disabled]
HT Spread Spectrum: [auto]
PCle Spread Spectrurn(SPP): [Disabled]
PCle Spread Spectrurn(MCP): [auto]
SATA Spread Spectrum: [Disabled]
**FSB & Memorv Config**
FSB - Memory Clock Mode: [auto]
FSB - Memory Ratio:1:2
FSB (QDR), MHz: [auto]
Actual FSB (QDR), MHz: 1333.3
x MEM (DDR), MHz: auto
Actual MEM (DDR), MHz: 1333.3
P1: [AUTO]
P2: [AUTO]
**Memory Timing Setting**
Memory Timing Setting: [manual]
tCL (CAS Latency): 7
tRCD: 7
tRP: 7
tRAS: 20
Command Per Clock: [auto(1T)]
** Advanced Memory Settings **
tRRD: [Auto(4)]
tRC: [Auto(33)]
tWR: [Auto(12)]
tWTR: [Auto(16)]
tFAW: [Auto(21)]
tREF: [Auto]
trfc: [auto(60)]
**System Voltages**
CPU Core: [auto] (1.19v)
CPU FSB: [auto] (1.1v)
Memory: [1.8]
nForce SPP: [auto] (1.30v)
nForce MCP: [auto] (1.5v)
GTLVREF Lane 0: [Auto] -30mv
GTLVREF Lane 1: [Auto] -30mv
GTLVREF Lane 2: [Auto] +00mv
GTLVREF Lane 3: [Auto] +00mv
**CPU Configuration**
Limit CPUlD Maxval: Disabled
Intel Speedstep: Disabled
xPPM Mode: [Native]
CPU Thermal Control: [Disabled]
C1E Enhanced Halt State: [Disabled]
Execute Disable Bit: [Enabled]
Virtualization Technology: [enabled]
CPU Core 0: [Enabled]
CPU Core 1: [Enabled]
CPU Core 2: [Enabled]
CPU Core 3: [Enabled]

 

[supersyz]

I did some testing and got some strange results, i set the fsb @1600 and left the ram @1333
left everything on auto and it booted fine . I then did fsb @1333 and ram @1600 1.9v everyting on auto and it booted fine . Then i linked them both with everying on auto and it locked as windows loaded i dont get it, any ideas anybody?

 

[matt100]

to be honest you want to be avoiding auto if you're going for a decent clock, set everything as a discrete value and at least then you can ensure your board isn't setting some ridiculously high or low voltage for something or not unlinking your pcie frequency etc etc.

Might be something as simple as your NB voltage needs to come up a notch.

Auto is bad though because there are plenty of situations where too much voltage is just as bad as too little with the added fun of being potentially terminal for a component or the board.

 

[supersyz]

to be honest you want to be avoiding auto if you're going for a decent clock, set everything as a discrete value and at least then you can ensure your board isn't setting some ridiculously high or low voltage for something or not unlinking your pcie frequency etc etc.

Might be something as simple as your NB voltage needs to come up a notch.

Auto is bad though because there are plenty of situations where too much voltage is just as bad as too little with the added fun of being potentially terminal for a component or the board.

That makes perfect sense as i noticed on auto some things went above the volts i would use. I just find it strange how i can run 1600fsb or 1600ram with auto settings but i cant link them on auto settings?

Thnx so much for your reply as im running out of ideas as ive had this prob for months lol, was fine when i first got the pc i could overclock so easy. I can get 4ghz now with just upping multi x on 1.35 no probs but i just cant link @1600