Windows BSOD when launching Destiny 2

William Harpur · Mar 14, 2025

Hi,

Been working on this for some time. I have reinstalled windows from a bootable USB.

Disabled any and all overclocks and cannot seem to find the issue.

MINIDUMP IS:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 43

Microsoft (R) Windows Debugger Version 10.0.27793.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\031325-13234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.000 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 43

Microsoft (R) Windows Debugger Version 10.0.27793.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\031325-13234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff800`76c00000 PsLoadedModuleList = 0xfffff800`77af47a0
Debug session time: Thu Mar 13 18:21:05.705 2025 (UTC + 0:00)
System Uptime: 0 days 23:11:38.551
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols

Loading unloaded module list
....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`770b7ce0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffc98c`c4a45cf0=????????????????
10: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffc98cc4a488e0, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffffc98cc4a48838, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for BEDaisy.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 953

Key : Analysis.Elapsed.mSec
Value: 45019

Key : Analysis.IO.Other.Mb
Value: 17

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 24

Key : Analysis.Init.CPU.mSec
Value: 531

Key : Analysis.Init.Elapsed.mSec
Value: 648754

Key : Analysis.Memory.CommitPeak.Mb
Value: 91

Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000

Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2410.2.2

Key : Bugcheck.Code.LegacyAPI
Value: 0x139

Key : Bugcheck.Code.TargetModel
Value: 0x139

Key : Dump.Attributes.AsUlong
Value: 0x31808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : FailFast.Name
Value: CORRUPT_LIST_ENTRY

Key : FailFast.Type
Value: 3

Key : Failure.Bucket
Value: 0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function

Key : Failure.Exception.Code
Value: 0xffffffffc0000409

Key : Failure.Exception.Record
Value: 0xffffc98cc4a48838

Key : Failure.Hash
Value: {59d8eb10-b2e4-7df6-f6a5-49968226dbb8}

Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7497cf94

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 1

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 38408431

Key : Hypervisor.Flags.ValueHex
Value: 0x24a10ef

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 0x3f7

BUGCHECK_CODE: 139

BUGCHECK_P1: 3

BUGCHECK_P2: ffffc98cc4a488e0

BUGCHECK_P3: ffffc98cc4a48838

BUGCHECK_P4: 0

FILE_IN_CAB: 031325-13234-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x31808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffe008d4756540

TRAP_FRAME: ffffc98cc4a488e0 -- (.trap 0xffffc98cc4a488e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe008ca0ea688 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80076e1207a rsp=ffffc98cc4a48a70 rbp=ffffb981b29e5180
r8=0000000000000002 r9=0000000000000000 r10=ffffe008c17ffa01
r11=0000000000001001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KiProcessThreadWaitList+0x17a:
fffff800`76e1207a cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffffc98cc4a48838 -- (.exr 0xffffc98cc4a48838)
ExceptionAddress: fffff80076e1207a (nt!KiProcessThreadWaitList+0x000000000000017a)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000003

EXCEPTION_STR: 0xc0000409

STACK_TEXT:
ffffc98c`c4a48a70 fffff800`76e11cec : ffffe008`00000000 00000000`00000001 ffff9406`00000002 00000000`00000000 : nt!KiProcessThreadWaitList+0x17a
ffffc98c`c4a48b10 fffff800`76e805e3 : 00000000`00000000 00000000`00000000 ffffe008`ca1c8040 ffffe008`d5fdc010 : nt!KiExitDispatcher+0x4c
ffffc98c`c4a48b70 fffff800`5823f14c : 00000000`00000400 ffffe008`d5fdc010 00000000`00000000 00000000`00000000 : nt!KeInsertQueueApc+0x263
ffffc98c`c4a48c30 00000000`00000400 : ffffe008`d5fdc010 00000000`00000000 00000000`00000000 00000000`00000000 : BEDaisy+0x76f14c
ffffc98c`c4a48c38 ffffe008`d5fdc010 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x400
ffffc98c`c4a48c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe008`d5fdc010

STACK_COMMAND: .trap 0xffffc98cc4a488e0 ; kb

SYMBOL_NAME: BEDaisy+76f14c

MODULE_NAME: BEDaisy

IMAGE_NAME: BEDaisy.sys

BUCKET_ID_FUNC_OFFSET: 76f14c

FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {59d8eb10-b2e4-7df6-f6a5-49968226dbb8}

Followup: MachineOwner
---------

***Moved from Windows / Windows 11 / Performance and system failures***
Click to expand...

:)

Capoo.W - MSFT

Hi, William Harpur.

Thank you for posting in the Microsoft Community.

From your description, I understand that you are experiencing a Windows blue screen when launching Destiny 2. I understand your confusion about this issue.

First of all, I appreciate that you have tried to solve the problem by reinstalling Windows on your own by enabling USB and disabling all overclocking attempts.

Perhaps other users will be able to troubleshoot similar issues based on the solutions you have tried. Let me express my gratitude to you.

You are experiencing a blue screen of death (BSOD) when launching Destiny 2. BSODs are usually caused by hardware or driver issues.

Make sure your graphics card drivers are up to date. You can download the latest drivers directly from the graphics card manufacturer's official website.

Excessive hardware temperatures can also cause BSODs. Please ensure that the CPU and GPU temperatures are within the normal range.

Unstable power supply can also cause BSODs. Make sure your power supply is stable enough and can meet the needs of the system.

From the blue screen analysis information you provided, the system encountered a KERNEL_SECURITY_CHECK_FAILURE (139) error, specifically due to LIST_ENTRY corruption (double removal problem). This error is usually related to kernel data structure corruption.

BEDaisy.sys is a driver related to the BattlEye anti-cheat system. Since the blue screen analysis mentioned that its timestamp could not be verified, it may be that this driver caused the problem.

Please uninstall and reinstall BattlEye:

Open the installation directory of "Destiny 2" and find the BattlEye folder.

Run Uninstall_BattlEye.bat.

Restart the game and BattlEye will be automatically reinstalled.

We look forward to hearing from you!

Best Regards.

Capoo - MSFT | Microsoft Community Support Specialist

Jon-Symo

Yes, I still had BSOD crashes after the 3.63.16003 update with Sophos anti-virus. Removing the Sophos has allowed both Halo and Destiny to launch.

MancSoulja

Same issue here, it started when using Norton to scan Xbox Game Pass folders would cause a BSOD, now just launching some Game Pass games will cause BSODs.

NicoNaus

I'm having the same issue. I'm using a Microsoft Surface Pro 3 running Windows 10, build 9926.

Upon launching Microsoft Bingo, the app tries to sign in, and then I get a BSOD. This happens every time.

Skepticality

I believe when it comes to destiny 2 gamesharing wont work as its linked to the account it first launches on

Windows BSOD when launching Destiny 2