A Question...

Associate
Joined
15 Jun 2008
Posts
143
I can clock my Q6600 to 7 x 400 (not yet tested higher yet because of the issue below). I'm using a G0 stepping on an Asus P5B Deluxe WiFi AP motherboard. The overclock is stable, based on Orthos/3DMark runs etc and the temperatures give no cause for concern either. However, sometimes (fairly often) following a warm reboot the PC appears to boot just fine (as far as I can tell) but the graphics card doesn't initialize and the monitors stay in their standby state. It doesn't seem to be a problem from a cold boot.

Any ideas?

FWIW, the rest of the system is 4Gb of Corsair 6400 memory (running 1:1 at its nominal rating), a 4850 and a Seasonic 600W PSU. The cooler is an Arctic Cooling Freezer 7 Pro. OS is Vista x64.
 
I'm running the 1226 BIOS, there are 2 later ones, both beta I believe, that add support for various CPUs and fix a POST issue with 3870x2 graphics cards. I suppose my issue could be related to the 3870 one even though I'm using a 4850.

If I can't turn up anything else, I'll give the latest BIOS a go...
 
Manually set the RAM divider and timings. Disabled all the C1E stuff. Set an appropriate vcore/vram. Locked the PCI/PCI-E bus speeds.

All the other voltages (NB etc) have been left on 'auto'.
 
OK, still looking for a little help with this please...

I'm now running the latest BIOS for my motherboard and this hasn't had any effect. To recap, when I oc my board and restart the graphics card doesn't initialize (ie. the monitors stay blank, even though it appears that the PC is booting fine). Since updating to the latest BIOS it seems that sometimes Vista doesn't like to shutdown/restart either.

The monitors always come on following a cold boot and the PC is Orthos stable on it's overclock. In fact if I run 6 x 400 I still get the same issue so it appears to be related solely to the FSB.

Any ideas..?
 
That fact that the system POSTs and boots into windows suggests the system is fine.

What happens with everything at stock? If it doesn't work on stock settings or safest settings, then it's likely to be a driver issue is it's still booting.

If it's ok then it's can't be a driver issue but more likely to be a setting you havn't applied on your overlclock. Are you locking the PCI bus on your overclock?

Just one other thing... have you plugged both ATX power connectors to the motheroard?
 
Thanks for the reply and suggestions.

Yes, the mobo has its full complement of power connections. At stock the system is absolutely fine and yes, the buses are locked.

I'll continue to play with it but it's pretty aggravating - I guess a move to a more modern mobo/chipset might be the easiest answer but I'd sooner stretch some more life out of this one if possible.
 
Just in case anyone searches on this:

It turns out I needed to lock the PCI-E bus at 101 instead of it's nominal 100. I have no idea why but this seems to have resolved this (touch wood...).
 
Back
Top Bottom