Well, if you know me at all, you'll know i've recently thrown in the towel on fixing the chronic downclocking on my 9262 with dual 8800s. My last effort was to install the 1.00.17 BIOS straight from Clevo. It did not work.
So I went on vacation for a week. When I came back, I was playing Witcher when I had a BSOD due to the nvlddmkm.sys file. I decided that a possible fix would be to put the latest BIOS from Sager back on my laptop (I had originally tried it earlier to solve my downclocking, but no luck). I'll chart a quick course:
1) Computer came with 1.00.17aS BIOS
2) Installed 1.00.20aS BIOS to try fix downclocking -- no luck
3) Installed 1.00.17 Clevo BIOS to try fix downclocking -- no luck
4) Installed 1.00.20aS BIOS -- downclocking fixed!
Now, I did not reinstall drivers at all in between the last BIOS flash, in fact, I have been very scientific about all of my attempts to fix downclocking, and the ONLY thing I did differently this time was disable SLI before the BIOS flash from 17 to 20aS. When I restarted after the BIOS flash, I noticed my clocks were at full. I re-enabled SLI and restarted, and my clocks were still at full!
The magic question: you're probably asking if I tried disabling SLI before flashing all those other times. The truth is, I can't remember, as that was a few weeks back. I really wish I could remember. My initial thought is that no, I did not disable SLI before flashing all those other times. I hope that is the truth, because otherwise, this fixed itself due to random chance/dumb luck.
Before and after the flash that fixed it, I had the 177.92 drivers installed from L2VG.
I recommend that if anyone is having downclocking issues, try disabling SLI, flashing to older BIOS, then flashing back up to newer ones.
I am so happy right now that I don't want to risk losing this fix I magically received, so I'm not going to install new drivers, even though I really, really want the 178.13 drivers. I don't want to lose this one, brief, shining instance of no downclocking which I have been granted.
-
If it works, don't fix it! So if the drivers you are using now work fine, there is no reason to try "newer" ones.
-
Leave the laptop on for as long as you can, as it seems like that the downclocking problem happens when you have already disabled / enabled SLi and reboot without changing the SLi settings again. -
Keep me posted on your laptop once it comes back from Sager. I'm really, really curious to know if it still downclocks. -
you can get 178.13 it wont affect down clocking... all the new drivers fix that issue.
-
-
Somehow I solved my downclocking
Discussion in 'Sager and Clevo' started by trias10, Oct 6, 2008.