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 44,316 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: Oldest
  1. Anonymous
    2021-03-11T19:51:28+00:00

    I have this happening with printing to Kyocera from any computer, Acer laptops using Outlook 365.

    Description      FixComments  HotFixID   InstallDate  InstalledBy          InstalledOn  Name  ServicePackInEffect  Status  
    
    Update                        KB4601056               NT AUTHORITY\SYSTEM  2/17/2021                                       
    
    Update                        KB4513661                                    10/7/2019                                       
    
    Security Update               KB4516115                                    10/7/2019                                       
    
    Update                        KB4517245                                    10/7/2019                                       
    
    Security Update               KB4521863                                    10/7/2019                                       
    
    Security Update               KB4535680               NT AUTHORITY\SYSTEM  1/18/2021                                       
    
    Security Update               KB4552152               NT AUTHORITY\SYSTEM  7/10/2020                                       
    
    Security Update               KB4560959               NT AUTHORITY\SYSTEM  7/10/2020                                       
    
    Security Update               KB4561600               NT AUTHORITY\SYSTEM  7/10/2020                                       
    
    Security Update               KB4565554               NT AUTHORITY\SYSTEM  7/15/2020                                       
    
    Security Update               KB4569073               NT AUTHORITY\SYSTEM  8/12/2020                                       
    
    Security Update               KB4576751               NT AUTHORITY\SYSTEM  9/10/2020                                       
    
    Update                        KB4577586               NT AUTHORITY\SYSTEM  2/26/2021                                       
    
    Security Update               KB4577670               NT AUTHORITY\SYSTEM  10/15/2020                                      
    
    Security Update               KB4580325               NT AUTHORITY\SYSTEM  10/15/2020                                      
    
    Security Update               KB4586863               NT AUTHORITY\SYSTEM  11/17/2020                                      
    
    Security Update               KB4598479               NT AUTHORITY\SYSTEM  1/14/2021                                       
    
    Security Update               KB4601395               NT AUTHORITY\SYSTEM  2/11/2021                                       
    
    Security Update               KB5000908               NT AUTHORITY\SYSTEM  3/10/2021                                       
    
    Security Update               KB5000808               NT AUTHORITY\SYSTEM  3/11/2021
    

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-03-11T22:26:04+00:00

    Hi John,

    Try to uninstall using Powershell or CMD

    Check its installed or not (Below Command)

    wmic qfe list brief /format:table

    If installed execute below

    wusa /uninstall /kb:5000802

    Please be noted above KB is for Windows 10

    I ran the wmic and i don't even have KB5000802.

    I just wiped this machine today, installed windows 10 64bit, have a kyocera printer, when i try printing test page it BSOD with APC INDEX MISMATCH win32kfull.sys

    This is on a Microsoft Surface.

    i do have this KB5000808  installed. i'll try uninstalling and report back.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-03-11T23:00:04+00:00

    Btw, you all may already read but there seems a workaround for the time being:

    https://www.windowslatest.com/2021/03/10/windows-10-kb5000802-march-update-is-crashing-pcs-with-bsod/

    I can understand this issue is unacceptable for small-to-very-large businesses which a majority of them are using Kyocera/Ricoh/Mita engines.

    Was this answer helpful?

    0 comments No comments
  4. Sumit 44,316 Reputation points Volunteer Moderator
    2021-03-12T03:06:18+00:00

    Via Christopher Leung [Windows] post on this thread:

    Bluescreen of death and restarts after KB5000802 - Microsoft Community

    Hi all,

    If you are running into a problem APC_INDEX_MISMATCH BSOD while printing, I recommend trying out these steps to mitigate the issues until Microsoft addresses the problem with the update.

    Section 1 - Enable Direct Printing. This should allow 32bit apps to print on 64bit OS without crashing.

    1. Identify the name of your printer. E.g., "Kyocera TASKalfa 820 KX"
    2. In an elevated command prompt, run rundll32 printui.dll,PrintUIEntry /Xg /n "Kyocera TASKalfa 820 KX". IfDirectappears on the line ofattribute:, that means direct printing has been turned on and you had the right settings - stop here and proceed to section 2.
      1. Note - replace the Kyocera TASKalfa 820 KX text with your printer's name
    3. IfDirectsetting is not on, in an elevated command prompt, run rundll32 printui.dll,PrintUIEntry /Xs /n "Kyocera TASKalfa 820 KX" attributes +direct
      1. Note - replace the Kyocera TASKalfa 820 KX text with your printer's name

    Often times, apps like Acrobat and OpenOffice runs as 32bit apps and this should be enough to workaround around the problem until Microsoft addresses the issue. But this will not solve the problem for 64bit applications printing on 64bit OS, nor 32bit applications printing on 32bit OS.

    Section 2 - Enable PrintIsolationAware appcompat fix to your printer. This should allow 64bit applications printing on 64bit OS and 32bit applications printing on 32bit OS without crashing.

    1. Follow the directions from the following page to acquire the Application Compatibility TookitDownload: Application Compatibility Toolkit (ACT) for Windows 10. | Microsoft Docs
    2. Follow the instructions -Creating a Custom Compatibility Fix in Compatibility Administrator (Windows 10) - Windows Deployment | Microsoft Docs- to use the Compatibility Administrator tool to apply the “PrinterIsolationAware” fix to the affected application

    Thank you,

    Christopher

    Was this answer helpful?

    0 comments No comments