Windows November Security Update KB5068861 is causing BSOD after updating. What is causing this?

The BSOD issues you're experiencing after installing the November Security Update KB5068861, particularly the "unloaded_without_cancelling_pending_operations" and "Attempted execute of noexecute memory" errors, may be related to driver incompatibilities or conflicts introduced by the update. Since you've already rolled back the update and verified that the BSODs do not occur afterward, it suggests that the update itself is likely the root cause.

Given that you've updated your chipset and graphics drivers, it's also worth checking for any other drivers that may need updates or may be causing conflicts. Additionally, reviewing the minidump files could provide insights into specific drivers or processes that are failing.

If the issue persists, you may want to monitor for any subsequent patches or updates from Microsoft that address these specific BSOD errors, as they often release fixes for known issues following major updates.

References:

• Azure VM cannot RDP - driver IRQL not less or equal
• Resolved issues in Windows 11, version 24H2

Hi. I'm David, and I'm happy to help you.

The minidumps do not mention any third-party driver, only generic system files.

I suggest you use the Driver Verifier utility. This utility is used to force the system to show the driver causing the problem.

Before turning on Driver Verifier, I like to create a restore point just in case. I suggest doing the same.

https://support.microsoft.com/windows/system-protection-e9126e6e-fa64-4f5f-874d-9db90e57645a

Turn on Driver Verifier, let the system crash 3 times, then turn off Driver Verifier. Share the minidumps that the crashes created.

1. Press Win + R, type verifier, and press Enter;
2. Select Create custom settings (for code developers) and click Next;
3. Check these options:

• Pool Tracking
• I/O Verification
• Deadlock Detection
• DMA Checking
• Security Checks
• Force pending I/O requests
• IRP Logging
• Miscellaneous Checks
• DDI compliance checking

4. Select Select driver names from a list;
5. Sort by Provider and choose all non-Microsoft drivers;
6. Click Finish and restart your computer. Driver Verifier will now monitor the selected drivers.

(Pay attention to the blue screen that is displayed. Sometimes, it may contain useful information.)

After the system crashes at least 3 times, follow the procedure below to disable the Driver Verifier.

1. Open Start and type cmd, right-click on Command Prompt and select Run as administrator.
2. Run the following commands at the Command Prompt one at a time:

verifier /reset
verifier /bootmode resetonbootfail

3. Then, restart the PC.

If the system no longer starts due to BSOD caused by the Driver Verifier, start it in Safe Mode and perform the above procedure to disable Driver Verifier.

https://support.microsoft.com/en-us/windows/windows-startup-settings-1af6ec8c-4d4a-4b23-adb7-e76eef0b847f

I await your reply.

Feel free to ask back any questions.

Thanks.

Just checking that the commands (needed to do in safe mode) means that driver verifier is now disabled?

Yes. When running the commands, regardless of whether it was in Safe Mode or not, Driver Verifier is disabled.

The Driver Verifier mentions the GVCIDrv64.sys driver. This is a Gigabyte driver, typically installed along with the Gigabyte APP Center or motherboard utilities, and it's a driver known for causing instability.

Since this driver is used by multiple Gigabyte applications/utilities, it's not possible to know which specific application/utility to uninstall to completely remove and disable it. Therefore, I suggest uninstalling any Gigabyte applications/utilities. Then, try updating Windows and see if it works as expected.

You don't need to enable Driver Verifier again. Leave it disabled.

If the BSOD occurs again, please share the minidump it created.

Feel free to ask back any questions.