Question Random stops working and it's hard to figure out why?
Question Random stops working and it's hard to figure out why?
Gameplay issues consistently occurring in Apex Legends (Steam). I recognize there are reports indicating problems, though I’m still struggling to pinpoint the exact cause. I’ve experimented with various solutions but haven’t found a resolution. Previously, I played Apex several years ago without any difficulties. Recently, after restarting the game, I started experiencing crashes since installing it, likely due to the current DX12 version. These issues appear only within the game, not in the menus (I’ve let it idle for hours without problems).
This problem doesn’t occur in League of Legends or other titles. I used to have frequent crashes in Borderlands 3 until I turned off my overclocking feature, which resolved the issue.
My system specs are a 5800x3d, 3060, 2x16GB RAM, with ample power and no overheating. The crashes previously triggered a "fatal error" message related to DXGI_DEVICE_REMOVED 0x887a0005, but now I’m seeing nothing and it seems like the system is failing to boot properly.
I’ve tried numerous NVIDIA drivers—both older and current—and have disabled overclocking, undervolt settings, reinstalled the OS, checked for files, enabled secure boot, turned off spot shadows, adjusted power settings, activated debug mode in NVIDIA, and even increased TDR timeout. I also changed my power plan and ensured RTX was off.
FPS caps were applied, VSync disabled, and game memory was reduced. Despite these efforts, the issue persists. The 3060 and 5800x3d graphics cards are only a year old, yet they still cause problems. I play a lot of League of Legends and have never encountered this issue before. I don’t see any crash logs in the Apex folder, though occasionally I get an Event Viewer entry.
The event description for ID 153 from nvlddmkm isn’t available. It might be that the component triggering this event isn’t installed on my machine or the installation is corrupted. You may need to install or repair it locally. If the event happened on another device, the display information should have been saved with it.
Additional details included in the event:
- Device: Video3
- Error: GPUID 500
- Message: The resource exists but isn’t found in the table.
- Possible cause: Either the component is missing or installation is damaged.
If this is just an Apex or engine problem, it’s unlikely to be solvable on my end. Any suggestions or tips would be greatly appreciated. It’s really frustrating to have such issues with games I play regularly!
Welcome to the forums, newcomer!
i have a 5800x3d, 3060, 2x16gb ram, plenty of power - my pc temps do not get hot AT ALL
Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time. Including all driver versions you've worked with would help us two fold.
I recall Apex Legends had an anti-cheat app you'd need to install, see if uninstalling that helps.
CPU: 5800x3d (one-year-old)
CPU cooler: DeepCool AK620 (same age as above)
Motherboard: gigabyte b550 aorus elite atx am4 (2020)
Bios: F24
Ram: g.skill ripjaws v series 32 (2x16) 3200hz (one-year-old)
SSD: (the game is stored here) western digital sn550 500gb m.22280 (2020)
HDD: seagate barracuda compute 2 TB 3.5" 7200 RPM (2020)
GPU: MSi geforce RTx 3060 ventus 2x oc 12GB gddr6 (one-year-old)
PSU: EVGA supernova 750 GA 750 W 80+ gold certified fully modular ATX (2020)
Chassis: fractal design meshify c atx mid tower case (2020)
OS: W10 22H2
Monitor: main monitor (game runs on) acer VG240Y P
second monitor acer SB220Q
I originally assembled this PC in 2020, and all the components marked as one-year-old were bought and installed in mid-2024.
The Nvidia drivers I attempted to use are:
561.09 (currently installed here)
576.28
581.08
I disabled Apex's vsync and haven't experienced any crashes yet, though it typically causes issues once a day. The reason vsync might be triggering this is unclear at the moment.