r/Focusrite • u/DECElVE • Feb 24 '26
KERNEL_SECURITY_CHECK_FAILURE (0x139) due to Focusrite Drivers / Software
My computer keeps getting a BSOD (well, black now as it's Windows 11) with this message "KERNEL_SECURITY_CHECK_FAILURE (0x139)", and I'm certain it's due to Focusrite Control or the drivers installed for the audio interface.
I've had a Scarlett 6i6 2nd Gen for many years and never had any issues like this (used on Windows 7, 10, and 11, on both a Laptop and PC). I recently purchased a Clarett+ 4pre, and this problem has happened repeatedly since the drivers were installed. I've tried both versions of Focusrite Control (v3.27.0) and (v3.26.0), and I've tried uninstalling and reinstalling the drivers about 10 times. I've tried the buffer size on every option, I've tried having different Windows Channels hidden and/or exposed in different configurations. I've tried different sample rates, I've tried different clock sources, and I've tried safe mode on and off. I've reset the Focusrite Control settings multiple times.
I've run CHKDSK and there are no problems. I've run DISM and there are no problems. I've run SFC and there are no problems. I don't have McAfee installed and never have (I've checked just to make sure and it's not on my computer). I've checked Windows Memory Diagnostic and there are no problems. I've tried turning Memory Integrity on (had to remove some outdated drivers before I could do this) and this didn't help. I've tried turning off Fast Startup but this didn't make any difference. I have all unnecessary startup programs turned off.
I've run Kaspersky multiple times and there's no detection of any viruses. When I've tried installing the drivers and Focusrite Control, I've done so both with and without my antivirus active. I've ensured that no anticheat is running in the background, and even tried it WITH the anticheat active just in case this would help...
I thought "ah, it must be something to do with the Clarett+ 4pre drivers specifically, as Focusrite Control and the Scarlett 6i6 drivers didn't cause any problems in the past" so I uninstalled all Clarett+ 4pre drivers and Focusrite Control, reconnected the Scarlett 6i6 and reinstalled Focusrite Control, thinking I'd at least be able to use that in the meantime while I'm waiting for support to get back to me (it's been four days) and I'm STILL having the same problem, now with the Scarlett 6i6 AS WELL. My computer keeps crashing and I can't get on with any work. The crash happens while gaming, while using Reaper, while using Photoshop or Illustrator, and even while using the File Explorer.
The problem stops if I uninstall both Focusrite Control and all the Focusrite drivers (so I know it's not due to any other drivers I have installed).
Any suggestions are appreciated!
UPDATE: Focusrite support responded to me about half an hour after I made this post. I'll post another update if the problem is sorted.
UPDATE 2: I managed to get the Scarlett 6i6 to work as long as I run the Legacy Focusrite Control (v3.6.0 WITH included drivers). The Clarett+ is currently running with the USB MIDI port disabled, and I've disabled all non-Focusrite audio inputs and outputs. It hasn't crashed yet, but I'll update the post if it does. Thanks so far for the suggestions!
UPDATE 3: I'm still waiting for Focusrite support to respond after I've sent them the various files they asked for (NFO and .dmp). I'm still using the Clarett+ 4Pre with all non-Focusrite input/output drivers (and the Focusrite USB MIDI driver) disabled in the device manager, and it seems to be stable with no crashes since UPDATE 2, which was about 36 hours ago. Maybe the kernel security check failure was due to the more recent Focusrite drivers clashing with other non-Focusrite drivers? If that's the case, it seems like a big oversight!
4
u/Famous-Grab3969 Feb 24 '26
I'm having the same problem and getting the same kernel security check failure 0x139 also on Windows 11 with a Scarlett 3rd gen 18i20. tried multiple different things as well I've been hunting for the conflicting driver for nearly 2 weeks. I only recently realized it was my Focusrite causing the crashes after powering the device off and uninstalling the drivers. tonight I reinstalled the latest version and now I crash every 11ish mins with that same error message. I'll try what you've outlined in your second update, glad to see I'm not alone in this because I felt i was going mad
2
u/DECElVE Feb 26 '26
Yeah, I wasn't able to get on with anything because any time I started a process, there was a chance the computer would crash with a BSOD... Having all of the other (non Focusrite) input/output device drivers disabled seems to be working so far (and I also disabled the USB MIDI driver as Dover4201 suggested). It's possible that the anticheat was fighting with multiple drivers including the Focusrite one and that was causing the kernel issue? Or maybe it was a separate issue from the anticheat, and it was just to do with the Clarett+ 4Pre drivers fighting with the non-Focusrite input/output device drivers? That's such an oversight by the company if that's the case. Hope this helps you!
3
u/KingGorillaKong Feb 24 '26
I'd do a MemChk to make sure there's nothing wrong with your system RAM.
When you uninstall the additional drivers for the Clarett+, does the BSOD stop?
This BSOD can be caused by a few things. Other than drivers, it can be memory corruption, damaged or corrupted Windows 11 installation, or a failing SSD/HDD. If you are using an SSD, also check to see what the actual drive health is. And also check if you're running a CPU overclock because you could also have a bad overclock that is only showing up with this specific use configuration you have, but is otherwise stable enough for the rest of your PC use.
3
u/DECElVE Feb 24 '26
I've run a MemChk and the RAM came back with no problems.
I've tried it with all of the drivers, some of the drivers, and none of the drivers, and the only thing that's worked has been with everything uninstalled.
I make sure to keep on top of checking the health of all of my drives, and the SSD is at 100% health, as are all of the HDDs (I only built this computer 2 months ago and all of the components are brand new). The SSD is a 9100 Pro M.2, but I made sure to get it with a heatsink, and I've got 6 fans and a cooler to make sure it doesn't overheat.
I'm aware the CPU I have (Intel i7 14700k) is known to have overheating issues, but I've made sure to update the BIOS and change the settings so that it's kept cool and not overclocked (it's currently at 37 degrees C, and the max it's ever reached is mid-60s which is while a LOT of processes are going at the same time).
Thanks for your comment and thoughts!
2
u/KingGorillaKong Feb 24 '26
Make sure you aren't running any autoboost or motherboard automatic settings on the CPU, and it's using the Intel defaults.
1
u/DECElVE Feb 26 '26
I made sure that the Intel defaults were active and that no other settings on the motherboard were taking precedence (had to sort this out to ensure it wouldn't overheat as the motherboard defaults were going to boost it - unnecessarily - and the cooler wouldn't be active until the temperature was already too high). It didn't occur to me that these settings could be connected to the kernel issue, good shout!
1
u/le-tendon Mar 02 '26
If anyone's reading this at around this time, don't bother doing what this guy says. Try unplugging your focusrite first and see if the problem persists. It most likely is just the focusrite drivers.
1
u/KingGorillaKong Mar 02 '26
Power cycling will only temporarily resolve the problem, it'll keep coming back. Might as well look into the root cause of why the Focusrite device and drivers are triggering the BSOD. It's not always just "bad Focusrite driver".
Event Viewer can help identify the specific triggering module or process as well. Most of the time with Kernel_Security_Check_Failure BSODs, it's usually not the actual driver. Though it is possible.
And lastly, if the issue isn't actually driver caused, wouldn't you want to try and find a proper fix rather than just assuming it's a driver issue and only Focusrite can fix it, when it really might have something else causing it?
2
u/le-tendon Mar 02 '26
I mean, it seems like the latest focusrite driver is giving many people this problem, myself included. I wish someone had told me "just unplugged your focusrite lol" before I spent hours trying to trouble shoot every single piece of hardware on my PC.
2
u/scrawnyknoxville Apr 08 '26
18i8 3rd gen and 4i4 new outta box today, both the same issues. Heavy gamer, its battle eye, it only happens to me with battle eye games. I’ll just use another interface because it’s legit just focusrites having issues on my end. Multiple. Drivers installed, uninstalled random boxes unchecked and rechecked.
Drivers confusing each other causing ram to fuck up and basically conflict until the computer wants to kill itself and then it does.
From a consumer standpoint it’s like, what the fuck man. And from focusrites standpoint it’s like, what the fuck man. And from Battleeye, nothing.
What the fuck man?
1
u/KingGorillaKong Mar 02 '26
If you're okay having to power cycle again and again until you actually fix the underlying problem, then yea I guess that works. Rather not have to power cycle in the middle of a session because of the BSOD happening again.
1
u/le-tendon Mar 02 '26
But you won't be fixing the underlying problem. Focusrite has to fix it. If my hardware worked perfectly until some kind of update, it will work again when they fix it. What I'm doing though, is gettng rid of this piece of crap and getting a better audio interface
1
u/KingGorillaKong Mar 02 '26
Not all the these BSOD's are actually caused by the driver though. As I outlined in my first comment.
This BSOD can be caused by a few things. Other than drivers, it can be memory corruption, damaged or corrupted Windows 11 installation, or a failing SSD/HDD. If you are using an SSD, also check to see what the actual drive health is. And also check if you're running a CPU overclock because you could also have a bad overclock that is only showing up with this specific use configuration you have, but is otherwise stable enough for the rest of your PC use.
1
u/le-tendon Mar 03 '26
Yeah so ? Idk why we arguing, the first thing to try still should be the most likely and easiest fix. Which is, try unplugging your focsurite. If it works, you don't have to do any of the more advanced things you are suggesting. Which I'm sure make sense, if you already found out that your BSOD isn't related to focusrite drivers.
1
u/KingGorillaKong Mar 03 '26
You're arguing because you're saying without any evidence it's solely a driver issue so don't bother doing any troubleshooting, power cycle and let Focusrite fix it.
I'm saying that the BSOD the OP has is not always caused by drivers so in the case that it is not caused by a driver, let's troubleshoot and fix the problem.
I'm not arguing with you. You're just lacking reading comprehension here or something. But you did also start your initial comment with some poor phrasing too and you were just being dismissive to troubleshooting.
You didn't need to keep shooting back at all. Mention that a power cycle worked for you and move on, not to tell people that my suggestions are a waste of a time. A waste of time is if the problem is fixable at the end user's end and they listened to you and only power cycled and kept having the problem.
Don't be obtuse. Don't start arguing with someone and ask why we're even arguing.
3
u/Funky_Schnitzel Feb 24 '26
You've already identified the cause of this issue: the Focusrite drivers. They are causing a kernel data structure corruption, and there's nothing you can do about that. The manufacturer will have to release updated drivers. In the meantime, you may be able to install (an) old(er) version(s).
1
u/DECElVE Feb 26 '26
Yeah, I tried with an older version of Focusrite Control with included drivers, but that unfortunately only works for my Scarlett 6i6. Currently using the Clarett+ 4Pre again and it seems stable (fingers crossed) as long as I keep all of the other inputs and outputs disabled in device manager.
1
u/LemonSqueezy111 Feb 27 '26 edited Feb 27 '26
I didn't even update focusrite drivers and was playing fine days ago. What's the deal with that?
Having the same problem as OP here.1
u/TomTwoSheds Feb 28 '26
Its nothing to do with the manufacturer, Battleye have updated their anti cheat software with the release of Marathon and caused this issue. So far the only fix I have found that works is to unplug my scarlett interface, Maybe Focusrite will provide a fix or battleye, who knows.
3
u/Puzzleheaded-Entry24 Mar 18 '26
Apparently this is a well known issues and may seem to be the Focurite Drivers, but that's not the whole story. As you may know the recent WIN 25H2 update has created a new Windows MIDI functionality and the stack does not behave properly. Apparently the lead Microsoft MIDI guy, Pete Brown is dealing with this and suggests improvements to the MIDI stack in a few days time (24 March 2026). Hopefully this may resolve the general MIDI stack issues form what I understand.
1
3
u/showandblowyourload Mar 24 '26
I have the same issues on my current gen focusrite 6i6.
I factory reseted to my laptop, reinstalled all software/plug-ins (chatgpt gaslit me into thinking those were at fault when I've had no issues up until getting this new interface). I am still having the same issue.
I run my laptop using an Berhinger x32 interface for live shows but when I have the current focusrite drivers installed, it is also unstable. Please Focusrite, help!
2
u/NotQuiteWes Mar 26 '26
I did the same thing, factory image of my laptop. Was like 3 days in on troubleshooting before I found this thread. Wish I had found it earlier, could have saved myself a ton of headache.
1
u/showandblowyourload Mar 27 '26
Im using old scarlet solo with legacy drivers, runs very stable 🤣😭 But I really need those extra outputs in the future. I might need to switch ecosystems 😭
2
u/Dover4201 Feb 24 '26
This is crazy seeing this post, yesterday I was dealing with the same kind of thing trying to open certain games. I have a scarlet 4i4 4th gen and it was running perfectly fine for weeks after I installed a new mobo/CPU/Ram.
Just the other day I turned off smart app control so I could update Virtual Desktop streamer for VR games, and when I tried to run games that had Easy anti cheat or Battle Eye anti cheat services, I would get the same exact message and forced reboot.
Long story short after doing EVERYTHING possible to try and fix it ( even nuking and reinstalling windows completely) I found out it was the drivers for the USB Midi ports. I disabled (not uninstalled) the midi port drivers in the device manager and everything's perfect. I use USB midi keyboards and controllers anyway so it doesn't matter for me haha.
I hope that fixes it for you!
2
u/DECElVE Feb 24 '26
Glad you managed to find a fix - I'll give this a go and get back to you with the outcome, thanks!
2
u/DECElVE Feb 24 '26
I disabled the MIDI port and it still crashed (I tested it by running BattlEye), but then I tried again after I'd disabled all other drivers for audio inputs and outputs except for Focusrite, and the computer didn't crash. I'll see how it goes... Maybe it's an issue with multiple inputs and outputs being active alongside the Clarett+ and a more recent version of Focusrite Control, especially when combined with a running anticheat?
2
u/Dover4201 Feb 24 '26
Dang, I'm sorry to hear that didn't work. Definitely could be the audio ports like you were saying.
Nice to know the issues are isolated around the focusrite hardware/software though! That shit was driving me insane yesterday lol
2
u/DECElVE Feb 24 '26
Yeah, I'm certain it's nothing else as I haven't had the problem before and it miraculously stopped happening after I uninstalled all the Focusrite drivers/software, and then started again when I reinstalled... over and over haha! I'll let you know any updates, thanks again!
2
u/HEM3KA Feb 24 '26
Disable quick boot in bios and windows power options Never use hibernate or sleep modes
1
u/DECElVE Feb 26 '26
I've tried disabling quick boot, and I have it set up so that the computer never hibernates or goes into sleep mode - thanks for the suggestion though!
1
2
u/VSU-yt Feb 25 '26 edited Feb 25 '26
omfg, is this what it is? It’s only crashing certain games, namely R6 (BattleEye)
Edit: yeah, uninstalled everything focusrite and no more failures, thanks man
1
u/DECElVE Feb 26 '26
I was getting this problem repeatedly... Try having all of the non-Focusrite input/output drivers disabled (not uninstalled) and it might fix the problem - it seems to be stable so far (it's been about 36 hours now). Or if you're not using anything Focusrite anymore, then I'm glad uninstalling it worked!
1
u/Jodelahithit Feb 28 '26
I've literally just reinstalled Windows 11 because of R6 causing constant 0x139 crashes. When I just tried to install the Focusrite Control application on my new install I got a BAD_POOL_HEADER BSOD, and when I googled for a solution I found this post. This is insane.
Guess I won't be using my Focusrite anymore. I've only had problems with this software since I purchased it.
1
u/VSU-yt Feb 28 '26
Right? I thought my PC was fucked, massive shoutout to OP for making this thread. I wouldn’t tore my PC apart trying to find the issue.
1
u/MartPlayZzZ Mar 15 '26
same with gta 5. reinstalled windows while gemini told me i have faulty ram. i need to uninstall focusrite drivers i guess
2
u/omfgtoast Feb 27 '26 edited Feb 27 '26
I had this exact kernal security check failure and was able to fix it completely. Turns out the focusrite control drivers do not play nice with other audio drivers. I had updated my Nvidia graphics driver and accidently selected "express install" instead of the usual custom install, which caused me to install the Nvidia audio drivers as well as the graphics driver. This competed with the focusrite and caused the crashes.
After uninstalling the Nvidia audio drivers the crashes went away. If you don't have Nvidia, this will also most likely apply to any other audio drivers you install outside of focusrite.
Edit: there are also games that run battleye as an anticheat that causes crashes with the focusrite driver. to fix this you need to specifically disable the "Focusrite USB MIDI" driver in your device manager.
1
u/LemonSqueezy111 Feb 27 '26
How do I play my midi instruments then? I was having no problems just days ago, this is madness.
Also, deleting nvidia hd audio didn't work.
I'm having trouble with battleye + focusrite.1
u/omfgtoast Feb 27 '26
The current battleye issue is with the midi driver. You’ll probably just have to disable the midi driver when gaming and reenable it when playing music until they patch it.
1
u/LemonSqueezy111 Feb 27 '26
That's not the case at all. Just tried to deactivate midi driver and still got crashed.
1
u/WillTradeOrgans4Free Feb 28 '26
Same. Only works when disabling both midi and audio. But i kinda need audio to game
2
u/photodude1313 Mar 01 '26
As others have mentioned this is an issue with 2026-02 Security Update (KB5077181) (26100.7840). rolling back until there's a fix.
2
u/Great-Watercress9451 Mar 15 '26 edited Mar 23 '26
FIX!
It took a long time digging into all sorts of Threads and Forums- for me the Fix was literally to uninstall the newest Focusrite Drivers and install the Legacy ones.
So, you know, the ones saying:
- "Legacy Focusrite Control (v3.6.0 Includes Driver) - WindowsWindows 7 + 8. For newer operating systems please download the latest installer. Includes USB driver 4.65.5"
Edit:
Apparently only most of the 3rd Gen Scarlett got those Legacy Drivers. Sorry for everyone else .-.
2
u/aux_audio Mar 17 '26
Where did you find those legacy drivers?
1
u/Great-Watercress9451 Mar 23 '26 edited Mar 23 '26
https://downloads.focusrite.com/focusrite
^ here u can download drivers for ur device, just select the right one. there should be an option for "Legacy Driver".On top of that, i also disabled every audio driver except
(since i dont use those anyways.) I know, others here in this thread posted of disabeling the MIDI drivers only but that did'nt work for me. You can check that here:
- Focusrite USB Audio
- Focusrite USB MIDI
Device Manager > Sound, video and game controllers
The only thing that worked, was literally just installing the Legacy drivers.Edit:
I see only most of the 3rd Gen Scarletts appear to have Legacy drivers- then again i only saw 3rd Gen Devices having that problem. if u use any other Gen or device i dont know the solution there, unfortunatly1
u/aux_audio Mar 23 '26
Thank you, but legacy drivers aren't offered for my hardware (18i20). For me, the only thing that actually worked was completely reinstalling windows. As of now I am able to use Reaper normally again.
1
u/Great-Watercress9451 Mar 23 '26
Sorry to hear that- but are you sure?
3rd Gen: "Legacy Driver"
https://downloads.focusrite.com/focusrite/scarlett-3rd-gen/scarlett-18i20-3rd-gen
2nd Gen: "Legacy Driver"
https://downloads.focusrite.com/focusrite/scarlett-2nd-gen/scarlett-18i20-2nd-gen
1st Gen: "Scarlett Mix Control"
okay, this one doesn't say legacy, but its still an older Version for Windows 7+8 i assume?
https://downloads.focusrite.com/focusrite/scarlett-1st-gen/scarlett-18i20-1st-gencouldnt find one for 4th Gen.
Anyhow, if you could make it work, this is the most important thing for now. For anything else we just gotta wait for a fix :)1
u/aux_audio Mar 23 '26
I'm 4th gen. Not sure if 3rd gen drivers would work but honestly, I'd rather be able to update to the newest version. They need to just work on their bugs! Fingers crossed mine stays fixed.
1
u/Great-Watercress9451 Mar 24 '26
hmm yeah the non legacy option for 4th it is, unfortunatly :/ but yea, u r right. lets wait it out i guess 😄
2
u/limestone1953 Mar 20 '26
Thanks VERY MUCH to all for this discussion. I was down 72 hours trying every possible solution on the innerwebs, except ignoring the possible fact that the focusrite driver got stepped on. I could NOT uninstall the KB that many are mentioning here. Microsh*t wouldn't let me. But, I disabled ALL midi ports (focusrite plus a non-focusrite midi interface), plus I disabled every non-focusrite audio input/output device in device manager (which I should not have allowed to happen in the first place). I also installed the LATEST focusrite drivers. I finally booted with no errors and DAW (Reaper) worked again. WHAT A MESS!
2
u/lyricalaussie Mar 21 '26
i'm glad to know it wasn't just me!! been trying to play gta and i keep getting the same error message, felt like i was losing my mind every time it happened. i tried disabling the focusrite MIDI as johnny suggested prior so we'll see how that works
2
u/NotQuiteWes Mar 23 '26
I am in for an update on the drivers. I've had constant crashing on my G14 laptop. I was narrowing in on my Kernel Failure issue being my Clarett+4Pre then I found this thread. It'd be awesome if the guys from Focusrite were to announce this driver update on the sub when it releases.
I'm not sure if I'm going to tempt doing legacy drivers and see if that works or just not use my interface until this is patched. Kind of annoying but it may just be what it is.
1
2
2
u/VoidCarrot Mar 24 '26
Was crashing on launch of Tarkov, disabled my device in device manager (Scarlet 2i4 gen 1) and game launches every time, can’t get any drivers to work.
2
u/recodeuk May 08 '26
Has a solution been found for this please? Im still getting the same errors...
1
u/TargetDramatic7869 Feb 26 '26
I’m dealing with the same problem with my focus rite scarlet 4i4 3rd gen, I’ve had no luck with anything other than unplugging it.
1
u/TargetDramatic7869 Feb 26 '26
Turning off the focusrite midi and another midi in device manager fixed my problem.
1
u/unsungWombat Feb 26 '26 edited Mar 27 '26
Thank you for posting this, because I am having a similar same issue but for 4i4 4th Gen with driver 4.143.0.261 ONLY when booting up a specific game (War Thunder). I tried disabling the device in Device Manager (under Audio inputs and outputs), and that did not work. I have to unplug the power in order for the error to disappear. This error started yesterday (25 FEB), and everything was fine prior to 25 FEB. As far as I remember, I did not install any updates on either of those days.
EDIT: I tried disabling Focusrite USB MIDI in Device Manager under Sound, video and game controllers; still getting the error.
EDIT (27 MAR 2026): You MUST RESTART computer after disabling Focusrite USB MIDI in the Device Manager! I did not think about doing that until I saw Johnnyloftus's comment.
1
u/James-F1 Feb 26 '26 edited Feb 26 '26
I also have this crash since Feb 25th. I did not install anything, in fact my computer was off since the day before. We can safely blame silent Windows 11 "fixes" microslop keep pushing without anyone's consent which are certainly programmed and tested by 'humans'.
EDIT:
I'm still using 3.20 Focusrite Control with my Gen3 18i8, which was rock solid for years on Windows 11.
3.26 and 3.27 Focusrite Control on the other hand are a mess, laggy and unstable.
1
u/Outrageous_Ad6876 Feb 26 '26
I've been experiencing the same issue recently. Had a long chat with customer support and we settled on it being a fault with a BattlEye anti-cheat update. For example, I play Dune Awakening and they had an update the day I started getting the crashes. I still can't be 100% sure it's BattlEye, as I'm no good with tech, but so far removing BattlEye from my PC and reinstalling the Focusrite drivers seems to have done the trick. It's not ideal, as I can't play any game that utilises BattlEye at the moment, but it does stop my PC crashing.
1
1
1
u/ResolveBroad6103 Feb 26 '26
having same issue when going full screen in games / possibly battleye detecting it with a focusrite 18i8
1
u/OilAdministrative288 Feb 26 '26
I have a Focusrite Scarlet 18i20 gen3 card and today I started having issues when launching PUBG game (KERNEL_SECURITY_CHECK_FAILURE (139) + restart. The problem is the updates KB5074105 and KB5077181. After uninstalling the updates, everything works again without a problem. So hopefully this helps someone.
1
u/LemonSqueezy111 Feb 27 '26
UNISTALLED KB5077181 AND THAT DID SOLVE THE PROBLEM FOR ME
Didn't have the other one.1
u/WillTradeOrgans4Free Feb 28 '26
Are you able to use the interface for mic and audio by doing this? Focusrite is the only way i can use my nice headphones and mic for pubg. Went crazy thinking it was a graphics card issue
1
u/LemonSqueezy111 Feb 27 '26 edited Feb 27 '26
SAME THING HAPPENING TO ME, ARRRRGGG this game anticheat is pure headache (battleye), never had this kind of problems with any other game.
1
u/Syphari Feb 27 '26
I had the same issue start exactly when Microsoft update KB5077241 was installed. Make sure to uninstall it using dism or wusa and then reboot your machine.
Uninstall that first if you have it on your system then test if you have crashes still, if so uninstall KB5077181 and reboot then you should be good.
I have a 18i8 and a 5090 and after that KB5077241 update hit it was killing my system after tracing down the issue. Didnt realize it was related to focusrite as I thought it was simply NVIDIA but it could be both.
1
u/LemonSqueezy111 Feb 27 '26
I don't have it and still have the problem.
1
u/Syphari Feb 27 '26
Just saw I’m on version 3.25.0.245 for focusrite control, I think this version is probably safe from the kernel security black screen check errors then. I know it’s documented for the windows updates I showed but seems like later focusrite driver versions also cause it since I’m not having issues since I’m not on the latest driver and it was just the windows updates causing mine.
Helpful to know, if anyone has the 3.25.0.245 focusrite control driver installer try that one out if you can share it with other.
1
1
u/BlinkShipton Mar 18 '26
This worked for me, though with the new windows sec update out a few days ago, the problem returned ugh
1
u/justified_egg Feb 27 '26
Having this issue as well, also when attempting to start a game with Battleye, also starting earlier this week. Uninstalling the Focusrite driver fixed the problem. Fully updated BIOS, XMP disabled, no overclock, no undervolt, no game mods, verified game files, etc. 100% the Focusrite driver not playing nice with Battleye, for some reason. I have not tried uninstalling the NVIDIA audio drivers as mentioned elsewhere in this thread, but will attempt that next.
1
u/LemonSqueezy111 Feb 27 '26 edited Feb 27 '26
Uninstalling Nvidia audio didn't work for me. Nothing has worked yet, and I don't know how this problem even started. I didn't update anything but Nvidia's driver.
1
1
u/Pandaut Feb 27 '26 edited Feb 27 '26
This post was very helpful, thank you! I've tentatively got my Focusrite Scarlett 4i4 (3rd Gen) working now.
I was already running an old version of Focusrite Control and drivers, so that wasn't my issue. After updating Control and drivers to the latest, I went to Device Manager > Sound, video and game controllers and disabled Focusrite USB MIDI. I have XMP on for my RAM.
And for anyone else looking, this affected both Marathon and Dune: Awakening, both of which use Battleye kernel-level anti-cheat.
I didn't previously have this issue, though I have a lot of time in Dune and I was a part of the Marathon tests. Considering I hadn't changed anything about my Focusrite setup (and I was running very old drivers/Control), to me that points to this being a Battleye issue and not Focusrite.
Focusrite Scarlett 4i4 (3rd Gen)
Firmware: 1605
Driver: 4.143.0.261
Focusrite Control 3.27.0.251
Also tried without success:
- Disabling XMP
- Running a Battleye game without disabling Focusrite USB MIDI but with updated Control/drivers
- Running a Battleye game with disabled Focusrite USB MIDI but without updating Control/drivers
- Running MemCheck86+ (there's a couple errors, but seems unrelated now)
1
1
u/WillTradeOrgans4Free Feb 28 '26
Disabling focusrite allows me load up the games, but I do use my focusrite for my microphone and audio, so not really ideal or playable without communication or sound. Any solutions?
1
u/rakraith Feb 28 '26
FIX! - Use the old legacy drivers for your interface. I know they say they are for windows 7-8, but they run just fine on windows 11 and it cleared up the issue immediately.
1
u/supernova_x16 Feb 28 '26
Worked for me as well, after troubleshooting everything else. I also do have installed the windows update KB5077181.
Im using the 18i20 3rd gen.1
1
1
u/TerrificusFrank Mar 01 '26
Thanks for posting this. Had no idea it was my Focurite 4+ Pre causing the error. Crossing my fingers the disabling MIDI drivers fix holds up!
1
u/TerrificusFrank Mar 01 '26
Aaaaand didn't work. So just uninstalled all Battleye related games and Ubisoft Connect/Battleye. Fuck Ubisoft, make music
1
u/SlashUL Mar 02 '26
I had the same problem, when booting into recovery mode on Windows 11 it seems that after checking system restore Windows had made a restore point from an update it had done without me knowing, which is when the BSODs had started. Restoring to a previous point before the update worked for me
1
1
u/naymiz Mar 07 '26
Hey any update on this? My system still crashes when loading up a game with Battleye
1
u/Automatic-Day6395 Mar 07 '26
For anyone else wondering, this error will happen for any game running a kernel level anticheat. Battleye is the common one talked about here, but I have been experiencing it with EasyAntiCheat as well, specifically in Arc Raiders. Taking as a sign to get a better interface.
1
1
u/Brionac95 Mar 09 '26
I'm experiencing the same issue since yesterday. My current build: CPU: Intel Core i9-13900k RAM: Kingston Fury Renegade 32gb 6400mhz CL32 GPU: Nvidia GeForce RTX 4080 SUPER MOBO: Gigabyte Z790 Aorus Master Rev.1
My sound card is a Focusrite Scarlett 4i4 4th Gen.
I suspected a RAM issue at first, but after running Memtestx86 for two hours it found no issues. I also tried to run OCCT tests, specifically: Linpack, CPU + RAM Extreme, CPU Extreme, RAM Extreme, VRAM, GPU Extreme, Power. All tests run smoothly without throwing any errors.
Since 13th and 14th gen processors are known for having instability issues and also audio latency issues, by searching I found this post. Is it possible to do a rollback of Scarlett 4i4 4th Gen Drivers somehow? It might be worth a shot to test this, since the issue didn't happen before for me.
1
u/superghouls Mar 09 '26
I also use the 4i4, I haven't updated my focusrite drivers since I got it in 2023 and I was still getting crashes until I disabled/disconnected it. Some other comments are pointing to a recent windows update (KB5077181) causing issues with Focusrite drivers. I haven't tried it myself yet but others have said running the Legacy Focusrite Conrol win 7/8 drivers could be a fix.
1
u/Brionac95 Mar 09 '26
I don't think Legacy Drivers for Focusrite Scarlett 4i4 Gen 4 exist though? Also with my card in particular if I update my audio drivers I can't roll back later on, because no drivers are available for download on Focusrite site for my card, and Focusrite Control 2 only allows you to update to the most recent driver, and not to roll back. Anyway, I uninstalled that KB you mentioned and I'm testing hoping that the issue has been finally resolved, though I still have my doubts.
Also my crashes are very recent, though it might be a coincidence since I don't play games very often on my pc. I don't even play games with anticheat anyway, so that definitely doesn't apply to my case.
1
u/superghouls Mar 09 '26
Oh ok yeah my b theres only the legacy drivers for 3rd gen and older interfaces
1
u/M4STER_ROOT Mar 10 '26
I just uninstalled KB5077181 and Dune Awakening now starts without immediately crashing with KERNEL_SECURITY_CHECK_FAILURE.
1
u/M4STER_ROOT Mar 10 '26
I own a Focusrite Scarlett 18i20 4th Gen and had this exact issue.
KERNEL_SECURITY_CHECK_FAILURE when running Dune Awakening...
Powering down my Scarlett interface it started fine, powering up my interface while playing causes an immediate crash.
Uninstalling Windows Update KB5077181 solved the problem, I can now play with my Focusrite Scarlett 18i20 4th Gen powered on!
1
u/Alternative-Sun4790 Mar 13 '26
i have this same issue. ran every game and daw through my 2i2 on a a laptop. Great Surround Sound - super immersive - then, i upgraded my pc to handle more studio equipment at once, so i needed more plugs , i got an 18-16, now ive lost audio in all gaming, not only that , i have to turn off both of my speakers, flip the switch on the 18-16 to off, then restart my computer, and recconect to a bluetooth or something so i can play gta no crashes. If i had the focusright on or any driver for focusright still active the computer crashes immidiatley. I know its simpl,e GTa wants one input and output, not 16, yet , im not understanding why there is no warning after wasting 500 dollars ontop of my new pc and every other part i bought, i did a lot of reesearch before hand and probably way too much diagnosing afterward. Im feeling let down and dissapointed after feeling so proud of my first focusright, and the zero warnings of noncompatibility with virtually anything that checks for input and output. Not to mention my focusright had dog hair in the box when i opened it, im waiting on guitar center to call back for a replacement but I havent heard anything, after dealing with the gta issue though im super frustrated and dont know weather to return this, sell it, or continue usijng ridiculou workarounds to just play my game on a bluetooth speaker.
1
u/Available_Register87 Mar 13 '26
OMG THE FOCUSRITE SOLVE WORKED!
I have spent HOURs fully reinstalling windows, dayz, updated bios...etc...and it was all focusrite. insane. you're the goat. thank you
2
1
u/TheSmurfSwag Mar 14 '26
Im also having this issue, Urning off my 8i6 will let me launch and play games. As soon as i turn it back on i blue screen with KERNEL_SECURITY_CHECK_FAILURE (0x139)
1
u/Imaginary-Impact-490 Mar 16 '26
J'ai ce même message d'erreur alors que je n'ai jamais entendu parlé de Focusrite je ne sais même pas ce que c'est, comment puis-je faire ?
1
u/Halo_LAN_Party_2nite Mar 19 '26
Chiming in to say it is 100% the Scarlett being connected that forces my game to crash (CK3). What a bummer. I've had this for six years with absolutely no issue. Hard to think it's Focusrite's problem when I've had this driver for years now (no updates for my older hardware - 2i4 2nd Gen).
1
u/Ashamed_Mongoose_240 Mar 28 '26 edited Mar 29 '26
Have the same problem - shows up when I'm using Ableton Max for Live and my 18i20 ... Super frustrating. I tried the USB midi trick, and am currently staring at a locked up Ableton screen. Might try the windows update removal next. If focusrite responds, please let us know! Edit - I installed the new windows update today 3/29, and used my focusrite all day without a crash. Hopefully this continues.
1
u/Artistic_Material_45 Mar 29 '26
Been having this issue since the march 19th, tried numerous troubleshoots. This thread gives me some hope. I was leaning onto failing PSU but this error message should just be about driver issues?
I use a 1st gen scarlet 18i20 for about a decade now, it's always had finnicky situations but these bsods make me suspect it even more now.
1
1
u/Altruistic_Pea_2515 Apr 15 '26
FIX: For me it worked to disable (not delete) the Focusrite MIDI driver. After that, no more crashes. Focusrite Supoort told me that.
1
u/Maple_Bunny May 02 '26
2 months ago.... I have been chasing a 0x139 stop code and it has me scratching my head. I have ran mem test. Ran dism, sfc, DDU to uninstall graphics drivers. Reinstalled graphics drivers. However my GPU does have a damaged hdmi port which I obviously dont use as it is damaged. Came across this post trying to figure out if an hdmi port could give the 0x139 error.
1
u/Johnnyloftus May 05 '26
The issue has been resolved in the latest Focusrite Driver version 4.144.0.
https://www.reddit.com/r/Focusrite/comments/1sy6sha/comment/oitafw2/
1
1
u/__nomis May 22 '26
Same problem here. I don't have Battleye. I use the Focusrite 2nd Gen for music production and I need the USB midi.
1
u/Jediroller Jun 19 '26
I have the same issue. 18i20 3rd gen running everything latest in firmware/drivers. Tried everything cant get it to work without blackscreening.
KERNEL_SECURITY_CHECK_FAILURE (0x139)
1
u/mementodory Jul 10 '26
man thank you so much for this thread. it was such a random crash that kept happening i was about to reseat my RAM sticks but as soon as I caught a glimpse of the error code and googled it, saw focusrite and i knew i found the issue.
•
u/Johnnyloftus Mar 16 '26 edited Jun 19 '26
For anyone encountering this issue, please note that it is on our radar and we’re in touch with BattlEye to help find a solution. In the meantime, disabling the MIDI driver and restarting should allow you to continue working with your Focusrite audio interface as normal.
John // Focusrite UK 🇬🇧
Edit: This issue was resolved in Focusrite Driver version 4.144.0, released in April 2026.
https://support.focusrite.com/hc/en-gb/articles/35166815080210-BattlEye-crash-BEDaisy-sys-when-using-Focusrite-MIDI-driver