| Previous | Next |
| KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL | SAVER_NONRESPONSIVEPROCESS |
VIDEO_DXGKRNL_LIVEDUMP
DirectX graphics kernel live dump for VIDEO_DXGKRNL_LIVEDUMP
VIDEO_DXGKRNL_LIVEDUMP is bug check code 0x00000193. This code identifies a diagnostic live dump from dxgkrnl or the graphics kernel stack. It can be raised to capture GPU scheduler, TDR, memory, or display miniport state without necessarily halting the whole machine.
How to read it in a dump for VIDEO_DXGKRNL_LIVEDUMP
- Look for the graphics engine, adapter, process context, and TDR state in the dump.
- The app using the GPU may only be the workload that exposed a driver or hardware problem.
- Display miniport and dxgkrnl symbols are central to interpretation.
What to check for VIDEO_DXGKRNL_LIVEDUMP
- Collect GPU driver version, TDR events, and display miniport logs.
- Try controlled update or rollback of GPU drivers.
- Correlate with media, browser hardware acceleration, gaming, or compute workloads.
References for VIDEO_DXGKRNL_LIVEDUMP
- Timeout detection and recovery
- Crash dump files and live dump context
- Microsoft Bug Check Code Reference
- Analyze a kernel-mode dump with WinDbg
Dump evidence for VIDEO_DXGKRNL_LIVEDUMP
For VIDEO_DXGKRNL_LIVEDUMP, 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 “VIDEO_DXGKRNL_LIVEDUMP”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for VIDEO_DXGKRNL_LIVEDUMP
- Run WinDbg
!analyze -v, then inspect the documented meaning of each VIDEO_DXGKRNL_LIVEDUMP parameter instead of relying only on the probably-caused-by line. - For VIDEO_DXGKRNL_LIVEDUMP, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with video / dxgkrnl / livedump.
- For VIDEO_DXGKRNL_LIVEDUMP, 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 VIDEO_DXGKRNL_LIVEDUMP before collecting the dump and event logs. For VIDEO_DXGKRNL_LIVEDUMP, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Dump evidence for VIDEO_DXGKRNL_LIVEDUMP
For VIDEO_DXGKRNL_LIVEDUMP, 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 “VIDEO_DXGKRNL_LIVEDUMP”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for VIDEO_DXGKRNL_LIVEDUMP
- Run WinDbg
!analyze -v, then inspect the documented meaning of each VIDEO_DXGKRNL_LIVEDUMP parameter instead of relying only on the probably-caused-by line. - For VIDEO_DXGKRNL_LIVEDUMP, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with video / dxgkrnl / livedump.
- For VIDEO_DXGKRNL_LIVEDUMP, 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 VIDEO_DXGKRNL_LIVEDUMP before collecting the dump and event logs. For VIDEO_DXGKRNL_LIVEDUMP, 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.