Game keeps crashing : log inside

So im trying to figure out what is causing this error. it only ever seems to happen when playing new world and happens most frequently when in OPR .

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19041 (1566) MP (12 procs) Free x64
Product: WinNt
Edition build lab: Windows NT 10.0.19041.1566
Machine Name:
Debug session time: Sun Mar 20 11:16:25.000 2022 (UTC - 7:00)
System Uptime: 0 days 1:29:51.126
Process Uptime: 0 days 0:31:54.000

Loading unloaded module list

Cannot read PEB32 from WOW64 TEB32 fefefefe - Win32 error 0n30
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(3160.1234): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify checksum for ntdll.dll
00007ffb`e09cd3f4 fe ???

ExceptionAddress: 00007ffbc6f414d3 (VCRUNTIME140!memcpy+0x00000000000001e3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000020
Attempt to write to address 0000000000000020

PROCESS_NAME: NewWorld.exe

WRITE_ADDRESS: 0000000000000020

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.


EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000020

IP_ON_HEAP: fefefefefefefefe


@Partiesplayin Please can you contact our support team here: New World - Support | Amazon Games. They will be able to investigate this further for you today!

I may have found the answer . Initial testing was promising, but further testing on my end may be required . After looking over the error i noticed a trend and it was memory . I looked at my page file size in windows and it was only set to 8096 gb and i was running the game at 4k resolution… Turing this up to 25gb min to 41gb max resulted in a smooth game play experience with no crashes . I will do some further testing and see if the problem is still present .

So I have payed a couple short 1hr or so sessions lately without any crashes, so I do think it could have been because for some reason my virtual memory was set too low.

Welp, i guess the issue is not resolved… game locked up then crashed twice in outpost rush.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.