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
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:
For the Dlls,
I went into file explorer then i browsed down to sys 32
did a search for .dll
selected files in the current folder only using the advanced search
then did a select all - ctrl + a then a delete
this then deleted all dll files currently not in use
deleting all the corrupted ones
then i reinstalled direct x etc
So i did that just now, however i skipped the dll's that were locked under Trusted installer, should i do it once again to remove the dll's listed under Trusted installer as well? I did everything that wasnt running or listed under trusted installer.
I didnt want to blanket remove everything as tbh that sh had me worried i was going to brick my pc but doing what you described with advanced search and sfc/scannow reported no issues, so going to carry on with the rest of your steps and see if it works for me now.
thank you for the relatively quick reply as well!
Edit: doing as i described above didnt fix the issue still ;-; and i attempted it again, but was gonna say screw it and do trusted installer even though that concerned me, but it only said try again, skip, and cancel. Didnt show continue(with the administrator icon) So i believe i followed your steps the same as you if im not mistaken. Reinstalled directx, visual C++, and still having the error issue, I didnt get any popups from directx saying i had missing or corrupted dll's either. So i appreciate your help/steps, but doesnt look like its fixing the issue for me.. ☹️
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: 0x440
Faulting application start time: 0x01db3e2d9baf2428
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: unknown
Report Id: c1e9bf9e-5473-4001-8931-af38ef8b021d
Faulting package full name:
Faulting package-relative application ID:
Community Highlights
- EA_Blueberry7 years ago
Community Manager
