Question Valorant crashing - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s

ringmany

Distinguished
Nov 6, 2014
209
8
18,695
Hi everyone,

Around 1 week ago, the game Valorant started crashing for me every time I tried to launch it. I haven't experienced this error with any other game except for Valorant.
When I try to launch the game, I get the error:

"A critical error has occurred and the process must be terminated.
Would you like to create a crash dumpt o adi the developers in troubleshooting this issue? This may take up to 5 minutes."

Inside of my dmp file I'm searching and I can see various errors such as:

Code:
EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffd3f7819e9 (VCRUNTIME140!memset+0x0000000000000049)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000008000000000
Attempt to write to address 0000008000000000

PROCESS_NAME:  VALORANT-Win64-Shipping.exe

WRITE_ADDRESS:  0000008000000000 

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

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000008000000000

STACK_TEXT:  
00000038`0a77e2d8 00007ff6`097b7dca     : 00000000`68000000 00007ff6`1015b6e0 00000000`68000000 00000000`00000004 : VCRUNTIME140!memset+0x49
00000038`0a77e2e0 00007ff6`097c111a     : 00007ff6`1015b6e0 00000000`68000000 00000158`000000f0 00007ff6`0cb2e966 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x8490ba
00000038`0a77e310 00007ff6`097a449b     : 00000000`68000000 00000000`00000000 00000038`0a77e460 00000000`00000004 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x85240a
00000038`0a77e360 00007ff6`097aaa69     : 00000202`784b0006 00000000`00000004 00000000`00000004 00000038`0a77e6c8 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83578b
00000038`0a77e560 00007ff6`0979d449     : 00000038`0a77e6b0 00000038`0a77e6c8 00007ff6`100bfd30 00007ff6`100bfd30 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83bd59
00000038`0a77e590 00007ff6`097aa997     : 00007ff6`1010c880 00000000`00000000 00000038`0a77e649 00000038`0a77e6b0 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x82e739
00000038`0a77e5d0 00007ff6`0979ebfd     : 00007f00`1010c880 00000000`00000000 00007ff6`10139f80 00000000`00000000 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83bc87
00000038`0a77e6b0 00007ff6`097a8d73     : 00007ff6`1010c880 00000000`00000000 00000000`00000000 00000000`00000000 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x82feed
00000038`0a77f510 00007ff6`097a904e     : 00000000`00000000 00000000`00000000 00000000`00000001 00000038`0a77fa10 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83a063
00000038`0a77f560 00007ff6`0979e817     : 00000038`0a77fa10 00000000`00000001 00007ff6`0cddb2d0 00007ff6`0cb2e778 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83a33e
00000038`0a77f9b0 00007ff6`0599c92b     : 00007ff6`0cdde1c8 00007ff6`0cb2e7a9 00000000`00000000 00000000`00000000 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x82fb07
00000038`0a77f9f0 00007ffd`445be473     : 00007ff6`0cf7c8f0 00000000`00000001 00000000`00000000 00000000`00000000 : VALORANT_Win64_Shipping!png_get_uint_16+0x18e2b
00000038`0a77fa30 00007ff6`0cb2f4d8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ucrtbase!initterm+0x43
00000038`0a77fa60 00007ffd`45da7374     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : VALORANT_Win64_Shipping!agsCheckDriverVersion+0x33a78
00000038`0a77faa0 00007ffd`4699cc91     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000038`0a77fad0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


STACK_COMMAND:  ~0s; .ecxr ; kb

FAULTING_SOURCE_LINE:  d:\a01\_work\12\s\src\vctools\crt\vcruntime\src\string\amd64\memset.asm

FAULTING_SOURCE_FILE:  d:\a01\_work\12\s\src\vctools\crt\vcruntime\src\string\amd64\memset.asm

FAULTING_SOURCE_LINE_NUMBER:  122

FAULTING_SOURCE_CODE:  
No source found for 'd:\a01\_work\12\s\src\vctools\crt\vcruntime\src\string\amd64\memset.asm'


SYMBOL_NAME:  VCRUNTIME140!memset+49

MODULE_NAME: VCRUNTIME140

IMAGE_NAME:  VCRUNTIME140.dll

FAILURE_BUCKET_ID:  INVALID_POINTER_WRITE_ONE_BIT_c0000005_VCRUNTIME140.dll!memset

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  14.29.30139.0

FAILURE_ID_HASH:  {92715b37-d150-b398-68cb-597045db1bd6}

Followup:     MachineOwner

I've followed all of their instructions the support team provided (which is basically just deleted and reinstall).
I've deleted the entire game, all folders, files, uninstalled all traces of it. Then reinstalled probably 5 times now. On different drives to be sure.

I've removed all 4 sticks of RAM one by one, to check if it's a hardware issue with them. Same error each time, even with only 1 stick of RAM, changed each restart.

My graphics card drivers are on the latest version, as is my windows. I haven't made any changes to my PC as far as I'm aware.

I'm not sure what else to check. The support team hasn't given me anything to work with, and I'm not certain if it's an issue with the game itself or my PC. I'm not getting errors on other games. If anyone has any suggestions it would be appreciated.

I've attached a copy of the dmp here:
https://drive.google.com/file/d/1mjDgBHiKxU9BDnSTvMv3tW_VG1HfeBBg/view?usp=sharing