Overclocking - Gfx Problem

Associate
Joined
19 May 2004
Posts
1,037
Location
Horsham, West Sussex
Wasn't sure whether to post in Overclocking or Graphics but decided the problem is more to do with overclocking.

I have the following

aBit IP35
Intel E6750
Crucial Ballistix 2x1GB (1066MHz)
Geforce 8800 GTS

I've been slowly clocking my CPU - not too much and the RAM is actually running under spec.

Problem has been observed at the following

Clock = 370 and 375
RAM = 1.25
Multi = 8

CPU = 2.96 and 3.00
RAM = 925.0 and 937.5

Sometimes the graphics card doesn't start up properly resulting in a black screen. At first I thought the computer hadn't booted but when I powered off\on I got the message that windows hadn't been shut down properly. So I think everything had started up apart from the graphics output.

Now it doesn't do this all the time. And it hadn't done it at all until I reached these speeds.

PCI bus is fixed at 100MHz
Voltages are at default.

Is this coincidence or is it possible that something to do with my overclock could do this? - If so is it that my voltages need increasing - which ones?

Cheers,

Nigel
 
Have you read the basic overclocking sticky? I've also just started experimenting and found it pretty good.

I did experience what sounds like a problem when I was just ramping up the clock without changing the voltages so its definitely worth trying upping the Vcore a little and see whether it helps.
 
Yes I have read that and am quite familiar with overclocking.

I wasn't asking about specific CPU, RAM, temperature crashing problems but about the Graphics Card not starting up properly - whether this is a coincidence or could it realted to the overclocking in some way.

BTW when it does start I can play games like Crysis for as long as I want without any problems.

So I didn't think it could be voltage related but will try and see if it makes a difference.

Cheers,

Nigel
 
I think its very much related as I've never experienced the problem until I started pushing the FSB and as soon as reverted to the previous Bios settings the problem disappeared.
 
Back
Top Bottom