nTune and OverDrive: Overclocking With AMD and Nvidia
AMD and Nvidia both offer their own overclocking apps as well, called OverDrive and nTune, respectively. They’re less specialized than the utilities from the motherboard manufacturers, though they are limited to certain chipsets rather than specific motherboards.
nTune: For nForce Only
nTune, Nvidia’s app developed in-house, only works with the vendor’s chipsets—at least as far as overclocking the CPU is concerned. It won’t work with the company’s first generation of chipsets or with mobile versions. But if you have an nForce chipset, the program will let you overclock the processor and memory and change their voltages, as well as the chipset voltage.
You can download the latest version of nTune here (opens in new tab).
Tips: nTune will run on platforms that don’t use an nForce chipset, but only for graphics card adjustments. You won’t be able to overclock the CPU.
OverDrive: AMD And Overclocking
AMD’s OverDrive is the equivalent of Nvidia’s nTune, an application for monitoring motherboards that use the maker’s CPUs. The program works only with AMD chipsets (7-series) and AMD processors. With it, you can overclock the processor with very granular control. For example, you can select a different frequency for each core of a Phenom. Naturally, memory and HT performance are also adjustable. Voltages are adjustable, too.
The latest version of OverDrive can be found on AMD’s page, here.
Tips: We tested the OverDrive software with a Phenom in one of our articles: AMD 790GX: RV610 For Enthusiasts? The SB750 southbridge’s new options—like ACC—are only available on boards that feature the new piece of I/O logic, though.
Still, if you have a prebuilt machine with no BIOS overclocking functionality, some of this software is invaluable.
Spot on with RivaTuner and ATI Tool.
Both great apps for overclocking your GPU.
Good work trying to get the masses intrested in overclocking!
"The Cryptographic Subsystem has failed a mandatory algorithm self-test in bootstrap." (Error code 0x000000123)
Forget googling the error code, you'll only find me asking what that means and something else in Chinese.
I don't know if this will help, but I found a couple things regarding the Cryptographic Subsystem:
One article from IBM discusses it as part of their CPUs. The C.S. (Crypto Subsystem) on their chips runs at a certain clock speed.
I'm including the google cache for word reference as well as the original article:
Another thing I found was the detail of the C.S. in the patent which is "a secure subsystem to prevent unauthorized
replacement of a storage device containing a boot-up executable code by
establishing a secure path between a secure boot device and a host
processor based on an electronic keying mechanism"
Maybe somehow the C.S. was affected by the O.C. to the boot device?
Only a theory, but I hope the information helps.
There are advantages to overclocking from windows too actually. Other than being lazy that is.
When you're booting your system at an overclocked state, chances are your vrm's can't keep up at powerup for some reason I don't know. So your oc will fail. That I assume is the reason that gigabyte boards shutdown and restart when changing such settings - to avoid the problem.
If you oc from windows, the changes being made are significantly less than from 0 to preset.
Regarding the programs - I have some comments on them. They might be brilliant in some situations, but they don't nessecarily work.
For instance on my work pc, a hp dc7800 with an e6750, setfsb can only read the fsb, it can't set it - no matter which of the 3 types I tried (mmt, slp and the other one). I suspect hp deliberately did something to prevent it from working. So on oem systems you may not find the solution you were looking for in software.
And atitool didn't work very well with my 8800gtx. It could set the gpu and mem speed, but the artefact check isn't able to figure out if the shader speed is too high. So even though it'd run 20 minutes scanning for artefacts in atitool, a 3dmark test would crash at the nature scene when the lights were rendered. So don't rely on the button to automaticly find the best frequency if the shader is linked to the gpu speed.
ps. on all ati hd48x0 cards I've seen so far, the max gpu setting available in overdrive (790 or so) seemed stable - no need to run the check :)
Besides things like cool'n'quiet and whatever Intels version is (Speedstep?), why would chipset manufacturers even open-up software interfaces for overclocking, when for so many years they were completely against it? Now days anyone can click the "+" in Gigabytes Overdrive and gain a few extra percent. Must make it hard to sell processors in granularities of a couple hundred MHz when you can overcome that through software without any changes to voltage or mupltipliers.
Anyway, good article. Its nice to see the 3rd-party software that can be used, especially if you have no options from the hardware vendor.
My guess is this--your FSB chipset has different timings/subtimings (like ram does) that are invoked when setting the FSB in the BIOS depending on what frequency is set, and these are referred to as "strappings" (I don't know exactly why, but the reference to "bootstrap" in your error code makes me think this is referring to these "strappings")--some timings/subtimings that work at one frequency (one strapping) are too tight for higher frequencies (in another strapping), so as the FSB is changed in the BIOS, a new strapping is used for the new FSB--it might be that when OC'ing your CPU in the BIOS, you got into a regime in your FSB where the timings just don't mesh well for whatever reason (like there's no good set of timings on the FSB), and some errors are encountered relating to the strapping, spitting out that error code. When you OC in windows, the strapping for the FSB initially set in the BIOS is used, regardless of how the FSB is changed in the software (i.e. the timings of the FSB chipset are not changed at all when increasing the FSB in the software since the FSB was not changed in the BIOS at all)--my guess is that the strapping corresponding to the FSB in the BIOS just happens to work better for your clocks, which is counter-intuitive to me, but then again, nothing works exactly like you'd expect... That's my best guess...