xaff-xaff/bugchecksuppressor — explained in plain English
Analysis updated 2026-05-18
Research how HVCI protected Windows kernels can still be manipulated through data-only hooks rather than code patches.
Study SEH unwind and RtlUnwindEx as a mechanism for recovering from a kernel fault without a full crash.
Use as a starting point for exploring PatchGuard suppression techniques on HVCI and kCET enabled systems.
| xaff-xaff/bugchecksuppressor | 6x-u/enrinanime | ali-pahlevani/2d_scan_merger_ros2 | |
|---|---|---|---|
| Stars | 14 | 14 | 14 |
| Language | C++ | C++ | C++ |
| Setup difficulty | hard | hard | hard |
| Complexity | 5/5 | 4/5 | 4/5 |
| Audience | researcher | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Visual Studio 2022 with the WDK, a test-signing certificate, and a Windows 11 24H2 VM with HVCI and kCET enabled.
BugcheckSuppressor is a proof-of-concept Windows kernel driver, tagged "poc" and "rootkit" in its topics, that catches kernel crashes, the kind that normally cause a Blue Screen of Death, and lets the system keep running instead of rebooting. It targets a specific technical challenge: doing this without triggering HVCI, short for Hypervisor-Protected Code Integrity, a modern Windows security feature that prevents any software from writing new code into the kernel at runtime. The core problem it explores is that HVCI makes the traditional approach, patching a few bytes of kernel code to intercept a crash, impossible. BugcheckSuppressor works around this by using only data-only hooks: it modifies pointers in a writable data table, HalPrivateDispatchTable, rather than touching any executable kernel code. HVCI only guards code pages, not data pages, so this swap goes undetected. When a crash fires, the hook intercepts it before the blue screen appears. It then uses the kernel's own built-in error-recovery mechanism, called SEH unwind, via RtlUnwindEx, to cleanly walk back up the call stack, run all the cleanup code along the way, and land the system in a safe state. From the perspective of the rest of the OS, the bad driver that caused the crash simply failed to load and returned an error, as if nothing catastrophic happened. The README describes this as a thought experiment: the authors' stated motivation is exploring whether a full PatchGuard suppressor, PatchGuard being Windows' own kernel self-protection, is possible under HVCI. Tested on Windows 11 24H2 build 26200 with HVCI and kCET enabled. Written in C++.
A Windows kernel driver proof of concept that intercepts kernel crashes using only data-pointer hooks, avoiding HVCI's protection of kernel code, so the system stays running instead of blue-screening.
Mainly C++. The stack also includes C++, Windows Driver Kit, Windows kernel.
No license information is provided in the source material.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly researcher.
This repo across BitVibe Labs
Verify against the repo before relying on details.