Stability problem on my e6600

[Gooses]

My computer appears to be hanging (Just seems like it locks up, display still there but can't do anything)

I had my e6600 overclocked to 3319 mhz a 1475 QDR, I had it at 1.475 vCore i think and a 1.45 NB, and I could run OCCT for 20 minutes (Was just doing quick tests, nothing conclusive) but I was doing that on an OC profile I made that is stripped from all start up programs pretty much so, I rebooted and went into my profile and during start up while everything was loading it locked up. Any Ideas?

[Dadi_oh]

Originally Posted by Gooses

My computer appears to be hanging (Just seems like it locks up, display still there but can't do anything)

I had my e6600 overclocked to 3319 mhz a 1475 QDR, I had it at 1.475 vCore i think and a 1.45 NB, and I could run OCCT for 20 minutes (Was just doing quick tests, nothing conclusive) but I was doing that on an OC profile I made that is stripped from all start up programs pretty much so, I rebooted and went into my profile and during start up while everything was loading it locked up. Any Ideas?

So just to be clear are you saying that you have been running stable for a long time and then, without changing anything, it has become unstable?

Or are you saying that as part of your recent overclocking process you only checked stability in a stripped down session but when loading all drivers and programs it locks up?

If it were the first case (a sudden change in stability) then it could be a degrading component.

If it were the second case then there may be a particular driver or program that is reacting badly to the OC.

Either way, try backing off on the overclock to factory defaults and then gradually increase the frequencies until you can recreate the lockup. Only OC one thing at a time... for example keep memory frequency at stock or less while increasing the CPU FSB.

[Gooses]

Recent overclock.

And, if I find at which OC the problem happens? Do you have a solution THEN? or is this just a way to get a stable OC by cutting it down some, even though it is an program problem and not my hardware having issues?

[sswilson]

Originally Posted by Gooses

Recent overclock.

And, if I find at which OC the problem happens? Do you have a solution THEN? or is this just a way to get a stable OC by cutting it down some, even though it is an program problem and not my hardware having issues?

If a program behaves badly under OC, but works fine at stock speeds then there is a problem with the OC.

It could be that there's some higher memory functions going on during startup and a slight boost to mem voltages might fix the issue. Same goes for NB voltage.

[Dadi_oh]

Originally Posted by sswilson

If a program behaves badly under OC, but works fine at stock speeds then there is a problem with the OC.

It could be that there's some higher memory functions going on during startup and a slight boost to mem voltages might fix the issue. Same goes for NB voltage.

What he said

It sounds to me that the issues are related to the HW. SW will run the same at OC frequencies as at default frequencies (albeit faster).

You just need to make the appropriate adjustments in frequencies and voltages to get to a stabel overclock. Takes patience and lot's of testing but that's the fun part

[Gooses]

Thanks guys, I boosted my NB another .05 and my mem .1 and I booted with no problems, have been running OCCT for an hour, also played Spore for a bit, no problems yet, OCCT is running a 6 hour test, so hopefully I got it running stable at 3.26 ghz, load temp of 53.

[Dadi_oh]

Originally Posted by Gooses

Thanks guys, I boosted my NB another .05 and my mem .1 and I booted with no problems, have been running OCCT for an hour, also played Spore for a bit, no problems yet, OCCT is running a 6 hour test, so hopefully I got it running stable at 3.26 ghz, load temp of 53.

That's the ticket...

Finding the right mix of frequencies, voltages, and temps is what it's all about. And a good load temp you have so you might even get more out of it.

[sswilson]

Originally Posted by Gooses

Thanks guys, I boosted my NB another .05 and my mem .1 and I booted with no problems, have been running OCCT for an hour, also played Spore for a bit, no problems yet, OCCT is running a 6 hour test, so hopefully I got it running stable at 3.26 ghz, load temp of 53.

Good to hear!!

[Gooses]

Originally Posted by Dadi_oh

That's the ticket...

Finding the right mix of frequencies, voltages, and temps is what it's all about. And a good load temp you have so you might even get more out of it.

Yeah, well I am planning on WC soon so I can push it farther without worrying about the temps, hopefully 3.6 to 4.0 not sure what you can force an E6600 when you try hard enough lol

[1Tanker]

Originally Posted by Gooses

Yeah, well I am planning on WC soon so I can push it farther without worrying about the temps, hopefully 3.6 to 4.0 not sure what you can force an E6600 when you try hard enough lol

More realistically...3.4-3.6..even with water. It takes exceptional chips to hit 3.8-4.0 stable. GL