cannot find N56v manual, so n56vb says something about camera...you have one?
Try a usb mouse yet?
and any issues with Nvidia's GeForce GT 630M GPU and cake walk Sonar on these forum past posting data bases? 
 
I think turning off redundant devices helps solve many problems in bios, not so much in windows control panel/system/devices, as windows still loads the drivers for those devices if not done in bois or detects them. and then disables them, when selected or made to do so ...but in bios when disabled, no driver is loaded in windows, which could help solve or reduce issues?...Just saying.

skitch_84
Also, I just opened some other projects and the issue seems to be isolated to just this one project. What in the world does that mean!?

Just out of curiosity, if you hit the global plugin bypass ("E") does the issue go away? It almost sounds like you have a plugin with look ahead and a buffer that is too small. Some plugins are meant to mix only, and require a larger buffer; although 512 is about as high as I have needed to mix and you are already there.
 
If the above doesn't show a plugin issue, another thing to try is to save the project first with a new name. Then start deleting tracks one by one (playing back between each) to see where/if it resolves. Another option that works for certain situations is to select all tracks and in the Track View, bounce to new tracks. There have been a few cases where a bad track will hang that bounce function on the bad track itself.

By default there is a setting that allows to use multiple projects in Preferences.
 
If you open one project, then open another - this first is hidden behind but may use resources.
Close one before opening next - or turn off "File - Advanced" "Allow only one project open at a time" checkbox.
 
just a thought....

Update:

I figured out the cause of the problem. Well, let me reword that. I figured out the plugin that was causing the problem, but I still don't know what the problem was exactly. 

So, I use u-he Satin Tape Emulation on every mix. I generally put an instance of it on every track as well as on my premaster bus. For some reason, that instance on the premaster was the cause of all this trouble. If I turned it off, the crackling would go away. I turn it back on and it would come back. It's very odd because I've done this exact same thing on numerous other mixes and never had a problem. So, my solution was to remove it from my premaster bus, bounce all of the tracks to a new track, then put the "premaster" Satin on that new track in order to get that 'tape glue' on the full mix. Same effect, just one more step is all. 

I'm curious if anyone has any ideas as to what the actual issue was. Anyone? :)

have this on one project with a external VST plugin on opening the project.
when I turn the VST off and on again, extreme cracks are gone.
I would not try bouncing to tracks as I'm not sure if it will add 1 roundtrip of latency to the audio files, like you would get on an export.
First thing I'd try is to remove the plugin, then save the project with a new name to a new folder, as a bundle file.
Then open/close Sonar and add the plugin again and see if it's gone.
If not, I can emagine it must be impossible for the music software industry to make all software out there compatible to eachother...

skitch_84
Update:

I figured out the cause of the problem. Well, let me reword that. I figured out the plugin that was causing the problem, but I still don't know what the problem was exactly. 

So, I use u-he Satin Tape Emulation on every mix. I generally put an instance of it on every track as well as on my premaster bus. For some reason, that instance on the premaster was the cause of all this trouble. If I turned it off, the crackling would go away. I turn it back on and it would come back. It's very odd because I've done this exact same thing on numerous other mixes and never had a problem. So, my solution was to remove it from my premaster bus, bounce all of the tracks to a new track, then put the "premaster" Satin on that new track in order to get that 'tape glue' on the full mix. Same effect, just one more step is all. 

I'm curious if anyone has any ideas as to what the actual issue was. Anyone? :)

It's probably a dodgy plugin (sometimes you don't find out till much much later), there are probably new conditions that are making it behave that way.
 
Is it 32 or 64 bit? Are there any updates for it?

The advice in post #9 may still apply and as you now think it's a plugin issue I recommend running Windows update several times and checking the optional updates (could be a library issue).
 
You may also consider a VST reset followed by a rescan:
https://www.cakewalk.com/Support/Knowledge-Base/2007013315/SONAR-X3-Full-VST-Rescan-Recommended-for-Upgraders
 
 
Ta

Splat

skitch_84
Update:

I figured out the cause of the problem. Well, let me reword that. I figured out the plugin that was causing the problem, but I still don't know what the problem was exactly. 

So, I use u-he Satin Tape Emulation on every mix. I generally put an instance of it on every track as well as on my premaster bus. For some reason, that instance on the premaster was the cause of all this trouble. If I turned it off, the crackling would go away. I turn it back on and it would come back. It's very odd because I've done this exact same thing on numerous other mixes and never had a problem. So, my solution was to remove it from my premaster bus, bounce all of the tracks to a new track, then put the "premaster" Satin on that new track in order to get that 'tape glue' on the full mix. Same effect, just one more step is all. 

I'm curious if anyone has any ideas as to what the actual issue was. Anyone? :)

It's probably a dodgy plugin (sometimes you don't find out till much much later). 32 or 64 bit? Are there any updates for it?
The advice in post #9 may still apply and as you now think it's a plugin issue I recommend running Windows update several times and checking the optional updates (could be a library issue).
 
Ta

I just checked u-he's site and it appears I have the latest version. There are 32bit and 64bit versions available, but I generally only install the 64bit versions, so I should be using the 64bit one. I'll check for Window's Updates as well. If I experience this in another project, I'll send a message off to u-he and see if they can track down the issue, assuming it's a problem with the plugin. 

Cheers - sorry I edited my post above there is further advice (VST reset) - thanks...
I strongly recommend you check out all the other advice as well in #9 just to be sure there isn't another factor.
 
Cheers...