Ryan_Fpv
New Member
I have been overclocking my gigabyte HD4890 using CCC's Overdrive. I would bump it up 5/10mhz and then run the stability test to make sure it was working fine...
I ended up getting it to 985mhz on the core clock and 1115mhz on the memory clock and it passed the stability test in overdrive. As you would, you would go for the 1000mhz milestone. When I ran the test, the screen didn't come up the normal weird colour shit that is normally does, but just switched off. No signal was coming from the video card (well, the analog/digital message came up on my monitor as it does when it cannot find a signal).
I restarted, loaded back into windows, checked everest and GPUz and they both say my clocks are reset back to their default (900mhz/975mhz). When I try to load CCC though, the screen will flicker once and then it will just go black and come up the no signal thing and I'm left to restart the computer.
So, if when the 1000mhz core clock test failed CCC reset it back to default clocks, why is CCC still buggering up when I try to run it?
I ended up getting it to 985mhz on the core clock and 1115mhz on the memory clock and it passed the stability test in overdrive. As you would, you would go for the 1000mhz milestone. When I ran the test, the screen didn't come up the normal weird colour shit that is normally does, but just switched off. No signal was coming from the video card (well, the analog/digital message came up on my monitor as it does when it cannot find a signal).
I restarted, loaded back into windows, checked everest and GPUz and they both say my clocks are reset back to their default (900mhz/975mhz). When I try to load CCC though, the screen will flicker once and then it will just go black and come up the no signal thing and I'm left to restart the computer.
So, if when the 1000mhz core clock test failed CCC reset it back to default clocks, why is CCC still buggering up when I try to run it?