DreamForecast

slartabartfast
It seems there may be two issues here that may not be related. One is that you are having clicks and pops (presumably from dropouts) and the other is that you do not believe working random access memory is being assigned to Sonar and the various plugins appropriately.

How did you determine that your plugins are begging for memory?

1. I think you may be right.  However, despite the pops and clicks, I am not getting dropouts, which is weird.
2. I think the plug-ins need memory because
- they keep killing notes when I play too much (though those are fully polyphonic synths).  Also, there is a crackle sometimes when I play them. 
- a latency delay starts to develop (now I'm not sure if this is related to RAM or Sonar or soundcard -- sorry for being such a noob and thanks for putting up with it xD)
 
Yeah...

As Tom stated above it doesn't sound like your issue is specifically ram related. I would suggest that you load up a East West Quantum Leap synth or two in a new project and I'm guessing you will see an increase in ram usage. I believe your issue is related to configuration of audio and midi buffers. But there are already people here who can walk you through that better than I.

If sonar is dropping midi notes increase the midi buffer size in settings> midi there us a setting something like prepare midi. I usually set mine to 500 or 1000. This will help eliminate midi dropped notes.
 
I'm mobile at the moment so I can't look up the details. 
 

You should be able to tell if it's processor related or not by looking at the CPU usage meter on the control panel. As soon as one or more of the cores start peaking into the red, you're going to get pops and clicks. 
 
The latency delay could be related to plugins that use "look ahead" technology, for instance the Concrete Limiter. I would try turning off your effects one by one to determine if any particular ones are causing the latency. 

sharke
You should be able to tell if it's processor related or not by looking at the CPU usage meter on the control panel. As soon as one or more of the cores start peaking into the red, you're going to get pops and clicks. 
 
The latency delay could be related to plugins that use "look ahead" technology, for instance the Concrete Limiter. I would try turning off your effects one by one to determine if any particular ones are causing the latency. 

Thank you, it is indeed the Transient Shaper, one with look ahead.  You were spot on!  Thank you so much again!

Do re-enable the pagefile for the OS disk only, as system managed. It is needed for windows to do what all it does. Including recording data about errors.
 
 

sharke
You should be able to tell if it's processor related or not by looking at the CPU usage meter on the control panel. As soon as one or more of the cores start peaking into the red, you're going to get pops and clicks. 
 
The latency delay could be related to plugins that use "look ahead" technology, for instance the Concrete Limiter. I would try turning off your effects one by one to determine if any particular ones are causing the latency. 

Just a side point. Sometimes when my system is sitting idle my HP warning flag alerts me that I have high system or CPU usage... Really?! When no programs are running?! Something's going on in there!