Game Crash to desktop due to Access Violations

pvnco

New member
i have been experiencing random crash to desktop since july; switching to vulkan from dx11 appeared to work at first but has since resumed crashing: i have attached the .mdmp

here is some information i believe may be pertinent to the issue:

windmp shows access violations and errors in address ffffffffffffffff.

Exception: Access violation (0xc0000005)
Faulting module: scenesystem.dll
Fault address: scenesystem+0x4eb74
Type: INVALID_POINTER_READ (attempt to read ffffffffffffffff)
Thread: Source2 job thread (tier0!CThread::ThreadProc)

scenesystem+0x4eb74
scenesystem+0x6b06e
scenesystem+0x6b6e7
scenesystem+0x46885
scenesystem+0xbd40a
scenesystem+0xbcedc
scenesystem+0x10c5b1
scenesystem+0x122fcc
tier0!ReturnJobManualEventToPool
tier0!CThread::ThreadProc

Attempt to read from address: ffffffffffffffff
rdx = 0000005c1c96f81d


unit_status_overlay::m_vecOrigin CNetworkOriginCellCoordQuantizedVector
cell X/Y is outside of cell bounds (0->32)

Rendering API: Vulkan
GPU: RTX 4080, driver 581.15
OS: Win10 22H2 build 19045.6216
Command line: deadlock.exe -steam -console -vulkan
Memory: 64GB RAM, ~26% load at crash

thank you to all and any who attempt to diagnose.
 

Attachments

Last edited:
0xc0000005 almost always coincides with RAM instability, try disabling XMP/EXPO or reducing RAM frequency until it stops crashing. If it doesn't stop and you've tried everything else, replace the RAM.
 
You would have to test by lowering it or disabling XMP/EXPO. Source 2 exposes RAM instability where other games don't.
profile adjusted and memtest passed; subsequent benchmarks on gpu and stresstests on the cpu yielded no results; really sort of at the limit of my understanding outside of just watching performance gauges and trying to narrow down where the issue is.
 
Back
Top