Blue Screen of Death after closing BF2042 *FIX HAS BEEN FOUND*

@TIDDLES1  Much obliged.

...some people needed to disable all;

system32\drivers\AsIO2.sys

system32\drivers\AsIO3.sys
SysWOW64\drivers\AsIO.sys

SysWOW64\drivers\AsUpIO.sys

The only thing you possibly lose after disabling those drivers, is case lighting. /shrug
IMHO, system up-time is more important to me than case lighting.

But honestly, this is absolutely an EA issue.
I hope it gets patched Tues, but won't hold my breath.
It is EA after all.
And it wouldn't be EA without creating monumental screw-up's - from nothing.

@Rand0m_Digits Oh I did not realise that you had to disable all those files suppose I will keep them on a secondary backup folder as when I renamed those last two it kept telling g me it could not communicate with system files obviously for the motherboard if it is just lighting, I too can live without that as well.  I will re do this and post straight back if it fixes the crashing then at least I can come out of the game without the dreaded BSOD.  Thank you for explaining this to me I really do appreciate all the help you are showing me so thank you for explaining the process..

@Rand0m_Digits  I did what you explained I disabled all thse files you told me to and it worked exited out to the desktop and no BSOD.  It actually works so thank you for that info I would never ve been able to fix thsi without your help.

Hello everyone, I know this will be a long post to read, really sorry about, but I hope to clear up a few things:

The issue with the BSOD and the stop code: KERNEL APC PENDING DURING EXIT when exiting BF2042 seems to affect users who are using an ASUS or ASROCK mainboard and have the mainboard companion software ArmouryCrate installed (including the additional stuff like AsusFanControl, AI Suite, ASUS PC Probe etc.).

The ASUS drivers:

system32\drivers\AsIO2.sys - see: AsIO2.sys Windows process - What is it? (file.net)

system32\drivers\AsIO3.sys - see: AsIO3.sys Windows process - What is it? (file.net)
SysWOW64\drivers\AsIO.sys - see: AsIO.sys Windows process - What is it? (file.net)

SysWOW64\drivers\AsUpIO.sys - see: AsUpIO.sys Windows process - What is it? (file.net)

are used for the above mentioned software, so that the software can monitor and manage ASUS hardware, it isn't just for RGB lighting, so be aware of that.

But as already mentioned by others, there shouldn't be any harm by setting the startup type of these drivers to manual so that you can temporary play the game and also exit without a BSOD.

However you will not be able to use the any of above mentioned software as long as the drivers are stopped, but you can always re-enable them if they are needed or if you would like to use any of the above mentioned software again.

The issue probably needs to be resolved by both parties: EA and ASUS

- for EA/Dice by probably whitelisting the drivers in their new EA Kernel Anti-Cheat (as the issue didn't occur with Easy Anti-Cheat)

and

- for ASUS by correcting their programming for the drivers, as it looks to be some kind of failure in their programming: Bug Check 0x20 KERNEL_APC_PENDING_DURING_EXIT - Windows drivers | Microsoft Learn 

But I wouldn't rely on ASUS to fix this as soon as possible, as there are some reports which are a bit scary and it looks like they are still not solved: 

ASUS ASIO2.sys driver fun · Bof. Another blog. (syscall.eu)

ASUS ASIO2.sys exploitation · Bof. Another blog. (syscall.eu)

SecureAuth Innovation Labs (archive.org)

I hope that clears up a few things.

See you all on the battlefield 😉

Honestly, I am not playing until this gets resolved. Stopping the drivers and putting them on manual is causing constant 

Error code 2: File Not Found - AsIO3.sys!! error and when you close it, it appears after a while again. This one is on EA to fix, not ASUS.

@TIDDLES1  You're welcome, glad I could be of assistance. It's such a ridiculous bug to begin with.

@Cypress_CH  You must be kind of young.

These drivers you speak of, have been around the block for quite some time.

It's not recent.

Yes, the drivers can control other things... however, it's only for interaction - IE the user adjusting something through the bios right from windows desktop.

Many ppl like the integration. Some don't. They don't really give power-users much functionality, so they may be included within setup.exe's but are never used.

And I don't understand why you are suggesting other people to DOWNLOAD 3rd-party software to disable something that can very easily be done by hand, with just a simple rename. But it does tell me a lot about your level of 'systems understanding'.

I can appreciate your thoroughness in wanting to help fix things, for sure. But there are much better approaches to this issue.

And nothing needs to be 'downloaded' to temporarily rectify this problem.

As always in the tech world...

Mitigate and reduce the problem/s to its simplest form.

Always carry out the easiest solution, with the least amount of changes to the system.... (and, Document your changes)

"Because if it's not broke, there's no reason to fix it."

A final note,

In my 40+ hours of solving this I have not come across a single comment from anyone using ASROCK mb's.

However, ASROCK(a low quality OEM board manufacturer. Fry's used to give them away with CPU purchases. Half the time, they never worked.) is a sister company of ASUS, in a way.
Research it.

@Rand0m_Digits Thanks for your post and also for calling me kinda young.

I don't know your age, but if you call me young in my forties, I guess I have to appreciate that.

I know that these drivers have been around for several years, where did I mention those are recent?!

What I mentioned was that the problem with the BSOD and stop code: KERNEL APC PENDING DURING EXIT when exiting BF2042 started recently when Season 06 was released, more specifically when EA switched from Easy Anti-Cheat to the EA Kernel Anti-Cheat.

I don't like the integration either (and the additional bloatware it installs), which is also why I no longer have it installed (I had it installed when I first set up the computer, but I uninstalled it immediately).

The reason I suggested third-party software, which by the way are all legitimate tech tools, is because sometimes it is easier for a non-technical person to use the third-party software instead of the on-board Windows tools like msconfig, PowerShell, driverquery or devcon cmd etc.

I'm not here to argue with you about my level of "systems understandig" as you called it, but just as you can't understand me suggesting third-party software, I can't understand why you're recommending renaming drivers when there could be still software installed which relies on those drivers which could then lead to additional errors. Have you thought about that?

Now I could also say that your way of solving the problem is a lazy way, but that's not what I want at all and it's not my intention at all (don't get me wrong, I'm really not here to argue, I'm too old for that). I just want to show that you have to think outside the box and there can still be dependencies.

Ultimately, I think everyone here is old enough to decide for themselves how they want to solve the problem.

Regarding ASROCK:

I experienced such a case, but it turned out that the user switched from an Asus motherboard to an ASROCK motherboard due to a defect without reinstalling Windows and guess what: the drivers and software were still loaded, although these were obsolete. In this case, a special scenario, but not out of the question.

i did all the things regarding the asus drivers disabling but i get a popup every 5 minutes when playing saying there's an error from asus_framework.exe do you know how i could prevent the popups?