2600-k  3.4 GHz - When I overclock to 4.2 GHz (just the CPU chip no Ram or Graphics) all is good with intel burn test; passes everytime (running the Short Burn Tests).  No temp issues. 
 
However, when I run Sonar for about an hour or so I get the BSD (Sonar not being stressed at all).
 
With no overclocking I never get the BSD everything runs very smooth.
 
Mentioned it to Sonar Tech Support (called on another unrelated matter) and they said that Sonar is not set up for that.
 
Would Sonar make a difference for Overclocking the Chip?
 
Do I just need to back off a little more on the Overclock say from 4.2 GHz to 3.9 GHz or should I just forget about the whole ordeal and just use the factory settings (since they work)?
 
Could I be doing something wrong or is tech support right? If anybody would help, thanks.
 
 

Why overclock in the first place?

Your computer will be able to handle ANYTHING that Sonar can chuck out, provided you don't start pissing around with overclocking!

"Is Tech Support right?" Do you really need an answer?

Mentioned it to Sonar Tech Support (called on another unrelated matter) and they said that Sonar is not set up for that.

 
If you're going to over-clock, you need to be 100% sure the OC is rock-solid stable.
If it is... then any app (including Sonar) will run stable.
 
Are you using a motherboard that has settings to ensure a stable OC?
ie: You'll likely need to increase Vcore to achieve stability.
This will raise temps... and thus why you want a quality/substantial 3rd-party CPU cooler.
The stock cooler is "adequate" for stock speed.  When over-clocking, it's not up to the task... and it's far too noisy.

a 2600k should be able to run @ 4.5GHz all day long
assuming
1) you know what you are doing
2) you have good cooling (not intel fan)
3) your ram is decent (should not be OCing this anyway)

Sonar or any other program has nothing to do with a stable OC. the tech guy is wrong..
at best it just shows your OC is not right

jcschild


a 2600k should be able to run @ 4.5GHz all day long
assuming
1) you know what you are doing
2) you have good cooling (not intel fan)
3) your ram is decent (should not be OCing this anyway)

Sonar or any other program has nothing to do with a stable OC. the tech guy is wrong..
at best it just shows your OC is not right

Thats what I thought. 
 
Right now my system can handle anything sonar can throw at it (at this time but I'm not running many tracks at all).
 
I'm not using a stock cooler but I probably just don't know what I'm doing. 
 
IF I do need to overclock; due to more complex projects; I will look into what is going wrong a little closer.
 
But right now as Bristol said I will leave well enough alone.
 
I appreciate everyone's help!  Just wanted  to make sure it was not overclocking per say.

You should call intell tech support for info about the memory you are using. I have an i7 920 cpu and I had to downgrade my mem from 1600 to 1033 bacause of the same problem with Sonar....not anymore...

You should call intell tech support for info about the memory you are using. I have an i7 920 cpu and I had to downgrade my mem from 1600 to 1033 bacause of the same problem with Sonar....not anymore...

 
FWIW, You don't need to call Intel support.  
Test the RAM to be sure all is well.
With a current gen motherboard... and the right RAM... you can run the RAM stable at 1600MHz
As was mentioned, you don't want to over-clock the RAM.  That's a recipe for major instability...

gcruz


You should call intell tech support for info about the memory you are using. I have an i7 920 cpu and I had to downgrade my mem from 1600 to 1033 bacause of the same problem with Sonar....not anymore...

The ram is G skills Rip Jaws 1866 9-10-9-28 1.50v DDR3-1866 (4  stick set) made for my Z68 mother board with sandy bridge.  Everything was compatible.
 
I have it set to Auto setting that's giving a clock of 1600 with no issues (without CPU overclock).
 
When I was overclocking I also had it set to auto not overclock the ram.
 
Jim:  Yes - I have done memory test and all passed. 
 
Also, my mother board says that it can handle that 1866 ram with an overclock.  But I choose not to overclock so auto setting puts it at 1600.
 
I'm not saying it is not a ram issue it very well could be. 
 
Why is Mother board auto setting it at 1600 when it can go to 1866?
 
If it's the ram, wouldn't the problem still be happening all the time; overclock or not on the CPU?
 
 

If it's the ram, wouldn't the problem still be happening all the time; overclock or not on the CPU?

 
Agreed...
 
DDR3 is a common culprit.
If you're sure it's OK, move on to the next variable.
 
My guess is that you need to increase Vcore.
If you haven't done that... it's almost certainly the problem.

Jim Roseberry

If it's the ram, wouldn't the problem still be happening all the time; overclock or not on the CPU?

 
Agreed...
 
DDR3 is a common culprit.
If you're sure it's OK, move on to the next variable.
 
My guess is that you need to increase Vcore.
If you haven't done that... it's almost certainly the problem.

I was thinking the same thing but I don't want to get any hotter because my coolers is not that good.  Its got aluminum base, without the copper heat pipes actually touching the chip like some of the so called better ones do.
 
Anyhow,  If I lower change the overclock from say 4.2 down to 4.0 keeping Vcore the same that would be the same as raising the Vcore for the higher clock rate without raising the temp.  Right?
 
And if I run the High setting "IntelBurn Test" (thats the one from AgentGod) and it passes that;  why would Sonar still be causing problems (Sonar can't stress the CPU like a burn test)?  This I can't understand?
 
Thanks for you help.