APC INDEX MISMATCH BSOD error Today reported for more that 10 Dell desktops - Failed win32kfull.sys

Anonymous
2021-03-10T08:39:05+00:00

Hi Team,

Getting BSOD on more that 10 Desktops, Some reported while printing from PDF , Some during working on Excel , Some reported opening AutoCad

its random reporting , Checked the Dump and it shows  win32kfull.sys Fault not much .

any of you guys have faced similar or fixed .

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Sumit 43,876 Reputation points Volunteer Moderator
2021-03-10T09:27:09+00:00

Hi Toji,

Apart from Dave's response, did you Patch your PC yesterday?

I have some reports wrt Printing triggering a BSOD with the same code since yesterday.

Edit 12/03/2021

----------------------------------------------------------------------------------------

Microsoft has said that this is a known issue and is being investigated.

In the meantime, uninstall the update.

In the search, type cmd, right-click it and choose Run as administrator.

Paste the command given below:

wusa /uninstall /kb:5000802

Press yes and afterward pause the updates for 7 days.

(Replace 5000802 with 808 if you have Windows 10 version 1909)

------------------------------------------------------------------------------------------------

Additional information from therelease health:

Status Originating update History
Confirmed OS Build 19042.867 <br>KB5000802 <br>2021-03-09 Last updated: 2021-03-12, 11:03 PT <br>Opened: 2021-03-10, 06:04 PT
After installing KB5000802, you might receive an APC_INDEX_MISMATCH error with a blue screen when attempting to print to certain printers in some apps. This issue affects a subset of Type 3 printer drivers and does not affect printer drivers that are Type 4. If you are unsure which type your printer driver is, use the following steps:<ol><li><p>Press the Windows key+r or select <strong>Start </strong>and type <strong>run </strong>and select it.</p></li><li><p>Type <strong>printmanagement.msc </strong>and press enter or select the <strong>OK button</strong>.</p></li><li><p>If Print Management opens, continue to step 4. If you receive the error, <strong>Windows can not find 'printmanagement.msc'.</strong> then select <strong>Start </strong>and type <strong>manage optional features</strong> and select it. Select <strong>Add a Feature</strong> and type <strong>print</strong>, select the check box next to <strong>Print Management Console</strong> and select install. You will now need to start at step 1 again.</p></li><li><p>Expand <strong>Print Servers</strong>, expand your computer's name, and select <strong>Printers</strong>.</p></li><li><p>You can now see the Driver Type for each of your installed printer drivers.</p></li></ol>**Workaround:**To mitigate the issue, follow the instructions in this video. The Command Promptcommands from the video are as follows (you will need to replace KX driver for Universal printing with the name of your printer, as explained in the video):<ul><li><p><strong>rundll32 printui.dll,PrintUIEntry /Xg /n “KX driver for Universal printing”</strong></p></li><li><p><strong>rundll32 printui.dll,PrintUIEntry /Xs /n "KX driver for Universal printing" attributes +direct</strong></p></li></ul>Affected platforms:<ul><li><p>Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803</p></li><li><p>Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803</p></li></ul>**Next steps:**We are working on a resolution and estimate a solution will be available in the coming week.

---------------------------------------------------------------------------------------------------------------------

Update 03/15/2021

An out-of-band update KB5001567 is available that fixes the issue.

March 15, 2021—KB5001567 (OS Builds 19041.868 and 19042.868) Out-of-band (microsoft.com)

Highlights

  • Updates an issue that might cause a blue screen when you attempt to print to certain printers using some apps.

Direct download links for Windows 10 20H1 and 20H2:

32 bit:

http://download.windowsupdate.com/d/msdownload/update/software/updt/2021/03/windows10.0-kb5001567-x86_bafeb1bea06a5f39976de3406d3e33fb3cc2c6fe.msu

64-bit

http://download.windowsupdate.com/d/msdownload/update/software/updt/2021/03/windows10.0-kb5001567-x64_e3c7e1cb6fa3857b5b0c8cf487e7e16213b1ea83.msu

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

107 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-03-10T10:53:32+00:00

    Hi Toji,

    Apart from Dave's response, did you Patch your PC yesterday?

    I have some reports wrt Printing triggering a BSOD with the same code since yesterday.

    Yes , there was an update by digging more when we uninstalled KB5000802 it worked, tried on 2 desktop so far its working , will get back with more Info

    Thanks You

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-03-10T10:54:28+00:00

    Hi Dave,

    Uninstalled KB5000802 and it worked , digging into more details , Well appreciated for the swift check and support...

    Regards

    Toji

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-03-11T09:33:28+00:00

    I confirm, I have the same issue - Dell desktops with Triumph printers.

    After unistalling KB5000802 everything's fine.

    Regards

    Mike

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. DaveM121 915.5K Reputation points Independent Advisor
    2021-03-10T10:58:33+00:00

    Hi Toji, glad to Help!

    Since you posted the question, I discussed this with Sumit and did some reading and Microsoft have been made aware of the problem, they have pulled that update because of the bugs in it . . .

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments