Question Games crashing with memory errors (EXCEPTION_ACCESS_VIOLATION reading address) ?

[ringmany]

Hi everyone,

Around 1 month ago, various games of mine such as Valorant and Dead by Daylight started crashing for me every time I tried to launch it or mid game.

When I try to launch Valorant for example, I get the error:

"A critical error has occurred and the process must be terminated.
Would you like to create a crash dump to aid 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 :

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. Plus on 3 different hard drives and it's the same error regardless of the hard drive.

I'm also getting random errors on Dead by Daylight, although they are more rare and usually crashes the game, whereas Valorant I can't even start.

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 109500120 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 109499856 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 109436556 bytes

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 each time, changed each restart.

I've run sfc/scannow and various other commands to check for corruption, all fine.

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've uninstalled and re-installed my Nvidia drivers and re-installed. I've tried like 20 different forums.

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 a hardware or software issue or what else to check.

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

 

[Darkbreeze]

FULL hardware specs? Including exact model numbers where possible and for certain the exact model number and approximate age of the power supply?

 

[ubuysa]

This is a problem with the game, or your system is not capable of running it. The dump clearly shows a Valorant module (vcruntime140.dll) failing...

CONTEXT:  (.ecxr)
rax=0000003809a4d000 rbx=00007ff61015b6e0 rcx=0000008000000000
rdx=0000000000000000 rsi=0000000000000004 rdi=0000000000000000
rip=00007ffd3f7819e9 rsp=000000380a77e2d8 rbp=000000380a77e460
 r8=0000000000200000  r9=0000000000000000 r10=0000000000008000
r11=0000008000000000 r12=0000000000000000 r13=5555555555555555
r14=2545f4914f6cdd1d r15=000000380a77e610
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
VCRUNTIME140!memset+0x49:
00007ffd`3f7819e9 0f1101          movups  xmmword ptr [rcx],xmm0 ds:00000080`00000000=????????????????????????????????
Resetting default scope

In fact the call stack leading up to the bugcheck (which you read from the bottom up) is filled with Valorant function calls...

VCRUNTIME140!memset+0x49
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x8490ba
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x85240a
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83578b
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83bd59
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x82e739
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83bc87
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x82feed
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83a063
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83a33e
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x82fb07
VALORANT_Win64_Shipping!png_get_uint_16+0x18e2b
ucrtbase!initterm+0x43
VALORANT_Win64_Shipping!agsCheckDriverVersion+0x33a78
kernel32!BaseThreadInitThunk+0x14
ntdll!RtlUserThreadStart+0x21

The reference to the urctbase.dll module there is interesting. That's part of the Microsoft Visual C++ redistributable code, so it's possible these errors are happening because you don't have the necessary redistributable code installed. That may also be the reason why the other game you mentioned fails.

Check what Microsoft Visual C++ redistributables you need for these games. They should have been downloaded and installed with the games, but perhaps they weren't for some reason.

 

[ringmany]

FULL hardware specs? Including exact model numbers where possible and for certain the exact model number and approximate age of the power supply?

Full hardware list here:
https://uk.pcpartpicker.com/user/RingMany/saved/WXCWXL

My PC is probably around 7 years old at this stage.

 

[ringmany]

This is a problem with the game, or your system is not capable of running it. The dump clearly shows a Valorant module (vcruntime140.dll) failing...

CONTEXT:  (.ecxr)
rax=0000003809a4d000 rbx=00007ff61015b6e0 rcx=0000008000000000
rdx=0000000000000000 rsi=0000000000000004 rdi=0000000000000000
rip=00007ffd3f7819e9 rsp=000000380a77e2d8 rbp=000000380a77e460
 r8=0000000000200000  r9=0000000000000000 r10=0000000000008000
r11=0000008000000000 r12=0000000000000000 r13=5555555555555555
r14=2545f4914f6cdd1d r15=000000380a77e610
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
VCRUNTIME140!memset+0x49:
00007ffd`3f7819e9 0f1101          movups  xmmword ptr [rcx],xmm0 ds:00000080`00000000=????????????????????????????????
Resetting default scope

In fact the call stack leading up to the bugcheck (which you read from the bottom up) is filled with Valorant function calls...

VCRUNTIME140!memset+0x49
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x8490ba
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x85240a
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83578b
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83bd59
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x82e739
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83bc87
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x82feed
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83a063
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x83a33e
VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x82fb07
VALORANT_Win64_Shipping!png_get_uint_16+0x18e2b
ucrtbase!initterm+0x43
VALORANT_Win64_Shipping!agsCheckDriverVersion+0x33a78
kernel32!BaseThreadInitThunk+0x14
ntdll!RtlUserThreadStart+0x21

The reference to the urctbase.dll module there is interesting. That's part of the Microsoft Visual C++ redistributable code, so it's possible these errors are happening because you don't have the necessary redistributable code installed. That may also be the reason why the other game you mentioned fails.

Check what Microsoft Visual C++ redistributables you need for these games. They should have been downloaded and installed with the games, but perhaps they weren't for some reason.

Cheers for the suggestion.
I removed all versions of Microsoft visual C++ from my PC. Then I installed the latest ones they use, repaired any files and rebooted and sadly still getting the same error.

 

[Darkbreeze]

So, while I normally post this because in effect it often covers things that turn out to be the issue, I'm doing so here because it's REALLY likely one of these things is and it IS in the order of importance that you ought to go after it. One step at a time. Feedback from you on each step is kind of important too.

Gonna tell you though, too, that your Supernova G2 is getting VERY long in the tooth now. This might be a really good thing to go after first actually because at almost exactly 10 years old I just had to replace the G2 750w in my nephew's system which I had donated to him a few years back. Ten years, running a mid to upper tiered graphics card, is exceptional longevity really. Even if it isn't the problem it is something you should seriously consider replacing as it has to be at least that old now. Mine was ten. Yours is probably older.

If there are any steps listed here that you have not already done, it would be advisable to do so if for no other reason than to be able to say you've already done it and eliminate that possibility.

First,​

Make sure your motherboard has the MOST recent BIOS version installed. If it does not, then update. This solves a high number of issues even in cases where the release that is newer than yours makes no mention of improving graphics card or other hardware compatibility. They do not list every change they have made when they post a new BIOS release. In cases where you DO already have the latest BIOS version, simply resetting the BIOS as follows has a fairly high percentage chance of effecting a positive change in some cases so it is ALWAYS worth TRYING, at the very least.


BIOS Hard Reset procedure

Power off the unit, switch the PSU off and unplug the PSU cord from either the wall or the power supply.

Remove the motherboard CMOS battery for about three to five minutes. In some cases it may be necessary to remove the graphics card to access the CMOS battery.

During that five minutes while the CMOS battery is out of the motherboard, press the power button on the case, continuously, for 15-30 seconds, in order to deplete any residual charge that might be present in the CMOS circuit. After the five minutes is up, reinstall the CMOS battery making sure to insert it with the correct side up just as it came out.

If you had to remove the graphics card you can now reinstall it, but remember to reconnect your power cables if there were any attached to it as well as your display cable.

Now, plug the power supply cable back in, switch the PSU back on and power up the system. It should display the POST screen and the options to enter CMOS/BIOS setup. Enter the bios setup program and reconfigure the boot settings for either the Windows boot manager or for legacy systems, the drive your OS is installed on if necessary.

Save settings and exit. If the system will POST and boot then you can move forward from there including going back into the bios and configuring any other custom settings you may need to configure such as Memory XMP, A-XMP or D.O.C.P profile settings, custom fan profile settings or other specific settings you may have previously had configured that were wiped out by resetting the CMOS.

In some cases it may be necessary when you go into the BIOS after a reset, to load the Optimal default or Default values and then save settings, to actually get the hardware tables to reset in the boot manager.

It is probably also worth mentioning that for anything that might require an attempt to DO a hard reset in the first place, IF the problem is related to a lack of video signal, it is a GOOD IDEA to try a different type of display as many systems will not work properly for some reason with displayport configurations. It is worth trying HDMI if you are having no display or lack of visual ability to enter the BIOS, or no signal messages.

Trying a different monitor as well, if possible, is also a good idea if there is a lack of display. It happens.

Second,​

Go to the product page for your motherboard on the manufacturer website. Download and install the latest driver versions for the chipset, storage controllers, audio and network adapters. Do not skip installing a newer driver just because you think it is not relevant to the problem you are having. The drivers for one device can often affect ALL other devices and a questionable driver release can cause instability in the OS itself. They don't release new drivers just for fun. If there is a new driver release for a component, there is a good reason for it. The same goes for BIOS updates. When it comes to the chipset drivers, if your motherboard manufacturer lists a chipset driver that is newer than what the chipset developer (Intel or AMD, for our purposes) lists, then use that one. If Intel (Or AMD) shows a chipset driver version that is newer than what is available from the motherboard product page, then use that one. Always use the newest chipset driver that you can get and always use ONLY the chipset drivers available from either the motherboard manufacturer, AMD or Intel.


IF you have other hardware installed or attached to the system that are not a part of the systems covered by the motherboard drivers, then go to the support page for THAT component and check to see if there are newer drivers available for that as well. If there are, install them.

Third,​

Make sure your memory is running at the correct advertised speed in the BIOS. This may require that you set the memory to run at the XMP profile settings. Also, make sure you have the memory installed in the correct slots and that they are running in dual channel which you can check by installing CPU-Z and checking the Memory and SPD tabs. For all modern motherboards that are dual channel memory architectures, from the last ten years at least, if you have two sticks installed they should be in the A2 (Called DDR4_1 on some boards) or B2 (Called DDR4_2 on some boards) which are ALWAYS the SECOND and FOURTH slots over from the CPU socket, counting TOWARDS the edge of the motherboard EXCEPT on boards that only have two memory slots total. In that case, if you have two modules it's not rocket science, but if you have only one, then install it in the A1 or DDR4_1 slot.

Fourth (And often tied for most important along with an up-to-date motherboard BIOS),​

A clean install of the graphics card drivers. Regardless of whether you "already installed the newest drivers" for your graphics card or not, it is OFTEN a good idea to do a CLEAN install of the graphics card drivers. Just installing over the old drivers OR trying to use what Nvidia and AMD consider a clean install is not good enough and does not usually give the same result as using the Display Driver Uninstaller utility. This has a very high success rate and is always worth a shot.


If you have had both Nvidia and AMD cards installed at any point on that operating system then you will want to run the DDU twice. Once for the old card drivers (ie, Nvidia or AMD) and again for the currently installed graphics card drivers (ie, AMD or Nvidia). So if you had an Nvidia card at some point in the past, run it first for Nvidia and then after that is complete, run it again for AMD if you currently have an AMD card installed.

Graphics card driver CLEAN install guide using the Wagnard tools DDU



And last, but not least, if you have never done a CLEAN install of Windows, or have upgraded from an older version to Windows 10, or have been through several spring or fall major Windows updates, it might be a very good idea to consider doing a clean install of Windows if none of these other solutions has helped. IF you are using a Windows installation from a previous system and you didn't do a clean install of Windows after building the new system, then it's 99.99% likely that you NEED to do a CLEAN install before trying any other solutions.


How to do a CLEAN installation of Windows 10, the RIGHT way​

 

[johnbl]

I would start by reinstalling the directx download.
looks like some issue with the 2010 runtime. (maybe)
maybe this:
https://download.microsoft.com/download/8/4/A/8...

also looks like files were being run off of drive H: it might be exposing some bug

most people would reinstall windows as a fix but the reinstall of direct x might work.
(some old files from 2007, and 2010 might have fixes in the directx update)
note: INVALID_POINTER_WRITE_ONE_BIT
I would also check the power supply levels, overheating and make sure you do not have any bios overclock or a installed overclock driver.
(some of the old overclock driver get installed in different directories and overclock the overclock values) These can lead to one bit errors in the cpu. (bad timings in the electronics) blow dust out of cpu gpu and psu fans.

note: you might also want to delete your pagefile.sys and create another copy. turn of the system virtual memory then turn it back on. For the case where you get a corrupted memory image saved to the pagefile.sys.

 

[Darkbreeze]

If you do what I've suggested, basically every possible problem that isn't hardware will be addressed. Literally.