# ASIO crashes on windows 10

**URL:** <https://forum.juce.com/t/asio-crashes-on-windows-10/28253>\
**Category:** Windows\
**Created:** [June 25, 2018, 3:33pm UTC](https://forum.juce.com/t/asio-crashes-on-windows-10/28253 "2018-06-25T15:33:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tlacael](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tlacael](https://forum.juce.com/u/tlacael)\
**Post date:** [June 25, 2018, 3:33pm UTC](https://forum.juce.com/t/asio-crashes-on-windows-10/28253/1 "2018-06-25T15:33:07Z")

</div>

I have a customer who is experiencing consistent crashes when attempting to select his Focusrite interface via the ASIO driver on a 64 bit windows 10 machine. His drivers are up-to-date and he’s using a 2nd gen Scarlett 18i8.

I know that there was an issue previously with the 64bit Focusrite drivers on Windows ([ASIO Devices crashing in 64bit](https://forum.juce.com/t/asio-devices-crashing-in-64bit/18795)) but I wanted to see if anyone else has experienced this issue coming back. I cannot recreate the problem on my machines, but he is able to recreate it reliably with the JUCE audioPluginHost demo app (built with 5.3.1).

Unfortunately, I don’t have any stack traces from his machine yet, but I’m working on setting up a support session. Any clues in the meantime would be much appreciated!

Thanks

---

<div class="post-metadata">

**Author:** ![tlacael](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tlacael](https://forum.juce.com/u/tlacael)\
**Post date:** [June 25, 2018, 4:47pm UTC](https://forum.juce.com/t/asio-crashes-on-windows-10/28253/2 "2018-06-25T16:47:54Z")

</div>

Minor update:

I was able to examine the crash dump. All it says is:  
`The thread tried to read from or write to a virtual address for which it does not have the appropriate access.`

It seems to have a problem switching from Window Audio driver to ASIO. I managed to get it to work by manually editing the settings file, setting the device type to ASIO. This allowed me to then start the app and select the Focusrite device. But, if I go back to Windows Audio and then reselect ASIO it crashes again.

I retested this issue with the Audio Host built against 4.3.2 and it is the same.

---

<div class="post-metadata">

**Author:** ![DaveH](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/daveh/32/4924_2.png) [@DaveH](https://forum.juce.com/u/DaveH)\
**Post date:** [June 25, 2018, 8:13pm UTC](https://forum.juce.com/t/asio-crashes-on-windows-10/28253/3 "2018-06-25T20:13:10Z")

</div>

I have the same focusrite box. And when I choose the ‘FocuiteASIO USB’ option, everything goes quiet, until I realised I needed the Focusrite ‘Software (DAW) playback’ mixer added into the ‘Focusrite Control’ window. I’m using 5.3.2. I’m not getting a crash though.

---

<div class="post-metadata">

**Author:** ![tlacael](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tlacael](https://forum.juce.com/u/tlacael)\
**Post date:** [June 25, 2018, 8:31pm UTC](https://forum.juce.com/t/asio-crashes-on-windows-10/28253/4 "2018-06-25T20:31:51Z")

</div>

Thanks for the suggestion. The user’s device is routed correctly, it seems to be just a strange bug around initializing the ASIO driver.

---

<div class="post-metadata">

**Author:** ![midiculous](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/midiculous/32/582_2.png) [@midiculous](https://forum.juce.com/u/midiculous)\
**Post date:** [January 11, 2019, 4:15pm UTC](https://forum.juce.com/t/asio-crashes-on-windows-10/28253/5 "2019-01-11T16:15:45Z")

</div>

We are having this issue with all of our Focusrite customers. Is there anything that can be done? @tlacael did you figure out a better solution?

---

<div class="post-metadata">

**Author:** ![tlacael](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tlacael](https://forum.juce.com/u/tlacael)\
**Post date:** [November 25, 2019, 5:44pm UTC](https://forum.juce.com/t/asio-crashes-on-windows-10/28253/6 "2019-11-25T17:44:45Z")

</div>

I’ve come back to this after a while hoping that Focusrite would fix the issue on their end, but it still seems to be a problem.

I just updated the ASIO Focusrite driver to the latest 3.4.4, but now the problem is worse. When unplugging the device while a JUCE app is using it (like the Audio Plugin Host), the entire computer crashes. I can recreate it reliably on my machine now.

I get a blue screen with a SYSTEM\_SERVICE\_EXCEPTION stop code, saying that FocusriteUSBSwRoot.sys failed.

This may be a Focusrite bug, but Ableton manages to handle the disconnect gracefully. Perhaps there’s something that can be done on the JUCE end to fix this?
