scook
If the project is using 4GB of RAM it should not be swapping to virtual memory if the machine has 8GB. I doubt the project is using 4GB of RAM though, that sound like total system RAM use. As I said before, there may be some DAW treaking which could help.

Unfortunately, this is not the case.  Windows will "Swap out" even if there is ample memory if the focus is lost on the particular Window (i.e. Miniimized) as it sees it as "not in use", and will "remove" it from RAM to the Virtual RAM until it is brought back into "focus".  Swap file gets used, regardless of how much "physical" memory is available.

Not saying that it's not a "Tweak" issue...just saying that, with "Virtual Memory" turned on, it WILL get used...

This may be true but I do not believe swapping would be happening in this case do you?

scook
This may be true but I do not believe swapping would be happening in this case do you?

I tend to believe not...but who knows...

But, I would be doing what you suggested and eliminating the setting issues and every
thing else I could think of before looking there...as, having the optimum settings is
critical on any DAW...

EDIT: also, first thing I ALWAYS look at is CPU 1....if it's going red...either a plugin
is being a HOG, or something else is going on...

Do you have processor scheduling set to "background services" in system performance settings? I was having an issue awhile back and changing processor performance scheduling to programs instead of background services fixed it.
 
Rocky

I'll have to look. I did a defrag last night and some other maintenance. Cleaned out the disk and cache and whatever. I did a full system backup first...so if I have to I can revert back to yesterday. It sounds like something fundamental changed.

bluzdog
Do you have processor scheduling set to "background services" in system performance settings? I was having an issue awhile back and changing processor performance scheduling to programs instead of background services fixed it.
 
Rocky

It was set to background services. I changed it. I'll report back later.

If the machine was working fine prior (no dropouts running at a 128-sample ASIO buffer size), the most likely culprit is either EZD2 or AD2.  Both were literally just released.
 
You might check your DPC Latency (to see if a recent driver update, etc may be misbehaving). 
 
 

I'm going to go ahead and do a restore of my OS. My daw may be fine, but other things are acting strange. I've done something wrong. I'm sure running two instances of EZD2 and one instance of AD2 was the cause of the dropouts. Can any of you guys do that at a 128 buffer rate without clicks or dropouts?

I did 3 simple instrument tracks and MIDI in all 3 tracks and CPU 1 didn't even budge....

And you're on an i7....I'd say something else is the culprit....

My cpu hasn't been bad at all. Anyway my restore has been done, so I'll update later if it made a difference.