|
Lasereth, I have had that problem only once, and it was the motherboard that caused it. It was the ASUS A7V, which was a bitch of a board. Other than that, I never, and I say this in all serious, never have BSODs from a tested max overclock, run daily. I don't reboot for months at a time either, aside from occasional updates.
If you speed it up, test various parameters for a few weeks, then you get years of daily OC speed out of it. Test the obvious first, the CPU cache with highest multipliers, then lower the multi and test the buses. Next test the northbridge, where applicable. After that, bring the speed up on both bus and multi and run all those tests again. Once you've done that, checked hardware temps (I do them manually) and checked voltage stability under load, you have your set-in-stone overclock.
If you're bored in the evenings or in college, it's easy. Now that I'm working nights, there is no way I would have time for all of that, however.
I hardly use my machine now and I don't game anymore, so I'm running stock. As Shauk said it can eat electricity, so for me now the benefits are not there. But a couple of months ago, I was running 3.6GHz on my Q6600 for over a year. Never had one instability, even installing windows and linux.
__________________
We contend that for a nation to try to tax itself into prosperity is like a man standing in a bucket and trying to lift himself up by the handle.
-Winston Churchill
|