Error EXCEPTION_ACCESS_VIOLATION
Bodycam "EXCEPTION_ACCESS_VIOLATION" crash: what players report
What you see
The game freezes and closes, and the Bodycam Crash Reporter opens with "Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x…" above a list of Bodycam_Win64_Shipping lines. Some players get it at launch, others after a while in a match.
Cause not confirmed yetReported
Several players have hit this crash since the V0.8 update in September, with different addresses after "reading address". Nobody has found a fix that works for everyone and the studio has not named it. One player fixed it by updating their mods.
What players try
One at a time. Tell us whether each one worked and the next opens.
On 20 September a player on the official Discord said the game crashed at launch with this error. The next day they posted that updating the mods they had installed from Nexus Mods fixed the 0xffffffffffffffff version of it. Only one player has reported this, so it is not a confirmed fix, and it only applies if you use mods.
ReportedUse "Send and Close" with a line about what you were doing. The V0.8 notes say the studio added a crash reporter to "catch logs from all crashes", and the 18 September patch added more crash data from loadouts and settings "to help diagnose issues". It will not fix the crash for you, but it is the way this one gets fixed.
Confirmed- Note
The address after "reading address" varies
Players have posted 0xffffffffffffffff, 0x0000000000000008, 0x0000000000000018 and 0x0000000000000049. We have no evidence that these point to different causes, so this page covers them all.
Reported
Sorted. Glad that worked.
Nothing worked. Here's what to do next.
You've ruled out every step on this page, which is useful. Post this where the developers and other players will see it, so nobody makes you repeat yourself.
Might be a different problem
What we know and don’t
Still happening on V0.8. Between 18 and 26 September at least six players posted this crash in #general on the official Reissad Studio Discord. One wrote, in French, that it had stopped them playing since the last update. On 21 September a player on r/BodycamGame posted the same crash reporter window after “some time” in a match. The only reply asked whether they were overclocking, and there has been no answer since.
The address after “reading address” differs between players. The crash reporter lists only Bodycam’s own game executable, so the text in it doesn’t show whether the cause is a mod, a driver or the game.
The studio has not named this crash in its patch notes. The notes do mention crash fixes without naming them. V0.8 #2 fixed “a crash that could occur during online initialization”, and V0.8 #4 fixed “a memory issue affecting inventory / equipment handling”. We can’t tell whether either one was this crash. V0.8 #6, on 25 September, says it is “likely the last v0.8 patch” for now, so a fix may take a while.
If this looks like your crash, the reporter’s “Send and Close” button is the most useful thing to press. If you use mods, update or remove them first. That is the only fix anyone has reported.
Also shown as
EXCEPTION_ACCESS_VIOLATIONexception access violationexception_access_violation reading addressunhandled exception: exception_access_violationaccess violation reading addressreading address 0xffffffffffffffff
Last checked September 27, 2026. Source: r/BodycamGame, "Bodycam Crash".
Other errors
Still stuck? Check whether the servers are having trouble, or post what you see on the status page.
Bodycam V0.8.12.19346 (Steam build 25505592). Updated 2026-09-27. Numbers can change between patches. Maintained byLynxx.