VIDEO_DXGKRNL_FATAL_ERROR on Windows 11/10: Causes and Safe Fixes

TL;DR:

The VIDEO_DXGKRNL_FATAL_ERROR (Bug Check 0x113) on Windows 11 and 10 indicates a DirectX graphics kernel violation that is typically resolved by booting into Safe Mode and rolling back or updating OEM display drivers rather than immediately replacing hardware.
    ● Secure your BitLocker recovery key and back up data to an external drive before modifying startup settings or executing a Windows reset, as these actions risk permanently erasing accessible files.
    ● Avoid manually replacing the dxgkrnl.sys component with unverified downloaded DLLs; instead, use DISM and SFC commands, which are designed exclusively to repair corrupted Windows images rather than damaged GPU hardware.
    ● Use Wondershare Recoverit strictly to retrieve missing or inaccessible documents from a physically healthy storage volume after an interrupted update, as the software cannot diagnose or repair the actual blue screen stop code.

---

Ask AI for a summary

ChatGPT Perplexity Gemini Claude Grok Free Download Free Download Free Download

Seeing VIDEO_DXGKRNL_FATAL_ERROR on a blue screen? This Windows stop code is Bug Check 0x113, indicating that the Microsoft DirectX graphics kernel subsystem detected a violation. The message does not, by itself, identify a faulty graphics card or prove that a particular driver is responsible. Start with recently changed display drivers, updates and connected hardware; protect important files before attempting a reset or reinstall. Microsoft's Bug Check 0x113 reference explains the technical meaning.

This guide applies to Windows 11 and Windows 10, including systems that restart before the desktop loads. Settings names and available recovery options vary with the Windows build and manufacturer. If you cannot access Windows normally, jump to Safe Mode before attempting changes.

Part 1. What Does VIDEO_DXGKRNL_FATAL_ERROR Mean?

The crash is associated with the Windows graphics-kernel path, which coordinates work between the operating system and display components. Common investigation areas include graphics-driver changes, updates, unstable graphics hardware, firmware, power or overclocking problems. These are possibilities, not a diagnosis from the stop code alone.

For deeper diagnosis, preserve the exact stop code, when the failure occurs, and any crash dump under C:\Windows\Minidump if Windows can still create one. Advanced users or IT support can examine the dump rather than replacing hardware based on the error name alone.

Part 2. Before You Troubleshoot: Protect Your Files

A blue screen does not automatically delete personal files. But repeated hard restarts, an unstable drive, a reset or a clean installation can put accessible data at risk. Make a backup before making major system changes.

• If Windows starts, copy important documents, photos, projects and videos to a separate healthy drive or a supported cloud destination.
• If the PC is not stable enough to back up, avoid repeatedly installing tools or writing files to the affected disk. Consider professional help or a suitable independent recovery environment.
• If the drive makes unusual noises, repeatedly disconnects, is not detected, or shows other signs of physical damage, stop software recovery attempts and consult a professional.
• If BitLocker is enabled, locate the appropriate recovery key before changing recovery or startup settings. Do not disable encryption or format the drive as a shortcut.

Microsoft provides an overview of Windows recovery options. Use it to assess the consequences of any later restore, reset or reinstall action.

Part 3. How to Fix VIDEO_DXGKRNL_FATAL_ERROR on Windows 11 and 10

Work through these methods from the most reversible to the more intrusive. A driver rollback, for example, is usually preferable to resetting Windows when a crash began immediately after a graphics-driver update.

Start in Safe Mode When Windows Keeps Crashing

Use when: Windows repeatedly crashes before you can access Device Manager or Settings. Safe Mode loads a reduced set of drivers and services for diagnosis; it does not itself repair the underlying fault.

Step 1. Open Windows Recovery Environment. If Windows can still load the sign-in screen, hold Shift while choosing Power > Restart. If it cannot boot, use the manufacturer-supported recovery route or appropriate Windows installation/recovery media.

Step 2. Choose Troubleshoot > Advanced options > Startup Settings > Restart. The precise navigation can differ by release.

Step 3. Select 4 or F4 for Safe Mode; choose the networking option only if genuinely required. Sign in and continue with the graphics-driver checks.

If Safe Mode also crashes, stop repeating the same driver operations. Record the symptom and investigate hardware, storage health or a qualified repair service. See Microsoft's Safe Mode instructions.

Check or Roll Back the Display Driver

Use when: the blue screen began after a display-driver installation, graphics update or switching between integrated and discrete graphics.

Step 1. Right-click Start, open Device Manager, and expand Display adapters. Check each active graphics device; laptops may list both integrated and discrete GPUs.

Step 2. Open the adapter Properties > Driver. If Roll Back Driver is available and the crash began after a change, use it and restart. The button may be unavailable if Windows has no saved earlier driver.

Step 3. If a rollback is not available, note the driver version and move to a compatible update rather than downloading a random DLL or modifying dxgkrnl.sys.

If rolling back fixes the problem, avoid reapplying the same suspect package until an improved vendor version is available. A graphics-driver error cannot be established solely from the blue-screen text.

Install a Compatible Graphics Driver

Use when: Device Manager shows a driver problem, a suitable rollback is unavailable, or your PC maker provides a relevant corrected graphics package.

Step 1. Identify the exact laptop/desktop model, GPU, Windows edition and system architecture. For laptops, check the manufacturer's support page first because switchable graphics can depend on OEM-customized drivers.

Step 2. Download the correct signed graphics driver from your PC maker or the official Intel, AMD or NVIDIA site. Choose the version explicitly compatible with your device and Windows release.

Step 3. Follow the vendor's installer, restart and check whether the same stop code returns. Keep the prior package or restore option available when practical. Do not assume a generic newest driver is always the correct one.

If the crash persists after a verified driver change, do not repeatedly uninstall drivers without a backup. Continue with Windows update and system-integrity checks. The old NVIDIA installation window in legacy screenshots is version-specific and should not be used as a universal Windows 11 procedure.

Install Windows and Hardware Updates

Use when: the system has pending cumulative, optional driver or firmware updates supported by its manufacturer.

Step 1. In Windows 11 open Settings > Windows Update. On Windows 10, use Settings > Update & Security > Windows Update. Select Check for updates.

Step 2. Review available updates and install relevant, verified updates one group at a time if you are isolating a new crash. Restart when prompted.

Step 3. If the BSOD began just after a particular update, record its KB number and consult the current Microsoft known-issues guidance before removing anything.

Windows 10 reached end of standard support on October 14, 2025, for most editions. Check whether your device has an applicable extended security update arrangement; do not promise that old Windows 10 machines will receive all fixes. See Windows 10 support status.

Run DISM and System File Checker

Use when: you suspect Windows component corruption or recent failed servicing. These commands repair or check Windows system components, not a failing disk and not the DirectX hardware path itself.

Step 1. Open Command Prompt or Windows Terminal as administrator from a Windows session that is stable enough to finish the checks.

Step 2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to complete. This command targets the currently running Windows image; offline recovery uses different syntax and should not be improvised.

Step 3. Then run sfc /scannow, wait for the result and restart if Windows reports repaired components. Note the exact messages if a scan cannot complete.

Microsoft explains the order of these tools in the System File Checker guide. Neither command is a substitute for creating a copy of at-risk files, and SFC is not a bad-sector repair tool.

Use System Restore When the Error Began Recently

Use when: a suitable restore point predates the crashes and earlier troubleshooting did not resolve them. Save and verify important personal files first.

Step 1. Search Windows for Create a restore point, open System Protection, and choose System Restore; or find System Restore in Advanced options if Windows cannot start.

Step 2. Choose an appropriate restore point, review affected applications and drivers, then confirm only if the consequences are acceptable.

Step 3. After the restore, test a normal boot and check Event Viewer or the next error report if the system still crashes.

System Restore can undo some system changes, but it is not a substitute for a full file backup. If no restore point exists, do not manufacture one by reinstalling Windows.

Part 4. If Windows Still Will Not Start

If the previous steps do not help, separate software-level troubleshooting from signs of physical instability. Escalate carefully rather than attempting destructive repairs simply because the error is frustrating.

Check for Hardware Warning Signs

Check for repeated overheating, failed fans, abnormal GPU artifacts, unstable power, loose connections or hardware overclocking. Return supported overclock settings to defaults only if you understand the device and can do so safely. Desktop hardware checks should be performed with power disconnected and appropriate precautions; laptops may need professional service.

If more than one hardware component fails diagnostics or the PC repeatedly loses access to storage, avoid further write-intensive diagnostics until the data has been protected.

Use Windows Recovery Options Carefully

From Windows Recovery Environment, review Startup Repair, System Restore, and available options with their individual limits. A reset or clean installation is a last resort only after successful backup or suitable recovery planning.

Do not choose Remove everything, format the internal drive, or use DiskPart Clean merely to troubleshoot Bug Check 0x113. Even a reset described as keeping files can affect apps, settings and access, so verify a separate backup first. For encrypted systems, be prepared with the correct recovery key.

Part 5. Recover Missing Files After the Blue Screen

Wondershare Recoverit

Blue Screen Crash? Your Files May Still Be Recoverable

Download DownloadDownload

Missing important files after a VIDEO_DXGKRNL_FATAL_ERROR crash or Windows repair? Before resetting your PC, let Recoverit scan detectable storage for lost documents, photos, and videos. Preview recoverable files and save them safely to another drive.

Recoverit is not a tool for fixing VIDEO_DXGKRNL_FATAL_ERROR. It may be relevant if personal files became deleted, missing or inaccessible after a crash, an interrupted update or a recovery attempt. If files are still present, back them up rather than scanning needlessly.

Recover Files from a Detectable Storage Device

Use when: the affected HDD, SSD or external drive is detectable, there are no signs of severe physical damage, and files are truly missing. Avoid installing software or saving results to the same storage volume that contains deleted data.

Step 1. On a working computer, open Wondershare Recoverit and connect the relevant healthy, readable storage device when applicable. If recovering from an internal system disk, plan an appropriate separate environment so the installation itself does not overwrite missing data.

Step 2. Choose the detected device or location and start the scan. Do not format an unrecognized partition or initialize an unexpected drive to make it appear in the app.

Step 3. Review the found files, preview supported files where available, and recover selected data to a different healthy drive. Check that the recovered files open before continuing with any Windows repair or reset.

If Recoverit cannot detect the disk, the device disconnects continuously, or a drive shows physical faults, stop repeated scanning and consult a professional. Recovery success depends on the condition of the storage and whether the data has been overwritten.

For more detail, see the Recoverit official guide. These recovery steps apply to file loss; they do not diagnose the graphics driver or repair a blue screen.

Part 6. How to Prevent Another Graphics-Kernel Crash

Once the PC boots normally, focus on preventing recurrence rather than running unnecessary repair commands every day.

• Keep a verified copy of important files on storage that is separate from the PC.
• Use OEM-compatible graphics and chipset packages and record the versions before major changes.
• Monitor temperatures and cooling, especially when a crash occurs under GPU load.
• Keep Windows and device firmware supported and up to date where compatible.
• If crashes recur, preserve the stop code and diagnostic logs for targeted analysis instead of guessing the failing component.

Conclusion

VIDEO_DXGKRNL_FATAL_ERROR (0x113) indicates a serious DirectX graphics-kernel condition, but not a single proven cause. After backing up data, try Safe Mode, inspect recent graphics-driver changes, use verified OEM drivers and Windows servicing, and then consider System Restore or professional hardware diagnosis. Reserve Recoverit for actual missing or inaccessible files, not for blue-screen repair.