Context: This is the stock PC Steam DayZ Experimental 1.30 client, build 1.30.164014.27, with BattlEye enabled and no mods. Update 1.30 introduced the Jana 50 and Bitrak 682 motorbikes and official Many Motorbikes test servers. The player can join an official server and enter the world, but the client intermittently freezes and closes to desktop. No in-game crash dialog appears. The player did not need to mount a bike, ride, or switch camera view. The same crash also occurred on an ordinary official Experimental server.

Two documented Many Motorbikes runs on 25 September 2026 (local time):

• Run 1 started at 20:14. The game log recorded Motorbike_02_Red loading at 20:28:55, with 'Second driver found when parsing class Crew::Crew'. Windows logged the client crash at 20:29:25. A blue Jana 50 had visibly rendered earlier in that run.

• Run 2 started at 20:38. The log recorded Motorbike_02_Red loading at 20:39:11, then Motorbike_01_Blue being created and loaded at 20:39:13, again with the crew warning. Windows logged the crash at 20:39:21.

Windows Application Error repeatedly reports DayZ_x64.exe exception 0xc0000005 at the same fault address, 0x00007ff620c11f08. The corresponding executable RVA is 0x10d1f08, in a stack-probing routine. Older crashes have the same signature. Some occurred without any concrete bike entity recorded in the client log, so the bike load is a strong timing clue, not a proven root cause. The log records entity loading; it does not establish the bike's physical distance from the player.

Checks already performed: Steam file validation and a complete reinstall; Steam and NVIDIA overlays disabled; Discord overlay disabled and Discord closed; and reduced resolution. Crashes continued with the same fault address. The reduced-resolution Many Motorbikes run lasted about 15 minutes before failing. No current .mdmp or call stack was produced, even with Windows local dump collection configured.

A generic startup warning says STR_DN_MOTORBIKE is missing from the localization table, but it appears even in sessions with no concrete bike load. The rideable bike classes use separate existing name keys. This warning may be unrelated to the crash.

Please investigate the repeated client access violation and its possible relationship to motorbike entity loading. Guidance for obtaining a BattlEye-compatible crash dump or a developer-side symbolic trace would help identify the failing caller. DZEXP-196 reports a different trigger: switching camera view while riding.

1. Launch stock DayZ Experimental 1.30.164014.27 from Steam with BattlEye enabled and no mods.

2. Join an official Experimental Many Motorbikes server and enter the playable world.

3. Continue ordinary play. No bike interaction or camera switch is necessary. The timing is intermittent: one observed run lasted about 15 minutes; another froze within a minute of entering the world.

4. When the client freezes and closes without a DayZ error dialog, compare the new client error log with the Windows Application Error event. In two observed Many Motorbikes runs, the log recorded concrete motorbike entity loads 8–30 seconds before Windows recorded the same 0xc0000005 fault.

The crash has also occurred on a regular official Experimental server. In some of those sessions, the client log did not record a concrete motorbike load. The steps above describe the observed setup and result; motorbike loading is a suspected trigger, not a deterministic reproduction condition.

The unmodded Experimental client should remain open while official servers load motorbike entities. A server-provided bike should not cause a client freeze or access violation, whether or not the player interacts with it.