Railwhore

Ok 8 hours Orthos stable 9x333 v1.30. LOL, can't open control panel AT ALL. I just flashes a window and closes fast. If I back it down to UNDER 315 I can open it. This is redonkulous. Anything over 315 and it won't open! Temps are all normal (torture test never over 53 degrees all cores 60).
Raising cpu voltage does not fix the problem. Raised it up to 1.4625 and problem still exists. Related to northbridge voltages? Havent tried messing with those.

Q6600 & Asus P5k Deluxe
DDR settings are set to factory spec: 1.9v 5-5-5-12 Auto on all other settings in bios except the usual:
cpu spread spectrum: disabled
pci-e spread spectrum: disabled
pci-freq 100
dram freq ddr2-667
cpu volt 1.30v (1.216 in CPU-Z)
volt ref auto
volt damper auto
cpu pll volt auto
dram volt 1.90v
FSB term voltage is 1.40v
northbridge is 1.55v
northbridge ref is auto
southbridge auto

Please help me figure this problem out. Lowering speed to <315 fixes issue - raising vcore doesn't fix issue. But I really want 9x333! I was having troubles going 8x400, but I may try again and see what happens in that area. Thanks for any info!

DesertRat

so you jsut can't open windows control panel @ 9x333? lol. that's really wierd...:s

__________________

frupert

Are you on Windows Vista or XP?

GTT

try to increase the voltage just one step and try again. Happened to me before that my CPU won't respone for anything. But if it's only CP, and you can open everything els then it's your windows i guess.

__________________
3DMark06 = 17,153@3.60Ghz

FriscoPowers

it happened to me when I overclocked on vista too. weird...

Railwhore

Windows Vista Enterprise 64bit. I gues I will try 8x375/750 and see tonight.

Railwhore

Technically, I can't open CP OR Device Manager LOL. This is just soooo weird. So I am sitting at 9x310 lol. No CP or DM is a deal breaker for me .

Railwhore

Found this solution? (haven't tested it yet) here:

http://forums.extremeoverclocking.com/t267740.html

This problem with Control Panel is common and often discussed. I have this problem too. Obviously is caused due to drivers (e.g. nVidia) by high CPU speed. (If you will boot in safe mode, control panel is back, but in normal mode fails...)
I found this solution in other forums (and I'm using it):

1) Launch services.msc from a "Run" command.
2) Find "SL UI Notification Service". Sometimes this service isn't running (set it to automatic start!), then start it and after 5 sec stop it. If this service is running, stop it.
3) Find "Ready Boost" and stop it.
4) Find "Software Licensing", restart it and wait 5 secs.
5) Start "Ready Boost" and wait 5 secs.
6) Start "SL UI Notification Service"
7) Control panel will be back. No? Reboot and repeat...

Main goal is restarting service "Software Licensing". Other two services are dependent on this service and that's why this complicated procedure...

PS: Restarting "Software Licensing" may sometimes cause message about "not genuine" Vista or disallowed key change - reboot in this case and verify installation.



-------------------------------------------


Interesting to say the least...

Istrianac

Simple solution to your problem. I have a very similar setup to yours and have come across the same problem. Here's what fixed it for me:
Bios Version 404:
Jumper-Free Configuration:
Simply change your "FSB Strap to North Bridge" from 266MHz to 333MHz
Also make sure the settings below are as follows (if you're leaving all voltages at stock):
Transaction Booster: ENABLED
Relax Level: 0
Clock Over-Charging Mode: Auto
CPU Spread Spectrum: DISABLED
PCIE Spread Spectrum: DISABLED
*** Leave all other settings to AUTO ***

Go into "Configure Advanced CPU Settings"
Set all but the following 3 settings to DISABLED:
CPU Ratio Control: AUTO
Execute Disable Bit: ENABLED
PECI: ENABLED

That's it, you should be able to bump your FSB to 356MHz (3.2GHz) and your DDR to DDR-712MHz. 1:1 Ratio of 1424MHz FSB.

PRESTO! The Control Panel in Vista will now open!! It sure was weird when I first came across this problem and took me an entire day of troubleshooting my O/C until I fixed the problem.

Cheers!!