Windows 10: BSOD hal.dll + ntoskrnl.exe - DPC Watchdog Violation

Any idea ? This keeps happening to me, sometimes 3 times a day. Thermal info by the way is pretty much a consistent 60 degreesCelsius on my Phenom 1090T (16gb, Sandisk SSD). Not sure if that is relevant.

What I also notice is something the computer freezes for 10 seconds multiple times shortly before the crash. Never seems to happen when the PC is idle, only when being used, as it is on 24/7 and can happen 3 times in succession. Seems to happen mostly with teamviewer usage and youtube, but not only. Also not sure if relevant but when playing youtube videos the audio will sometimes sound robotic and stutter.

I did install the Snail Driver suite to update everything at once, but I found when it tried to update my graphics card I was just left with a black screen or crazy colours, so I had to stop using that. I think it updated most things though. It didn't seem to help with BSOD.

Here is an example of one of the errors, they are always DPC errors with the same info. Quick snapshot below and full log attached.

On Tue 20/06/2017 06:11:28 your computer crashed
crash dump file: C:\WINDOWS\Minidump\062017-21812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14ECE0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

:)

 

BSOD- DPC Watchdog violation

BSOD - DPC watchdog violation how to fix?

 

Recurrent DPC Watchdog Violations (Hal.dll + Ntoskrnl.exe)

Hi,

The past two weeks I've been having several BSOD with the DPC Watchdog Violation's error.

I've read on several forum, this website included, and I already know that this is supposed to be a driver issue, but for the life of me I haven't been able to find out which driver is causing the error.

I've updated all my driver and even uninstalled and clean installed my GPU driver, without any results.

I am running Windows 10 (x64), have BitDefender Internet Security as Antivirus.

MOBO: MSI 970 GAMING

GPU: MSI R9 R80 GAMING

CPU: AMD Fx-6300

HDD: Caviar Blue 1TB

I'm attaching the Minidump created during the most recent BSOD.

Minidump 01/23/2016

I'd appreciate any help, as this is affecting my daily usage of this machine.

 

Hi,

You are running too many AntiVirus and security software at the same time. This is a common cause for bluescreens. Remove all of them for testing purposes and use windows defender instead.

These programm have to be uninstalled:

Comodo Internet Security How to uninstall Comodo AntiVirus (CAV) - Powered by Kayako Help Desk Software ESET How do I manually uninstall my Windows ESET product?ESET Knowledgebase F-Secure How do I uninstall the product? - F-Secure Community
L: ftp://ftp.f-secure.com/support/tools...lationTool.zip Malwarebytes http://www.malwarebytes.org/mbam-clean.exe Steganos Uninstall - Steganos – Privacy Software made easy

There are filesystem error too:

Code: 2017-05-28T22 26:36.802 Error: Volume C: (\Device\HarddiskVolume2) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-28T22 26:36.983 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-28T22 26:58.669 Error: Volume \\?\Volume{00020b8f-0000-0000-0000-40c837000000} (\Device\HarddiskVolume3) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-28T22 26:58.746 Error: Volume \\?\Volume{00020b8f-0000-0000-0000-100000000000} (\Device\HarddiskVolume1) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-29T09 00:34.599 Error: Volume Windows 10 SSD (\Device\HarddiskVolumeShadowCopy6) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-05-29T09 00:34.830 Error: A corruption was discovered in the file system structure on volume Windows 10 SSD.[/quote]
To fix filesystem perform these steps:

Repair Windows Filesystem:

1. Open an elevated command prompt.
2. In the elevated command prompt, type these commands below, and press Enter:

dism /Online /NoRestart /Cleanup-Image /CheckHealth
dism /Online /NoRestart /Cleanup-Image /ScanHealth
dism /Online /NoRestart /Cleanup-Image /RestoreHealth
dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup
dism /Online /NoRestart /Cleanup-Image /AnalyzeComponentStore

sfc /scannow

chkdsk %systemdrive% /F /R /X
fsutil dirty set %systemdrive%

SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
For example, you would use sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted. SFC should be able to repair the files afterwards.
CHKDSK:
Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...

 

Thanks, I will do as described. Do I copy and paste all the command prompt instructions at once, or do I write each line, then press enter, then do the next line, press enter, and so on ? Or do I paste them all and press enter once ?

Finally, I only have Commodo and Eset running at once, the others are loaded when needed. F-Secure is a VPN, as is Steganos. Malwarebytes is meant to be only run when needed, but might be running in the background due to the 15 day trial. Commodo is my firewall only and Eset is my anti-virus only.

 

Yes, from line to line. Looking in your dumps it seems a little bit that an security software or filesystem issue could be the cause. I would try the suggestions I gave to rule that out.

 

Thanks. I did everything you said to type but it still crashed twice tonight, same error message. I even updated some more drivers. There seems no logic to it. Could it be the SSD ? It passed the chkdisk okay and there were no errors on the command prompt stuff. I checked my SSD with Hard Disk Sentinel and it passed okay. Very confusing.

 

atapi.sys ATAPI IDE Miniport Driver Windows Update Code: BugCheck 133, {1, 1e00, 0, 0}Probably caused by : atapi.sys ( atapi!AtapiHwInterrupt+6a )[/quote] Code: BugCheck FE, {5, ffff800159cc51a0, 10024397, ffff8001657a3688}Probably caused by : memory_corruption[/quote] Code: BugCheck 133, {1, 1e00, 0, 0}nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA Get from OEM for laptops *** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : atapi.sys ( atapi!AtapiHwInterrupt+6a )[/quote] HDAudBus.sys High Definition Audio Bus Driver Windows Update Code: BugCheck 133, {1, 1e00, 0, 0}Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::Isr+cf )[/quote] ntkrnlmp.exe see ntoskrnl.exe Windows Update Code: BugCheck 133, {1, 1e00, 0, 0}Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+1472ba )[/quote] Code: BugCheck 133, {1, 1e00, 0, 0} ndis.sys NDIS 6.20 Wrapper Driver Windows Update *** WARNING: Unable to verify timestamp for win32kfull.sys*** ERROR: Module load completed but symbols could not be loaded for win32kfull.sysProbably caused by : ndis.sys ( ndis!ndisMiniportMessageIsr+b8 )[/quote]
Code: Use !analyze -v to get detailed debugging information.BugCheck 133, {1, 1e00, 0, 0}Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::Isr+16c )[/quote] Code: BugCheck 133, {1, 1e00, 0, 0}*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+d33e )[/quote] Code: BugCheck 133, {1, 1e00, 0, 0}Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::Isr+1f3 )[/quote] Code: BugCheck 133, {1, 1e00, 0, 0}Probably caused by : atapi.sys ( atapi!AtapiHwInterrupt+34 )[/quote] Code: BugCheck 133, {1, 1e00, 0, 0}Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+d33e )[/quote] Code: BugCheck 133, {1, 1e00, 0, 0}Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+d33e )[/quote] Code: BugCheck 133, {1, 1e00, 0, 0}Probably caused by : atapi.sys ( atapi!AtapiHwInterrupt+34 )[/quote] Code: BugCheck 133, {1, 1e00, 0, 0}*** WARNING: Unable to verify timestamp for rt640x64.sys*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sysProbably caused by : atapi.sys ( atapi!AtapiHwInterrupt+34 )[/quote] The system failed to flush data to the transaction log. Corruption may occur in VolumeId: L:, DeviceName: \Device\HarddiskVolume14.(A device which does not exist was specified.)

Code: A corruption was discovered in the file system structure on volume C:.The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.[/quote]
Code: A corruption was discovered in the file system structure on volume Windows 10 SSD.The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.[/quote] hidusb.sys USB Miniport Driver for Input Devices Windows Update Code: The driver \Driver\HidUsb failed to load for the device USB\VID_05A4&PID_9881&MI_01\6&11ea56c&0&0001.[/quote] Code: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume8.(A device which does not exist was specified.)[/quote] Code: An error was detected on device \Device\Harddisk6\DR11 during a paging operation.[/quote]





Some of these steps you had indicated that you did but please repeat these so we can have it viewable in the thread:

1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


2) sfc /scannow


3) dism /online /cleanup-image /restorehealth


4) chkdsk /scan (run on each drive) (if it displays any corruption plan to run chkdsk /x /f /r overnight on the drive)


When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread


5) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)


6) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)


7) shutdown /r (you will reboot the computer so that it is in clean boot)


Evaluate the performance on your computer in clean boot during typical use. Are the boots faster or slower? Are the shutdowns faster or slower? Are the hangs more frequent, less frequent or the same? Are the spontaneous bsod more frequent, less frequent or the same?

8) Uninstall all Nvidia software and drivers:
The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.Display Driver Uninstaller Download version 17.0.6.7 Driver Uninstaller Download version 17.0.6.6



9) Were you previously using this software/driver: vdrive.sys Fengtao Software Inc DVDFab Virtual Drive Device Driver Download: Free download DVDFab, Download DVDFab for free -- Download and try out the best Blu-ray and DVD copy software.
Support: Fastest DVD Copy Software | Contact us It was a older misbehaving driver. If you still have any of this software please uninstall it.


10) Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.Memtest86+ - Advanced Memory Diagnostic Tool
Memory problems. - Microsoft Community

Please use the Microsoft snipping tool to make an image of the Memtest86+ and post and image into the thread.


11) Run one of these SMART tests on each of your drives:
CrystalDiskInfo - Software - Crystal Dew World
HD Tune website
Hard Disk Sentinel - HDD health and temperature monitoring
For all HD please also use Sea Tools for windows to perform SMART, short and long generic tests:
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows



Please use the Microsoft snipping tool to make an image of each SMART test result and post images into the thread.


12) Uninstall all Realtek drivers and update with new drivers
rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver http://www.realtek.com.tw/downloads/...&GetDown=false

 

After trying some stuff can u upload an new Log?

 

Hi, just a quick update. I have bookmarked this thread for future help, but because my PC hasn't BSOD in the last 2 days, which is very unusual, I am very reluctant to do anything else to it until it does. So if I get another BSOD I will come back to this thread and try everything else that is suggested. I really appreciate all of your help. Only other change I made in the last few days was getting a cheap USB sound card and using that instead of on-board audio (due to on board audio stuttering during mouse movement or HDD activity), but that could be coincidence.

I have both printed this page out and bookmarked, so if I get another BSOD, which I fully expect with my luck, I will be back on here. Thanks very much both of you.

 

BliardUK,
There was file system corruption reported in the logs on volume C (chkdsk /scan did not find it but a deeper scan can) so open administrative command prompt and run chkdsk C: /x /f /r (this may take many hours so plan to run overnight)

To see the results of the chkdsk:

Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials


CHKDSK: What is it and how do I run it? - Ask Leo!


How do I see the results of a CHKDSK that ran on boot? - Ask Leo!


How to find chkdsk results in Windows 10 - Winaero uses 26226 find

 

Okay, well, as expected I am back *Smile My bad luck rises again. In fact, this is my 2nd attempt at typing this message because my PC crashed 30 minutes ago, so when I got back on I started to type this and then it crashed again, so that was twice within minutes. Also to make it worse, the crash meant I had to use a recovery disc from Macrium Reflect as the crash broke my boot sector, see image attached.

So, I am going to start working through the above, starting with the chkdsk C: /x /f /r method and then moving on to the more detailed stuff. EDIT : Just realised I did the chkdsk C: /x /f /r already from the first post. So I will try the mem test next.

Thanks all. See image of Boot error code, which I fixed through a recovery disc, which thankfully I had to hand.

Attachment 141320

 

Please submit a new set of logfiles if you are able to.

Please can you fill in as many details as possible about you system in the system spec area of your profile.