Destiny 2 BSOD (Fixed)

[Peppr]

Launching destiny 2 blue screens my computer with error: page fault in unpaged area
Seems to be related to battle eye.

Here's the WhoCrashed analysis:

On Sat 11/09/2021 15:04:32 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\091121-35203-01.dmp
This was probably caused by the following module: bedaisy.sys (BEDaisy+0x2AD428)
Bugcheck code: 0x50 (0xFFFFF8058EC55080, 0x10, 0xFFFFF8058EC55080, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bedaisy.sys .
Google query: bedaisy.sys PAGE_FAULT_IN_NONPAGED_AREA

Can't play D2 until fix.

(Fix: What worked for me just now was deleting battle eye folder from game directory, the re verifying files on steam. Went into the folder afterwards and set the Battle Eye exe and Destiny 2 to launch as admin.

Just managed to boot the game with no crash.)

[HugoTaHell]

Are you on an ACER computer? The Googles says that crash seems to be caused by old Acer drivers. update drivers.

[Rogue]

https://www.tomshardware.com/how-to/fix-page-fault-error-windows-10

What makes you think battle eye?

[Peppr]

Originally posted by HugoTaHell:

Are you on an ACER computer? The Googles says that crash seems to be caused by old Acer drivers. update drivers.

Nothing acer in my setup, windows updates all done. GPU is up to date as well.

Originally posted by Rogue:

https://www.tomshardware.com/how-to/fix-page-fault-error-windows-10

What makes you think battle eye?

"This was probably caused by the following module: bedaisy.sys (BEDaisy+0x2AD428)"

BEdaisy is battleeye. Also uninstalling battle eye and launching the game, it doesnt blue screen until it makes me install battle eye. Also it's not pulling a driver as the problem. It's saying software problem.

[Rogue]

Originally posted by Peppr:

Originally posted by HugoTaHell:

Are you on an ACER computer? The Googles says that crash seems to be caused by old Acer drivers. update drivers.

Nothing acer in my setup, windows updates all done. GPU is up to date as well.

Originally posted by Rogue:

https://www.tomshardware.com/how-to/fix-page-fault-error-windows-10

What makes you think battle eye?

"This was probably caused by the following module: bedaisy.sys (BEDaisy+0x2AD428)"

BEdaisy is battleeye. Also uninstalling battle eye and launching the game, it doesnt blue screen until it makes me install battle eye. Also it's not pulling a driver as the problem. It's saying software problem.

Gotcha. There was a quote
"When starting my game with BattlEye enabled, my system crashes with a bluescreen (BSOD).

First of all, ensure that Driver Verifier is disabled on your system as it is currently known to cause problems with BE. You can find how to do so here: https://support.microsoft.com/en-us/help/244617/using-driver-verifier-to-identify-issues-with-windows-drivers-for-adva. To disable it please clear all of its settings and reboot your system. Secondly, please fully update your system’s BIOS. If that doesn’t help and the crashes persist please contact our support directly so we can investigate your issue."

Not sure if that will help you but it's a general fix so maybe.

[EDIT] Another BattleEye BSOD for a different game. On top of this another person commented saying that it was fixed after they verified game files as well.

Ok. It somehow worked. Not sure which step made it so but will list what i did (not in any particular order)

Driver updates, windows updates, antivirus scand, adwcleaner scan etc.

Uninstalling every battle eye file and veryfing game local files again.

Made battleye.exe ignored by antivirus, firewall, made it run by administrator and gave it "full control" check in properties->security tab (same for r6.exe and r6BE.exe)

Sfc /scannow, memory check, discs checks etc.

Basically every step listed in battleye troubleshooting faq (but after doing so it still hasnt been working)

[Peppr]

Originally posted by Rogue:

Originally posted by Peppr:

Nothing acer in my setup, windows updates all done. GPU is up to date as well.




"This was probably caused by the following module: bedaisy.sys (BEDaisy+0x2AD428)"

BEdaisy is battleeye. Also uninstalling battle eye and launching the game, it doesnt blue screen until it makes me install battle eye. Also it's not pulling a driver as the problem. It's saying software problem.

Gotcha. There was a quote
"When starting my game with BattlEye enabled, my system crashes with a bluescreen (BSOD).

First of all, ensure that Driver Verifier is disabled on your system as it is currently known to cause problems with BE. You can find how to do so here: https://support.microsoft.com/en-us/help/244617/using-driver-verifier-to-identify-issues-with-windows-drivers-for-adva. To disable it please clear all of its settings and reboot your system. Secondly, please fully update your system’s BIOS. If that doesn’t help and the crashes persist please contact our support directly so we can investigate your issue."

Not sure if that will help you but it's a general fix so maybe.

[EDIT] Another BattleEye BSOD for a different game. On top of this another person commented saying that it was fixed after they verified game files as well.

Ok. It somehow worked. Not sure which step made it so but will list what i did (not in any particular order)

Driver updates, windows updates, antivirus scand, adwcleaner scan etc.

Uninstalling every battle eye file and veryfing game local files again.

Made battleye.exe ignored by antivirus, firewall, made it run by administrator and gave it "full control" check in properties->security tab (same for r6.exe and r6BE.exe)

Sfc /scannow, memory check, discs checks etc.

Basically every step listed in battleye troubleshooting faq (but after doing so it still hasnt been working)

I'm going to do a fresh windows install then I'll try these. Thanks.

[Peppr]

After fresh windows install and bios update, launching the game no longer gave me a BSOD, but it didn't launch either. I heard a windows notification but one doesn't appear, and then nothing happens.

Turned off Windows Defender to see if it was being blocked. Also verified files on steam. None of those did the trick.

What worked for me just now was deleting battle eye folder from game directory, the re verifying files on steam. Went into the folder afterwards and set the Battle Eye exe and Destiny 2 to launch as admin.

Just managed to boot the game with no crash.

[KDM 16AAB]

Do you have any Gaijin games installed.

[Bis]

Originally posted by Rogue:

Originally posted by Peppr:

Nothing acer in my setup, windows updates all done. GPU is up to date as well.




"This was probably caused by the following module: bedaisy.sys (BEDaisy+0x2AD428)"

BEdaisy is battleeye. Also uninstalling battle eye and launching the game, it doesnt blue screen until it makes me install battle eye. Also it's not pulling a driver as the problem. It's saying software problem.

Gotcha. There was a quote
"When starting my game with BattlEye enabled, my system crashes with a bluescreen (BSOD).

First of all, ensure that Driver Verifier is disabled on your system as it is currently known to cause problems with BE. You can find how to do so here: https://support.microsoft.com/en-us/help/244617/using-driver-verifier-to-identify-issues-with-windows-drivers-for-adva. To disable it please clear all of its settings and reboot your system. Secondly, please fully update your system’s BIOS. If that doesn’t help and the crashes persist please contact our support directly so we can investigate your issue."

Not sure if that will help you but it's a general fix so maybe.

[EDIT] Another BattleEye BSOD for a different game. On top of this another person commented saying that it was fixed after they verified game files as well.

Ok. It somehow worked. Not sure which step made it so but will list what i did (not in any particular order)

Driver updates, windows updates, antivirus scand, adwcleaner scan etc.

Uninstalling every battle eye file and veryfing game local files again.

Made battleye.exe ignored by antivirus, firewall, made it run by administrator and gave it "full control" check in properties->security tab (same for r6.exe and r6BE.exe)

Sfc /scannow, memory check, discs checks etc.

Basically every step listed in battleye troubleshooting faq (but after doing so it still hasnt been working)

Dude you've saved me from dementia...
I had (hope it won't come back...) the same issue with escape from tarkov and battleyes.
I Tried everything without success.. Then I saw your comment :

Made battleye.exe ignored by antivirus, firewall, made it run by administrator and gave it "full control" check in properties->security tab (same for r6.exe and r6BE.exe

It was that... Thank you ..

[Foogle]

Originally posted by Peppr:

(Fix: What worked for me just now was deleting battle eye folder from game directory, the re verifying files on steam. Went into the folder afterwards and set the Battle Eye exe and Destiny 2 to launch as admin.

Just managed to boot the game with no crash.)

Hey, could you advise a little more detail on what you did here? I have the same problem and would like to fix it :-)

[Peppr]

Originally posted by Foogle:

Originally posted by Peppr:

(Fix: What worked for me just now was deleting battle eye folder from game directory, the re verifying files on steam. Went into the folder afterwards and set the Battle Eye exe and Destiny 2 to launch as admin.

Just managed to boot the game with no crash.)

Hey, could you advise a little more detail on what you did here? I have the same problem and would like to fix it :-)

Right click the game on steam, go to properties, local files. Right click the D2 exe and set it to run in administrator mode. That fixed it for me.

[WileyCat]

sorry to revive a dead thread but i followed the instructions in my case for tarkov and i got this again
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: fffff806c203c080, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: fffff806c203c080, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

Unable to load image \??\C:\Program Files (x86)\Common Files\BattlEye\BEDaisy.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Execute

Key : Analysis.CPU.mSec
Value: 5608

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 7870

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 50

BUGCHECK_P1: fffff806c203c080

BUGCHECK_P2: 10

BUGCHECK_P3: fffff806c203c080

BUGCHECK_P4: 2

READ_ADDRESS: fffff806c203c080

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: csrss.exe

TRAP_FRAME: ffffa30caa79abe0 -- (.trap 0xffffa30caa79abe0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff806c203c080 rbx=0000000000000000 rcx=ffffffffffffffff
rdx=ffffa30caa79ade0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff806c203c080 rsp=ffffa30caa79ad78 rbp=ffffa30caa79add0
r8=ffffa30caa79ade8 r9=0000000000000040 r10=00000000ffffffff
r11=0000000000000051 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff806`c203c080 ?? ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
fffff806`c203c080 ?? ???

STACK_TEXT:
ffffa30c`aa79a938 fffff807`5b4744bf : 00000000`00000050 fffff806`c203c080 00000000`00000010 ffffa30c`aa79abe0 : nt!KeBugCheckEx
ffffa30c`aa79a940 fffff807`5b2a4d70 : ffffa30c`00000000 00000000`00000010 ffffa30c`aa79ac60 00000000`00000000 : nt!MiSystemFault+0x1b171f
ffffa30c`aa79aa40 fffff807`5b409bd8 : fffff80a`72080000 00000000`ffffffff fffff80b`b2095eb8 00000000`00000040 : nt!MmAccessFault+0x400
ffffa30c`aa79abe0 fffff806`c203c080 : fffff80b`b23adcee ffffa30c`aa79aef0 00007ffc`a1e0d890 00000000`00000040 : nt!KiPageFault+0x358
ffffa30c`aa79ad78 fffff80b`b23adcee : ffffa30c`aa79aef0 00007ffc`a1e0d890 00000000`00000040 00007ffc`a1e0d7f0 : 0xfffff806`c203c080
ffffa30c`aa79ad80 fffff80b`b23ad997 : 00000167`17f50000 00000000`00001000 ffffce8b`2a01d140 00007ffc`a1e0d190 : BEDaisy+0x32dcee
ffffa30c`aa79ade0 fffff80b`b23ad838 : fffff80b`b20951d8 00000000`00000001 00000000`00000424 ffffa30c`aa79b04a : BEDaisy+0x32d997
ffffa30c`aa79afc0 fffff80b`b23a5ab5 : ffffa30c`aa79b150 ffffa30c`aa79b168 00000000`00000001 00000000`6c46624f : BEDaisy+0x32d838
ffffa30c`aa79b010 fffff807`5b69accc : ffffe18c`d906a240 ffffa30c`00000000 ffffa30c`aa79b168 ffffa30c`aa79b168 : BEDaisy+0x325ab5
ffffa30c`aa79b0b0 fffff807`5b69ae3a : 00000000`00000000 00000000`00000000 00000000`00101000 ffff8e41`4d34969b : nt!ObpCallPreOperationCallbacks+0x10c
ffffa30c`aa79b130 fffff807`5b694283 : ffffce8b`1b8da7a0 ffffa30c`aa79b2c0 ffffa30c`aa79b740 ffffa30c`aa79b740 : nt!ObpPreInterceptHandleCreate+0xaa
ffffa30c`aa79b1a0 fffff807`5b6f4629 : ffffa30c`aa79b740 ffffce8b`36f6c080 00000000`00000000 00000000`00000000 : nt!ObpCreateHandle+0xce3
ffffa30c`aa79b3b0 fffff807`5b6ab1df : 00000000`00000001 ffffa30c`aa79bb80 00000000`00000000 00000000`00000001 : nt!ObOpenObjectByPointer+0x1b9
ffffa30c`aa79b630 fffff807`5b5e83b0 : ffffe18c`d6dbb850 ffffce8b`36f6c080 00000000`00000000 ffffce8b`27b9d9a0 : nt!PsOpenProcess+0x3af
ffffa30c`aa79b9c0 fffff807`5b40e09d : ffffce8b`2a8b8080 0000005b`36dbed18 ffffa30c`aa79baa8 00000000`00000000 : nt!NtAlpcOpenSenderProcess+0x1c0
ffffa30c`aa79ba90 00007ffc`a1e0e194 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x3f2
0000005b`36dbecf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`a1e0e194


SYMBOL_NAME: BEDaisy+32dcee

MODULE_NAME: BEDaisy

IMAGE_NAME: BEDaisy.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 32dcee

FAILURE_BUCKET_ID: AV_X_(null)_BAD_IP_BEDaisy!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d0f5d3f5-7191-7057-d947-2c4e7ea23247}

any help at all would be loved

i get the same ♥♥♥♥ with the cycle frontier too but rust hng ect works fortnite works i just finally upgraded to a 3070 and 64 g's of corsair vengence and im getting my ass kicked by this

[WileyCat]

Made battleye.exe ignored by antivirus, firewall, made it run by administrator and gave it "full control" check in properties->security tab (same for r6.exe and r6BE.exe i followed these also verified the game files went into the windows firewall created exceptions did it through avg took ownership and made everything run as admin with full perms and i am about to lose it fr i just want to play my damned games

[mintTea]

is this under windows 10 or 11? i assume destony functions under either?

[WileyCat]

i am under windows 10 the latest update im actually updating my bio's and installing a 5800x right now
ill see if that works god i hope so i have the battlepass i paid for on the cycle to do and i gotta figure this out man i cant remeber how i fixed it last time ive tried everything short of of a full reinstall and reinstalling windows on a m.2 ssd is a pain in the rear and honestly ill just can tarkov and the cycle if they are my only games that do not work if it comes to it

[WileyCat]

destiny works for me aswell fortnite ect most battleeye games do