How can I fix this. When I try to download a game the launcher always crashes & this is what pops up

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000002300000048

ucrtbase
ucrtbase
ucrtbase
EpicGamesLauncher
EpicGamesLauncher
EpicGamesLauncher
EpicGamesLauncher
EpicGamesLauncher
EpicGamesLauncher
kernel32
ntdll

Im having the same problems

Im downloading games as well then it just crashes all of them do that for me

I’ve tried re-installing epic games still the same error

Yep i tried everything even uninstall everything and new windows 10 nothing worked

Same

I hope this gets fixed it happened to me two days a go

I mostly play rocket league

Hey, I figured it out on my son’s computer!

We were having this exact issue over and over on his PC, but nothing was solving it, not even reinstalling the OS.

Finally, I realized that the memory addresses in these crash reports were all fairly high address values (like the 0x0000002300000048 in this thread).

In our case at least, turned out it was happening because of a bad RAM stick! Apparently some recent change to the EpicGamesLauncher is putting something in higher memory addresses, and it’s hitting an area of RAM that had gone bad, but previously unnoticed.

Ran MemTest86, and boom, there it was… memory errors.

Pulled the bad stick, and boom, everything works again.

Hope this helps!

Greetings @GetRekt0290

Welcome to the Unreal Engine Community Forum! Did the launcher work prior and this recently start happening? If so, do you recall any updates, changes, etc around the time it happened? (Including your own hardware, Windows updates, etc)

The launcher is fine i tried running it in background and it wont crash only when I download any game it automatically crashes. And there is no changes/updates on my computer recently

That’s exactly what was happening on my son’s machine. Launcher would always come up just fine, but every single download would crash with this same error.

Use MemTest86 to check your RAM. It might be some bad memory, just like ours. (Pulling the bad memory stick fixed it!)

The same problem I used removed the old ram and placed with a ram that is on my other pc the same error