Blue Screen of Death after closing BF2042 *FIX HAS BEEN FOUND*
So every time i close BF2042 since the S6 update my PC keeps blue screening causing a LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Ampere_UserOC Crash on my RTX 3080 to crash never happened until after the S6 ...
@dragoonx008 The issue seems to be related to EA anti-cheat across multiple games, not just Battlefield. It can be fixed by going to: Windows Security > Device Security > Core Isolation > Turn on Memory Integrity(Toggle off/on if already on).
If this setting is not visible in the security section, you may have to enable virtualization in your BIOS. I had to do this for my system and the memory integrity setting appeared immediately after. I hope this helps anyone experiencing the same issue and saves you time searching around for a solution!
I did get rid of ASUS software using the Armoury crate uninstaller, also before that i used IOBit uninstaller to make sure all residues are clean but i still get BSOD upon closing BF2042.
As explained by the other users here on this thread the drivers below are not safe to be deleted as it serves as managing and controlling the hardware resources.
Just want to know if you have info if the devs are already aware of this issue as this is being experienced by a lot of users here on this thread(not to mention the others who are not reporting this issue)
It does not make sense for multiple end-users to go through all of this troubleshooting if the issue is being caused by the update of anti-cheat - BSOD upon exit of BF2042 did not happen before S6 patch.
I was also affected by this BSOD (KERNEL APC PENDING DURING EXIT) issue when exiting BF2042.
My system
ASUS ROG Strix X570-E Gaming
AMD Ryzen 9 5950X
64GB DDR4-3600
and solved it by disabling the mentioned ASUS drivers (there is no need to delete them, just disable them for your gaming session until this has been fixed by EA or ASUS).
If someone is still having this problem, could anyone provide me with the following registry keys (the ASUS drivers should currently be running on your system and you may not have all of these registry entries on your system).
In short: by editing the startup process of these ASUS drivers in the registry.
If you still have the problem, then the ASUS drivers are still active on your system.
Could you please export the registry entries mentioned and attach them here as *.reg files?
To do so, please open up the registry, browse to the location of the entry and do a right click in the left panel on the entry and select: Export and save them to your desktop.
I could then create some REG files for you and anyone else who still has the problem to activate/deactivate these ASUS drivers.
Please note that disabling these ASUS drivers will have an impact on software such as ASUS AI Suite or other ASUS fan controlling software! (I don't use ASUS AI Suite or any other ASUS fan controlling software as I use the software ICUE on my system.)
Here you have 3 files (the 4th one will be in the next post) I have changed the extension from .reg to .txt because it wasn't supported by this platform.
If you can please let me know how do you disable these drivers, and then how to re enable them. And what is missing in the system when disabled??
I used Autoruns by Microsoft/Sysinternals to disable those drivers. Windows error pop ups Asus Framework missing but can be ignored for now. Seems a mitigation until a proper fix by EA.
@SilverChris10 thank you for providing me the REG files.
Regarding your questions: if those drivers are disabled, it will have an impact on software such as ASUS AI Suite or other ASUS fan controlling software! (I don't use ASUS AI Suite or any other ASUS fan controlling software as I use the software ICUE on my system.)
If you would like to use the registry method, then to disable those drivers, follow the below instructions (or use one of the mentioned software at the end of the post).
To re-enable those drives using the registry method, set the start type back to:
"Start"=dword:00000001
@Mirakulas05 this is also a possible solution, but don't forget to change back the filename if this ever get's fixed by EA or ASUS 😉
Select the desired drivers (hold Shift and left click to mark more than one), then do a right click on your selection and first select: Change Status > and select: Stop > if they are running!
Do another right click on your selection, this time select: Change Startup Type > and set it to: Manual (see following screenshot)
Reboot your computer afterwards so the changes can take effect.
After rebooting check first with either ServiWin or Autoruns if the drivers are really stopped and set to manual startup.
If yes, then start BF2042 and as soon as you are in the main menu, exit the game, this time hopefully without any BSOD.
To re-enable the drivers with ServiWin:
Run ServiWin as Administrator
Select the desired drivers (hold Shift and left click to mark more than one), then do a right click and select first: Change Startup Type > and set it to: System (see following screenshot)
Reboot your system.
Please also note there is no need to rename or delete the drivers, as it should be enough just to set the startup type to manual.
This is also the cleaner and safer method than renaming a driver, as renaming a driver could have other side effects to your system or applications (like ArmouryCrate or other ASUS related software), and if needed, you can always re-enable them with either ServiWin or Autoruns again and everything should be back to as before.
I hope this helps in the meantime, until this gets solved by EA 😉
Edit: Updated instructions and added another reply: Post #140 to hopefully clear up a few things.
In my case it worked by disabing only Asusgio2 and Asusgio3 (then restart your PC). I have used Autoruns because its simplicity but all methods mentioned should work as well. Upon startup you will probably receive a windows warning that a driver could not be loaded. But that's all. Everything working as it should be!!
@SilverChris10 thanks again for your input, in this case it should be enough to just disable Asusgio2 and Asusgio3.
I don't get any driver error upon startup, but I also don't use any kind of ASUS software like ASUS AI Suite or any other ASUS fan controlling software, so thats maybe why.
And like you said, every method will work: either by editing the registry or using one of the mentioned software, all will do the same at the end 😉
I've gone through a lot of trouble shooting, did almost the same as @Mirakulas05 did, (I also used WinDbg to debug the minidump of the BSOD, then I used MSCONFIG to startup only with a minimal set of drivers, I also used DriverViewer to verify the drivers are not loaded and so on to find the culprit)
May I ask you, have you opened a support request at EA regarding this issue?
I used to get bsods when leaving the game. And now when you log in, when you select settings. Disabling drivers didn't help. Has anyone encountered this?
Having issues with Battlefield 2042? Join here to report bugs, and find help with, crashes, connectivity and more.13,104 PostsLatest Activity: 7 hours ago