I ran into this same issue while prepping my own Experimental 1.30 community server. My game client kept crashing when I went near Swarog (server didn't crash).

I thought it was my custom mods causing it and I was doing all kinds of stuff to isolate the problem, but after extensive all-day trial and error testing, it seems to be a potential vanilla 1.30 issue as in my research I stumbled across this OP thread which matches my symptoms but his experience does not include any mods.

I had ChatGPT Codex create an automated trial and error environment for me to rapidly test iterations of my server to reproduce this issue under as-close-to-vanilla-conditions-as-possible while still retaining admin tools, and, for what it's worth, here's what it said:

I’ve now reproduced this on DayZ Experimental 1.30.164014.27, Livonia, using a minimal server setup and an automated, repeatable freecam route.

My original crashes occurred near a custom trader area, so I initially suspected Expansion, custom objects, or a broken modded item. However, the crash also occurs without any custom content mods loaded.

Test setup

• Vanilla Livonia mission and economy data, with CF-Test and Community-Online-Tools-Test for freecam.

• A small client-side test helper drives COT’s existing camera along the same route each run.

• The route passes through X 5153 / Z 2236 and Polana, X 3280 / Z 2132, flying at approximately 250 m/s and climbing up to 400–500 m above terrain.

• Each surviving flight runs for 60 seconds.

• Other graphics settings remain fixed. Terrain view distance is 10,000 m and sceneComplexity is 750,000.

VANILLA CONTENT

- Low (1,400 m): Completed the full 60-second test.

- Very High (2,800 m): Crashed after approximately 11 seconds

while climbing above Polana.

- Extreme (3,200 m): Crashed after approximately 3 seconds.

WINTER CHERNARUS V2 + WINTER LIVONIA

- Low (1,400 m): Completed the full 60-second test.

- Extreme (3,200 m): Crashed after approximately 3 seconds.

The client exits, while the dedicated server continues running. The reproduced crashes generate the same Windows Application Error signature as my original crashes:

Exception code:       0xc0000005
Faulting module:      unknown
Reported fault offset/address: 0x00007ff6953e1f08

That address is included for correlation between runs on my machine; it is not a resolved function or stack trace. No usable native dump was produced during these tests, and the game logs end abruptly.

These results suggest a problem in the client’s rendering/visibility handling at longer object distances, potentially involving a vanilla asset or a particular scene viewed from altitude.

To be clear, this is not yet a completely unmodded reproduction, because CF, COT, and the camera helper remain present in all tests. The successful Low runs are also only one-minute tests. I cannot identify the exact model or engine fault from the available logs.

The reproduced client crashes did not leave an .mdmp file.