I can send a dump file if that would help.
a RAM failure that changed a bit in one of your pointers, the hardware failure could trigger an access violation also. Is there a symbols (.PDB) file for zibzmq-圆4-3.0.0.0 that might help to reveal a bad / closed ZMQ Context or Socket? I am (pretty sure) the ZMQ Contexts sockets are OK. Usually the cause is a logic bug, but if you had e.g. Perhaps you've already seen and fixed this in later versions? Msvcr100.dll!_threadstartex(void * ptd) Line 292Īt f:\dd\vctools\crt_bld\self_64_amd64\crt\src\threadex.c(292) I attach to it using VS2017 debugger and the app runs for a while then: BOOM! Exception thrown at 0x00000000743FBF7C (msvcr100.dll) in MyUI.exe: 0xC0000005:Īccess violation reading location 0x000000001EE6FFFF. Net app (4.7) crashes really hard under certain conditions.
Apparently, the solution requires players to amend setting both in-game, and within the graphics card settings themselves. It seems to be most prevalent for players who have enabled VSync, but can still effect players, even if they have disabled VSync. I finally solved it And this time I waited for 3 weeks, and successfully played for over 20 hours, before posting this edit. The error appears to be very closely linked to VSync. What is VSync? How To Fix Error Code 0xC0000005 And Stop Deathloop Crashing
0 kommentar(er)
