| Previous | Next |
| HAL_MEMORY_ALLOCATION | VIDEO_DRIVER_INIT_FAILURE |
BGI_DETECTED_VIOLATION
Boot graphics initialization violation for BGI_DETECTED_VIOLATION
BGI_DETECTED_VIOLATION is bug check code 0x000000B1. This code points at early boot graphics state, before the full desktop graphics stack is necessarily active. It can involve firmware framebuffer handoff, boot graphics library state, display miniport transition, or boot animation paths.
How to read it in a dump
- The boot phase and display stack state are critical.
- Do not confuse it with a later desktop GPU crash such as a TDR unless the dump stack shows the graphics stack transition.
- Firmware and GPU driver updates can both be relevant.
What to check
- Check firmware, display driver, Secure Boot/boot graphics changes, and recent OS updates.
- Compare headless, basic display, or safe-mode behavior.
- Collect boot graphics and display miniport stack information from the dump.
References
- Windows display driver model
- Boot-start driver distribution disk
- Microsoft Bug Check Code Reference
- Analyze a kernel-mode dump with WinDbg
Dump evidence
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 “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each 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 bgi / detected / violation.
- 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 this result before collecting the dump and event logs. 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.