Game Doesn't Close If You Try to Leave after Selecting Auto Queue Option
If you press auto queue after a match ends and then if it takes too long and you just wanna leave the menu and go back to loby; it doesn't go back to lobby anymore. The game keeps running in the background and you can't close it at all. Even trying to close the EA launcher itself doesn't close it; trying commands to force close it doesn't close it either. You have to either shut down the pc entirely or restart.
[Crash]The game causes my PC to crash and freeze.
In my environment, the game freezes within minutes of starting and becomes unresponsive to PC controls. The only way to restore normal operation is to force a restart using the physical power button. No other games experience crashes or freezes. This issue occurs 100% of the time upon entering the field. I have confirmed that the issue invariably occurs in the shooting range. Note that when the game crashes, the screen does not refresh, and no blue screen or similar error is displayed. I have attempted several workarounds, but the issue recurs in all cases. I believe the system requirements are met, but if there are any other verification methods or a checklist, please advise. [Environment] OS: Windows 11 Pro 25H2 (Build 26200.7171) CPU: Intel Core i7-10700F Mem: 32GB (8GB x 4) GPU: Nvidia RTX 2060 Super Apex Legends (Build ID in Steam): 20869454 [Already attempted] -> None of these resolved the issue - Rolling back the graphics driver - Changing the graphics card - Changing the game's installation storage location - Disabling VT-x in the BIOS - Replacing the power supply unit - Testing each memory module individually - Reinstalling the OS I hope this issue can be resolved as soon as possible.Report bug : developer-facing debug path
Apex Legends is exposing internal RTK/Nut script errors suring post-match progression. The error shows the full scripts path and functions. This should probably be hidden behind a generic error message. rtk/menus/post_game/progression/rtk_postgame_progression_controller.nut #1248 [RTKPropertyStruct_Script_SetValue] Props parameter is null @Respawn / @Playapexmy apex is bugging please help
basically every time i load up apex my game will just close completely it doesn't happen all the time but I'm only being able to play like 2 matches a day before it just stops working so if anyone knows how to fix this please help i load into the lobby and it will just close
Apex Legends Crash on Startup
Hello, I am having a persistent crash when launching Apex Legends on Steam. The game does not reach the lobby screen and immediately triggers the Crash Report Handler. The crash occurs every time on startup and generates new PACKER_xxxxxx.dmp files in the Temp directory. I have performed full system cleanup, reinstalled Easy Anti-Cheat, reinstalled Apex Legends, validated Steam files, cleaned the Temp folder in Safe Mode, and also checked system integrity (SFC / DISM). Nothing has resolved the issue. I also analyzed the crash dump using WinDbg, and the crash points to: Exception Code: c0000005 (Access Violation) Exception Address: 00007ffb0ec00000 [Hardware-enforced Stack Protection] Crash dump path example: C:\Users\TheKoswo\AppData\Local\Temp\PACKER_2321187_12824.dmp Despite reinstalling Easy Anti-Cheat, the game still fails to load at startup. **Steps already tried:** • Full reinstall of Apex Legends • Easy Anti-Cheat reinstall & repair • Steam file integrity check • Clearing AppData, Temp (even in Safe Mode) • Updating GPU drivers • Windows SFC /scannow • DISM Cleanup / RestoreHealth • No overlays, no background apps • BIOS and chipset updated **System Info:** Operating System: Windows 11 Architecture: x64 Game running through Steam Crash happens before reaching the main menu. I am uploading the crash dump file and screenshots along with this report. Please investigate this issue since the game is currently unplayable on my system. If needed, I can provide more logs or run diagnostic tools. Thank you.
The game crashed
Playstation 4 slim with latest Apex update 2.99 The game crashed after starting a new round with this message on the screen. rtk/menus/post_game/progression/rtk_postgame_progression_controller.nut #1248 [UI] [RTK][RTKPropertyStruct] [RTKPropertyStruct_Script_SetValue][RTKStruct_SetValue] Props parameter is nulApex has been booting my system into recovery mode for 4-5 months
System: MSI Bravo 15 C7vF • NVIDIA RTX 4060 8GB VRAM • AMD Ryzen 5 7535HS • 16GB RAM • 512GB NVMe (original) • 1TB NVMe (new drive) I've been experiencing this issue for the past 4-5 months ever since the time i got myself a new nvme (Predator GM7 1tb) at that time Apex had the fixed landing spot in ranked, just before Wild Card came out i think. for my gaming laptop. I for some reason ever since that day been getting that issue specifically on apex only. I played apex more than an hour and launches my pc into recovery mode. Then when i tried other games like Marvel Rivals, Helldivers 2, etc. for more than 3 hours, Nothing happens. Here is a list of what i have tried (1) Clean Windows Reinstall & System-Level Fixes, I've reinstalled windows 4 time ever since the issue happens nothing seems to change from doing this, still causing apex to launch to repair mode. Side note: after reinstalling windows i always install AtlasOS right after a reinstall. (I don't think it affects it though) (1.1). I've tried installing windows on my new NVMe and only apex in that same NVMe and have the C drive removed since it originally has the windows, My memory is still a bit fuzzy about this since nothing really significant really happened, which means it don't seem to work at all. (2) Verified game intergrity on both Steam and EA play, Nothing seems to be affected from doing this, still causing apex to launch to repair mode after a few matches ranked or LTMs. (3) Updated my drivers, I've always had my drivers updated (mainly nvidia tho) ever since it happened. until recently i just updated my BIOS and it still causing apex to launch to repair mode. (4) I moved my APEX from my D drive to my C drive, It still causes the issue if i were to have both the C and D drive in my system. (4.1). Unless if i were to remove my D drive, The issue never happened a single time if i were to play ranked or LTM's. I played for hours in apex and i have no problems at all. But this solution was not optimal for me. So i moved on to find the next solution which is having Apex on my C drive instead of my D drive. (5) I installed APEX on Steam and EA on my D drive and also my C drive; This solution worked half half i guess. It still crashes my game in like 2-3 matches in ranked, then couple of LTM matches if i have my D drive still in my system. But if i were to have apex on my C drive while i still have my D drive installed, i would still be booted into repair mode. (6) I returned the new NVMe and gotten a new one from the store i bought, Look at the image attached. The Black screen was the initial error that I got before I got the new NVMe. The Blue screen was the error that I have been getting ever since I got the new replaced one. Findings - Error Codes: Initially, the system would boot into Windows Boot Manager with the error code 0xC0000001. Later, it would also trigger a repair mode with the same error code. - Crashes occured on all the game modes i play Pubs, Ranked, Wild Card, LTM's except for Firing range. - The crashes are not recorded in the typical crash dumps. I can try giving screenshots of my event viewer but it is kinda difficult for me to understand what the issues because i don't really know what to look at. (If you are interested in looking what the logs are saying then do say so) Conclusion I am still unable to play apex properly for the past 4-5 months because of the update that occurred and also because at that time I upgraded my laptop by adding an additional 1TB NVMe for my gaming laptop. I tried all the methods that i have mentioned above, and it still doesn't solve the problem. It still stops me from playing the game properly and crashing mid-match. If anyone has a solution for me to try please let me know. I am desperate to play apex without an issue at all.
