Fix Call of Duty 4 crashes in Windows 10

As you know, USB is now being widely used in all devices with USB A as the leading type with most devices based on it. Peripheral devices such as Pen Drives, External Hard disks, and many more also use a USB port. On the other hand, USB C is also coming up to be the next big standard in the computing world because of its high transfer speeds, wider compatibility as well as support for external Graphics Processing Units. However, just recently, USB 3.0 ports have been reported to cause the following error to pop up on Windows 10 computers every time a USB device is plugged in.

“Not enough USB controller resources. The controller does not have enough resources for this device.”

To fix this error, here are some guidelines you can check out. Make sure to follow them carefully.

Option 1 – Try to use a lower generation USB port

The first thing you can do is to try using a lower generation USB port as this issue mostly occurs when a device is connected to a USB 3,0 port. This means that you have to plug in your device to a USB 2.0 port and then see if it fixes the error or not. You can easily decipher a USB 3.0 port from a USB 2.0 port as the former is in blue.

Option 2 – Try to use a dock

You could also try to use a dock to resolve the error. Note that when too much power on laptops and notebooks are drawn from the USB ports and as a USB 3.0 port draws more power compared to a USB 2.0 port. Thus, if you plug in your USB storage device into a USB 2.0 port with the help of a dock, it should fix the problem.

Option 3 – Try disabling the xHCI Mode option in the BIOS

• First, boot your computer into the BIOS.
• Once your computer has booted, go to the Advanced tab.
• Next, make sure that the entry for “xHCI Pre-boot mode” is set to Disabled under the USB Configuration section.
• Now save the changes you’ve made and then restart your computer to Windows 10 and see if the error is now fixed.

Option 4 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right click on each one of the USB drivers, especially the Generic USB Hub driver, and then select the Update Driver from the menu.
• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 5 – Run the Hardware and Devices Troubleshooter

You could also run the Hardware and device Troubleshooter to try and fix the “Not enough USB controller resources” error.

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

Windows has a lot of built-in tools that help you fix tons of system-related issues. One of them is the System File Check which is the tool you can use to conveniently replace potentially corrupted or missing system files with good ones. But what happens when it does not work? Well, you’ve come to the right place as in this post, you will be guided on how you can replace a corrupted single Windows system file manually with a known good copy of the file if the System File Checker scan is not working. When you encounter this issue with the System File Checker, it will be unable to replace the corrupted system files and returns an error message instead. And so to fix and replace corrupted system files in your Windows 10 computer without the help of System File Checker, you can refer to the instructions provided below. Step 1: First, you need to open the log files listed below and identify which particular file has been corrupted:

• %userprofile%Desktopsfcdetails.txt
• Log %WinDir%LogsCBSCBS.log

Step 2: You will see all the details on the given log files. Once you find out the name and the path of the file, you have to take ownership of this corrupted system file. Step 3: To take ownership of the corrupted file, you need to pull up Command Prompt by tapping Win + R keys on your keyboard and then type “cmd” and tap Enter. Step 4: After opening Command Prompt, type and enter the command below to execute it:

takeown /f FileNameAndPath

Note: In the given command, “FileNameAndPath” represents the name and the path of the corrupted file. For instance, the corrupted file is named “wuapi.dll”, then you need to type “takeown /f C:/Windows/System32/wuapi.dll” Step 5: Next, you need to grant administrators full access & control to the corrupted file and you can do that via Command Prompt again. Step 6: In the elevated Command Prompt, type and enter the following command to execute it:

icacls FileNameAndPath /GRANT ADMINISTRATORS:F

Note: We’re going to use the wuapi.dll again as an example. So the command should be like this: icacls “C:/Windows/System32/wuapi.dll /grant administrators: F”. Step 7: Now all that’s left to do is replace the corrupted system file with a good copy from a trusted source. Once you have a copy, open an elevated Command Prompt again and execute the following command:

copy NewFileLocation FileNameAndPath

Note: In the command given above, the “NewFileLocation” is the location where you have saved the copy of the file. For instance, if you’ve saved it on your desktop, this is how it should look: “copy C:/Users/<username>/Desktop/wuapi.dll C:/windows/system32/wuapi.dll”

Error Code 52 – What is it?

Error Code 52 is a device driver problem that users experience on any Windows 2000 operating system and later Windows systems.

The error occurs when the operating system prevents the peripheral device connected to the computer from functioning properly and is usually displayed by the following message:

“Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)”

Solution

Error Causes

Error Code 52 is triggered by the following factors:

• An incomplete program uninstallation
• An incomplete program installation
• Hardware is not removed properly
• System recovery from viruses
• An improper system shut down

Further Information and Manual Repair

Error Code 52 can pose severe risks to the overall health of your PC and any negligence in fixing it can be disastrous for your computer.

However, since the error code is like other device driver errors, resolving the error is relatively straightforward. Here are a few methods to resolve the error code.

Method 1 – Use System Restore

You can use system restore to roll back the system to a time when there was no error to eliminate the problem. Here is how you can use it:

1. Log in using an Administrator account
2. Click ‘Start’ button and select All Programs > Accessories > System Tools > System Restore
3. Click ‘Restore my computer to an earlier time’ and click ‘Next’
4. Select the last Windows restore point from the ‘On this list, click a restore point’ list, and click ‘Next’
5. Click ‘Next’ on the confirmation window to proceed
6. Restart your PC after restoration is complete

By restoring the system via a last saved system checkpoint, you can obtain undamaged Windows system registry files that can help avert the error code.

Method 2 – Run the Troubleshooting Wizard

If restarting your PC does not help, you will have to find the exact nature of the problem by running the troubleshooting wizard for the device and address the problem accordingly. To do this, proceed with the following steps:

1. Run Device Manager on your PC
2. Click on the program under the installed programs that are creating problems for you
3. Click on the ‘General’ Tab
4. Click ‘Troubleshoot’
5. Upon opening, the Troubleshooting Wizard will ask a series of questions regarding the error. Answer the questions and follow its directions for solving the error code.

After following the directions of the Troubleshooting wizard, make sure to restart your PC for the changes to take effect. Then check if your device is still causing problems.

Method 3 – Manually uninstall and reinstall the device driver

Uninstalling and then reinstalling the device driver can help solve the error.

You can do this by firstly logging in as Administrator and open Device Manager. Select the device that is causing the problem and double click it and make sure that the peripheral is connected properly to the PC.

Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 4 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will do the trick, however, it may be time-consuming especially when you would have to resort to your hardware user manual.

Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer.

DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically.

It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 52.

It also has the added advantage of being able to backup and restores your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly.

Click here to download DriverFIX to fix Error Code 52 quickly and effectively!

What is Error Code 29?

Code 29 is a Device Manager error commonly seen whenever a hardware device driver reports a problem. This error code indicates that the resources needed for operation are not available.

The computer hardware basically requires drivers to interface with the operating system. Drivers comprise multiple components and are supplemented with other resources provided by the BIOS (a physical chip on the motherboard).

The BIOS contains a set of basic input and output instructions for the computer system to boot, load drivers, and more.

Its firmware provides resources that drivers require to interface with other essential components. However, when the firmware fails to provide the requested resources, the device drivers stop functioning; this results in error codes like code 29.

Error code 29 is usually displayed in the following format:

“This device is disabled because the firmware of the device did not give it the required resources” Code 29

Solution

Error Causes

Error code 29 may be triggered due to several reasons. These include:

• Outdated drivers
• Corrupted drivers
• BIOS misconfiguration
• The device firmware is corrupt
• Previous attempt to update the driver failed

To avoid inconvenience and to ensure your computer keeps working at its optimal pace, it is recommended that you repair error code 29 on your PC immediately. Delay may limit you from using certain hardware attached to your system properly.

Further Information and Manual Repair

To repair error code 29, you don’t have to hire a professional and spend hundreds of dollars. Here are some quick and effective DIY methods that you can try to resolve this issue in minutes even if you don’t have any technical background.

Method 1 - Reboot Your PC

Sometimes, error codes like code 29 may pop up on your computer screen due to some temporary glitch with the hardware. Rebooting can resolve the issue easily.

Therefore, before you do anything, try restarting your PC. It could be all you need to repair code 29. However, if the error code continues to persist, try the other methods given below.

Method 2 - Clear the CMOS

This may sound technical but it isn’t. To begin, with CMOS is an acronym for Complimentary Metal Oxide Semiconductor.

It is a term that is used to describe motherboard memory that contains the BIOS settings. Clearing CMOS helps reset the BIOS settings to their default manufacturer levels. It’s easy to do and is an effective troubleshooting step to resolve error code 29.

To do this, simply:

1. Enter the BIOS setup utility  by restarting your PC
2. Watch for an entering setup message
3. Enter the BIOS access key. Usually, the key is F2 or F12. However, the key may differ from manufacturer to manufacturer. You may want to check the manufacturer’s website first to find out the BIOS access key before you restart your PC.
4. ‘Reset BIOS settings’ to their default factory levels.

Method 3 - Enable the Device in the BIOS

Error code 29 may appear if a device is disabled. In such a scenario, simply follow the same steps as discussed in method 2, and in the advanced BIOS settings, look for disabled devices.

Enable the devices in the BIOS so that you use them easily.

This will hopefully resolve the issue. If it doesn’t, then this means the error code 29 is caused by either corrupted or outdated drivers. Try method 4 to resolve this issue successfully.

Method 4 - Identify the Problematic Device Drivers and Update them

Whether the error code 29 is caused by a misconfigured, corrupted, or outdated driver, simply update the new driver version to resolve. When doing it manually, you will first have to find and identify the problematic device drivers in the Device Manager.

You can access the Device Manager by going to the start menu and then simply typing Device Manager in the search bar.

Access the Device Manager and the properties to identify problematic drivers. Problematic drivers are normally displayed with a yellow exclamation mark.

Once you have spotted problematic drivers, simply update new drivers to resolve them. Though there is nothing technical about it but it may be time-consuming.

Method 5 - Install Driver Assist to Update Drivers Automatically and Regularly

A good alternative to manual driver update is DriverFIX. Simply download and install DriverFIX on your PC to update all problematic drivers in seconds. This is a cutting-edge program designed to resolve all kinds of device driver problems.

It is user-friendly and compatible with all Windows versions.

The intelligent programming system deployed inside this software program enables it to identify and detect all problem drivers automatically thereby sparing you from the hassle.

Furthermore, it also matches the drivers with the latest and compatible versions and updates them on a regular basis.

It takes the guesswork out of finding misconfigured and corrupted drivers and fixes driver-related problems and error codes like code 29 right away.

Click here to download DriverFIX to repair Device Manager error code 29 on your system without any hassle.

If your Windows PC encounters an error, it will display a Blue Screen of Death or BSOD error which usually comes up for a fraction of second and creates some logs or Dumps Files as what other user prefers to call it and then boots your PC suddenly. This process usually takes place quickly that most users find it hard to get the error code and won’t probably be able to check what really went wrong with their PCs. This is where the dump files come in. They are stored internally in your computer and can only be accessed by an administrator. They are classified into 4 main types and in Windows 10 they are either:

1. Complete Memory Dump
2. Kernel Memory Dump
3. Small Memory Dump (256 KB)
4. Active Memory Dumps

Dump Files are useful as they could help you in resolving the problem and so you need to configure your Windows 10 PC to create them but first, you need to make a system restore point. This is essential as you are about to modify some system files as well as critical Windows 10 settings. There are two ways you can create Dump files – first is by modifying the settings in the Startup and Recovery and lastly is via the WMIC command line. Refer to the instructions prepared below to be guided on how you can create Dump files after any BSOD error using these options.

Option 1 – via Startup and Recovery

• Type in “control panel” in the Cortana Search box and then click on Control Panel from the search results to open it.
• After opening Control Panel, you need to make sure that you view the contents by their Category then click on the header link which is labeled “System and Security” or you could also right-click on the This PC icon and then click on Properties.
• Next, select the Advanced system settings from the left panel. Once you do, a new and small window will pop up.
• Under the newly opened window, look for the section called Startup and Recovery and then click on the Settings button.
• And from the System Failure section, you can choose any option from the drop-down for Write debugging information such as:
  • None – this means that there is no dump file created by Windows
  • Small Memory Dump – this means that Windows will create a Minidump file on BSOD
  • Complete Memory Dump – this means that Windows will create a Complete Memory Dump file on BSOD
  • Automatic Memory Dump – this means that Windows will create an Automatic Memory Dump file on BSOD
  • Active Memory Dump – this means that Windows will create an Active Memory Dump file on BSOD

Note: The complete dump needs a page file that is allowed to be the size of the physical memory installed in your PC with a dedicated 1 MB of space for just the page header.

• Now once you have selected the most suitable option for you, just click on OK/Apply and then exit.
• Restart your PC to successfully apply the changes made.

Option 2 – via the WMIC command line

• The first thing you need to do to create Dump files via the WMIC command line is to tap the Win + X keys combination or simply right-click on the Start button and then select the Command Prompt (Admin) option. You could also type in “cmd” in the Cortana search box and then right-click on Command Prompt from the results and select Run as administrator.
• After that, type in any of the commands given below depending on your preferences so that your Windows 10 PC will be configured to create Dump Files:
  • No dump file: wmic RECOVEROS set DebugInfoType = 0
  • Small Memory Dump: wmic RECOVEROS set DebugInfoType = 3
  • Kernel Memory Dump: wmic RECOVEROS set DebugInfoType = 2
  • Complete Memory Dump: wmic RECOVEROS set DebugInfoType = 1
  • Automatic Memory Dump: wmic RECOVEROS set DebugInfoType = 7
  • Active Memory Dump: wmic RECOVEROS set DebugInfoType = 1

Note: A complete dump has to have a Page file which is allowed to be the size of the physical memory installed on your PC accompanied by a 1 MB space for just the page header.

• Now type in “exit” in the Command Prompt to exit it.
• Restart your PC to apply the changes made successfully.

What Is Runtime Error R6034?

Runtime Error r6034 is one of the most commonly occurring errors.  This error usually arises in Windows Vista and Windows 7. The message that appears to the user states ‘An application has made an attempt to load C runtime library incorrectly, please contact the support team for more information’. As the message suggests, this problematic error occurs simply because an application attempts to load the C runtime library without a manifest.

Solution

Error Causes

Runtime Error r6034 occurs when the system compiler fails to compile the working application. While this is the primary reason, there are some other conditions that trigger Runtime Error r6034 which are outlined below.

• Existence of viruses and malware in the system.
• Corrupt or missing system files.
• Power outages.
• Hardware problems.
• Hardware driver problems.

There are several other reasons that may trigger Runtime Error r6034 that are beyond the scope of this article. Regardless of what triggers this error, it is crucial to ensure that it is fixed as soon as possible.

Further Information and Manual Repair

There are several ways to deal with Runtime Error r6034. However, one of the most effective ways is listed below as follows.

• When this error occurs, restart your computer. Make sure you press F8 before the windows logo is displayed.
• Choose safe mode and press enter.
• Go to the ‘Start’ button and type ‘msconfig’ in the search box. Press enter.
• The MSConfig program will now open.
• Choose ‘Start up’ in the general tab and then click on the ‘Load Start Up’ item.
• Click on the ‘Services’ tab. Now click ‘Hide all Microsoft Services’ and then choose ‘Disable All’.
• Close the system configuration window.
• Restart the computer.

After restarting your computer, you will notice that the Runtime Error r6034 has been removed. If this approach fails to deliver the desired results, it is advised to follow the steps listed below.

• Go to the start button. In the search box, type ‘System Restore’.
• When System Restore appears, click on it.
• The system restore window will open. Make sure any process or application that’s open is now closed.
• In the System Restore window, if a calendar list appears, it means the restore point is open. Now choose the point from where the error appeared and click Next.
• This process may take some time. Your system will restart automatically and the Runtime Error r6034 will disappear.

The previous Windows versions all came with Microsoft's browser Internet Explorer. A lot of users love it because not only that it is easy to use. It is also very fast. Users didn’t have to worry about compatibility because it is almost always compatible with its Windows Version. When they introduced Windows 10, they changed the name of the browser from Internet Explorer to Microsoft Edge. It is faster and more user-friendly compared to its predecessors. But after the Creator Update, some experienced receiving the inet_e_resource_not_found error code. In contrary to what everyone expects, you actually don’t have to uninstall and reinstall the Microsoft Edge App. What you can do is reset the browser in your Apps & Features Settings in your Microsoft Settings.

To reset the browser you can follow the steps below:

1. Click on the Windows icon and go to settings.
2. Click on Apps and this will bring you to the Apps & Features page. Look for Microsoft Edge from the list of Apps and click on it.
3. Choose Advance Option
4. Scroll down then Under Reset, click on repair or reset. When you repair it will fix the existing problem but the data that caused the problem may still be present and can still cause problems. If you click on reset, it will delete all the cache and cookies that are installed in your browser but it will save your Favorites as well as your bookmarks.

Another way to resolve this is by disabling the feature TCP Fast Open on Microsoft Edge. To disable this, go ahead and follow the steps below:

1. Open the Microsoft Edge browser.
2. Type in about: flags on the Address (URL) bar.
3. Under Networking, uncheck the Enable TCP Fast Open.
4. Close your Microsoft Edge browser and open a new one.

Flushing the DNS also worked for other Users. Sometimes, the error code the inet_e_resource_not_found is caused by a corrupted DNS cache. There are 2 ways to flush your DNS. The first option is to use the command prompt to run the command.

1. To access the Command prompt or CMD, you can search for it on Cortana or you can click on the Windows icon to access the Programs, scroll down to the Windows System folder and click on it.
2. A dropdown menu will show up, click on Command Prompt which is the first on the list.
3. Type in the code ipconfig /flushdns and press enter.
4. There will be a message that will show that says Windows IP configuration successfully flushed the DNS Resolver Cache
5. Exit the CMD by typing exit and press enter.

The easiest way to do this is to Press the keys Window + R on your keyboard. Type in ipconfig /flushdns in the search box and hit enter or click on OK. These are only some of the ways to resolve the inet_e_resource_not_found. There are other ways to further troubleshoot this issue such as reinstalling your Wifi Adapter Driver or adjusting the DNS Server Address. But most of the time, users are able to resolve the issue with the steps provided above.

One of the common causes of Blue Screen of Death or BSOD errors is system driver files due to varying reasons. So if you encounter a Stop error caused by some system driver files such as isapnp.sys, gv3.sys, storahci.sys, or myfault.sys, on your Windows 10 PC, then this post should help you fix the problem. These system driver files are associated with different error codes. The isapnp.sys file is related to the following error codes:

• SYSTEM SERVICE EXCEPTION
• PAGE FAULT IN A NONPAGED AREA
• KERNEL DATA INPAGE
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED.

While the gv3.sys file is related to the following BSOD error codes:

• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN NONPAGED AREA.

On the other hand, the storahci.sys file is related to these error codes:

• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN NONPAGED AREA.

And the myfault.sys file is associated with this error code: SYSTEM SERVICE EXCEPTION. Although this system driver file causes different kinds of Blue Screen errors, some of their potential fixes are quite the same so you need not carry out tons of troubleshooting steps. But before you troubleshoot the problem, you might want to check out System Restore first, especially if you create a System Restore point from time to time. To perform System Restore, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first and boot your computer into Safe Mode.

Option 1 – Use the System Configuration utility

Note that this first fix is only applicable for Blue Screen errors associated with the myfault.sys file.

• In the Cortana Search box, type “MSConfig” and click on the “System Configuration” entry to open it.
• After opening System Configuration, go to the Processes tab.
• Then scroll down and look for the “Digital Line Detection” process and disable it.
• Now restart your computer and check if the Stop error is fixed or not.

Option 2 – Try to update, rollback or disable related device drivers

Incompatible and outdated drivers can also cause computer malfunctioning or crashing as well as Blue Screen errors. To fix that, you can update, roll back or disable the device drivers in your computer.

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• After opening the Device Manager, from the list of device drivers, look for the “WIN ISA Bus Driver” if you are facing a Stop error related to the isapnp.sys file. While you have to look for the Sony Recovery CDs PCG-Z1RAP Series device drivers if you face a Stop error concerning the gv3.sys file. For the storahci.sys, on the other hand, look for any outdated drivers and update them.
• To update or roll back or disable these drivers, just right-click on each one of them, and depending on your preference, you can either select “Update driver”, “Disable device” or “Uninstall device”.
• After that, restart your PC and see if it helped in fixing the Blue Screen error.

Option 3 – Use System File Checker

One of the built-in tools in Windows that you can use to fix Blue Screen errors is the System File Checker. This built-in command utility can help you restore corrupted or missing files as well as replace bad and corrupted system files. Chances are, any of the aforementioned system driver files might be corrupted so to fix them, use System File Checker.

• First, right-click on the Start button and click on the “Command Prompt (Admin) option.
• Next, type in the sfc /scannow command and hit Enter to execute it.

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Now restart your computer.

Option 4 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors. You can find it in Settings, under the Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options.
• Note that you might have to boot your PC into Safe Mode.

A lot of Windows 10 users have reported recently that their computers are frequently crashing with a Blue Screen error with an error code “VIDEO_DXGKRNL_FATAL_ERROR”. This kind of Stop error appears not so often and its bug check value of 0x00000113 is an indication that there is some violation in the Microsoft DirectX graphics kernel subsystem. This error also occurs when there is a corrupted driver that interferes with the GPU’s normal functionality. According to some security experts, this kind of error is reported to only occur in Windows 10 PCs. Users started getting this error right after a large Windows Update. The cause of this error might have something to do with a violation in the DirectX graphics kernel subsystem where there could be a bad DirectX install or some corrupted Dynamic Link Library or DLL. Aside from that, the error might also be caused by the Nvidia driver which might have crashed or it could also be that there is an intermittent power supply. Moreover, an outdated BIOS as well as a third-party security program might be the ones behind this Blue Screen error. Whichever the case may be, you need to fix the VIDEO_DXGKRNL_FATAL_ERROR BSOD error by following the instructions given below carefully.

Option 1 – Try checking if the NVIDIA graphics card is enabled and update it as well

Although the problem is quite massive, the fix could be as simple as enabling the NVIDIA graphics card if it turns out to be disabled. There might be some strange reason why your graphics card disables itself. Thus, the best and first option you can try is to check if the NVIDIA graphics card is enabled or not. To do so, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then type “devmgmt.msc” in the field and hit Enter to open the Device Manager.
• After opening the Device Manager, look for the Nvidia graphics card option among the list of device drivers. Once you found it, check if it is enabled or not. If it’s not enabled, you should see a gray arrow pointing downwards. Right-click on the card and select Enabled.
• Next, right-click on the graphics card once more and click on the Update Driver Software option and then click on the “Search automatically for updated driver software” option.

Option 2 – Update or uninstall third-party security program

As mentioned, the VIDEO_DXGKRNL_FATAL_ERROR Blue Screen error might be caused by a third-party security program that’s installed on your computer. So you have to either update it or uninstall it to resolve the issue.

Option 3 – Check the power supply for any inconsistency

The Blue Screen error might also be caused by an intermittent power supply. If there is any intermittent changes between the main supply and the battery power, it might lead to bad contact on your supply to the charger and thus, causes the VIDEO_DXGKRNL_FATAL_ERROR Stop error to appear. So to check if this scenario is applicable to you, you have to monitor your computer for any frequent changes between the power supply and the battery power. If you see that the supply is displaying power On and Off, see if the same goes when the power supply is disconnected. However, if it does not occur, you might have to purchase a new power adapter cable and replace the one that you have right now.

Option 4 – Reinstall the Graphics card drivers

• Tap Win + R to open Run then type “devmgmt.msc” in the field and hit Enter to open the Device Manager.
• From there, look for the Display adapters and uninstall each one of the graphics card drivers by right-clicking on them and selecting the Uninstall device option.
• After uninstalling the graphics card drivers, close the Device Manager and tap Win + R to open Run once again.
• After that, type “appwiz.cpl” in the field and hit Enter to open Programs & Features in the Control Panel.
• Next, look for any program that’s related to your GPU manufacturers like Nvidia, AMD, or Intel. Right-click on any GPU-related entry and click on Uninstall to uninstall them and then follow the next on-screen instructions that appear afterward.
• Now restart your computer.
• Once your computer has restarted, go to the GPU manufacturer’s website and download the latest driver version for your graphics card model and then install it.
• Restart your computer once again. That should fix the problem.

Option 5 – Try checking if there are any BIOS updates available for your PC

Updating the BIOS may help you resolve the BSOD error. You can just go to the OEM’s website as they offer utility software that can download BIOS firmware and update it without any problem. BIOS updates usually offer enhancements and fixes to some issues like this one.

Option 6 – Perform a System Restore

Performing a System Restore on your computer can also help you fix the VIDEO_DXGKRNL_FATAL_ERROR Blue Screen of Death error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.