JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will be temporarily offline tomorrow for scheduled maintenance. Click here to view latest Destiny Server and Update Status.

Help

Help us help you.
10/4/2025 12:07:20 AM
1

Destiny 2 + Ba

This is getting out of hand. More than 35 crashes from the release of Edge of Fate. Could you please help me? This bugcheck analysis reveals that the crash is caused by a faulty anti-cheat driver (BEDaisy.sys) from BattlEye, which is sometimes crashing my system with a PAGE_FAULT_IN_NONPAGED_AREA while running Destiny 2. [spoiler] [quote]******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffa38145f2ac2f, memory referenced. Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE. bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the processor decided the fault was due to a corrupted PTE. bit 4 is set if the fault was due to attempted execute of a no-execute PTE. - ARM64: bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the fault was due to attempted execute of a no-execute PTE. Arg3: fffff8066b9e26b7, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for BEDaisy.sys KEY_VALUES_STRING: 1 Key : AV.Type Value: Write Key : Analysis.CPU.mSec Value: 1828 Key : Analysis.Elapsed.mSec Value: 32379 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 26 Key : Analysis.Init.CPU.mSec Value: 953 Key : Analysis.Init.Elapsed.mSec Value: 28041 Key : Analysis.Memory.CommitPeak.Mb Value: 111 Key : Analysis.Version.DbgEng Value: 10.0.27920.1001 Key : Analysis.Version.Description Value: 10.2506.23.01 amd64fre Key : Analysis.Version.Ext Value: 1.2506.23.1 Key : Bugcheck.Code.LegacyAPI Value: 0x50 Key : Bugcheck.Code.TargetModel Value: 0x50 Key : Dump.Attributes.AsUlong Value: 0x21008 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 : Failure.Bucket Value: AV_W_(null)_BEDaisy!unknown_function Key : Failure.Exception.IP.Address Value: 0xfffff8066b9e26b7 Key : Failure.Exception.IP.Module Value: BEDaisy Key : Failure.Exception.IP.Offset Value: 0x6426b7 Key : Failure.Hash Value: {4024c46b-040f-2932-f980-447accda06b7} Key : WER.System.BIOSRevision Value: 5.27.0.0 BUGCHECK_CODE: 50 BUGCHECK_P1: ffffa38145f2ac2f BUGCHECK_P2: 2 BUGCHECK_P3: fffff8066b9e26b7 BUGCHECK_P4: 2 FILE_IN_CAB: 100325-29984-01.dmp DUMP_FILE_ATTRIBUTES: 0x21008 Kernel Generated Triage Dump FAULTING_THREAD: ffff938023b89040 READ_ADDRESS: fffff806b2dc44c0: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse ffffa38145f2ac2f MM_INTERNAL_CODE: 2 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 (!blackboxwinlogon) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: destiny2.exe STACK_TEXT: ffffa381`45f28f18 fffff806`b20d1fa8 : 00000000`00000050 ffffa381`45f2ac2f 00000000`00000002 ffffa381`45f29180 : nt!KeBugCheckEx ffffa381`45f28f20 fffff806`b2049860 : fffffc7e`00168cc0 ffff8000`00000000 ffffa381`45f2ac2f 0000007f`fffffff8 : nt!MiSystemFault+0x7a0 ffffa381`45f29010 fffff806`b24ad6cb : 0000005a`33042ff8 00000000`00000000 00000000`00000004 fffffc00`2d198210 : nt!MmAccessFault+0x630 ffffa381`45f29180 fffff806`6b9e26b7 : 33eb8b04`fff6b1d6 00000004`02020202 00007fff`fffd0000 ffffffff`ffff0000 : nt!KiPageFault+0x38b ffffa381`45f29310 33eb8b04`fff6b1d6 : 00000004`02020202 00007fff`fffd0000 ffffffff`ffff0000 20ffa381`45f296b0 : BEDaisy+0x6426b7 ffffa381`45f29318 00000004`02020202 : 00007fff`fffd0000 ffffffff`ffff0000 20ffa381`45f296b0 ff00005c`d8ed1189 : 0x33eb8b04`fff6b1d6 ffffa381`45f29320 00007fff`fffd0000 : ffffffff`ffff0000 20ffa381`45f296b0 ff00005c`d8ed1189 00000000`00000004 : 0x00000004`02020202 ffffa381`45f29328 ffffffff`ffff0000 : 20ffa381`45f296b0 ff00005c`d8ed1189 00000000`00000004 00000000`00041f70 : 0x00007fff`fffd0000 ffffa381`45f29330 20ffa381`45f296b0 : ff00005c`d8ed1189 00000000`00000004 00000000`00041f70 fffff806`6b67d4f9 : 0xffffffff`ffff0000 ffffa381`45f29338 ff00005c`d8ed1189 : 00000000`00000004 00000000`00041f70 fffff806`6b67d4f9 00000000`00000000 : 0x20ffa381`45f296b0 ffffa381`45f29340 00000000`00000004 : 00000000`00041f70 fffff806`6b67d4f9 00000000`00000000 00005cd8`ed118920 : 0xff00005c`d8ed1189 ffffa381`45f29348 00000000`00041f70 : fffff806`6b67d4f9 00000000`00000000 00005cd8`ed118920 00000000`00000001 : 0x4 ffffa381`45f29350 fffff806`6b67d4f9 : 00000000`00000000 00005cd8`ed118920 00000000`00000001 00000000`00041f07 : 0x41f70 ffffa381`45f29358 00000000`00000000 : 00005cd8`ed118920 00000000`00000001 00000000`00041f07 00000000`00000011 : BEDaisy+0x2dd4f9 SYMBOL_NAME: BEDaisy+6426b7 MODULE_NAME: BEDaisy IMAGE_NAME: BEDaisy.sys STACK_COMMAND: .process /r /p 0xffff938fdd6d4040; .thread 0xffff938023b89040 ; kb BUCKET_ID_FUNC_OFFSET: 6426b7 FAILURE_BUCKET_ID: AV_W_(null)_BEDaisy!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {4024c46b-040f-2932-f980-447accda06b7} Followup: MachineOwner ---------[/quote][/spoiler]
English
#Help #pcsupport

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • Hello there, Thank you very much for reaching out to us. I'm sorry to hear that you are crashing due to this driver. To look into some troubleshooting and additional information, we recommend checking out [url=https://www.battleye.com/support/faq/]BattlEye's FAQ page[/url]. If you have any further issues, questions, or concerns, we'd encourage you to reach out to their support team for additional assistance.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon