Apex Crash erorr 0xc0000005
My apex legends kept crashing without errors, i got simular eception code on two different application; Isass.exe and r5apex.exe. I tried every possible fix i could find online but nothing helped. F...
Forum Discussion
EA_Mari
Community Manager
Community ManagerHey folks,
Could we please get a DxDiag from each one experiencing the Crash error? I've attached the link with instructions. Thank you all for reporting this.
Hey,
I have been having the same issue mentioned by OP
my thread: https://answers.ea.com/t5/Technical-Issues/Apex-legends-Access-Violation-c0000005/m-p/14276617
contains all my troubleshooting steps.
dxdiag shows nothing wrong with drivers..
Thanks,
any help is appreciated
- @MrRandomAlex I've merged your thread over with this one so it can all be in one place.
Thanks for the update!Resolved My Issue: Step-by-Step Guide
Hey everyone,
After troubleshooting an issue for some time, I was able to resolve it on my own. I understand that this type of problem can be difficult to fix, but with my background, I figured it out. Here's
how I did it:
Resolution Steps:
Disable .NET Framework:
I started by disabling .NET Framework from the optional Windows features, rebooted, then re-enabled it.Delete .dll Files:
I navigated to the System32 folder and carefully deleted every single .dll file in that folder itself (but not any files in subfolders).Run System File Check:
I ran the command sfc /scannow. Although it reported no issues, it was part of the process to ensure the system was intact.Reinstall DirectX:
I downloaded the DirectX web installer online and reinstalled the necessary files to restore missing or corrupted system files.Fix Missing Files:
After reinstalling DirectX, I received some popups indicating missing files. I downloaded each of the missing .dll files, ensuring I chose the 64-bit versions, and moved them into the System32 folder.Install Visual C++ Redistributables:
To ensure no other issues remained, I downloaded and ran the Visual C++ Redistributable Runtime Package (All-in-One).
Additional tool if issues persist (windows process monitor) - here
Good Luck!
By following these steps, I was able to solve the issue. I hope this guide helps you resolve similar problems. Good luck!
Going to try to follow your steps shortly, however i have genuine doubts that you deleted EVERY .dll in your system32 folder, could you clarify what .dll’s you removed?
Having just checked the system32 folder, i did notice eac dll’s that i didnt find before when looking for traces of files related to apex, so i’ll start with those. But im just looking to see if you know what you deleted (like if its still in your recycling bin or if you remember what it was you deleted)
i havent disabled/reenabled .net frameworks in the the optional windows features, so your troubleshooting steps do include steps i havent taken yet, as well as your point to delete .dlls in the system32 folder.
Just wanting something more clear before i actually delete a number of dll’s from system 32, since i think i would know what not to remove, but the statement of deleting them all could lead to other users bricking their windows if they read your comment.
Also i have had procmon installed for some time now, but wasnt able to determine the problem with the crashing using it, as i dont know if it has always been the case, but it seems eac is crashing the game when i open procmon, seemingly due to it being flagged by EAC. So looking to see what you had done different if you are able to run apex with procmon open.Thank you for your suggestions, i will let you know shortly if it solves the issue for me!
Update:
Having followed your steps to try to remediate the issue, I am still getting an lsass error when launching apex. I only deleted eac dll's that seemed to not get properly removed in the past, as i saw a similar dll show up when launching apex, but it was removed after closing apex. So just looking to see what different dll's you might have deleted, as thats the only thing I can guess that you did differently than me so far.
Faulting application name: lsass.exe, version: 10.0.19041.4239, time stamp: 0x4aaafe3f
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x444
Faulting application start time: 0x01db3e266343e9fe
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: unknown
Report Id: 1a190bac-2451-4e7c-9c21-6ff984efb129
Faulting package full name:
Faulting package-relative application ID:
Community Highlights
- EA_Blueberry7 years ago
