wont stay at the clock speed i use

Associate
Joined
6 Jul 2006
Posts
1,507
Location
co durham
as you can see from my sig the overclock i have and its been fine till i installed the new nvidia drivers and when it rebooted it came up running at 3.16ghz so went into the bios and all settings are set for it to run at 4.03ghz,now speedstep and the others are al disabled so why has it all of a sudden gone like this any ideas please,running bios f11 but there is a f13c out but dont think that would help
 
I had a Gigabyte DS3 but with the 965P chipset. It too randomly stopped holding my overclock. If I set anything above the 266 defaul FSB it would revert to 267. Unfortunately, seen as the board runs fine at stock speeds, Gigabyte arent the slightest bit interested in replacing it, so I bought an IP35 Pro and replaced it.
 
thanks for the advice but mine is a p35 board and its the first time it has done it and its been clocked for the last 6 months at these speeds,just seems srange that i change the drivers of the card and the clock speeds go,i know it cant be the drivers but havent got a jumper to reset the bios so might just take the battery out and see if that helps
 
my ga-p35-ds3l would do this. It could be fine for weeks and weeks then lose the overclock. The settings in the BIOS saved but were not enforced in windows. The only way I could get around it was to flash the BIOS.... which is eventually how i killed the board :(
 
Might be something in that - my E2160 on a 965P-DS3 board was stable for months til I changed to the 184.48 Nvidia driver, then it crashed suddenly and lost the overclock (went back to the cold boot problem where the O/C had to be reset each power up) and graphics crashes 1-2 time per night. I fiddled with the settings as I thought the CPU might be on the way out but it settled again (still with some graphic-related crashes to this day). Might be related to the OP problem -was it the 184.48 driver causing the original problem ?

cjph
 
I had something similar with my old P965-DS3P mobo, stable as hell till 1 day it decided it wasn't, turned out, for me anyway that upping the NB voltage a notch or 2 fixed it so give that a go.

EDIT: I've also had something similar with my P5Q-Deluxe, running vcore of 1.3025 for a few months, then started crashing so have had to up that to 1.3225 (or something similar).
 
Back
Top Bottom