DPC Watchdog violations while watching Youtube, caused by HAL

Rule 4
No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc) - it is forum policy that no help shall be given to people who knowingly steal software or services.


One of the main reasons for this is that the act of pirating the software will inevitably change the working of the software and make investigation and repair impossible. Please install a legitimate copy of the software and if you are still experiencing the issue we will be pleased to assist - No further assistance will be provided until we are satisfied that the software is genuine.



Software that diverts activation.

What else do you need? I provided the screenshot of the Windows Licensing which was never affected, and provided a new DM Report that should show that the software and the service that you referred to has been uninstalled.

@ctclark1
Happy holidays.
There is a green light to provide help.

There was 1 BSOD mini dump file.
When debugged it did not display a definitive misbehaving driver.

For all tests/steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.

1) open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) 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 edit then copy > paste into the thread

5) chkdsk /x /f /r
This may take many hours so plan to run overnight.

C:\Windows\system32>chkdsk /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: y
reboot

Run the command on all drives/partition using the syntax chkdsk /x /f /r c: or chkdsk /x /f /r d: changing the drive letter to the applicable drive letter.
6) Find the chkdsk reports in the event viewer and post the results into the thread using the information in this link:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

7) Run HDTune: (all drives)
http://www.hdtune.com/
to check the health,
scan for errors, no quick scan but full scan
run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 General Tips Tutorials

8) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 6 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

9) Update: rt640x64.sys
Updating a driver: Updating a driver. - Microsoft Community

These tests can be performed overnight:
chkdsk /x /f /r
HD Tune full error scan
Memtest86+ version 5.01

Code:

Event[764]:  Log Name: System  Source: Disk  Date: 2017-10-16T16:18:48.549  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ClarkCT1  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.Event[765]:  Log Name: System  Source: Disk  Date: 2017-10-16T16:18:48.549  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ClarkCT1  Description: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.

Code:

Event[2076]:  Log Name: System  Source: storahci  Date: 2017-11-14T06:22:44.845  Event ID: 129  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ClarkCT1  Description: Reset to device, \Device\RaidPort0, was issued.

Code:

Event[2077]:  Log Name: System  Source: Disk  Date: 2017-11-14T06:22:45.062  Event ID: 153  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ClarkCT1  Description: The IO operation at logical block address 0x3d075c37 for Disk 2 (PDO name: \Device\00000026) was retried.

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:

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/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:

rt640x64.sys

Realtek NICDRV 8169 PCIe GBE Family Controller driver

http://www.realtek.com.tw/downloads/...&GetDown=false

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.

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:

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:

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

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:

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.