Heh. I routinely screw up stuff like that. I screw up in real life too. Yesterday I couldn't find my wallet. Tore up the whole house and finally found it in the trash bin outside.
 
I have never had any issues with any of the updates. Kingston is the best one so far, just smokin.

I can't be positive that it's due to Kingston, but in the short time since the update I've had a lot of crashes (SONAR will close...).
 
In particular, while editing thirteen tracks of drums using Selection Groups, I have had one crash after another while simply cutting sections and sliding them over to align with the beat. Like a dozen crashes while working on one project. Not so good.

That is a fairly normal editing procedure. If slip editing really has had a fatal bug introduced,
we should hear an outcry from everyone pretty soon.
 
From personal experience, I would suspect a failing RAM stick.
Kingston's claim to fame is increased performance, so it almost certainly is using
memory differently, which may mean it makes use of more memory if it finds it.
As a result, it may be hitting a faulty section on your 32 GB that so far
has never seen any action.
 
Microsoft has a free memory testing program that must be downloaded onto a floppy disk
(I hope it works with CDs by now).
You must then boot from that disk. Select the most thorough test and leave it running overnight.

I would expect the entire OS to BSOD with a memory issue.

First thing I would do is look in the windows event viewer. Also rule out problem plugins (starting in Sonar safe mode). Make sure windows update has been run recently, and audio interface firmware and drivers are updated.

Or give specific steps to reproduce a possible bug.

Kingston is great for me. I've logged lots of hours with no gripes, just fun.

jpeterson, thanks. I recently did a full memory scan which found no problems.
 
Dr. A, also thanks. All drivers are up to date. I will check the event viewer and try safe mode and report. I also have a SONAR Problem Report in the works. I will also try doing the same thing in a fresh project to see if I can reproduce it.
 
Additional information: While I was editing the selection group of tracks, moving the clips became slower and slower. That is, I would click and drag the clip to align the drum hits with the beat, and it would take longer and longer to actually move, up to ten or twelve seconds in the end. Splitting the tracks and slip editing to get crossfades worked at the usual speed. Performing Bounce to Clips on the thirteen tracks restored things to normal. Also, just before each crash, I noticed that the Split tool cursor or the Slip Edit cursor did not change back to the normal Smart Tool cursor. That was always the precursor to a crash.