Re: Apex Crash erorr 0xc0000005

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:

@MrRandomAlex & @iitsMtv I wouldn't delete any of the DLLs in the Windows folder as those shouldn't be manually deleted, edited, moved, altered, etc. The Windows folder houses your system's files, so making any changes can cause more corruption and further issues where you would have to then reinstall Windows from a USB drive, as your PC may be too corrupted to be able to reinstall Windows itself.

Instead, you can, (and should), repair these files by:

- Open the Command Prompt in administrator mode

- Type, "DISM /Online /Cleanup-image /Restorehealth" (without the quotes), and wait for it to finish.

Note: DISM stands for "Deployment Image Servicing and Management tool". It often repairs Microsoft related files, such as issues with Window apps. Some problems with the next file checker can only be fixed after running this one first.

- Now type, "sfc /scannow" (without the quotes), and wait for it to finish.

Note: sfc stands for "System File Checker". This one will repair system files, (such as important Windows drivers).

- Lastly, restart your PC.

Should you need to reinstall Windows, (especially if your PC is unable to reinstall Windows itself), here's how you can reinstall on Windows 10 and on Windows 11.

If you need help creating the Media Creation Tool, using the tool, etc., please contact Microsoft Support.

Note: There's an option to keep your files, installed programs, and system settings as long as you're able to use the tool while logged onto your PC. If you're unable to use your PC at all due to it being unable to startup, then the tool can only be used to reinstall Windows completely, (at which point you could only select to keep your files).

Well its already said and done, and i previously did everything you just stated with no fix. You also previously stated what you said in your comment at the beginning of this thread and that didnt fix anything, so restating isn't much help. 

I already commented that i didnt have any issues afterwards, so i see no point in coming in telling us not to do it when i clearly already did.

We really just need a respawn dev to communicate whats happening with the error and if it is being investigated/recreated on their end and if it may be getting resolved soon, or if its not related to apex and it is a windows issue. 

it didn’t brick my pc and i didnt have any errors afterwards using sfc/scannow or using Dism /Online /Cleanup-Image /ScanHealth, and Dism /Online /Cleanup-Image /CheckHealth

i understand the severity of modifying files in the windows folder, however windows has built in protections to prevent certain files from being removed(unless you modify privileges and replace trusted installer with administrator)

Not everything located in the system 32 folder is integral to the windows operating system even though much of it is. Which is why it was specified to only do the system 32 folder and not any subfolders, as well as the words MrRandomAlex used “carefully”. 

if a dev was communicating with their steps to resolve the issue, i wouldnt be trying everything i could to remediate the problem. However its been over a month, that I've personally, as well as others have been dealing with the issue with no communication from EA support or respawn devs on ways to fix the issue! 

i have everything installed on separate drives and backed up my windows beforehand incase i somehow wound up messing something up. I just didnt want to go back through the process of reinstalling windows when i already did 5 months ago which is why i was initially hesitant but i’m just tired of the crashes happening and its only apex thats having this issue. (and as i previously stated, other EAC games) 

I Had corrupt system files in my case the only way to restore them was to delete them and reinstall the correct ones,

Deleting system 32 files will not "brick" any system unless you delete files being actively used.

This problem may have many iterations but for me that's what fixed it,

I ended up looking into this error code 0xc000007b which was occurring when I tried to open unity

Fixing that error code subsequently fixed this one as well 0xc0000005.

Valorant was the same story same exact error - 0xc000007b 

Meaning I had 32 bit system files installed rather than 64

Specifically these 2 

msvcr120.dll

and

msvcp120.dll

Downloading the 64 bits of these and adding them to the system 32 folder resolved my issues -> 0xc000007b 

Nothing wrong with deleting system files btw windows has plenty of features in place to stop you from bricking a system. 

If it were for IT guys saying to not touch system files you would need to reinstall windows to fix simple problems every time

Solution that resolved the lsass.exe/r5apex.exe errors!

Press Start then search PowerShell
Right click it then select Run as administrator
Copy and paste the command below then press Enter

reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa /v RunAsPPL /t REG_DWORD /d 2 /f;reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa /v RunAsPPLBoot /t REG_DWORD /d 2 /f;

After some more digging around online, I found a microsoft answers forum about someone having issues with lsa protection, and using the powershell command that was given,

I did not get the lsass.exe application error when opening the game and after playing for the normal amount of time i would run into the crash, it has yet to happen, so I believe this has resolved the issue!

Also here is a video explaining the same solution, but doing it manually instead of using a powershell script (found it previously but wasnt sure if it was applicable to windows 10, but after looking around online, it is!) 

@MrRandomAlex while I know you said your solution had fixed the issue for you, just wanted @ you to explain what I found/used.

Thanks for leaving your solution,

Always best to help future users that may visit this thread,

Hey folks, 

Thanks for sending the DxDiag. I can see that some of you managed to fix this, just want to check with the others if the issue is still present? 

Did u fix it??