Since Nov 8 the client crashes within 0.5 to 10 seconds of my character being placed in the world anywhere near Vavilovo on server 6133. Crash is either 0xC00000FD STACK_OVERFLOW at an address ending in AF998 (two confirmed dumps) or a hard freeze with no crash footer, which the launcher records as 0xC0000005 STATUS_ACCESS_VIOLATION. Crash fires right after Create entity type 'SurvivorM_Peter' while nearby world objects begin streaming. Script log is clean (no VM exception).

Reproduction:

1. Log into 6133 with any character located near Vavilovo water well. Client crashes during or immediately after the 15 second login countdown.

2. Log in with a character farther out, walk toward Vavilovo. Client crashes on approach.

3. Log in with a character farther out and walk away from Vavilovo. No crash.

Evidence this is server-side, not client-side:

• Three different characters affected (two Steam accounts).

• Reproduced on two separate PCs.

• Same accounts play normally on other servers, including 1PP officials and other 3PP Asia Pacific servers.

• Same characters play normally on 6133 once outside the Vavilovo area.

• Persists across a scheduled server restart on Nov 8.

• Thousands of hours played, no prior history of this crash. Caches cleared, PC restarted, no change.

Suspected cause:
A corrupted persisted object or item in Vavilovo on 6133 that causes recursive entity processing on the client when it streams in.

Attached:
Launcher troubleshooting bundle containing crash dumps from Nov 8 16:15, Nov 8 17:44, Nov 9 21:33, RPT files from Nov 8 and Nov 9, DxDiag, and Windows event logs.

Request:
Please inspect the persistence for Vavilovo on 6133 and remove the offending object, or advise if this is a 1.30 map issue.