Sep 29, 2015 Ultimate How to Overclock Pascal GPU Guide - GTX 1060, GTX 1070, GTX 1080, GTX Titan X - Duration: 21:37. JayzTwoCents 1,072,385 views. Enable overclock with coolbits sudo nvidia-xconfig -a -cool-bits=28 -allow-empty-initial-configuration So far, everything is ok, I see that the xorg.conf has been updated properly but when I reboot, my xorg.conf goes back to a previous version without the overclocking.
trodas
Jun 04, 2005 However, does this CoolBits Linux port offer the reliability of its Windows counterpart and fix the issues that NVClock has yet to address? Today we have a short guide on how to enable CoolBits with these new NVIDIA drivers (1.0-7664), how to change your core and memory speeds, and the results we obtained when using the CoolBits utility. Nvidiux is a graphical Nvidia GPU overclocking tool for Linux. The GUI tool takes care of everything needed to overclock Nvidia graphics cards, making it as easy to use as Afterburner, the popular MSI GPU overclocking tool. Jan 12, 2007 Owners of newer video cards can use nVidia's CoolBits or NVCLOCK (which can use Coolbits as a backend). And before I forget, you should be using the binary 'nvidia' driver. You cannot perform overclocking with the open source 'nv' driver.
![Coolbits Coolbits](/uploads/1/1/9/5/119551527/490848902.jpg)
- Joined
- Jan 3, 2007
How To Install And Use Coolbits Overclock Pc
- Messages
- 454 (0.09/day)
System Name | celer |
---|---|
Processor | Pentium 4 650 3.4GHz 2MB L2 |
Motherboard | MSI PM8M3-V |
Cooling | Thermalright SI-128 SE |
Memory | 2048MB OCZ 2-3-2-5 2T at 200Mhz |
Video Card(s) | Sapphire Radeon R9100 |
Storage | 250G Samsung 850 PRO (MZ-7KE256BW) - 1024G WD Black (WD1003FZEX) |
Display(s) | 19' iiyama ProLite E1980SD 1280x1024 75Hz DVI |
Case | Eurocase moded |
Audio Device(s) | onboard |
Power Supply | Enermax 620W Liberty |
Mouse | Logitech MX510 red |
Keyboard | eTech PS/2 keyboard |
Software | Win XP SP3 |
Benchmark Scores | http://hwbot.org/submission/2455634_ |
How To Install And Use Coolbits Overclock Pro
For some old school fun and testings I sometimes overclock really old hardware, like FX 5600XT or FX 8600GT, FX 6800GS, FX 6800GT...
Now for the FX 5600XT card I use old beta Forceware 45.28 that I modifield slightly and using these Coolbits let me improve the performance by overclocking the card:
(the only important part for the clock adjustment is the 'CoolBits'=dword:0000000f.
The performance scale nicely and all is good... except some more modern 3DMarks require more modern drivers to operate.
Surprisingly using the modern drivers AND Coolbit overclock result in sluggish performance. For example 3DMark03 goes from 2551 to 563 marks:
http://hwbot.org/submission/2885484_
http://hwbot.org/submission/2885483_
Yes, on the Forceware v93.71 drivers I have a slightly different O/C (365/301 vs 370/305 on the old drivers), but nowhere near to 'justify' such performance drop.
Now this is not specific on the 3DMark, all 3D apps go sluggish after using the Coolbits on more recent drivers. For example Aquamark3 - Forceware 61.76, stock 234/200: 13341 points: http://hwbot.org/submission/2885479_
Overclocked to 365/301 by Coolbits: 6640 points: http://hwbot.org/submission/2885477_
So there IS a dramatic slow-down, when I use more recent Forceware drivers (tried v61.76 and v93.71) AND Coolbits.
Same I observed on other mentioned videocards, like the FX 6800 and 8600 one, so it is not tied to the FX 5600XT only.
Therefore I look for more recent Coolbits, found there:
http://downloads.guru3d.com/download.php?det=815
Again, I used them at first completely, then removed them - for example that easily it could be done:
...so I could strip them to the bare important for clock changes:
Now this is different value that the 0000000f used before, so I hoped... and it caused the exactly same slow-downs. That make me a 'bit' puzzled, so I started searching and I found third version of Coolbits:
http://en.wikipedia.org/wiki/Coolbits
It probably won't be any surprise now, when I write that this once again enabled the O/C possibility, but caused sluggish performance.
...
So I give up on Coolbits and used Riva Tuner. It does work w/o reinstalling on new Windows, the O/C is limited to 355/300 (600 effective) and once again - after overclocking, the performance go bad. Slow. Terrible. Even some image quirks, at 355/300, when 370/306 works nicely with old drivers.
...
Now could anyone tell me, what is going wrong there? Why Coolbits / or any O/C in general, cause slow down of graphic?
I hoped I could find someone else who had the same problem years and years ago, I manage to find some threads where people appear to having the similar troubles:
http://www.pcreview.co.uk/threads/coolbits.2806125/
'I just overclocked the GPU a tiny bit, the frame rate and graphics slow down and become juddery'
...but that is too few results from my search... so perhaps I doing something wrong, like overoptimizing by disabling the nVidia help service or the startup programs that was put there by the nVidia drivers install...?
Once again - if I did not touch the overclocking, the performance is like it should be. After Coolbits = sluggish speed.
Or could it be, that any WHQ nVidia drivers lock-out the overclock by intentionaly slowing things down and I could only use beta drivers for overclock?! Could that be? And where to get some old beta drivers anyway? There are all WHQ ones, except one Quadro Beta Driver:
http://www.nvidia.com/object/winxp-2k_archive.html
Now for the FX 5600XT card I use old beta Forceware 45.28 that I modifield slightly and using these Coolbits let me improve the performance by overclocking the card:
(the only important part for the clock adjustment is the 'CoolBits'=dword:0000000f.
The performance scale nicely and all is good... except some more modern 3DMarks require more modern drivers to operate.
Surprisingly using the modern drivers AND Coolbit overclock result in sluggish performance. For example 3DMark03 goes from 2551 to 563 marks:
http://hwbot.org/submission/2885484_
http://hwbot.org/submission/2885483_
Yes, on the Forceware v93.71 drivers I have a slightly different O/C (365/301 vs 370/305 on the old drivers), but nowhere near to 'justify' such performance drop.
Now this is not specific on the 3DMark, all 3D apps go sluggish after using the Coolbits on more recent drivers. For example Aquamark3 - Forceware 61.76, stock 234/200: 13341 points: http://hwbot.org/submission/2885479_
Overclocked to 365/301 by Coolbits: 6640 points: http://hwbot.org/submission/2885477_
So there IS a dramatic slow-down, when I use more recent Forceware drivers (tried v61.76 and v93.71) AND Coolbits.
Same I observed on other mentioned videocards, like the FX 6800 and 8600 one, so it is not tied to the FX 5600XT only.
Therefore I look for more recent Coolbits, found there:
http://downloads.guru3d.com/download.php?det=815
Again, I used them at first completely, then removed them - for example that easily it could be done:
...so I could strip them to the bare important for clock changes:
Now this is different value that the 0000000f used before, so I hoped... and it caused the exactly same slow-downs. That make me a 'bit' puzzled, so I started searching and I found third version of Coolbits:
http://en.wikipedia.org/wiki/Coolbits
It probably won't be any surprise now, when I write that this once again enabled the O/C possibility, but caused sluggish performance.
...
So I give up on Coolbits and used Riva Tuner. It does work w/o reinstalling on new Windows, the O/C is limited to 355/300 (600 effective) and once again - after overclocking, the performance go bad. Slow. Terrible. Even some image quirks, at 355/300, when 370/306 works nicely with old drivers.
...
Now could anyone tell me, what is going wrong there? Why Coolbits / or any O/C in general, cause slow down of graphic?
I hoped I could find someone else who had the same problem years and years ago, I manage to find some threads where people appear to having the similar troubles:
http://www.pcreview.co.uk/threads/coolbits.2806125/
'I just overclocked the GPU a tiny bit, the frame rate and graphics slow down and become juddery'
...but that is too few results from my search... so perhaps I doing something wrong, like overoptimizing by disabling the nVidia help service or the startup programs that was put there by the nVidia drivers install...?
Once again - if I did not touch the overclocking, the performance is like it should be. After Coolbits = sluggish speed.
Or could it be, that any WHQ nVidia drivers lock-out the overclock by intentionaly slowing things down and I could only use beta drivers for overclock?! Could that be? And where to get some old beta drivers anyway? There are all WHQ ones, except one Quadro Beta Driver:
http://www.nvidia.com/object/winxp-2k_archive.html