Gta V Enhanced constant random crashes and BSODs after few mins of gameplay ( STATUS_ACCESS_VIOLATION / PAGE_FAULT_IN_NON-PAGED_AREA / ATTEMPTED_WRITE_TO_READONLY_MEMORY )

Question

Gta V Enhanced constant random crashes and BSODs after few mins of gameplay ( STATUS_ACCESS_VIOLATION / PAGE_FAULT_IN_NON-PAGED_AREA / ATTEMPTED_WRITE_TO_READONLY_MEMORY )

Zak 100

The laptop is basically brand new with an upgraded ssd and only recently installed a clean/fresh windows 11 home copy from usb (in part to resolve this problem) with drivers from -> https://rog.asus.com/laptops/rog-strix/rog-strix-scar-16-2024/helpdesk_download/

The following are Event Viewer logs within the time-frame from opening the app to it crashing:

"Session "NT Kernel Logger" failed to start with the following error: 0xC0000035"

"Session "Cloud Files Diagnostic Event Listener" failed to start with the following error: 0xC0000022"

"Faulting application name: GTA5_Enhanced.exe, version: 0.0.0.0, time stamp: 0x00000000

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x00007ffbea0b9350

Faulting process id: 0x3EA8

Faulting application start time: 0x1DD2A4CECB88C67

Faulting application path: E:\Steam\steamapps\common\Grand Theft Auto V Enhanced\GTA5_Enhanced.exe

Faulting module path: unknown

Report Id: 27d470bd-e8cb-4751-903b-f0acf5fdc356

Faulting package full name:

Faulting package-relative application ID: "

"The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit."

PS: BSOD-ing with the following:

What failed: BEDaisy.sys

Pretty sure this has something to do with the kernel anti-cheat: Battleye.

Device Specs: Screenshot 2026-08-12 171531

The following cmds were run as admin to try to solve the issue:

dism.exe /online /cleanup-image /scanhealth
dism.exe /online /cleanup-Image /checkhealth
dism.exe /online /cleanup-image /restorehealth
dism.exe /online /cleanup-image /startcomponentcleanup
sfc /scannow
chkdsk C: /f /x /r
chkdsk D: /f /x /r
chkdsk E: /f /x /r

Have also contacted Rockstar Support, Battleye, NVIDIA and ASUS for a resolution but none provided.

This issue has been ongoing for months now. I just want to play the game I paid for, please help. Do lemme know if any other information is required from my end to get a better understanding on the issue.

Zak 100

This still happens... Any technical expert? Please help.

Here is the recent Bugcheck Analysis from the Minidump.

nt!KeBugCheckEx:
fffff806`b9efd0a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffeb03`7450ee40=0000000000000050
7: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................................
Loading User Symbols

Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        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: ffffeb0396ae3538, 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: fffff8066e6942eb, 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.PTE
    Value: Invalid

    Key  : AV.Page.Virtual
    Value: 0xffffeb0396ae0000

    Key  : AV.Type
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 921

    Key  : Analysis.Elapsed.mSec
    Value: 5106

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    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_BEDaisy!unknown_function

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8066e6942eb

    Key  : Failure.Exception.IP.Module
    Value: BEDaisy

    Key  : Failure.Exception.IP.Offset
    Value: 0x5442eb

    Key  : Failure.Hash
    Value: {36b04c21-521f-babb-382f-2a12c3ddef17}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    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: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    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

    Key  : WER.System.BIOSRevision
    Value: 5.27.0.0


BUGCHECK_CODE:  50

BUGCHECK_P1: ffffeb0396ae3538

BUGCHECK_P2: 2

BUGCHECK_P3: fffff8066e6942eb

BUGCHECK_P4: 2

FILE_IN_CAB:  090426-19296-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffdb0dcedf3040

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  ffffeb0396ae3538

WRITE_ADDRESS: fffff806ba9c54d8: Unable to get MiVisibleState
 ffffeb0396ae3538 

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IP_IN_PAGED_CODE: 
BEDaisy+5442eb
fffff806`6e6942eb 4431840400dd3e98 xor     dword ptr [rsp+rax-67C12300h],r8d

STACK_TEXT:  
ffffeb03`7450ee38 fffff806`b9cea0d1     : 00000000`00000050 ffffeb03`96ae3538 00000000`00000002 ffffeb03`7450f0a0 : nt!KeBugCheckEx
ffffeb03`7450ee40 fffff806`b9c92ed6     : ffffeb03`7450f0b4 ffff8000`00000000 ffffeb03`96ae3538 0000007f`fffffff8 : nt!MiSystemFault+0x661
ffffeb03`7450ef30 fffff806`ba0bd3cb     : 00000002`00000048 00000000`00000004 ffffeb03`7450f500 ffff9100`767aa100 : nt!MmAccessFault+0x646
ffffeb03`7450f0a0 fffff806`6e6942eb     : fffff806`6e401cf2 ffffb40a`043e5de0 00000000`00000003 1fffff00`cdc2a4c7 : nt!KiPageFault+0x38b
ffffeb03`7450f238 fffff806`6e401cf2     : ffffb40a`043e5de0 00000000`00000003 1fffff00`cdc2a4c7 fffff806`b9e3074c : BEDaisy+0x5442eb
ffffeb03`7450f240 ffffb40a`043e5de0     : 00000000`00000003 1fffff00`cdc2a4c7 fffff806`b9e3074c 00000000`00000000 : BEDaisy+0x2b1cf2
ffffeb03`7450f248 00000000`00000003     : 1fffff00`cdc2a4c7 fffff806`b9e3074c 00000000`00000000 fffff805`2e150000 : 0xffffb40a`043e5de0
ffffeb03`7450f250 1fffff00`cdc2a4c7     : fffff806`b9e3074c 00000000`00000000 fffff805`2e150000 00000000`00000003 : 0x3
ffffeb03`7450f258 fffff806`b9e3074c     : 00000000`00000000 fffff805`2e150000 00000000`00000003 00000000`00000000 : 0x1fffff00`cdc2a4c7
ffffeb03`7450f260 ffffb409`f9c19cc0     : 00000000`00000008 00000000`00040293 00000000`000000ff 00000000`00000008 : nt!MiIsPdeOrAboveAccessible+0xdc
ffffeb03`7450f290 00000000`00000008     : 00000000`00040293 00000000`000000ff 00000000`00000008 00000000`00040293 : 0xffffb409`f9c19cc0
ffffeb03`7450f298 00000000`00040293     : 00000000`000000ff 00000000`00000008 00000000`00040293 00000000`00000001 : 0x8
ffffeb03`7450f2a0 00000000`000000ff     : 00000000`00000008 00000000`00040293 00000000`00000001 ffffeb03`7450f580 : 0x40293
ffffeb03`7450f2a8 00000000`00000008     : 00000000`00040293 00000000`00000001 ffffeb03`7450f580 ffffeb03`7450f580 : 0xff
ffffeb03`7450f2b0 00000000`00040293     : 00000000`00000001 ffffeb03`7450f580 ffffeb03`7450f580 fffff806`b9e3074c : 0x8
ffffeb03`7450f2b8 00000000`00000001     : ffffeb03`7450f580 ffffeb03`7450f580 fffff806`b9e3074c 00000000`00000000 : 0x40293
ffffeb03`7450f2c0 ffffeb03`7450f580     : ffffeb03`7450f580 fffff806`b9e3074c 00000000`00000000 00000000`00040293 : 0x1
ffffeb03`7450f2c8 ffffeb03`7450f580     : fffff806`b9e3074c 00000000`00000000 00000000`00040293 00000000`00000000 : 0xffffeb03`7450f580
ffffeb03`7450f2d0 fffff806`b9e3074c     : 00000000`00000000 00000000`00040293 00000000`00000000 00000000`000000ff : 0xffffeb03`7450f580
ffffeb03`7450f2d8 ffffb409`f9c19cc0     : 00000000`00000000 ffffffff`ffffffff 00000000`00040282 00000000`00000073 : nt!MiIsPdeOrAboveAccessible+0xdc
ffffeb03`7450f308 00000000`00000000     : ffffffff`ffffffff 00000000`00040282 00000000`00000073 1fffff00`cdc2a4c7 : 0xffffb409`f9c19cc0


SYMBOL_NAME:  BEDaisy+5442eb

MODULE_NAME: BEDaisy

IMAGE_NAME:  BEDaisy.sys

STACK_COMMAND: .process /r /p 0xffffdb0dac4dd040; .thread /r /p 0xffffdb0dcedf3040 ; kb

BUCKET_ID_FUNC_OFFSET:  5442eb

FAILURE_BUCKET_ID:  AV_BEDaisy!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {36b04c21-521f-babb-382f-2a12c3ddef17}

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

2 answers

Your answer

Answer 1

Hello. Zak;

I looked up the error codes. A few results came up for the error codes. Now, One of the error is lack of permissions also lack of space and the last one is from overclocking the CPU in the BIOS. Yes the anti cheat can be corrupt or something wrong with it. If there was something wrong with it then the other games would stop working too I would assume.

Administrator Fix \ Permissions Fix: Go to C:\Program Files (x86)\Common Files\BattlEye. Right-click BEService.exe, select Properties, and go to the Compatibility tab, Choose Change settings for all users. Check the box for Run this program as an administrator and hit Apply. Do the same for your GTA5.exe file inside your main game folder. Check the Permissions make sure the users are added properly so it can write to the file.

Anu-virus fix:

Templary disable anti-virus programs that maybe interfering with the EXE files.

Check to make sure the hard disk has enough room on it to make the SYS file bigger and smaller as needed.

Power fix: In control panel : change the power plan to balanced

Worst case, You can try to install the program to the C:\ hard drive to see if that is a cause. Some hard drives are different speeds and if the one is superfast it will "stall" waiting for the other hard drive to send it the information, resulting in a error code of no response.

--

User's image

--

Zak 100 Reputation points

2026-08-13T11:28:17.09+00:00

"Run this program as an admin" error (same with BE):

Recently BSOD-ed again, so sharing minidumps to get a better understanding on the root cause: https://drive.google.com/drive/folders/1ook3FS9fP6WBiMQPZBwcVJDdSFfR2tfG?usp=sharing

And changing power plan or messing with Windows Defender didn't fix the issue :(

The SSD is brand new, thus shouldn't be causing any problems; do let me know if something can be shared to get a better understanding on the problem.

On a side note, Event Viewer keeps showing the same error multiple times on startup:

"The PRI-Driver service failed to start due to the following error: The system cannot find the file specified."

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

1 deleted comment

Comments have been turned off. Learn more