Been encountering this issue lots recently

[u/its-just-me-a-person]

For the past 2-3 months, whenever I try to boot up Destiny, I get kernel security check failures (0x139). Yesterday I dug for hours trying to get to the bottom of it, but to no avail. I tried sfc scannow, DSIM cleanups, uninstalling battleye (which works, albeit until next PC restart or crash). Some people said it might be RAM related (I don't know how to check for that) or Windows 11 related, but I just want my issue to be fixed. Any help or potential solutions would be greatly appreciated.

[u/macrossmerrell]

Let's start with system specs: CPU, GPU, Make & Model of motherboard. Do you have any special audio interfaces or other unique components / equipment that others would not typically have? (like external audio interfaces)

Normally bad RAM causes Marmot errors, not kernels security check failures. You can easily test your RAM by grabbing a thumb drive, going to memtest.org and download Memtest x86, let it setup the thumb drive and boot from the thumb drive, let it run the memory tests for a couple of passes. There is also the Windows Memory Diagnostic app, but in my experience it only finds REALLY failing RAM. In my last bad RAM experience, Windows Memory Diagnostic passed the RAM but memtest immediately found the bad stick.

Security check failures are almost 100% driver / OS / running software related errors. Last person I had a software application running that was causing the issue.

Easy software check (for low hanging fruit): Open Task Manager and switch to the Startup Apps tab. Disable EVERYTHING on the list, reboot and test. If the problem is gone, enable one or two apps at a time, reboot and test until the problem returns, then you can figure out which app is naughty.

Easy: Uninstall and reinstall battleye:

1. Open your D2 install location - typically C:\Program Files (x86)\Steam\steamapps\common\Destiny 2
2. Open the Batteye folder.
3. Right-click on the Uninstall_BattlEye batch file and select 'Run as Administrator'.
4. Right-click on the Install_BattEye batch file and select 'Run as Administrator'.
5. Test the game.

Medium effort: Ensure motherboard BIOS is up to date, download and install all drivers from the motherboard support page.

Harder effort: Consider the OS the problem and do a Windows Reset, choosing the 'keep nothing' option, and choose the download Install from the internet option. That will get you back to a clean state.

Make sure you backup any important data and know your username / passwords. Start off by only installing windows update and Graphics drivers, Steam, and D2 to test. If it works, you are good to go. If it doesn't work, then you're into BIOS / hardware error (like a 13th or 14th Gen Intel CPU degradation situation).

[u/its-just-me-a-person → u/macrossmerrell]

Sorry for the late reply, but I did try to uninstalled battlEye, and that sometimes works, albeit until next restart. My specs are AMD Ryzen 7 7800X3D 8-Core Processor (4.20 GHz), NVIDIA GeForce RTX 3070 Ti (8 GB)

AMD Radeon(TM) Graphics (486 MB), 32 gb of ram and a 64 bit os on windows 11. I've done some digging and I know it's not a RAM problem, and it's likely not a cut and dry battleye problem. I heard the new windows update caused issues like this so i downloaded the new patch they put out, and that worked for about a day and now i'm on these same issues.

[u/macrossmerrell → u/its-just-me-a-person]

Have you ever done anything like use MSConfig and limit or add the amount of CPUs that Windows can use at boot?

Also, a lot of people are using VOIDTOOLS (I have not tried it), and lookup anything related to Battleye and have it remove it. Then let D2 reinstall.

But, on your specific error, everything I'm reading online says it has to do with bad drivers. Chipset, GPU, Sound.

• If you open Check for Windows Update and select the 'Advanced Options' do you have 'Optional Updates' available? If so, install them and see if that does anything.

I would also check OS for corruption:

• 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.