0x00000113 VIDEO_DXGKRNL_FATAL_ERROR – Causes and Troubleshooting Guide

Quick Answer

VIDEO_DXGKRNL_FATAL_ERROR (0x00000113) is a Windows Blue Screen of Death (BSOD) error indicating that the Microsoft DirectX Graphics Kernel subsystem has detected a violation that prevents normal system operation.

The DirectX Graphics Kernel is part of Windows responsible for managing graphics-related operations and communication between the operating system, graphics drivers and display hardware.

This error is associated with the Windows graphics subsystem. Possible areas requiring investigation include graphics drivers, GPU-related software, display hardware, hybrid graphics configurations and system stability. However, the stop code alone does not identify the exact faulty component.

Recommended troubleshooting starts with checking recent graphics driver or Windows updates, installing an appropriate graphics driver from the computer or GPU manufacturer, removing unstable overclocking settings and examining crash dump files if the error continues.

What Is VIDEO_DXGKRNL_FATAL_ERROR (0x00000113)?

VIDEO_DXGKRNL_FATAL_ERROR is a Windows bug check (also called a stop error or system crash) with the hexadecimal value 0x00000113.

According to Microsoft, this bug check indicates that the Microsoft DirectX graphics kernel subsystem has detected a violation.

The DirectX Graphics Kernel is commonly associated with the Windows graphics infrastructure and the management of graphics devices. It works with display drivers and other graphics components to coordinate operations such as rendering, display output and graphics resource management.

When a fatal condition is detected in this subsystem, Windows may stop running and display a blue or black error screen, depending on the Windows version and configuration.

The error is not proof that the graphics card itself is physically damaged. A driver problem, software conflict, hardware instability or another underlying issue may be responsible.

Common Symptoms of VIDEO_DXGKRNL_FATAL_ERROR

A computer experiencing this error may display one or more of the following symptoms:

• A Blue Screen of Death with the stop code VIDEO_DXGKRNL_FATAL_ERROR.
• The hexadecimal bug check value 0x00000113.
• Unexpected computer restarts or shutdowns.
• System crashes while playing games or running graphics-intensive applications.
• Crashes during video playback, rendering or other graphics-related activities.
• Display freezing or unexpected screen interruptions before a crash.
• Repeated crashes after installing or updating a graphics driver.
• Crashes when switching between integrated and dedicated graphics on computers with hybrid GPU configurations.

These symptoms are not exclusive to this particular bug check. The actual error code and crash dump should be examined to determine whether the problem is related to the graphics subsystem.

Possible Causes of Error 0x00000113

Microsoft's bug check documentation identifies the DirectX graphics kernel subsystem violation but does not establish one universal cause for every occurrence. The following are potential areas to investigate rather than confirmed causes.

1. Graphics Driver Problems

An outdated, corrupted, incompatible or unstable graphics driver may interfere with communication between Windows and the graphics hardware.

Graphics drivers are responsible for providing the operating system with the functionality required to operate the GPU. Problems introduced by an update, an incorrect driver package or a damaged installation may contribute to graphics-related system crashes.

This is particularly worth investigating when the error begins immediately after a graphics driver update or installation.

2. Incompatible Graphics Driver Updates

Not every graphics driver version works equally well with every computer configuration.

A driver intended for a particular GPU or operating system may not be appropriate for another hardware configuration. Laptop manufacturers may also provide customized graphics drivers for systems that use integrated and dedicated GPUs together.

If the problem started after installing a new driver, testing the previous stable version may help identify whether the update is involved.

3. Integrated and Dedicated GPU Conflicts

Some laptops and desktop computers contain more than one graphics processor.

For example, a system may use Intel integrated graphics alongside a dedicated NVIDIA or AMD graphics card.

These systems use hybrid graphics technology to switch between graphics processors depending on workload and power requirements.

Driver compatibility, graphics switching and power-management problems may be relevant when investigating crashes on these systems.

4. GPU Overclocking and Hardware Instability

Overclocking increases graphics processor operating frequencies beyond the manufacturer's standard settings. Although it can improve performance, unstable settings may affect system reliability.

Memory overclocking, undervolting or aggressive power settings may also contribute to instability.

If the computer has been modified using GPU tuning software, restore the graphics card to its default settings and check whether the crash continues.

5. Graphics Hardware Problems

A malfunctioning GPU, unstable power delivery, defective graphics memory or other hardware problems may contribute to graphics subsystem failures.

Possible warning signs include graphical artifacts, repeated crashes under graphics workloads, unexpected display loss and instability across multiple applications.

However, a 0x00000113 error alone does not confirm GPU hardware failure. Hardware diagnostics and crash dump analysis are necessary before considering component replacement.

6. Windows Updates and Software Compatibility

Windows updates can change system components and driver interactions. In some situations, an update may expose an existing graphics driver or hardware compatibility problem.

Recently installed applications, graphics utilities, screen-recording software and GPU monitoring tools may also be worth investigating if the crashes began after their installation.

7. Power Management and Sleep-Wake Problems

Graphics devices operate through different power states depending on whether the computer is active, idle, sleeping or waking up.

Problems involving graphics drivers, device power management or hybrid graphics configurations may become noticeable during these transitions.

Microsoft has documented a historical Windows 8.1 issue involving stop error 0x00000113 when waking certain computers from sleep. That issue involved systems with Intel HD Graphics and an additional AMD Radeon GPU. It should not be assumed to explain all occurrences of this error.

How to Fix VIDEO_DXGKRNL_FATAL_ERROR in Windows 11 and Windows 10

Follow the troubleshooting methods below in order. Start with non-disruptive checks before attempting advanced driver removal, firmware changes or hardware replacement.

1. Restart the Computer

A temporary graphics subsystem failure may not happen again after a restart.

1. Save any available work if Windows is still responding.
2. Restart the computer normally.
3. Allow Windows to complete startup.
4. Use the computer normally and observe whether the error returns.

If the error occurs only once, further troubleshooting may not be necessary. However, repeated crashes require additional investigation.

2. Install Windows Updates

Windows updates may include operating system fixes, compatibility improvements and hardware driver updates.

To check for available updates:

1. Press Windows + I to open Settings.
2. Navigate to Windows Update.
3. Select Check for updates.
4. Install applicable updates.
5. Restart the computer if required.

On Windows 10, the corresponding option is available under Settings > Update & Security > Windows Update.

After updating, check whether the graphics-related crash continues. If the error began immediately after a particular update, investigate that update as a possible contributing factor rather than assuming that installing more updates will always resolve the problem.

3. Update the Graphics Driver

An appropriate graphics driver is important for stable communication between Windows and the graphics processor.

First, identify the graphics hardware installed in the computer.

1. Right-click the Start button.
2. Select Device Manager.
3. Expand Display adapters.
4. Note the graphics device or devices listed.
5. Visit the official support website of the computer or graphics card manufacturer.
6. Download the appropriate graphics driver for the exact hardware and Windows version.
7. Install the driver according to the manufacturer's instructions.
8. Restart the computer.

Official graphics driver resources include:

• NVIDIA Driver Downloads
• AMD Drivers and Support
• Intel Download Center

For laptops, check the laptop manufacturer's support website first, especially when the system uses integrated and dedicated graphics together.

Important: Do not install a graphics driver simply because it has a higher version number. Confirm that it supports the installed GPU and operating system.

4. Roll Back the Graphics Driver

If the BSOD started after a graphics driver update, reverting to the previous driver version may help determine whether the new release is responsible.

1. Right-click Start and open Device Manager.
2. Expand Display adapters.
3. Right-click the affected graphics device.
4. Select Properties.
5. Open the Driver tab.
6. Select Roll Back Driver, if available.
7. Follow the on-screen instructions.
8. Restart the computer.

The Roll Back Driver option may be unavailable if Windows does not have a previous driver package available.

5. Reinstall the Graphics Driver

If updating or rolling back the driver does not resolve the issue, reinstalling the graphics driver may help correct an incomplete or damaged installation.

1. Download the appropriate replacement graphics driver before removing the existing installation.
2. Open Device Manager.
3. Expand Display adapters.
4. Right-click the affected graphics device.
5. Select Uninstall device.
6. Follow the available instructions and restart the computer.
7. Install the previously downloaded manufacturer-supported driver.
8. Restart Windows again if required.

Windows may temporarily use a basic display driver while the manufacturer driver is unavailable.

For complex driver corruption or persistent conflicts, a clean driver installation may be considered using the GPU manufacturer's supported procedure. Third-party driver removal utilities should be used cautiously and only when necessary.

6. Disable GPU Overclocking and Restore Default Settings

If GPU tuning software is installed, return the graphics processor to its standard operating settings.

1. Open the graphics tuning application, if installed.
2. Locate the GPU frequency, memory frequency, voltage and power settings.
3. Restore the manufacturer's default settings.
4. Disable custom overclocking profiles temporarily.
5. Restart the computer.
6. Test the system under the workload that previously caused the crash.

Do not increase GPU voltage or apply additional overclocking settings as a troubleshooting experiment.

7. Check for Graphics Device Errors in Device Manager

Device Manager can help identify graphics devices that Windows has detected as having problems.

1. Press Windows + X.
2. Select Device Manager.
3. Expand Display adapters.
4. Look for a yellow warning symbol beside a graphics device.
5. Right-click the device and select Properties.
6. Review the Device status information under the General tab.

If Windows displays a device error code, record it and investigate that specific code. It may provide additional information about the graphics device or driver problem.

8. Check GPU Temperature and Hardware Stability

Excessive temperature or unstable hardware operation can contribute to graphics-related problems.

Use a monitoring utility supplied or recommended by the hardware manufacturer to inspect GPU temperature and operating conditions.

Check the following:

• Whether GPU temperatures increase unusually under load.
• Whether cooling fans operate correctly.
• Whether air vents are blocked by dust or other obstructions.
• Whether the graphics card is properly seated, where applicable.
• Whether the graphics card receives the required power supply.
• Whether the system experiences graphical artifacts or display interruptions.

For desktop computers, hardware inspection should be performed with the system powered off and disconnected from its power source. If the user is unfamiliar with internal computer components, seek assistance from a qualified technician.

Do not open a laptop or dismantle a graphics card unnecessarily, particularly when the device is under warranty.

9. Check Windows System Files

Corrupted Windows system files may contribute to operating system instability. System File Checker (SFC) and Deployment Image Servicing and Management (DISM) are built-in Windows tools that can help identify and repair certain Windows component problems.

These tools do not specifically repair every DirectX graphics driver failure, but they can help determine whether Windows system component corruption is also present.

Requirements: An administrator account is required.

1. Right-click Start.
2. Select Terminal (Admin) or Windows PowerShell (Admin), depending on the Windows version.
3. Run the following command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for the operation to finish. Then run:

sfc /scannow

Allow the scan to complete without closing the terminal window.

Restart the computer if repairs were performed and check whether the issue continues.

10. Update BIOS and Firmware When Appropriate

BIOS and firmware updates may contain hardware compatibility, power-management and device stability improvements.

However, updating BIOS is not a guaranteed solution for VIDEO_DXGKRNL_FATAL_ERROR. Consider it only when the computer manufacturer documents a relevant improvement or when diagnostics indicate a firmware-related issue.

Before updating BIOS:

• Identify the exact computer or motherboard model.
• Download firmware only from the manufacturer's official website.
• Read the update instructions and prerequisites.
• Ensure that the computer has a reliable power supply.
• Do not interrupt the update process.
• Back up important data and record existing firmware settings where appropriate.

An interrupted or incorrect BIOS update can make a computer unusable. Do not install firmware intended for another model.

11. Use System Restore if the Problem Started Recently

If the BSOD began after installing a driver, application or Windows update, System Restore may help return Windows to an earlier working configuration.

1. Press Windows + R.
2. Type rstrui.exe and press Enter.
3. Select Next.
4. Choose a restore point created before the problem started.
5. Review the affected programs and drivers, if available.
6. Follow the instructions to begin the restoration.
7. Allow Windows to restart and complete the process.

System Restore is not a substitute for backing up important personal files. Review the restore point carefully before proceeding.

Advanced Troubleshooting for IT Professionals

If the error continues after basic troubleshooting, additional diagnostics may be required. IT professionals can use crash dump analysis, Windows debugging tools and system event records to investigate the underlying failure.

1. Locate Windows Crash Dump Files

Windows may create a memory dump when a bug check occurs. These files can contain information about the system state at the time of the crash.

Common dump locations include:

• C:\Windows\Minidump – Small memory dump files.
• C:\Windows\MEMORY.DMP – A kernel or complete memory dump, depending on the configured dump type.

The availability and size of dump files depend on Windows configuration, available storage and whether dump generation completed successfully.

To check memory dump settings:

1. Open Windows Search.
2. Search for View advanced system settings.
3. Open the Advanced tab.
4. Under Startup and Recovery, select Settings.
5. Review the Write debugging information option.
6. Check whether an appropriate memory dump type is configured.

Do not delete crash dump files before completing the investigation. They may contain valuable diagnostic information.

2. Analyze the Crash Dump Using WinDbg

Windows Debugger (WinDbg) is a Microsoft debugging tool that can be used to examine Windows crash dump files.

Download it from the Microsoft Windows Debugging documentation.

To perform an initial investigation:

1. Open WinDbg.
2. Select the option to open a dump file.
3. Choose the relevant file from the Windows crash dump location.
4. Allow the debugger to load the symbols and analyze the dump.
5. Enter the following command in the debugger command window:

!analyze -v

This command requests a detailed analysis of the crash.

Review the following information where available:

• Bug check code and its parameters.
• Failure bucket and crash classification.
• Faulting instruction and associated module.
• Driver names and stack information.
• Graphics-related diagnostic information.

Important: A module such as dxgkrnl.sys appearing in a crash stack does not automatically prove that the Microsoft graphics kernel file is corrupted or defective. It may be involved because the failure occurred while Windows was processing graphics operations.

Similarly, the presence of a third-party graphics driver in the crash stack is an investigative clue, not conclusive proof that the driver is responsible.

3. Examine Event Viewer Logs

Event Viewer can provide additional information about system crashes, device errors and driver-related events.

1. Press Windows + R.
2. Enter eventvwr.msc.
3. Expand Windows Logs.
4. Select System.
5. Review events recorded around the time of the crash.
6. Look for relevant BugCheck, display driver, hardware or unexpected shutdown events.

Record the event source, event ID, timestamp and complete error description.

Event Viewer entries should be interpreted in context. For example, an unexpected shutdown event may simply record the consequence of a BSOD rather than identify its original cause.

4. Investigate Driver and Hardware Changes

Compare the crash timeline with recent system changes.

Useful investigation points include:

• Recent graphics driver installations or updates.
• Windows cumulative or feature updates.
• New GPU monitoring or tuning utilities.
• Changes to BIOS or firmware settings.
• New graphics cards, monitors or display adapters.
• Changes in power supply or hardware configuration.
• Crashes that occur only under a specific graphics workload.

Correlating these changes with crash dump information can help narrow down the investigation.

5. Use Driver Verifier Only When Necessary

Driver Verifier is an advanced Windows diagnostic utility that can test driver behaviour and help identify certain driver-related problems.

It is not a routine repair tool and should not be enabled on every computer experiencing a graphics-related BSOD.

Driver Verifier can increase system instability, cause additional crashes and prevent Windows from starting normally if a problematic driver is detected.

Only experienced administrators should consider using it, with appropriate backups and a recovery plan. Verification should be targeted at suspected third-party drivers rather than indiscriminately applied to all drivers.

Microsoft provides additional guidance in its Driver Verifier documentation.

Special Considerations for NVIDIA, AMD and Intel Graphics

The troubleshooting approach may differ depending on the installed graphics hardware.

NVIDIA Graphics Cards

• Check whether the installed NVIDIA driver supports the exact GPU.
• Investigate whether the issue started after a driver update.
• Restore default GPU tuning settings.
• Check GPU temperatures and power connections.
• Review crash dump information for NVIDIA driver references such as nvlddmkm.sys.

AMD Radeon Graphics

• Install the graphics driver intended for the specific Radeon hardware.
• Check whether integrated and dedicated graphics drivers are compatible.
• Investigate recent changes to AMD graphics software.
• Restore default tuning and power settings.
• Check for hardware instability under graphics workloads.

Intel Integrated Graphics

• Identify the exact Intel graphics processor.
• Check the driver version and supported Windows release.
• For laptops, verify whether the computer manufacturer provides a customized graphics driver.
• Investigate graphics switching and sleep-wake behaviour.
• Review crash dump references to Intel graphics driver modules.

For computers with multiple graphics processors, investigate the complete graphics driver configuration instead of updating or removing only one driver without considering the other device.

What Is the Difference Between VIDEO_DXGKRNL_FATAL_ERROR and Other Graphics BSOD Errors?

Several Windows stop codes relate to graphics processing, but they represent different bug check conditions.

Stop Code	Error Name	General Meaning
0x00000113	VIDEO_DXGKRNL_FATAL_ERROR	The DirectX graphics kernel subsystem detected a violation.
0x00000116	VIDEO_TDR_FAILURE	Windows detected a graphics timeout and failed to recover the display driver successfully.
0x00000117	VIDEO_TDR_TIMEOUT_DETECTED	A graphics timeout was detected.
0x00000119	VIDEO_SCHEDULER_INTERNAL_ERROR	The video scheduler detected a fatal violation.

These errors can involve overlapping graphics-related symptoms, but they should not be treated as interchangeable. Each stop code requires investigation based on its specific bug check information.

For additional details, refer to Microsoft's Windows Bug Check Code Reference.

How to Prevent VIDEO_DXGKRNL_FATAL_ERROR

Although not every graphics-related system crash can be prevented, the following practices can help maintain system stability.

• Install graphics drivers from the GPU or computer manufacturer's official website.
• Use drivers compatible with the installed Windows version and hardware.
• Avoid unnecessary driver modifications and unofficial driver packages.
• Restore default GPU settings if overclocking causes instability.
• Keep Windows and supported hardware firmware appropriately updated.
• Maintain proper computer ventilation and cooling.
• Use a suitable power supply for desktop graphics hardware.
• Monitor repeated display driver failures and investigate them early.
• Maintain regular backups of important data.
• Keep crash dump files when investigating recurring BSOD errors.

Frequently Asked Questions (FAQs)

1. What does VIDEO_DXGKRNL_FATAL_ERROR 0x00000113 mean?

It means that the Microsoft DirectX graphics kernel subsystem has detected a violation serious enough to trigger a Windows bug check. The exact underlying cause must be determined through driver, hardware and crash dump investigation.

2. Is VIDEO_DXGKRNL_FATAL_ERROR caused by a faulty graphics card?

Not necessarily. The error is related to the graphics subsystem, but it does not confirm physical GPU failure. Graphics drivers, software compatibility, hardware instability and other system-related conditions may need investigation.

3. Can updating the graphics driver fix error 0x00000113?

Yes, an appropriate graphics driver update may resolve the issue when an outdated or incompatible driver is involved. If the problem started after a recent update, rolling back to a previously stable version may be more appropriate.

4. What is dxgkrnl.sys?

dxgkrnl.sys is a Windows system component associated with the DirectX graphics kernel. It participates in graphics-related operations between Windows and display drivers. Its appearance in a crash dump does not automatically mean that the file itself is damaged.

5. Can VIDEO_DXGKRNL_FATAL_ERROR occur during gaming?

Yes. Graphics-intensive applications can expose existing driver, hardware or graphics subsystem stability problems. However, a crash during gaming does not automatically mean that the GPU is defective.

6. Can overheating cause a graphics-related BSOD?

Excessive temperature may contribute to hardware instability, depending on the computer and graphics hardware. Check cooling performance, temperature readings and hardware behaviour before concluding that overheating is responsible for the error.

7. Does reinstalling Windows fix VIDEO_DXGKRNL_FATAL_ERROR?

A clean Windows installation may resolve certain software or system configuration problems, but it is not a guaranteed solution. If the underlying problem involves defective hardware or an incompatible graphics driver, the error may return after reinstalling Windows.

8. What should I do if the error occurs repeatedly?

Check the graphics driver version, recent Windows and hardware changes, Device Manager status and system event logs. If the problem continues, collect the memory dump files and analyze them using WinDbg. Consider professional hardware diagnostics if software troubleshooting does not identify the cause.

When Should You Contact Technical Support?

Contact the computer manufacturer, graphics card manufacturer or a qualified IT technician when:

• The computer repeatedly crashes despite installing an appropriate graphics driver.
• Windows cannot start normally because of repeated graphics-related BSOD errors.
• Display artifacts, unexpected shutdowns or hardware instability are present.
• Crash dump analysis suggests a possible hardware or firmware problem.
• The system is under warranty and requires internal hardware inspection.
• The computer is used for business-critical workloads and repeated crashes are affecting operations.

Provide the technician with the exact stop code, Windows version, graphics hardware model, driver version, crash frequency and relevant dump files. This information can help reduce unnecessary troubleshooting and component replacement.

Official References and Further Reading

1. Microsoft Learn – Bug Check 0x113: VIDEO_DXGKRNL_FATAL_ERROR
2. Microsoft Support – Troubleshooting Windows Unexpected Restarts and Stop Code Errors
3. Microsoft Learn – Windows Debugging Documentation
4. Microsoft Learn – Driver Verifier
5. Microsoft Support – Historical Windows 8.1 Stop Error 0x00000113 Issue
6. Microsoft Learn – Windows Bug Check Code Reference

Conclusion

VIDEO_DXGKRNL_FATAL_ERROR (0x00000113) indicates a fatal violation detected by the Windows DirectX graphics kernel subsystem. Although graphics driver problems are an important area to investigate, the stop code does not identify a single confirmed cause.

Start by checking recent driver and Windows changes, installing the correct manufacturer-supported graphics driver, restoring default GPU settings and examining hardware stability. If the problem continues, use Windows crash dump files and debugging tools to identify more specific evidence.

Accurate diagnosis is important because replacing a graphics card or reinstalling Windows without identifying the underlying problem may not resolve the issue.