Allow me to preface this with the statement that 90% of this problem has been mitigated, but I am still getting this one random pop/click.
 
The specs for the laptop are Win7 64bit running on a Duo-Core 2.5 with 4 GB of ram.
 
I use ASIO mode.
I have NOT disabled speed step. My only other choice is "lowest performance" mode.
I have enabled processor power to 100% for both minimum and maximum.
I have disabled power management for the PCI, which I believe is where my TI Firewire chip set ExpressCard is inserted.
I have disabled the network card, wireless LAN, and firewall.
I have disabled the audio in device manager.
I have disabled the anti-virus, malwarebytes and ccleaner.
I have disabled scheduled defrags.
I have removed anything from my startup folder that may interfere and disabled any program that I can think of that may be doing something in the background.
I use a TI chipset for my firewire to connect my interface (Expresscard or something, can't remember, as I had to by two different ones for two different laptops).
 
Is it settings or something else I am missing.
 
LatencyMon says I am doing good...no real spikes over the green. I will have to run it again and wait for the pop/click to appear and see if it responds.
 
Thanks for any ideas you come up with.
 
 
 
 
 
 
 

if you have any budget, bump the ram up to  at least 8 gig to take advantage of your x64 os
you can also try running wdm instead of asio driver mode, or vice-versa, you didn't say which you're using
hth

Are the pops really random, or do they occur, say, at splitpoints? So it's not a question of having splits not at zero crossing?

4GB is a shockingly low amount of memory for a 64bit OS. Open up Task Manager, check the Performance Tab, and make sure you aren't up at the limit of your Physical Memory. If you are, that'll be a non-starter for high-performance work.
 
You may also just want to increase the ASIO buffer size for your audio drivers. Dropouts are usually because Sonar isn't able to fill the buffer as quickly as the sound card requires, but a larger buffer gives Sonar a bigger time window in which to meet this need.

I have  to reduce the the buffer to 256, as I am using TH2, or at least trying to. If this is the culprit, then it is back to mic'ing.
 
I can check on the performance as you suggested.
 
I do not understand "spitpoints", can you educate me on what to look for?
 
TNX

By 'splitpoints' it means gaps between clips, where the waveform won't be continuous. When they are played back there can be a small click sound as the audio engine transitions between 2 different waves in the space of a single sample. This will only apply to you if you're hearing the noises when playing back previous recordings.
 
In your case, I suspect your computer is not powerful enough to handle a 256 sample buffer, an external interface, and a fairly demanding VST at the same time. What does your CPU usage look like when this is happening?

O.K., thanks.
 
No, all I was doing was learning how to use, and experimenting with TH2, and no recording was taking place, or not tracking was taking place.
 
I will check CPU usage.

If the buffer size issue does not help, try to disable all the settings which affect power.
This is sometimes difficult on laptops. Choose the high performance power profile and then go in an edit it so that both min and max CPU performance are 100 %.
Boot into the bios and disable any speedstep or turbo boost features. You do not want any CPU throttling to take place.
Also remember than some laptops just cannot do real-time audio.
 

I am almost positive I have addressed the throttling and power issue, to your expectations.
 
And yes, it may just be the laptop.
 
I will double check and edit my OP.

Disable battery helped me on one.