March Windows 10 update appears to cause blue screen of death when printing

Blue Screen of Death Windows 10
Blue Screen of Death Windows 10 (Image credit: Windows Central)

Updated March 11, 2021: Microsoft has since confirmed that the issue is present in several versions of Windows 10.

Updated March 16, 2021: Microsoft fixed the issue. You can install the fix with an optional Windows 10 update.

What you need to know

  • Some PCs show the blue screen of death following the latest Windows 10 update.
  • The issue only seems to occur when trying to print to certain printers.
  • Reports claim that Kyocera, Ricoh, Zebra, and other types of printers are related to the issue.

The March Windows 10 update (Windows 10 KB5000802 (opens in new tab)) appears to be causing the blue screen of death to appear for some users. A Reddit thread and a report by Windows Latest share several stories of people who have run into issues since installing the latest Windows 10 update. The issue seems to occur when trying to print something, though it may only affect certain printing situations.

"This update seems to be causing blue screens when printing to Kyocera Universal Print drivers. Have had at least 20 confirmed cases from 4 different clients already and it's only been an hour into the day," a person told Windows Latest.

The Reddit post and ensuing thread also mention Kyocera printers. According to the post on Reddit, updating to a newer Kyocera driver did not work.

In addition to reports of issues involving Kyocera printers, people have seen the blue screen of death when using Ricoh, Zebra, and other types of printers.

As is the case with many issues with Windows 10, we don't know the extent of this issue yet.

When the issue does occur, it can be done by a simple everyday task, printing anything. People have run into the issue when attempting to print from Notepad, Office, and other apps. PCs don't seem to see the blue screen of death unless they are trying to print to one of the affected printers.

Many people in the Reddit thread worked around the issue by uninstalling the Windows 10 KB5000802 update. That may solve this specific issue, but that update also includes several important fixes and security updates. Hopefully, Microsoft can get to the bottom of the issue quickly to remedy the situation.

Sean Endicott
News Writer and apps editor

Sean Endicott brings nearly a decade of experience covering Microsoft and Windows news to Windows Central. He joined our team in 2017 as an app reviewer and now heads up our day-to-day news coverage. If you have a news tip or an app to review, hit him up at (opens in new tab).

  • Just updated and no issues printing to my Xerox B215 printer.
  • Got the heads up by a twitter friend. I don't think he was printing at all. But well. Seems like they pulled this update, I can't get it.
  • It just happened to me when someone started a presentation in Teams. Tried it again after the meeting with a friend and it did it again. This update seems to be extremely finicky.
  • It's worse than this. There are some issues with deployment in Enterprise as well, with quite frequent crashes per day.
  • What's a printer? 🤣
  • The update broke Photoshop for me.
  • Causing serious issues here. Have found that changing the static IP of the printer, removing the device and creating via TCP identification has worked but come on Microsoft. This is embarrassing.........
  • Welp, I think this "fix" in a new Beta Insider build has something to do with the white papers of death:
    "We fixed an elevation of privilege security vulnerability documented in CVE-2021-1640 related to print jobs submitted to “FILE:” ports. After installing Windows updates from March 9, 2021 and later, print jobs that are in a pending state before restarting the print spooler service or restarting the OS will remain in an error state. Manually delete the affected print jobs and resubmit them to the print queue when the print spooler service is online."
  • No issues printing to Brother MFC Printers.
  • I actually saw the blue screen of death yesterday for the first time in many years, but I was not trying to print, only working in a couple of browsers with many tabs, open plus many word documents open and a bunch of other stuff so I assumed I just had too much going on.
  • I thought it only happened when you printed to certain print drivers with printer objects on print servers... In that case it should not affect home users.
  • That's a worst case for this. MS doesn't care so much about home users. This is affecting businesses, and Microsoft DOES care about them.