Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asio driver crashing windows after closing OBS #125

Open
santimagames opened this issue Sep 19, 2022 · 4 comments
Open

Asio driver crashing windows after closing OBS #125

santimagames opened this issue Sep 19, 2022 · 4 comments

Comments

@santimagames
Copy link

santimagames commented Sep 19, 2022

Plugin Version
obs-asio v3.1.1

Describe the bug
When using the asio input as an audio source, OBS will crash the windows with a blue screen after closing down the app. Apart from ASIO, I'm using webcam input, some text and a logo image on the screen. I'm using Windows 10 with 21H2 update. The OBS and the plugin version is 64 bit. Plugin works properly with OBS 28.0.1 during usage.

The issue disappeared after I've uninstalled the plugin. The previous versions of the plugin won't work with OBS 28.0.1

@TheCakeGit
Copy link

TheCakeGit commented Feb 7, 2023

I have the same issue with 3.1.1. and OBS 29.0.2 with a Saffire Pro 40 reproduced in a similar fashion to how the OP did. No other audio is being used, I just need to open and close OBS - then BSOD, and PC reboots. Uninstall the plugin - all is fine. Repro'd under Windows 10 and 11, I don't experience this crash anywhere else and I'm not using any other audio applications that may lock something.

Versions 2 of the plugin won't work with the latest OBS. Nothing in Windows or Blue Screen View utility that is of any use, but it does point to the HAL. I run a lot of other audio applications for years with this ASIO driver (Mix Control 3.7, FW Driver 4.3.0.41017) and have had no issue.

BTW no other third party plugins are installed.

Thanks...

@Andersama
Copy link
Owner

Very odd, especially @TheCakeGit because you're using similar hardware to what I had while I was developing the plugin (a Saffire Pro 26). Definitely would've been a pain to have been bsoding when developing the plugin. Do either of you have other asio devices / drivers installed? I'm curious because the Juce version of the plugin tries to work with all the installed asio devices listed in the windows registry, in theory any malfunctioning driver could cause problems.

@TheCakeGit
Copy link

I don't have issues with Saffire Pro drivers anywhere else. Very reliable. Realtek internal motherboard has its own internal interface but I'm not using that, and certainly not the ASIO driver. Not installed any rubbish either like ASIO4ALL.

@Andersama
Copy link
Owner

Unfortunately it's not as though there's any obvious errors in the plugin at this point, more than likely it's something to do with Juce or drivers. Could do some process of elimination, have you eaither used any other Juce based projects with your asio device? There's a VST host called carla that I know uses Juce, if you bsod with that software in a similar way that'd help work things down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants