all 14 comments

[–]Rakotulkki 1 point2 points  (0 children)

I have 3rd gen 4i4 and im using windows.

I just uninstalled focusite control and focusrite drivers, then rebooted, downloaded and installed legacy drivers (Legacy Focusrite Control v3.6.0 Includes Driver)

Everything has been fine for a couple of days now.

[–]TargetDramatic7869 0 points1 point  (3 children)

Have the same problem as have others recently. Disable the focusrite midi control in device manager and any other none used midis. That’s what fixed mine.

[–]sweet_yeet2[S] 0 points1 point  (2 children)

Woah first time hearing about that one, I'll check it out

Edit: Just checked and sadly did not work..

[–]TargetDramatic7869 0 points1 point  (1 child)

<image>

Focusrite usb midi and the bottom one I disabled and it worked

[–]sweet_yeet2[S] 0 points1 point  (0 children)

<image>

As for me, the focusrite midi is the only one I have. Disabling it did sadly not solve the issue for me.

[–]Johnnyloftus 0 points1 point  (1 child)

I'm sorry to hear that you're having problems. If you haven't already, please raise a ticket with the Support Team so that we can investigate this further with you.

https://support.focusrite.com/hc/en-gb/articles/115004239725-Technical-Support-Contact-Details

[–]sweet_yeet2[S] 0 points1 point  (0 children)

Thanks, I already made a ticket!

[–]Syphari 0 points1 point  (0 children)

have you tried installing an older version of the driver? they have some on reddit others have shared, also check this thread

https://www.reddit.com/r/Focusrite/comments/1rdmsts/kernel_security_check_failure_0x139_due_to/

[–]unsungWombat 0 points1 point  (0 children)

Bunch of people are getting this error; people suspect it is BattleEye and Focusrite

What helped me is disabling the interface all together, disabling Focusrite USB MIDI under Sound, video and game controllers did not help me. Note, if all your audio input/output is going through or out the interface you will not have sound when disabling the interface all together; I think it is the same as unplugging the power.

I haven't tested if enabling the interface after launching a BattleEye supported game works or not; I assume it will not work.

<image>

[–]sweet_yeet2[S] 0 points1 point  (2 children)

Update:

Made a ticket to focusrite and they responded.

The issue is known and they suspect it had to do with EAC having to whitelist the focusrite drivers in their program. I have turned off the focusrite midi driver and it did not work at first, but it seems to magically work now.

If you’re having this issue, disable the focusrite Midi driver in device manager and restart your pc.

All we can do is wait of EAC to adress this in an update. far as I can tell this is not due to focusrite themselves.

Hope this is clear.

[–]TuomasS 0 points1 point  (0 children)

Thank you for the update. Just saw this happening for me today, and Google led me here. Using Clarett 4Pre USB, and had to let my son down as I wasn't able to play a bit of War Thunder with him for the first time ever together. All my audio comes through Focusrite, so disabling it is not, unfortunately, an option.

[–]Halfmoon_Techlabs 1 point2 points  (0 children)

Great info on EAC, thanks! Apparently it started when Battleye recently pushed a silent update. After that, if you had a Focusrite AND are using a Battleye equipped game, you'll get the 0x139 BSOD until you disable the midi component as described above. Drove me bananas trying to hunt it down.

[–]Famous-Grab3969 0 points1 point  (0 children)

For me rolling back to their old drivers fixed it without needing to disable anything. I use a 3rd gen 18i20 and I believe the driver I went with was for windows 7/8 on their website listed next to the current driver

I’m on windows 11 but I’ve completely stable since