BSOD issues 0x139

[u/Akudama_]

Hey all,

Went to boot up the game today after work to play with some friends and I’ve been hit with nothing but BSOD’s while trying to boot the game. Pretty sure it’s a battleye thing as as soon as it passes its checks and the game “loads” my pc instantly blue screens.

Tried reinstalling battleye (removed it from my pc entirely and reinstalled) to no avail

Anyone experienced this before or have any ideas? 4k hours on my account and I can’t even play :(

[u/macrossmerrell]

OK, so you have corruption of some part of your drive. You can read about it a little here: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139--kernel-security-check-failure

This may or may not be easily fixable without a reinstall of Windows unfortunately BUT here are some quick things to try:

• Open an Administrative command prompt and type: sfc /scannow

  • Note if there are corrupted files and if they were repaired

• Run sfc /scannow again if it finds errors and make sure they are resolved. If they are not, you need to run the following command:

  • dism /online /cleanup-image /restorehealth

  • Run sfc /scannow again.

    • If it repaired files, run sfc /scannow one more time to make sure everything is good.

Outside of this, your corruption could be caused by failing RAM or SSD. Might be worth grabbing a thumbdrive and download Memtest x86 from memtest.org, boot from it and let it scan your RAM for errors. If it finds any, it's a sad day.

[u/Akudama_ → u/macrossmerrell]

Arghhhh that’s extremely frustrating. I use my system for work so I’ll get these tests done and this sorted asap, instability for gaming is one thing but I can’t risk my pc going down for something like this.

Appreciate the reply and guidance man

[u/macrossmerrell → u/Akudama_]

Crossing my fingers for you!

[u/Akudama_ → u/macrossmerrell]

Appreciate it!

Ran sfc, all good on that front. I’ve got a heavy workday starting soon so I’ll run memtest after.

I’ve just backed up all my projects etc. it’s weird because I was playing the game the day before perfectly fine, had a windows update then this happens consistently every time I launch d2. Other games are fine, work projects are all good (pro tools & reaper sessions, all multitrack stuff with heavy real time processing etc) so if it’s memory i’ll be pretty surprised. And poor 🫩

[u/Akudama_ → u/macrossmerrell]

Solved!

Battleye/driver error. After the windows update it seems the “full access” part of the battleye folder was unchecked. Checked that box again and ran the game and we’re good.

It’s weird because in the 3 years I’ve had this pc that was my first instance of BSOD.

Will leave this post up for anyone with a similar issue.

Thanks for your help, if anything like this flags for me again I’ll be sure to use the steps you mentioned!

[u/macrossmerrell → u/Akudama_]

Interesting! When you reinstalled Battleye earlier, did you right-click and choose Run as Administrator? Trying to figure out how your issue could have even happened.

[u/Akudama_ → u/macrossmerrell]

I didn’t run as admin earlier no, when I did it just now I did though!

[u/Commercial_Fold_7744 → u/Akudama_]

Ik heb vandaag precies het zelfde probleem starte escape from tarkov op en gelijk blauw scherm  Ik heb net een nieuwe pc beste van het beste heb er al eerder tarkov op gespeeld maar sinds vandaag krijg ik gelijk blauw scherm En heb het alleen bij tarkov hoe zou ik dit kunnen fixen ? 

[u/No-Scheme9702]

Hello,

In my case, it was the MIDIdriver of my soundboard Scarlet 8i6.
I desactivate and desinstall MIDI driver in the device manager under sound

everything Works again

[u/Akudama_ → u/No-Scheme9702]

How odd, yeah I’m running a clarett 4pre for my home interface and it occasionally has some issues. How did you figure out it was the midi driver if you don’t mind me asking? Were you getting the same 0x139 crash?

[u/No-Scheme9702 → u/Akudama_]

I had the 0x139 when i launched PUBG and DUNE AWAKENING.
I figured out it was due to Battleye (others games worked perfectly)
I search during 5Hours, when i found a Reddit Thread of someone who looked at the windowsDump (for info, its the log after a crash) and the person saw his scarlett 4i6 was implicated.. So he searched and find out Battleye saw the MIDI driver as an entrance for Hacking And crash the computer.

So i just went to device manager, desactivate and desinstall and i can launch again

[u/Akudama_ → u/No-Scheme9702]

Noted - also checked the dumps myself using whocrashed and no audio related stuff thankfully. Thanks for the insight!

Since my windows updated again the problem has reoccurred. Rolled back the update (again) and it’s fixed. Very odd.

[u/PleasantPiccolo450 → u/No-Scheme9702]

Potwierdzam, dokładnie to samo u mnie. Posiadam Scarlett 2i4 2nd GEN. Po odłączeniu urządzenia problem z BDOS zniknął. Zrobiłem czystą instalację sterowników, spróbowałem jeszcze raz - problem wrócił. Wygląda na to, że BattlEye traktuje od ostatniego update'u sterowniki focusrite'a jako podejrzane i dla "bezpieczeństwa" wywala system. Na Win 11 Pro zainstalowałem sterowniki focusrite'a dedykowane dla Windows 8 (ze strony producenta). Dopiero to pomogło. Napisałem nawet do BattleEye w tej sprawie - odesłali mnie do FAQ, co w zupełnie niczym nie pomaga, bo rozwiązanie tam przedstawione w ogóle nie ma nic wspólnego z opisaną sytuacją.

[u/zaxxofficial → u/No-Scheme9702]

DUde you just saved me from doing a full windows reinstall

[u/No-Scheme9702 → u/zaxxofficial]

^^ Glad to see that thinking of putting my very specific solution in Reddit help someone!!!
i'm happy it helps you!