I think you might need a little perspective shift on how overclocking works at a metaphorical level.
You have a car, you have a set speed you want it to run at and when you hit the pedal it revs up to hit that speed every time.
When you start the car, it gets a bit of juice. This is your idle voltage~ it purrs. If you can boot into Windows, you have usually enough voltage to start it up. This is important to note, because when you increase your multiplier you're increasing your Turbo~ not the original clock of the CPU. You've given it enough juice to recognize this setting and sit on itself purring.
When it's time to hit the gas, you engage your turbo mode~ at this point you now need fuel to power this mode. Like injecting gasoline into the engine. Your motherboard at this point will inject fuel~ while at the same time trying to regulate it so fuel is going in constantly. With most motherboards though~ this may not be the case and the voltage can fluctuate.
If you don't have enough fuel to power your turbo mode, the car shuts off~ pbbblrrlttt~ lights go out, engine whines down~ hear a hissing sound from under the hood. You just blue screened. You may need more fuel. Though at this point this is usually the case with this chip, it could be your RAM having errors or other hardware.
An immediate blue screen on load, for me~ is usually a sign of not enough voltage set on the motherboard to hit that gas pedal and engage the turbo~ (vroooom~ x3) but if it takes a bit of time before you get the BSOD, look at your voltages.
Are they dropping a lot on load than on idle? You may be suffering from V-Droop. What this means is you have enough fuel going into the engine at idle, but when you hit the gas~ your motherboard isn't able to keep pumping that same amount to keep it running~! So it sputters and dies.
At this point, though you may have the magic number to keep your engine running~ because it DROPS on load, you went under the cutoff needed!
In my case, 1.34 was enough to keep the engine running on load, but if I set my voltage to 1.34... whenever I went to load, it'd drop to 1.32~ sometimes lower... and pbbllltttrrt~ it would blue screen.
So this is where your LLC (Load Line Calibration) or Vdroop control comes in. By engaging this to a slightly higher setting, you allow your super cool motherboard to actually resist this voltage drop while also aggressively setting your idle voltage a little higher. Making the idle and load voltages 'tighter'. So when you hit the gas~ it doesn't drop as much.
For my voltage to be stable~ I had to increase it to Ultra High~ leaving it at high, at the same voltage~ I'd BSOD on Prime95 everytime, not because of my set voltage, but because it'd drop every single damn time I hit the gas! I could technically keep increasing the voltage so that it was so high, it wouldn't drop under the cutoff when I needed it... but that's excessive~ with LLC I don't need to overcompensate for Vdroop!
The important thing is to get your motherboard to a point you can even run Prime95 LONG enough to see these voltages, and see your temps! If it's shutting off so soon that you can't even get there, increase your voltage. When you can finally monitor the voltage drop~ play with LLC, and then lower your voltage so it's tighter.
Hopefully you'll hit your sweetspot, and you'll be beating people on the mountains of Akina or Wangan in no time. Don't try to cut me off though, or I'll dust you. :3
Edited by Inverse - 6/21/11 at 12:16pm