Does it not name the offending driver at the end of the BOSD

Wookiee
Does it not name the offending driver at the end of the BOSD?
 

nope


I guess it might be instructive to find the dump file that the system creates and see if I can decode it.

Possibly, I know there are some tools out there that can read and give meaningful information but I have know idea which ones are the best been a long while since I had to deal with BSOD and dump files.

Is you MoBo bios up to date?

Furry paws crossed you find a solution soon.

Try to temporary switch Sonar into WDM mode and/or on another interface (internal). That can exclude audio driver from possible problems (or confirm that is the problem...).

dantarbill

Wookiee
Does it not name the offending driver at the end of the BOSD?

nope


I guess it might be instructive to find the dump file that the system creates and see if I can decode it.

Try this https://www.nirsoft.net/u.ls/blue_screen_view.html

If you've got JBridge installed, you could try enabling the "Load using JBridge wrapper" by going into Cakewalk Plugin Manager, clicking on AAS (the VST2 version) and clicking the Plugin Properties button.
 
When loading via JBridge, there's a settings button that has a bunch of options that can you can tweak. I've found JBridge can help with dropouts and GUI issues with certain plugins.
 
M.

I agree with azslow and 35mm.  Hardware and drivers are the usual culprits for BSOD.
 
+1 for BlueScreenView from NirSoft that Brando suggested for viewing BSOD mini dumps.  This can often point you towards an offending driver.

I managed to narrow down the likely culprit.  It appears to be related to the ancient ASIO driver for my M-Audio Firewire 1814 interface (running version 5.10.0.5058).  When I run in WASPI mode, the AAS stuff doesn't blow up the system (but then I have to run at at least 12 ms latency in order to get smooth audio).
Also...

• Set system to WASPI
• Instantiate a recent AAS synth (like Ultra Analog VA-2) in a project
• Verify that it works
• Close the project without saving it.
• Reopen the project (still with no AAS plug).
• Change the driver mode to ASIO
• Click on Apply
• Gets the same BSOD

It appears that the AAS plug has left the system in a state that pisses off the driver, even though the AAS code is no longer running.

I have all the AAS instruments but on win7 OS so I can't offer any insight into your issue other than to say that I am not experiencing any problems at all on that system. FWIW though, I have always found AAS support/customer service to be among the best, so if there is a significant delay in getting back to you I would say based on my experience that is unusual, so it might be worth checking that something hasn't gone wrong in the communication process. (IE did they get your message in the first place / did they already reply and you didn't get it for some reason?)

I have indtalled VA-2 trial (2.1.0) and can instantiate it as VST3 without problem.
 
Since I use FW Audiophile, I guess that is the same driver as 1814.
 
I periodically get BSOD from this interface. When it is chained with 410 I get BSODs regularly. But when it is alone, I have no reproducible problems, just 1-2 crashes per week, sometime in DAW, sometime in games... Note that I was choosing FW cards carefully (PCI before, PCIe now).
 
As you can see in my signature, I have finally decided to buy "real" audio interface. And while I am just a home player, I think it was worse the money... Also after combining it with "real" DAW, I have stop wondering how people can use DAWs on stage.. But I still have audiophile connected all the time, periodically start Sonar and use "real" staff when needed only.