| Previous | Next |
| WIN32K_CALLOUT_WATCHDOG_LIVEDUMP | CALL_HAS_NOT_RETURNED_WATCHDOG_TIMEOUT_LIVEDUMP |
WIN32K_CALLOUT_WATCHDOG_BUGCHECK
WIN32K_CALLOUT_WATCHDOG_BUGCHECK is bug check 0x1A2. Microsoft states that a callout to Win32k did not return promptly. Parameter 1 identifies the thread blocking prompt return from the Win32k callout; parameters 2, 3, and 4 are reserved.
This is the bug-check counterpart, not the 0x1A1 live-dump code
WIN32K_CALLOUT_WATCHDOG_LIVEDUMP (0x1A1) is explicitly reserved for live dumps and can never be used for a real bug check. The 0x1A2 value is the stop-code counterpart. Keep the distinction because a live dump allows the operating system to continue, whereas a bug check represents a system stop.
Thread-centered analysis
- Start with the thread address in parameter 1 and inspect that thread's stack and wait state.
- Determine what the thread is waiting on or executing and which component is preventing prompt return from the callout.
- Do not decode reserved arguments as timeout durations or object addresses.
References
- Microsoft: Bug Check 0x1A2 WIN32K_CALLOUT_WATCHDOG_BUGCHECK
- Microsoft: 0x1A1 live-dump counterpart
- Microsoft: WinDbg !thread extension
Looking for a different code? Search another status or error code.