| Previous | Next |
| BUGCODE_USB3_DRIVER | NDIS_NET_BUFFER_LIST_INFO_ILLEGALLY_TRANSFERRED |
SECURE_BOOT_VIOLATION
Secure Boot integrity failure
SECURE_BOOT_VIOLATION is bug check code 0x00000145.
This bug check is raised when the Secure Boot trust chain or policy validation fails in a way Windows treats as fatal. The relevant layer can be firmware configuration, boot manager policy, boot-start driver signing, or protected boot state.
How to read the parameters
- Use the bug check parameters and boot log to identify the failing object or policy stage.
- This differs from an ordinary driver load failure because the boot integrity path is involved.
- Firmware variables, db/dbx updates, and boot configuration can matter.
What to check in the dump
- Check recent firmware updates, Secure Boot key database changes, bootloader changes, BitLocker recovery events, and unsigned boot-start drivers.
- Verify that test-signing, custom Secure Boot keys, or debugging settings are intentional.
- Do not disable Secure Boot as the first diagnostic step unless you already captured the failure evidence.
References
Looking for a different code? Search another status or error code.