I've been having a ton of problems with Windows 10 and Sonar, especially since I received the "November Update" to Win10 over the weekend. I thought it was just updates, but it took over the computer for 5 hours (yet another day's work lost).
 
Win10 seems to obsolete older USB gear, so I removed a bunch of things and "upgraded" to all the latest versions. So, after upgrading to Sonar Pro, buying a neww audio interface and going through all manner of so-called upgrades I now have an unstable system that keeps crashing. 
 
Today I thought I had it sorted after I upgraded ASIO4ALL to version 2.13 - everything was playing along nicely. And then Sonar Pro crashed AGAIN when I reloaded the project. So, I've been able to do hardly any work over the last 3 months. 
 
The support staff at Cakewalk have been helping a fair bit - but everything is getting worse. It started with Sonar just freezing when it launched, or when opening a project. Now, it just plain crashes.
 
Personally, I would like to be able to keep my studio up to date and not have to upgrade/downgrade/uninstall/reinstall/rollback the apps and the OS when I just want to make music. Crazy.

softwhirr
 
Today I thought I had it sorted after I upgraded ASIO4ALL to version 2.13 - everything was playing along nicely. And then Sonar Pro crashed AGAIN when I reloaded the project. So, I've been able to do hardly any work over the last 3 months. 

 
Sorry to hear you are having problems softwhirr, but asio4all is quite likely part of your woes. I would start there as it is notoriously problematic. You would be far better off with a dedicated audio interface with proprietary asio drivers.

Doktor Avalanche

softwhirr
Windows 10 and Sonar? It's cost me a lot of time and money so far, but I hope in the end it's better than keeping an out of date studio. Reinstalling my apps and OS every time there is an "upgrade" is not something we should have to accept. I just want to make music. 

Which is why you should always wait at least 6 months before installing any brand new OS on a critical machine. Unless you don't mind running into issues and involuntary testing other software.

Heh heh - talk about shutting the stable door after the horse has bolted ;) All my other previous updates to Cakewalk stuff and OSs have been fine within 3 months of new versions (I'm talking Win95 to XP to 7 to 10). Based on this it seemed good to continue with the upgrade. I just want to get it working again. 

tenfoot

softwhirr
 
Today I thought I had it sorted after I upgraded ASIO4ALL to version 2.13 - everything was playing along nicely. And then Sonar Pro crashed AGAIN when I reloaded the project. So, I've been able to do hardly any work over the last 3 months. 

 
Sorry to hear you are having problems softwhirr, but asio4all is quite likely part of your woes. I would start there as it is notoriously problematic. You would be far better off with a dedicated audio interface with proprietary asio drivers.

Well, I did have the Focusrite working on Saturday, but after the Win10 upgrade, Sonar crashed on start up. I found "ASIO4ALL" references in the crash log, so I installed the latest version and managed to get it working. But for some reason I can no longer select the Focusrite device within Sonar - not sure how to get it back though - any ideas? 

I'm back off the road shortly and will try again with Win 10 November Update...



Thx all for your suggestions and experiences.

too much dropuot with my foccusrite Scarlet 18i20.......

softwhirr

tenfoot

softwhirr
 
Today I thought I had it sorted after I upgraded ASIO4ALL to version 2.13 - everything was playing along nicely. And then Sonar Pro crashed AGAIN when I reloaded the project. So, I've been able to do hardly any work over the last 3 months. 

 
Sorry to hear you are having problems softwhirr, but asio4all is quite likely part of your woes. I would start there as it is notoriously problematic. You would be far better off with a dedicated audio interface with proprietary asio drivers.

Well, I did have the Focusrite working on Saturday, but after the Win10 upgrade, Sonar crashed on start up. I found "ASIO4ALL" references in the crash log, so I installed the latest version and managed to get it working. But for some reason I can no longer select the Focusrite device within Sonar - not sure how to get it back though - any ideas? 

If the Focusrite has its own asio drivers, I would uninstall asio4all completely. You do not need it. It is an asio wrapper for sound cards that do not have proper asio drivers (Internal laptop soundcards etc).
 
You can only have one asio driver active at a time. If you have asio4all selected in device manager, you will not be able to select any other device. Make sure you deselect it first, then select your focusrite asio driver.
 

jbow, I just looked at an HP Laptop with the same issue.  This is a known problem with a Microsoft update:
 
Many people have reported "caused by a recent optional Platform Update for Windows 7 x64-Edition (KB2670838).This update Is causing b.s.o.d's with igdpmd64.sys as the culprit."  So the solution is to uninstall that update.
 
How to FIX:
Open Control Panel > Programs > Uninstall Programs > View Installed Updates > Find  and uninstall KB2670838 > Restart computer > Open Windows Update > Check for Updates > Under optional downloads find KB2670838 right click and HIDE it.
That's it until Microsoft releases a permanent fix.
Note: This update is having interference with onboardly manufactured AMD Graphics of mentioned notebook models.
 
 
I did this on an HP dv6t-6b00 and it seems to have fixed the issue...Good luck!
 

softwhirr
Well, I did have the Focusrite working on Saturday, but after the Win10 upgrade, Sonar crashed on start up. I found "ASIO4ALL" references in the crash log, so I installed the latest version and managed to get it working. But for some reason I can no longer select the Focusrite device within Sonar - not sure how to get it back though - any ideas? 

Pleae stop running ASIO4ALL esp with Focusrite devices. Uninstall it now. If you don't believe me contact Focusrite who will say the same thing. They will conflict.

Once your have got rid of them then make sure you are on the latest Focusrite drivers from the web.

I tried (testing) using ASIO4ALL with a Focusrite Saffire Pro 40.  The ASIO4ALL corrupted the Focusrite drivers and the drivers for the PC sound card I was using at the time.  I had to uninstall the ASIO4ALL, reboot the PC and then reinstall the Saffire Pro 40 and PC sound card drivers.