Hi abacab,
Thank you for your excellent suggestions. I spent the day following up on them; I've learned more about Win10 today than I knew when I started, but I still don't know enough...if you know what I mean.
 
Since nothing I did seems to work, I uninstalled Sonar Platinum, and reinstalled with my anti-virus checkers off, but the result, and the message: "SonarPlt.exe has stopped working." continues you appear with this newly downloaded copy.
 
I have also have Sonar X LE, Sonar X3 Producer (x64), and Sonar X3 Studio (x64) on my computer, so maybe those will have to go too, and then I should uninstall/reinstall Sonar Platinum? Could there be a conflict with those other three versions?
 

booksmusic
Hi abacab,
Thank you for your excellent suggestions. I spent the day following up on them; I've learned more about Win10 today than I knew when I started, but I still don't know enough...if you know what I mean.
 
Since nothing I did seems to work, I uninstalled Sonar Platinum, and reinstalled with my anti-virus checkers off, but the result, and the message: "SonarPlt.exe has stopped working." continues you appear with this newly downloaded copy.
 
I have also have Sonar X LE, Sonar X3 Producer (x64), and Sonar X3 Studio (x64) on my computer, so maybe those will have to go too, and then I should uninstall/reinstall Sonar Platinum? Could there be a conflict with those other three versions?
 

Having multiple versions of Sonar installed usually works fine, and is recommended, as they each install to their own directories.
 
Sounds like you have a weird problem for sure.  Hopefully someone will come up with a better idea!  Hang in there, the answer is usually in the last place that you look :-)
 
I will say though, that if your setup worked fine until a couple of weeks ago, I would really look harder to determine what change happened to your system or software that broke Sonar,  and then eliminate it.
 
The situation would be totally different if you were setting it up for the first time.  Then there would be plenty more questions about audio drivers and configuration, etc.  But your system did work at one time originally ...

booksmusic
"...a box is displayed for a moment on the lower right of my screen with this info:
"ASIO4All.v2-SONAR.PLT 512 Samples 44.1mhz".
That's it, and I have no idea of how to fix the problem..."

"ART X-Connect gives you high-quality 16-bit/48kHz recording quality"
 
This mismatch is probably what started the problem.  Knowing that, someone here may know what went wrong.  It sounds like you have compounded the problem by trying all those other fixes...but maybe not.
 
 

Try this:
computer off
unplug the ArtX
Boot computer
When fully booted, check the little windows speaker icon in the lower right.  Is there an X over it?
If there is, go into Device Manager and re enable your Realtek driver.
Do not plug in the ArtX at any time...yet.
If not, right click the icon and see what driver windows is using.  It should be just the Realtek.
 
Open Sonar.
 
If you can get to the start screen, do NOT open any project. 
X out the start screen (just close it - x in top right corner)
 
Go to Preferences - Drivers settings.
What is your bit rate and sample rate set at?
What driver, if any, is available in the drop down?
 
Let's start with that.
 
Your goal is to get that far, and set the Bit rate and sample rate to 16 and 48.
I don't know if Realtek will let you do that...hopefully it will.
Let me know how far you get.

I will add this...16/48 is a very odd combo.  I doubt any of your current projects were recorded at those settings.  You will have to open all those with your ASIOforALL driver.  New projects you can use the new cable/interface...but you will get no sound, or crashes, when you have a mismatch like that, and you are asking for a world of hurt in the long run.  It sounds like you want to record guitar with that cable...you can but all your projects must now use that and only those settings - 16/48.  You will not be able to use that cable to record guitar into any of your current projects.
 

booksmusic
At the time this happened I was trying out a new ART TConnect USB guitar 1/4inch-USB cord. I had set the audio input to the asio4all driver but got not sound from my speakers.

Hmmm... Just re-read this comment.  Sounds like a good place to look "at the time this happened".

Thanks for the help.
 
You're right: the problem began when I tried to use the ART guitar/usb cord (supposed to be plug and play) to record guitar audio into SonarPlt. I probably made the mistake of selecting ASIO4all as the driver when I couldn't get any sound when attempting to record with that setup. After that I unplugged the usb end of the cord and shut down Sonar. I probably should have gone back into Preferences and switched back to the original driver before shutting down, but didn't. It was after that, that I couldn't start Sonar again - ever again, as it turns out... So I can't open Sonar to make any changes - hence this thread and cry for help.
 
Also I've gone to Device Manager and re-check every driver for every device and they are all up to date and working. I don't understand the advice to "re-enable your Realtek driver", I don't know where to look for that in Device Manager. I've searched my computer, without finding any reference to Realtek - so please clarify that instruction. And although it is true that when I start the computer I get a little red-x on the speaker icon in the tray until I turn on the speakers, after which it disappears.
 
[Still waiting for word from the Tech Dept!]

booksmusic
Thanks for the help.
 
I don't understand the advice to "re-enable your Realtek driver", I don't know where to look for that in Device Manager. I've searched my computer, without finding any reference to Realtek - so please clarify that instruction.

I believe that was a general reference to your on-board audio.  I think many modern PC motherboards that have integrated on-board audio make use of Realtek audio processors and drivers. I see that you have a Sound Blaster. Is that an integrated on-board audio solution for your PC, or an add-on card?
 
Anyway, if you look in Device Manager under Sound, Video, and Game Controllers you will see all of the audio devices currently connected to your system. 
 
Uninstall ASIO4all if you haven't already. I would then follow-up by unplugging any external audio hardware, USB audio devices, etc.  Then go into Device Manager and right click on any audio devices remaining. Select uninstall on them and then reboot.
 
Look see if there is anything showing up now in Device Manager under audio devices after the reboot.  If there is anything left it is probably on-board audio that automatically re-installed during the reboot.  You can disable it in device manager or reboot to your system BIOS setup and disable the on-board audio there.  Reboot.
 
Try this again before starting Sonar:

booksmusic
Hi Chuck,
Thanks for the help. I tried a rename of the AUD.Ini file and deleting it, but I'm still getting the same result.
Regards,
Reynold

 
Now try Sonar again.  See if you can open preferences.  If it works, now try enabling the on-board audio and see if Sonar still launches.  At this point just make one change at a time & then test. If you have an issue, back out the change.

The main issue here is that your USB guitar cable is a one way audio device, it is not full duplex.  So in ASIO mode you can enable either the Soundblaster card, or the cable, but not both at the same time.  It your guitar bable has a WDM driver, and Soundblaster has a WDM driver, and can be set to 16/48 to match the guitar cable's ONLY available setting, then you are in luck.  Until that happens you will not be able to hear anything from the guitar. 
 
That fact that Sonar will no longer open at all makes me think the Driver settings that are currently residing within Sonar, which are inaccessable to change, are preventing Sonar from fully loading.  Now, if you can figure out where those settings reside ie. in the .INI file or some such accessible file openable and editable in Notepad...then you can perhaps salvage this problem...but I don't know how to do that.

USER32.dll is caused by a few things, viruses, registry corruption and a damaged DLL library.
A damaged DLL library is more often than not caused by a corrupt registry or virus, so essentially its 2 things.
once you rule out virus (Malwarebytes - Run it) as im wondering about where you downloaded ASIO4ALL from ?