Fix and Resolve Error Code 100013 - DPC Watch DOG Violation Windows Server 2016 & 2019

If you are looking to resolve error code 100013, then you are in the right spot. Check out our straightforward steps to resolve the issues mentioned in this article.

The BSOD or the Blue Screen of Death is one of the most dreaded error messages that you would come across while using a computer. However, the BSOD error can range across many different variants, and one of the issues you may face on your Windows Server 2016 and 2019 would be the PC Watchdog Violation error, also indicated by the error code 100013. How to resolve this error and get your PC or laptop back to the working status? Here are some few tips that should be helpful.

Resolve Error Code 100013 – What is DPC Watchdog Violation Error?

The DPC Watchdog Violation Error is one of the common issues you would be facing on your Windows operating system. One of the most feared BSOD issues, it manifests itself in the form of an error code DPC_Watchdog_Violation, it can hit your computer due to a host of reasons.

Some of the most common reasons would include an SSD firmware not supported, an SSD version that is old enough or the compatibility with the hardware. Corrupted system files can be yet another issue that may be affecting your functionality. Ensure that the firmware version of your SSD is up to date and is not altered in any manner by an outdated firmware.

Resolve Error Code 100013 – How to fix the DPC Watchdog Violation Error?

Several causes can produce the DPC Watchdog violations error as we have already outlined in the introduction above. However, you may not be able to address the issue if you are not aware of the exact problems that may be affecting you.

The fixes indicated here should be helpful enough in addressing the concerns effectively.

Fix 1 – Remove the External devices connected to your device

The first step that should ideally address the concerns should be to disconnect all the external devices that are connected to your device. There can be several devices that include external hard drives, external SSDs, printers, and scanners. Begin reconnecting the devices one by one, and the error should be gone. This method is referred to as the System of Elimination.

Remove all the devices and begin connecting the issue with each of them until you find the exact device that may be causing the problem.

Fix 2 – Update Your SSD Firmware

If you are using an SSD based drive on your computer system, it may be practical enough to update the SSD firmware. The best option in this direction would be to download the latest firmware for your drive and update your solid state drive right away.

We would, however, advise opting for the official firmware from the manufacturer website. Of course, you will need to have access to the exact model number of your SSD. Finding it should not be difficult either. The Device Manager option should let you know the exact model number of your SSD and the correct firmware that it is currently on.

Fix 3 – Check the Corrupted System Files

Corrupt system files are what would cause the issue on your system and perhaps lead t the Blue Screen of Death error. Resolving the DPC Watchdog violation error can be one of the problems that can affect your system to a considerable extent.

Make sure that the Windows system files are intact and not corrupted. The Check Disk command can be an excellent option to address the issue of corrupted system files. Here is how you can get it quickly done –

Launch Command Prompt on your system.
Type in the following command and press Enter

 CHKDSK C: /F /R

Your device will not be able to check for the correctness of the files right away because the file system is in use. You will be asked to verify whether you would want to schedule the checking when the computer starts next time.
Confirm by pressing Y and ENTER.

Now restart your computer. This will make the computer reboot and check the system files and their integrity. Never turn off the computer when it is checking your files for accuracy and efficiency.

Fix 4 – Scan your system files

The System File Checker or SFC is one of the best options you would want to go with if you are looking to address the concern of DPC Watchdog Violation error. Do note that you will need to launch Command Prompt using the Command Prompt.

Follow the steps here below –

Launch Command Prompt as an administrator.
Type in the following command

              SFC /scannow

This will begin scanning your system files and fix the issues if any concerning your Windows system. Wait patiently till the scanning is completed and your system is restarted. If it does not reboot, you can reboot it manually.

Fix 5 – Use BlueScreenView to check the functionality

Whenever a DPC Watchdog violation error happens on your Windows device, it creates a minidump file. This file is saved in the C:WindowsMinidump folder.

You should also be able to find the files through the event viewer, which should also give you the options like how to stop the occurrence and other instructions related to the folder and file formats. The BlueScreenView should be an excellent option for working with this context. The application diagnoses all the possibilities of BSOD error and its consequences.

Fix 6 – Use System Restore (Only Applicable to Client OS’es like Windows 10)

System Restore should perhaps be the last resort you would want to opt for if you find any of the above tips fail to resolve the issues. System Restore should be one of those options that would be able to address most of your concerns.

However, it should be advisable to boot into your computer in the safe mode so that you will be able to apply System Restore. Make sure you restore your system to a time where your server was working without any difficulties.

Fix 7 – Update the Chipset Driver

This can be one of the common issues if you have upgraded from the older Windows version to the newer one. You may be using the driver iastor.sys which is not compatible with your Windows 10 based ecosystem. Microsoft has claimed that it is investigating the issue and is destined to come with a solution quite soon.

However, for now, it may be a good idea to replace the iastor.sys file with storahci.sys. This is how you would do it –

Go to your Device manager
Choose the IDE ATA/ATAPI controllers and expand it.
Choose the controller as Standard SATA AHCI Controller or any other SATA AHCI Controller.
Install the drivers for the controller by letting the system choose the appropriate driver automatically.

Any Other solutions?

Well, apart from the above fixes and solutions available to address the DPC Watchdog violation error, there have been a few specific updates from different users. Though these can be segmented solutions and may not be able to help every one of us, it may not be a bad idea to give it a thought.

Disable AVG Antivirus – Some users have reported that turning the AVG antivirus or disabling it has been successful in removing the BSOD error. Though there is no solid proof to indicate the interrelation between the two, it may be a little worthy enough to give it a try. If it works for you, it can be a good idea to migrate to some other antivirus solution or check the options to update it so that you will continue using AVG antivirus without being affected by Blue Screen of Death issues.

Reinstall Display Driver – Uninstalling the display driver and reinstalling it has been shown to addressing the BSOD syndrome and help you achieve the perfect solution. Just make sure that you boot your device into Safe Mode and reinstall the Display driver.

Apart from those updates, yet another solution that may prove to be helpful would include checking if the operating system is updated. One of the best choices would be to install the Windows Update that reads 2017-06 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4022715).

The Concluding Thoughts

Those were a few tips that should assist you in choosing the right fixes for addressing the issues related to DPC Watchdog Violation error on your Windows Server 2016 and 2019. Your concerns should ideally be resolved by following any one of the right solutions that have been outlined in this compilation.

We hope these steps helped to resolve error code 100013. Do check out the options outlined in this compilation and share your thoughts and experiences with us.