Win32k Atomic Check Failure BSOD: 3 Ways to Fix it

Keeping your system up to date might help

Reading time icon 2 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

WIN32K_ATOMIC_CHECK_FAILURE

In some instances, you might encounter Win32k_Atomic_Check_Failure BSOD, and if that happens, today we’re going to show you how to properly fix it.

How can I fix the Win32k_Atomic_Check_Failure error?

1. Keep Windows up to date

  1. Press the Windows key + I to open the Settings app.
  2. Select Windows Update and click on Check for updates.
    check updates windows 11 taskbar overflow not working
  3. If there are updates available, they will be automatically downloaded.

2. Reinstall and update Bluetooth drivers

  1. Press the Windows key + X and select Device Manager.
    open device manager
  2. Locate your Bluetooth driver and right-click it.
  3. Choose Uninstall device and then click on Uninstall to confirm.
    Uninstall device
  4. After doing that, click the Action menu and pick Scan for hardware changes.

Once the default driver is installed, check if the problem is gone. If the issue persists, do the following:

  1. Visit your motherboard manufacturer’s website.
  2. Locate your model on the list and go to the Drivers section.
  3. Find the latest Bluetooth driver and download it.
  4. Once downloaded, run the setup file to install it.

3. Use Bluetooth dongle or wired peripherals

  1. Disable Bluetooth on your device. You might need to disable it from Device Manager as well.
  2. Connect a Bluetooth dongle and check if the problem still exists.
  3. Alternatively, try using wired devices instead or Bluetooth ones.

Win32k_Atomic_Check_Failure 0x00000160 is a rare error, and it usually affects Windows Insiders or developers, so if you’re a regular user you most likely won’t ever encounter it.

This isn’t the only issue you can encounter, and we wrote about SOC_SUBSYSTEM_FAILURE and CRITICAL_INITIALIZATION_FAILURE in our older guides.

We also have a guide on CRYPTO_SELF_TEST_FAILURE, so don’t miss it for more information.

More about the topics: BSOD

User forum

0 messages