| Previous | Next |
| CONNECTED_STANDBY_WATCHDOG_TIMEOUT_LIVEDUMP | LIVE_SYSTEM_DUMP |
WIN32K_ATOMIC_CHECK_FAILURE
The WIN32K_ATOMIC_CHECK_FAILURE bug check has a value of 0x00000160. This indicates that a Win32k function has violated an ATOMICCHECK.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
WIN32K_ATOMIC_CHECK_FAILURE Parameters
| Parameter | Description |
|---|---|
| 1 | Count of functions on the stack currently inside of an ATOMIC operation |
| 2 | Reserved |
| 3 | Reserved |
| 4 | Reserved |
Dump evidence for WIN32K_ATOMIC_CHECK_FAILURE
For WIN32K_ATOMIC_CHECK_FAILURE, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “WIN32K_ATOMIC_CHECK_FAILURE”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for WIN32K_ATOMIC_CHECK_FAILURE
- Run WinDbg
!analyze -v, then inspect the documented meaning of each WIN32K_ATOMIC_CHECK_FAILURE parameter instead of relying only on the probably-caused-by line. - Find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with win32k / atomic / check.
- For WIN32K_ATOMIC_CHECK_FAILURE, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by WIN32K_ATOMIC_CHECK_FAILURE before collecting the dump and event logs. For WIN32K_ATOMIC_CHECK_FAILURE, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.