Hi,
Just to point out that if you're using
EasyAntiCheat this is known to cause
game issues in the past especially on
Insider builds.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Other games run fine. But whenever I try and load into a map, my whole setup crashes. During one troubleshooting crash, the text "Your computer ran into a problem and needs to restart" flashed on screen a couple of seconds. I'm not sure if this matters, but I did recently upgrade my graphics card.
And for clarity, I can boot the game and go thru all of the menus without issue.
Here is my system information.
Product Name: PRO Z690-A WIFI DDR4
OS: Microsoft Windows 11 Pro Insider Preview 64-bit Ver.2009 (OS build 29553.1000)
BIOS Version: 1.K0
BIOS Release Date: 10/21/2024
CPU: 12th Gen Intel(R) Core(TM) i7-12700KF
Memory: 128 GB @
- 32 GB DDR4-2132, Corsair CMK64GX4M2E3200C16
- 32 GB DDR4-2132, Corsair CMK64GX4M2E3200C16
- 32 GB DDR4-2132, Corsair CMK64GX4M2E3200C16
- 32 GB DDR4-2132, Corsair CMK64GX4M2E3200C16
Graphics: MSI RTX 5070 12G Series, 12227 MB
Drive: SSD, WD_BLACK SN750 SE 1TB, 931.51 GB
Drive: HDD, ST6000VX001-2BD186, 5589.03 GB
Network: Intel(R) Wi-Fi 6E AX211 160MHz
Network: Intel(R) Ethernet Controller (3) I225-V #2
Power Plan: GUID: f4c6c1ad-6b5d-42ca-bd06-ac37044f129e (Ultimate Performance)
Please find attached my system event log.
I have tried lowering my graphics settings in hopes I could get the game to a least load me in with no avail
I have verified my game file integrity twice without issue. I have also ran the windows file scan and no corrupted files were found.
I have uninstalled and reinstalled both Fortnite and the Epic Games Launcher.
I have updated my graphics card to the latest hotfix as new as today (3/25).
Please advise. Thank you.
Izach
Hi,
Just to point out that if you're using
EasyAntiCheat this is known to cause
game issues in the past especially on
Insider builds.
Well think i only the one heating the wall, but clearly, kernel library changes.
Thats releated with EasyAntiCheat and DMA kernel secure system.
My end of the dumpchk 032826-17953-01.dmp
*
Bugcheck Analysis *
*
REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: ffffa43788097740, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: ffffffffffffffff, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This BugCheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object's reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.
Debugging Details:
*** WARNING: Unable to verify timestamp for EasyAntiCheat_EOS.sys
BUGCHECK_CODE: 18
BUGCHECK_P1: 0
BUGCHECK_P2: ffffa43788097740
BUGCHECK_P3: 2
BUGCHECK_P4: ffffffffffffffff
PROCESS_NAME: System
SYMBOL_NAME: EasyAntiCheat_EOS+2c67fb
MODULE_NAME: EasyAntiCheat_EOS
IMAGE_NAME: EasyAntiCheat_EOS.sys
FAILURE_BUCKET_ID: 0x18_OVER_DEREFERENCE_EasyAntiCheat_EOS!unknown_function
FAILURE_ID_HASH: {0eb77321-e151-4133-7e68-a13d8e5edc75}
Followup: MachineOwner
You can find the dump files in C:\Windows\Minidump
copy Minidump folder to C:\
take Ownership and replace all child object permission entries last copied folder C:\Minidump
Install debugging tools from windsdk https://go.microsoft.com/fwlink/?linkid=2349110
open powershell in the C:\Minidump folder
<code>
$sep = ";"
$env:DEBUGGERS_PATH = "C:\Program Files (x86)\Windows Kits\10\Debuggers\x64"
$env:Path = "$($env:DEBUGGERS_PATH)$($sep)$($env:PATH)"
dumpchk file_name .dmp
</code>
change the file_name to one of your dmp files
let dumpchk terminate reading the dump file.
i had the same issue :
"REFERENCE_BY_POINTER"** (code d'arrêt Windows 0x00000018)**
Restored before last update and no more crash.
z790 and 13900k.
The behavior described matches a Windows stop code (blue screen) that only appears when loading into Fortnite, while other games work fine. This points to a game‑specific driver or compatibility issue rather than general hardware failure.
Since the system is on Windows 11 Pro Insider Preview (build 29553.1000) and Fortnite uses Easy Anti‑Cheat, there is a known incompatibility between Windows 11, version 24H2 and some Easy Anti‑Cheat drivers that can cause MEMORY_MANAGEMENT blue screens on devices with Intel Alder Lake CPUs, which matches the 12th Gen Intel Core i7‑12700KF.
Follow these steps in order:
MEMORY_MANAGEMENT).Win + X → Event Viewer.MEMORY_MANAGEMENT on Intel Alder Lake+ with vPro.MEMORY_MANAGEMENT and crashes only occur when Easy Anti‑Cheat loads (entering a match), this is likely the same class of issue.If the system is stable in all other workloads and only Fortnite triggers the blue screen, the most effective long‑term fix is typically:
References: