Can A Roland Interface Cause Sonar Issues?

I have had ongoing problems with X1b-X1d.  The Sweetwater tech wants to try replacing the V-Studio 700 I/O (interface) with a MOTU as a test.  His theory is that bad code in the interface could be causing issues.
 
I did not consider that likely; however, in Jim's thread below which documents X2 issues, he notes that he is using a Roland interface.
 
The verdict: X2a is not good. Unstable and buggy as all heck
 
Here are examples of my issues.  I'd like y'all's thoughts on whether or not they could be related to the interface.
 
Just a few examples:
• Cut, Copy, Paste stop working and require a PC reboot.
• Upon open, a project that was OK before has messed up Ins/Outs (e.g., MIDISPORT C redirected to Fantom, VS700 5-6 redirected to VS700 1-2, etc.).
• Unexplained crashes that are often, but not always, caused by opening the Staff view.
• Audio engine stops working when another virtual instrument (soft synth) is added.  For example, everything is fine with 7 soft synths but all audio stops when an 8th is added.  The number varies. Note that I have 12GB of memory, run in 64-bit, and task manager shows less than 5GB in use.
• Crashes caused by opening a second project for cutting and pasting data.  Sometimes the audio engine stopes; sometimes Sonar crashes completely.

Sorry a driver may work well with an earlier piece of software but not very well with later software or different software. Its a common misconception that just because X works then it must be Y.  I suggest following my advice first before making assumptions. Cheers.

Interesting.  There seems to be a difference of opinion about the effect of Windows versioning on Sonar.  in answer to the questions:

Windows 7 Home Premium Service Pack 1
The PC was built with Windows 7 at Sweetwater
Sweetwater recebtky upgraded me to X1 d.  I don't know the details of the procedure

At one point the entire system was shipped back to Sweeetwater.  They wiped Windows, Sonar, and all my software and reinstalled.  This is also my second I/O unit since Sweetwater has been extremely gracious about replacing and rebuilding everything to eliminate problems.

I am not sure which drivers and firmware we are talking about, but if you guys truly think that could be a problem, I would ask Sweetwater to do it remote so they will know the status.

I was mainly interested in whether anyone thought the type of problems described could be caused by the interface.  I don't want to blow off Sweetwater's suggestion since they are standing behind the system, but installing a new interface is not a trivial proposition since I am using a bundled V-Studio solution (software, I/O, control surface).

So, when you replace the 700r I/O with the MOTU as a "test" does that mean you pay for the MOTU during the test?

Konrad,
 
I'm not prone to jumping on the BAD EQUIPMENT bandwagon just yet.
 
Just a few examples:
• Cut, Copy, Paste stop working and require a PC reboot.
 
Does this happen often or once in a blue moon... if it happens often.... take the 700 r offline and edit by keyboard and mouse for a minute or two.... however long it usually takes for cut copy and paste to stop working.... work about 5 minutes longer just to be sure... if cut, copy and paste don't give up then it could be a hardware issue or a driver issue rather than Sonar Issue.   If I understand correctly, the Console will work independantly of the audio interface and vice versa.  If using the keyboard, C,C and Paste keep on trucking, PLUG IN THE Console and work with it to see if CC and P quits working...  if it does quit working, take the console off-line and see if AUDIO INTERFACE can run independent of the console and work with CC and P...  the process of elimination may be able to point to which piece is the offending one.
• Upon open, a project that was OK before has messed up Ins/Outs (e.g., MIDISPORT C redirected to Fantom, VS700 5-6 redirected to VS700 1-2, etc.).
• Unexplained crashes that are often, but not always, caused by opening the Staff view.
• Audio engine stops working when another virtual instrument (soft synth) is added.  For example, everything is fine with 7 soft synths but all audio stops when an 8th is added.  The number varies. Note that I have 12GB of memory, run in 64-bit, and task manager shows less than 5GB in use.
• Crashes caused by opening a second project for cutting and pasting data.  Sometimes the audio engine stopes; sometimes Sonar crashes completely.
 
This would be another issue I would try removing the console and just using mouse and keyboard to replicate the problem.  Crashes... sheesh ... I've not had one since XP.... it doesn't mean that windows 7 can't have problems, but a clean install is time consuming and tedious. ( I would be more prone to trying to reinstall Cakewalk before redoing Windows...)  Sometimes your registry, over time can get polluted, numbers and files can get truncated.  That would cause crashes and a fresh install of the program can "sometimes" restore the registry settings.