0x00000114 VIDEO_SHADOW_DRIVER_FATAL_ERROR – Causes and Troubleshooting Guide
Quick Answer VIDEO_SHADOW_DRIVER_FATAL_ERROR (0x00000114) is a Windows Blue Screen of Death (BSOD) error indicating that the Windows shadow driver has detect...
Quick Answer
VIDEO_SHADOW_DRIVER_FATAL_ERROR (0x00000114) is a Windows Blue Screen of Death (BSOD) error indicating that the Windows shadow driver has detected a violation that prevents normal system operation.
Microsoft identifies this bug check as 0x00000114 and describes it as a very infrequent error. Its official documentation is primarily intended for Windows driver developers and does not provide a universal consumer-level fix or a definitive list of causes.
When this error occurs, troubleshooting should focus on identifying the driver or system component involved in the crash. Reviewing recent driver changes, checking graphics-related software, examining Windows crash dumps and performing hardware diagnostics can help narrow down the problem.
What Is VIDEO_SHADOW_DRIVER_FATAL_ERROR (0x00000114)?
VIDEO_SHADOW_DRIVER_FATAL_ERROR is a Windows bug check, commonly known as a Blue Screen of Death or BSOD. Windows displays this error when its shadow driver detects a violation that it cannot safely handle.
A bug check is a protective mechanism used by Windows when a critical kernel-mode condition prevents the operating system from continuing safely. The system stops and may automatically restart to prevent further instability.
Microsoft documents this error under the Windows driver bug check reference. According to its documentation, this particular error occurs very infrequently.
Important Error Information
| Parameter | Description |
|---|---|
| Error Name | VIDEO_SHADOW_DRIVER_FATAL_ERROR |
| Bug Check Code | 0x00000114 |
| Hexadecimal Code | 0x114 |
| Error Type | Windows Stop Error (BSOD) |
| Category | Windows Driver / Graphics Subsystem |
| Official Description | The shadow driver has detected a violation. |
| Frequency | Very infrequent, according to Microsoft |
What Does the Shadow Driver Mean?
The term shadow driver appears in Microsoft's Windows driver documentation in connection with this bug check. The official description confirms that the driver has detected a violation.
However, Microsoft's public documentation does not provide a detailed consumer-level explanation of the internal condition that triggers this particular bug check. It is therefore important not to assume that every occurrence represents a defective graphics card or a conventional display driver failure.
Because the error belongs to the video-related bug check family, examining the graphics and display environment is a reasonable troubleshooting starting point. The actual component responsible should be established through crash analysis wherever possible.
Symptoms of Error 0x00000114
A computer experiencing VIDEO_SHADOW_DRIVER_FATAL_ERROR may exhibit one or more of the following symptoms:
- A sudden Blue Screen of Death appears with the stop code
0x00000114. - Windows unexpectedly restarts after displaying the error.
- The system becomes unavailable while a critical driver-related failure is being handled.
- A crash dump file may be generated for further investigation.
- The error may appear again if the underlying condition remains unresolved.
- Display-related instability may occur around the same time, although it is not a confirmed symptom of every 0x114 crash.
These symptoms are not exclusive to this error. The exact behavior depends on the circumstances surrounding the system failure.
Possible Causes of VIDEO_SHADOW_DRIVER_FATAL_ERROR
Microsoft's official documentation does not publish a definitive list of root causes for bug check 0x114. Therefore, the following items should be treated as areas to investigate rather than confirmed causes of this specific error.
1. Graphics or Display Driver Problems
Graphics drivers provide communication between Windows and the computer's graphics hardware. Driver defects, incompatible versions or unexpected interactions between graphics components can contribute to system instability.
If the BSOD started after installing or updating a display driver, investigate that change first.
2. Recently Installed Hardware or Drivers
New hardware may introduce additional drivers and services into Windows. Compatibility problems or conflicts between newly installed components and existing drivers can cause system instability.
Pay particular attention to recently installed display adapters, graphics-related devices and associated software.
3. Graphics Software or Display Configuration Changes
Changes to graphics utilities, display management software, remote display components or other software interacting with the display environment may be relevant during an investigation.
Record any software installations or configuration changes made shortly before the crash.
4. Windows System or Driver Component Corruption
Damaged Windows system files or incorrectly installed driver components can cause unexpected operating system behavior.
System file integrity checks may help identify certain types of Windows component corruption, although they do not directly diagnose the shadow driver violation.
5. Hardware Instability
Hardware problems can contribute to Windows crashes, particularly when they affect the graphics subsystem or system stability.
Potential areas to investigate include:
- Graphics card or integrated graphics hardware.
- System memory (RAM).
- Motherboard and related hardware connections.
- Power delivery and system cooling.
- Hardware instability caused by overclocking or unsupported configuration changes.
These are general diagnostic possibilities, not documented causes specific to bug check 0x114.
How to Troubleshoot VIDEO_SHADOW_DRIVER_FATAL_ERROR (0x00000114)
Follow the troubleshooting procedures below in order. Start with non-disruptive checks before attempting advanced driver changes or system recovery operations.
Step 1: Restart the Computer
If the error occurred only once, restart Windows and check whether the computer operates normally.
- Allow Windows to complete the restart process.
- Sign in normally.
- Observe whether the BSOD appears again.
- Record the applications or activities that were running when the crash occurred.
A single successful restart does not establish that the underlying issue has been resolved. Monitor the system for repeated failures.
Step 2: Disconnect Recently Added Hardware
If the problem started after connecting new hardware, investigate that device before changing other system components.
- Shut down the computer completely.
- Disconnect recently added non-essential external devices.
- If applicable, have a qualified technician check recently installed internal hardware.
- Start Windows again.
- Check whether the error returns.
Do not disconnect internal components while the computer is powered on. Avoid removing essential devices required for normal system operation.
Step 3: Check Display Adapters in Device Manager
Device Manager can help identify display devices that have reported driver or device problems.
- Press
Windows + X. - Select Device Manager.
- Expand Display adapters.
- Check whether any device displays a warning symbol.
- Right-click the relevant display adapter and select Properties.
- Review the Device status information.
- Record any displayed error code or message.
If Windows reports a device problem, investigate the manufacturer's recommended driver and compatibility information.
Step 4: Update the Graphics Driver
If the graphics driver is outdated or a known compatibility issue has been identified, installing an appropriate driver may help.
- Identify the graphics hardware manufacturer and model.
- Visit the official support website of the computer or graphics hardware manufacturer.
- Locate the driver intended for the installed Windows version and hardware model.
- Review the release information and compatibility requirements.
- Download the appropriate driver.
- Follow the manufacturer's installation instructions.
- Restart the computer if required.
For laptops and branded desktop computers, the system manufacturer's validated graphics driver may be preferable to a generic driver package.
Important: Do not install random third-party driver packages. Avoid replacing a working driver with an incompatible version merely because it is newer.
Step 5: Roll Back a Recently Updated Graphics Driver
If the BSOD began immediately after a graphics driver update, restoring the previous driver version may help determine whether the update introduced the problem.
- Open Device Manager.
- Expand Display adapters.
- Right-click the relevant graphics device.
- Select Properties.
- Open the Driver tab.
- Select Roll Back Driver, if available.
- Follow the instructions and restart Windows.
Administrator permissions may be required. The rollback option may be unavailable if Windows does not retain the previous driver package.
If the issue started after a Windows Update or driver installation, record the update details before attempting further changes.
Step 6: Start Windows in Safe Mode
Safe Mode starts Windows with a limited set of drivers and services. It can help determine whether a problem is associated with additional drivers or software loaded during normal startup.
To access Safe Mode:
- Open Settings.
- Navigate to System > Recovery in Windows 11.
- Under Advanced startup, select Restart now.
- After Windows Recovery Environment loads, select Troubleshoot.
- Select Advanced options > Startup Settings.
- Select Restart.
- Press
4orF4to enable Safe Mode.
In Windows 10, the equivalent recovery option is available under Settings > Update & Security > Recovery.
If Windows does not start normally, Windows Recovery Environment may also be accessible through the manufacturer's recovery options or automatic recovery process.
How to interpret the result: If the problem does not occur in Safe Mode, additional drivers, services or software loaded during normal startup become useful areas to investigate. This result does not independently identify the faulty component.
Note: If BitLocker device encryption is enabled, Windows may request the recovery key when accessing certain recovery operations.
Step 7: Install Available Windows Updates
Windows updates may include operating system fixes, driver compatibility improvements and security updates.
- Open Settings.
- Select Windows Update.
- Click Check for updates.
- Review the available updates.
- Install appropriate updates from Microsoft.
- Restart the computer when required.
Optional driver updates should be evaluated for compatibility with the actual hardware. Do not install unrelated drivers simply because they appear in the optional updates list.
Step 8: Check Windows System File Integrity
If there is evidence of Windows system file corruption, use the System File Checker (SFC) utility to examine and repair protected system files.
Open Command Prompt or Windows Terminal as an administrator and execute:
sfc /scannow
Allow the scan to complete. Windows will report whether integrity violations were found and whether repairs were successful.
If SFC reports that some files could not be repaired, the Deployment Image Servicing and Management (DISM) utility can be used to service the Windows component store.
Run the following commands from an elevated Command Prompt:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
After DISM completes, run SFC again:
sfc /scannow
Important: These utilities address certain Windows image and protected system file problems. They are not specific repair tools for VIDEO_SHADOW_DRIVER_FATAL_ERROR and may not resolve a driver or hardware problem.
Step 9: Check for Hardware Instability
If the error continues after software and driver checks, investigate the computer's hardware.
Recommended diagnostic checks include:
- Run the memory diagnostic utility provided with Windows.
- Use the computer manufacturer's hardware diagnostic utility.
- Check graphics card temperature and cooling conditions using appropriate manufacturer tools.
- Check whether the system is running unsupported CPU, GPU or memory overclocking settings.
- Inspect graphics card power connections and other internal connections through a qualified technician.
To run Windows Memory Diagnostic:
- Press
Windows + R. - Type
mdsched.exe. - Press Enter.
- Select Restart now and check for problems if you are ready to restart.
- Allow the memory test to complete.
- Review the diagnostic results after Windows starts.
Save your work before starting the memory test because the computer will restart.
Advanced Troubleshooting: Analyze the Crash Dump
When the error occurs repeatedly, analyzing the Windows crash dump can provide more useful information than applying generic driver fixes.
A crash dump records information about the system state when Windows encountered a critical failure. The available information depends on the configured dump type and the nature of the crash.
1. Locate the Crash Dump File
Windows may store crash dump files in the following locations:
C:\Windows\Minidump- Small memory dump files.C:\Windows\MEMORY.DMP- A kernel or complete memory dump, depending on the configured dump type.
Not every system generates both types of dump files. Their availability depends on Windows configuration, available storage and the circumstances of the crash.
2. Check the Dump Configuration
To review the configured memory dump settings:
- Press
Windows + R. - Type
sysdm.cpland press Enter. - Open the Advanced tab.
- Under Startup and Recovery, select Settings.
- Review the Write debugging information option.
- Check the configured dump type and dump file location.
Ensure that the system drive has sufficient free space and that the required page file configuration is available for the selected dump type.
3. Analyze the Dump Using WinDbg
WinDbg is Microsoft's debugging tool for analyzing Windows crashes, driver failures and kernel-mode problems.
To investigate a dump file:
- Install WinDbg from Microsoft's official documentation or supported distribution channel.
- Open WinDbg.
- Select the option to open a dump file.
- Locate and open the relevant
.dmpfile. - Allow the debugger to load the required symbols.
- Run the following command in the debugger command window:
!analyze -v
This command requests a detailed analysis of the current crash dump.
4. Examine the Debugging Results
Review the following information where available:
- BUGCHECK_CODE: Identifies the Windows bug check code.
- BUGCHECK_P1 to BUGCHECK_P4: Displays the bug check parameters when available.
- MODULE_NAME: Identifies a module associated with the analysis.
- IMAGE_NAME: Displays an associated image or driver filename.
- STACK_TEXT: Provides the recorded call stack information.
- Probably caused by: Provides a debugger-generated indication of a possible responsible component.
These fields are investigative clues. A module appearing in the crash analysis is not automatically proof that the module itself is defective. Additional investigation may be necessary to establish the actual cause.
For bug check 0x114, do not assume that Microsoft has published detailed interpretations for all four parameters. Use the actual dump data and debugger output rather than assigning undocumented meanings to individual values.
5. Review Event Viewer Logs
Event Viewer can provide additional information about system failures and events immediately before or after the crash.
- Press
Windows + R. - Type
eventvwr.msc. - Navigate to Windows Logs > System.
- Look for critical or error events around the time of the BSOD.
- Review the event details and associated timestamps.
Check for relevant BugCheck, display driver, hardware or unexpected shutdown events. An unexpected shutdown event by itself does not identify the original cause of the BSOD.
When Should You Contact Technical Support?
Professional technical assistance may be appropriate when:
- The BSOD occurs repeatedly despite basic troubleshooting.
- The computer cannot start Windows normally.
- Crash dump analysis identifies a potentially faulty third-party driver that requires specialist investigation.
- Hardware diagnostics report errors.
- The computer is part of a business-critical environment.
- The error occurs on multiple computers with the same hardware or driver configuration.
When contacting the computer manufacturer or technical support team, provide the following information:
- Exact stop code:
VIDEO_SHADOW_DRIVER_FATAL_ERROR (0x00000114). - Windows edition, version and build number.
- Computer manufacturer and model.
- Graphics adapter model and driver version.
- Recent driver, software or hardware changes.
- Relevant Event Viewer logs.
- Available crash dump files and WinDbg analysis output.
Crash dump files may contain sensitive information from system memory. Share them only through trusted support channels and follow your organization's data-handling policies.
How to Prevent Repeated Windows Graphics-Related Crashes
Although there is no documented prevention method specifically for bug check 0x114, the following practices can help maintain system stability:
- Use compatible graphics drivers from the computer or hardware manufacturer's official website.
- Review driver release notes before installing major updates.
- Avoid installing unnecessary driver utilities and unofficial driver packages.
- Keep Windows updated with appropriate security and reliability updates.
- Maintain adequate cooling and ventilation.
- Avoid unsupported CPU, GPU and memory overclocking configurations.
- Investigate repeated hardware warnings instead of ignoring them.
- Maintain regular backups of important data.
- Record the details of recurring crashes to help identify patterns.
Frequently Asked Questions (FAQs)
1. What does VIDEO_SHADOW_DRIVER_FATAL_ERROR mean?
It is a Windows stop error with bug check code 0x00000114. Microsoft describes it as a condition in which the shadow driver has detected a violation.
2. Is error 0x00000114 related to the graphics driver?
It belongs to the video-related Windows bug check family, making the graphics and display environment relevant areas to investigate. However, the official description does not establish that every occurrence is caused by a conventional graphics driver problem.
3. Can an outdated graphics driver cause this BSOD?
Driver problems are a reasonable troubleshooting consideration when investigating video-related system crashes. However, an outdated graphics driver has not been established by Microsoft's 0x114 documentation as a definitive cause of this particular bug check.
4. Does VIDEO_SHADOW_DRIVER_FATAL_ERROR mean the graphics card is damaged?
No. The error does not independently prove that the graphics card is physically damaged. Driver, software, system and hardware investigations may be necessary before reaching that conclusion.
5. Can Safe Mode help troubleshoot error 0x00000114?
Yes. Safe Mode loads a limited set of drivers and services. Comparing system behavior in Safe Mode and normal startup can help narrow down whether additional drivers or software are involved.
6. Where are Windows BSOD crash dump files stored?
Small memory dumps are commonly stored in C:\Windows\Minidump. A configured kernel or complete memory dump may be stored at C:\Windows\MEMORY.DMP.
7. Which tool can analyze error 0x00000114?
Microsoft WinDbg can analyze Windows crash dump files. The !analyze -v command provides detailed debugging information that can help technicians investigate the failure.
8. Is VIDEO_SHADOW_DRIVER_FATAL_ERROR a common Windows BSOD?
No. Microsoft explicitly describes bug check 0x114 as a very infrequent error.
9. Should I reinstall Windows to fix error 0x00000114?
Reinstalling Windows should not be the first troubleshooting step. Investigate recent driver changes, system logs, crash dumps and hardware diagnostics first. Reinstallation may be considered only after appropriate diagnosis and data backup.
10. Does Microsoft provide a universal fix for bug check 0x114?
No universal consumer-level fix is documented on Microsoft's official bug check 0x114 reference page. The appropriate corrective action depends on the actual condition identified during investigation.
Official References and Further Reading
The following Microsoft resources provide authoritative information for understanding the error, investigating Windows stop codes and performing the recommended diagnostic procedures.
- Microsoft Learn: Bug Check 0x114 - VIDEO_SHADOW_DRIVER_FATAL_ERROR
- Microsoft Support: Troubleshooting Windows Unexpected Restarts and Stop Code Errors
- Microsoft Support: Windows Startup Settings and Safe Mode
- Microsoft Learn: Stop Code Error or Bug Check Troubleshooting
- Microsoft Learn: !analyze WinDbg Command
- Microsoft Learn: Analyzing a Kernel-Mode Dump File with WinDbg
- Microsoft Support: Update and Roll Back Drivers Through Device Manager
Key Takeaways
VIDEO_SHADOW_DRIVER_FATAL_ERROR (0x00000114) is a rare Windows bug check indicating that the shadow driver has detected a violation.
Because Microsoft's official documentation does not establish a universal cause or repair method, technicians should avoid assuming that the graphics card or display driver is necessarily defective.
The recommended approach is to investigate recent system changes, examine display-related devices and drivers, use Safe Mode where appropriate, check Windows integrity when indicated, and analyze available crash dumps with WinDbg.
Accurate diagnosis is essential before performing major driver replacements, hardware changes or Windows recovery operations.
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.