Windows 10: DPC Watchdog violations while watching Youtube, caused by HAL

I've performed some of these steps already but am running them all in the prescribed order now for sake of helping you find a solution. I used to work in tech support so these are nothing out of the ordinary for me, but I didn't run all of them before and the ones I did weren't run every time I tried troubleshooting this.

Below are the results of the first two commands. Attached is another DM dump of another DPC crash this morning prior to beginning this process. I'm beginning the next steps now.

Code: Microsoft Windows [Version 10.0.16299.125](c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.125 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully.[/quote]

 

The bugcheck was 133 and when debugged it did not display a definitive misbehaving driver.
Was the realtek driver updated before or after the latest BSOD?



Code: 12/17/2017 3:50 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff80011c02370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121717-11546-01.dmp \\?\C:\WINDOWS\TEMP\WER-24953-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER79D9.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B60.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B90.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_44ef41cad67a179a2f9dc12bac57f2c3bdd47f_00000000_cab_029a7b9e Analysis symbol: Rechecking for solution: 0 Report Id: 89b37e71-a7db-4b0c-944f-3e3597d71885 Report Status: 4 Hashed bucket:12/14/2017 1:00 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff8037de8c370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121317-10156-01.dmp \\?\C:\WINDOWS\TEMP\WER-23125-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER75BC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER760A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER761B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_ee704cb2458c6334bcdbff6eb5f4d0bfbfd7d3_00000000_cab_0270762a Analysis symbol: Rechecking for solution: 0 Report Id: 22cc5227-82e1-44cc-ba50-2def1bb6c0f7 Report Status: 4 Hashed bucket: 12/22/2017 6:30 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff803c5484370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122217-11062-01.dmp \\?\C:\WINDOWS\TEMP\WER-24015-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5B88.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BF6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C35.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_338f9457162d544348ec1bb7cadfd64fb23a5f5a_00000000_cab_02955c44 Analysis symbol: Rechecking for solution: 0 Report Id: cbcbf83f-c92b-40c6-a377-195830f282f8 Report Status: 4 Hashed bucket:[/quote] Code: 12/17/2017 3:50 PM Windows Error Reporting Fault bucket 0x133_ISR_nt!KeClockInterruptNotify, type 0 Event Name: BlueScreen Response: Not available Cab Id: 499a6a07-7858-4489-afc1-1bb8dc79eae2 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff80011c02370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121717-11546-01.dmp \\?\C:\WINDOWS\TEMP\WER-24953-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER79D9.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B60.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B90.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_44ef41cad67a179a2f9dc12bac57f2c3bdd47f_00000000_cab_291adc9a Analysis symbol: Rechecking for solution: 0 Report Id: 89b37e71-a7db-4b0c-944f-3e3597d71885 Report Status: 268435456 Hashed bucket:12/22/2017 6:30 PM Windows Error Reporting Fault bucket 0x133_ISR_nt!KeClockInterruptNotify, type 0 Event Name: BlueScreen Response: Not available Cab Id: 7a4c1dc5-40fb-4fcb-b692-2aff0664e9ce Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff803c5484370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122217-11062-01.dmp \\?\C:\WINDOWS\TEMP\WER-24015-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5B88.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BF6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C35.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_338f9457162d544348ec1bb7cadfd64fb23a5f5a_00000000_cab_0f11f2a8 Analysis symbol: Rechecking for solution: 0 Report Id: cbcbf83f-c92b-40c6-a377-195830f282f8 Report Status: 268435456 Hashed bucket: 12/14/2017 1:10 AM Windows Error Reporting Fault bucket 0x133_ISR_rt640x64!MPIsr, type 0 Event Name: BlueScreen Response: Not available Cab Id: 937a66b7-e88a-4e27-bf85-ecff1c125216 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff8037de8c370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\121317-10156-01.dmp \\?\C:\WINDOWS\TEMP\WER-23125-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER75BC.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER760A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER761B.tmp.txt \\?\C:\Windows\Temp\WERA47E.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_ee704cb2458c6334bcdbff6eb5f4d0bfbfd7d3_00000000_cab_13a56d35 Analysis symbol: Rechecking for solution: 0 Report Id: 22cc5227-82e1-44cc-ba50-2def1bb6c0f7 Report Status: 268435456 Hashed bucket:[/quote] Code: 12/18/2017 1:47 AM Windows Error Reporting Fault bucket 1950826289557810322, type 5 Event Name: AppxDeploymentFailureBlue Response: Not available Cab Id: 0 Problem signature: P1: 800706BE P2: 17 P3: 3 P4: windows.visualElements P5: 10.0.16299.98 P6: 5092 P7: P8: P9: P10: Attached files: \\?\C:\WINDOWS\TEMP\AppXDeploymentServer_FED400BF-777E-0001-1F24-D4FE7E77D301.evtx \\?\C:\WINDOWS\TEMP\AppXPackaging_FED400BF-777E-0001-1F24-D4FE7E77D301.evtx \\?\C:\WINDOWS\TEMP\AppxErrorReport_FED400BF-777E-0001-1F24-D4FE7E77D301.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66C9.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66DB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66FB.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_800706BE_c4b8b9eba53b3f4beae8a391f32ccbe6dd795588_00000000_24c2a49d Analysis symbol: Rechecking for solution: 0 Report Id: b0ea41e8-09be-438f-a852-fcf0da77981a Report Status: 268435456 Hashed bucket: 498cc3cb1b5121260b12ba2ca7962c92[/quote] Code: 12/18/2017 1:47 AM Windows Error Reporting Fault bucket , type 0 Event Name: AppxDeploymentFailureBlue Response: Not available Cab Id: 0 Problem signature: P1: 800706BE P2: 17 P3: 3 P4: windows.visualElements P5: 10.0.16299.98 P6: 5092 P7: P8: P9: P10: Attached files: \\?\C:\WINDOWS\TEMP\AppXDeploymentServer_FED400BF-777E-0001-1F24-D4FE7E77D301.evtx \\?\C:\WINDOWS\TEMP\AppXPackaging_FED400BF-777E-0001-1F24-D4FE7E77D301.evtx \\?\C:\WINDOWS\TEMP\AppxErrorReport_FED400BF-777E-0001-1F24-D4FE7E77D301.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66C9.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66DB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER66FB.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_800706BE_c4b8b9eba53b3f4beae8a391f32ccbe6dd795588_00000000_cab_0be66708 Analysis symbol: Rechecking for solution: 0 Report Id: b0ea41e8-09be-438f-a852-fcf0da77981a Report Status: 4 Hashed bucket:[/quote]

 

Violation of memory.
May be caused by a third party program.

unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
Unable to get MmNonPagedPoolStart
Searching special pool (0000000000000000 : 0000000000000000) for Tag: MmCa
The MmCa tag could not be found in special pool.
Unable to get MmNonPagedPoolStart
Searching special pool (0000000000000000 : 0000000000000000) for Tag: MmCi
The MmCi tag could not be found in special pool

Unable to get LeftChild of nt!_MMVAD_SHORT at ffff8d0e6c802820
failed to count VADs
PROCESS ffff8d0e6b0ec5c0
SessionId: 1 Cid: 092c Peb: 8f3363d000 ParentCid: 145c
DirBase: 0f4a3000 ObjectTable: ffffb40b4488fc40 HandleCount: <Data Not Accessible>
Image: chrome.exe
VadRoot ffff8d0e6c802820 Vads 0 Clone 0 Private 49839. Modified 23380. Locked 0.
DeviceMap ffffb40b3c2f5e10
Token ffffb40b3d9b9500
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
ElapsedTime 00:12:45.611
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 517040
QuotaPoolUsage[NonPagedPool] 57272
Working Set Sizes (now,min,max) (0, 0, 0) (0KB, 0KB, 0KB)
PeakWorkingSetSize 0
VirtualSize 2098377 Mb
PeakVirtualSize 2098981 Mb
PageFaultCount 0
MemoryPriority BACKGROUND
BasePriority 8
CommitCharge 55945
Job ffff8d0e72a10620
*** Error in reading nt!_ETHREAD @ ffff8d0e6e8c3700

 

CHKDSK results.

I have not gotten to updating the driver yet, I hadn't seen the troubleshooting steps until after the most recent bugcheck occurred. I'm just about to start the HD Tune process now and will continue moving on in order.

In regards to niknik's comments regarding Chrome, I use the same version and plugins (to my best knowledge) on my Laptop and experience no issues. The only difference being this computer, the desktop, uses the preview builds of Windows 10, whereas the laptop uses the standard release builds. But as I mentioned in the first post, this has been going on for months spanning numerous preview builds and even survived a complete wipe and reinstall of the OS.

 

The chkdsk report displayed:

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

 

I missed that when I browsed the log, oops. The system is currently in the middle of the HD error scan on my 2TB drive. I will let this finish as well as the error scan on the second SSD in the system and post those. After that would you like me to continue with the memory testing or attempt the driver update first and see if the problem occurs again?

 

There is flexibility in the order as its nice to make progress overnight.

Perform the chkdsk /x /f /r on all partitions using the syntax chkdsk C: or chkdsk D: changing the drive letter to the applicable partition/drive.

Perform the driver update at the earliest opportunity to reduce the frequency or eliminate the spontaneous BSOD.

The memory testing with Memtest86+ version 5.01 is best done overnight. So allow that test to run as long as possible. The more the passes the better the testing. It sometimes takes passes in the 20's to find malfunctioning RAM. When the testing has completed please use a camera or smart phone camera to take a picture an post and image into the thread.

 

Decision
Fall Creators Update random reboots WHEA_UNCORRECTABLE_ERROR (124)
I saw the blue screen appear when this browser was displayed.

 

HD Tune results, three drives arranged by rows. Clearly I need to look into the E: drive benchmarking issue however nothing that is running at the time of the crashes would be using that drive, especially not something that would only involve Youtube. The only data stored on that drive at present is data files for a game on Steam, which does not present any problems with crashes.

 

The driver was updated prior to running memtest.

The memtest results are shown in this image - 13 passes 0 errors

Dropbox - 1224171002a.jpg