A few issues with X3...

Hey all,
 
I've been having a few strange issues with X3; was wondering if anyone could help me out or was experiencing the same things.  I'll do my best to explain.  Firstly, my specs:
 
Sonar X3 (I've installed the X3b and X3c updates as well)
Alienware 14 laptop
Windows 8.1/64-Bit OS
Intel i7,  2.4 GHz processor
Lexicon Lambda USB interface
Using ASIO drivers
 
It should also be noted I have done a clean uninstall/reinstall of Sonar, my computer is up to date, and I have the latest drivers for my interface).
 
Problem 1:
 
After playing sound through any other program (WMP, Xbox Music, etc), upon reopening Sonar, it cannot find my audio interface.  I have to delete the aud.ini file and restart my computer and Sonar.  Then all is well in its world...until the next time I play anything through another audio program.  Note:  I have Sonar set to share drivers with other programs, and I have all other playback devices disabled.
 
Problem 2:
 
Sonar is corrupting audio files during import occasionally, presumably by messing up the sample rate (files play back out of tune, as if pitch bent.  Sometimes low, sometimes high.) I have to close Sonar and reimport the file.  It's fine the second or third time I do this.  Note: I have Sonar set to keep original sample rate/bit depth upon import.
 
Part two of this problem is that one day, all I did was open Sonar, and everything played back pitch bent.  Every single file was corrupted, and there was no way to fix it.  I had to start that song (of which I was already up to 24 tracks) completely over, as all the audio was garbage.  Slightly frustrating.  Another note:  I typically record at 24/48k; in rare cases 16/44.1k if it's just demo material.  So, nothing weird or obnoxious, and all well within the capabilities of Sonar and Lexicon.
 
Problem 3:
 
I cannot play back MIDI.  Sonar recognizes my interface as a MIDI device, and I have it selected, but when I go to play back MIDI, not only does it not play, but I then also have issues playing back audio, and have to delete the aud.ini file and restart my computer in order for the audio problem to be solved.  I don't typically work with MIDI, and I use the audio metronome, so for now this isn't an issue.  However, soon I plan on using EZDrummer, which requires MIDI capability, and I'm worried there will be issues here (even though it plays through an audio track, I'm worried the MIDI issue will cause problems before it gets sent to the audio track).
 
So, any takers?  Lol.
 
 

I was not aware of that; a quick scan of the fixes didn't seem to turn up any of my issues, but I will definitely install it and observe from there.  Thanks much!

According to Lexicon's site, the last driver update (the one I have) for the Lambda was for Windows 7, so there is that...but I've run Music Creator, with this interface, on several laptops with Windows 8/8.1 (including this one) without stability issues or bugs.  So I'm presuming the issue is Sonar, or something unique about it versus MC that my interface doesn't like.  Lol.  As far as I understand, though, on a basic level, they're the same (MC and Sonar), particularly driver-wise and with relation to interface communication.  So I don't know.

So, usually when you get play back that is too fast or too slow it is because different programs are seizing control of your interface. 
 
For example, if I open RME tools and use the Spectral Analyzer where sample rate is set to 48 and then open a Sonar project that is at 44.1, the Sonar project will appear to play too fast. The RME is still working at 48 because the RME app doesn't let go of it. The same can happen in reverse causing it to play back too slowly.
 
imho it's extremely unlikely that Sonar is messing up the import process.

That's what I thought too, that it seemed like a typical audio driver issue, but having done clean uninstalls/reinstalls of both Sonar and Lexicon, as well as using ASIO drivers (which I've never had a problem with), something's just weird about this lol.
 
I'm applying the X3e patch as we speak, and then we'll go from there.  Some of these problems (like the pitch bend/sample rate corruption) are very intermittent, so it might be a wait and see game.
 
I appreciate everyone's input!  :)