Page MenuHomeFeedback Tracker

0xC0000005 Status_Access_Violation
New, NormalPublic

Description

Been getting these about every 15 minutes since reinstalling a few days ago.

I have Followed all of these from the Bohemia Wiki:

Try changing the Memory Allocator you are using (default: "tbb4malloc_bi" - try "system" on Windows 7 and later)
Try joining another server, then rejoin the previous one.
Update the graphics card drivers to a newer version.
Rollback the graphics card drivers to an older version.
Check the temperature of your GPUs and CPUs.
Verify the integrity of the game cache using Steam.
Re-install DirectX.
Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again using this version (do not use the Repair function).
Run a Windows System File Check tool to repair corrupted system files.

The SFC scannow found a few files but that didn't fix it. I did a clean install on my graphics drivers and that didn't change anything. I have tried using 0 mods and that didn't change anything. I'm at a loss. In the last six months I have done a DRAM error check from a flash drive overnight and that didn't find anything either.

Details

Severity
Crash
Resolution
Open
Reproducibility
Random
Operating System
Windows 11 x64
Category
Game Crash

Event Timeline

parrote3 created this task.Feb 3 2025, 6:45 AM
parrote3 updated the task description. (Show Details)Feb 10 2025, 2:55 PM
dedmen added a subscriber: dedmen.Feb 17 2025, 6:02 PM

Well I don't know either...
You have submitted 7 crashes.
Each of these is something different, and they all look random and seem to make no sense, and I have never seen any of them before.

Your start parameters are quite weird

-exThreads=7 -enableHT -malloc=tbb4malloc_bi_x64 -hugePages -maxmem=0 -maxvram=8192 -noLogs -noPause

-exThreads=7 does nothing
-enableHT is considered to generally be worse for performance
-malloc does nothing
-maxmem, you are telling the game you have 0 bytes of memory???
-maxvram does nothing
-noLogs turns of logging, which is somewhat important when trying to diagnose problems.

I would assume you are having some hardware issue.