Win 10 dpc_watchdog_violation

My PC has recently begun getting BSOD's with the dpc_watchdog_violation error. The BSOD happens with varying intervals. I have not changed any hardware before the problem began occurring.

Hopefully one of you can help

Hi scruptus,

Welcome to the Ten Forums BSOD forum.

1) There are two log collectors: DM and BETA
The beta log collector will collect more useful folders and files.
At some time it will replace the DM log collector.
Run the beta log collector and post a zip into this thread.
The link is in the lower half of this webpage:
BSOD - Posting Instructions - Windows 10 Forums
https://www.tenforums.com/attachment...-v2-beta15.zip
(extract all > open)

2) Update the secs in the "My Computer" section:
System Specs - Fill in at Ten Forums | Windows 10 Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

3) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

4) If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab > scroll down to system and advanced > post an image into the thread

5) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 | Windows 10 Tutorials

6) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
7) re-install the Nvidia GPU driver from the Nvidia website
8) make sure that you check the clean install box and if available install the physx driver.
Display Driver Uninstaller Download version 17.0.8.2 (or newer version if available)
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA
Download Display Driver Uninstaller - MajorGeeks

9) Open administrative command prompt and type or copy and paste:
10) sfc /scannow
11) dism /online /cleanup-image /restorehealth
12) chkdsk /scan
13) 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

14) What is the overclocking history?
a) Make sure that there is no over clocking while troubleshooting.

15) On this link it does not display the BIOS version on the computer:
BIOS Version/Date American Megatrends Inc. 0807, 07/06/2017
PRIME Z270-P BIOS & FIRMWARE | Motherboards | ASUS Global


16) Please find the best Asus link that displays the current BIOS version and post a link into the thread: 0807
Then upgrade to the latest non-beta BIOS

17) Open device manager > click view > click show hidden devices > manually expand all rows > look for any row displaying a yellow triangle with black exclamation mark or unknown device > post an image into the thread

Code:

Name	NVIDIA GeForce GTX 1070
PNP Device ID	PCI\VEN_10DE&DEV_1B81&SUBSYS_85DC1043&REV_A1\4&38AB2860&0&0008
Adapter Type	GeForce GTX 1070, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1070
Adapter RAM	(1.048.576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f5be1f8d25335236\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f5be1f8d25335236\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f5be1f8d25335236\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f5be1f8d25335236\nvldumdx.dll
Driver Version	24.21.13.9907
INF File	oem12.inf (Section102 section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	1920 x 1080 x 60 hertz
Bits/Pixel	32
Memory Address	0xF6000000-0xF70FFFFF
Memory Address	0xE0000000-0xF1FFFFFF
Memory Address	0xF0000000-0xF1FFFFFF
I/O Port	0x0000E000-0x0000EFFF
IRQ Channel	IRQ 16
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_f5be1f8d25335236\nvlddmkm.sys (24.21.13.9907, 16,42 MB (17.212.744 bytes), 02/09/2018 18.25)

Code:

Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64	ROOT\NET\0001	This device is disabled.
Microsoft Visual Studio Location Simulator Sensor	ROOT\WPD\0000	This device cannot start.
Hyper-V Virtual Ethernet Adapter #2	ROOT\VMS_MP\0001	This device is disabled.

1) i've attached the new file

2) I filled out most things, tell me if more is needed

3) the attached image

4) no Ccleaner

5) turned off fast startup

6-8)Used DDU and reinstalled driver

9-13)

Code:

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

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.345

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\System32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  1734912 file records processed.
File verification completed.
  10198 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  1047 reparse records processed.
  2123552 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  1047 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  194321 data files processed.
CHKDSK is verifying Usn Journal...
  38434480 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 243376311 KB total disk space.
 217073408 KB in 703083 files.
    376180 KB in 194322 indexes.
         0 KB in bad sectors.
   1860755 KB in use by the system.
     65536 KB occupied by the log file.
  24065968 KB available on disk.

      4096 bytes in each allocation unit.
  60844077 total allocation units on disk.
   6016492 allocation units available on disk.

C:\Windows\System32>

14)No overclocking

15-16) I've updated my bios to version 1205 https://www.asus.com/Motherboards/PR...HelpDesk_BIOS/

17)the attached image

Thanks for the help!

1) The image displayed that the startup and recovery settings are set to automatic.
2) The log collector displayed small memory dump.

3) Was the log collector ran before the image?
4) Make sure the startup and recovery is set to automatic (reboot to keep setting changes)

5) Increase the free space on the windows drive to > 35 GB
(In general 15% -20% is often the best for performance)
(a minimum amount of free space is needed to prevent Windows from deleting files)
(and a certain amount of free space is needed for Windows upgrades)

6) See these links to troubleshoot the rows in device manager:
How to easily find drivers for Unknown Devices in Windows | PCWorld
https://www.howtogeek.com/193798/how...evice-manager/

7) If there any crashes:
a) run the beta log collector and post a new zip into the thread
b) open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > zip > post a one drive or drop box share link into the thread

8) When the troubleshooting has completed and the computer has displayed stability ( no BSOD for one week ) then you can modify the settings to your preference.

Code:

DriveLetter Size (GB) Free (GB) Device Path                                       
----------- --------- --------- -----------                                       
C:              232.1      23.6 \Device\HarddiskVolume3                           
E:             232.88      38.2 \Device\HarddiskVolume1

Code:

Event[4084]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2018-11-04T13:49:23.974
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-CLLL3O8
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

1-4) yeah it was set to small dump before the image, but i changed it to automatic

This time my pc ran for quite some time before the Bsod happend, but it happend again with the same error code.

I've attached the new log from the beta logger.
Here's a Onedrive link to the memory dump https://1drv.ms/u/s!Ak-q56RaHqoNiF8i88HCpOz4hS_T

1) For startup and recovery system failure:
a) Uncheck automatically restart
b) reboot

If automatically restart is checked it an be easy to miss bsod.
With automatically restart unchecked there should be a bsod window with bugcheck and : (
Sometimes it may display a misbehaving driver in the form *.sys
At the beginning of a bsod you may see a % counter.
If you see the % counter allow it to rise to 100% before rebooting so that there is sufficient time to create the dump file.

2) Increase the drive free space on the Windows drive to 35 GB or more (15% - 20% free space)

Code:

DriveLetter Size (GB) Free (GB) Device Path                                       
----------- --------- --------- -----------                                       
C:              232.1     28.39 \Device\HarddiskVolume3                           
D:              28.85     28.84 \Device\HarddiskVolume5                           
E:             232.88     51.05 \Device\HarddiskVolume1

3) Temporarily turn off Windows updates of non-Microsoft drivers:

Enable or Disable Driver Updates in Windows Update in Windows 10 | Tutorials

4) Uninstall Nvidia GPU > install a version that is different from: 25.21.14.1634


6) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
7) re-install the Nvidia GPU driver from the Nvidia website
8) make sure that you check the clean install box and if available install the physx driver.
Display Driver Uninstaller Download version 17.0.8.2 (or newer version if available)
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA
Download Display Driver Uninstaller - MajorGeeks

9) If there are bsod with multiple driver versions with the Nvidia GPU the hardware will need to be checked.
Some computers have a functioning display without a dGPU and allow checking the system for stability / instability.
The dGPU can be removed and for a period of time the computer is evaluated to see whether there are or are not bsod.
Please indicate whether there is or is not a functioning display with removal of the dGPU.

10) If the Nvidia GPU causes more bsod with a different driver then see if you can find a friend, neighbor, relative, or local computer store to swap the card.
There should be two tests.
The new card should be tested in the problematic computer.
The card from the problematic computer should be tested in another computer.

Code:

03/11/2018 17.12	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: fffff8003de6c378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\110318-4687-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10046-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER345E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER346E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER347D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER348E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_e6339f9df67e9996a82e67dd02c2ff9147070a5_00000000_cab_3ace02c5

Analysis symbol: 
Rechecking for solution: 0
Report Id: fc04cc5c-3d9b-4e5b-a847-f6a008512562
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
03/11/2018 17.10	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: fffff8003de6c378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\110318-4687-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10046-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER345E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER346E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER347D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER348E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_e6339f9df67e9996a82e67dd02c2ff9147070a5_00000000_03a0348d

Analysis symbol: 
Rechecking for solution: 0
Report Id: fc04cc5c-3d9b-4e5b-a847-f6a008512562
Report Status: 4
Hashed bucket: 
Cab Guid: 0
25/10/2018 18.11	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: fffff8010aee5378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\102518-7609-01.dmp
\\?\C:\WINDOWS\TEMP\WER-13218-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F6A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F7B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F89.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FB9.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_747aaac82c4c27372af73a42fc2fb94b8e19fb_00000000_cab_0f921b5e

Analysis symbol: 
Rechecking for solution: 0
Report Id: ee98cb1a-2784-40f9-9f9c-ae98f9d8533e
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
25/10/2018 18.09	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: fffff8010aee5378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\102518-7609-01.dmp
\\?\C:\WINDOWS\TEMP\WER-13218-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F6A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F7B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F89.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FB9.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_747aaac82c4c27372af73a42fc2fb94b8e19fb_00000000_03c43fb8

Analysis symbol: 
Rechecking for solution: 0
Report Id: ee98cb1a-2784-40f9-9f9c-ae98f9d8533e
Report Status: 4
Hashed bucket: 
Cab Guid: 0
12/11/2018 12.06	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: fffff8022b262378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\111218-4156-01.dmp
\\?\C:\WINDOWS\TEMP\WER-8937-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FDA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FDB.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FE9.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FFA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_e6e51b5a34a7d5e09b2adf12190e32d78bf2ac4_00000000_cab_3f91f930

Analysis symbol: 
Rechecking for solution: 0
Report Id: d75d022d-d850-499a-93dc-f5f2b476d256
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
12/11/2018 12.04	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: fffff8022b262378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\111218-4156-01.dmp
\\?\C:\WINDOWS\TEMP\WER-8937-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FDA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FDB.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FE9.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2FFA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_e6e51b5a34a7d5e09b2adf12190e32d78bf2ac4_00000000_03a82ff9

Analysis symbol: 
Rechecking for solution: 0
Report Id: d75d022d-d850-499a-93dc-f5f2b476d256
Report Status: 4
Hashed bucket: 
Cab Guid: 0
26/10/2018 15.16	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: fffff80278ced378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\102618-4593-01.dmp
\\?\C:\WINDOWS\TEMP\WER-6984-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B84.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B95.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BA3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BA4.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_ba58cf76dbb4bd457868edb6f52c1d335ae8af_00000000_cab_1afc2d3a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 07fc613b-abf6-4371-8a9f-aec1fa799ea9
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
26/10/2018 15.16	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: fffff80278ced378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\102618-4593-01.dmp
\\?\C:\WINDOWS\TEMP\WER-6984-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B84.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B95.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BA3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BA4.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_ba58cf76dbb4bd457868edb6f52c1d335ae8af_00000000_03a42ba3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 07fc613b-abf6-4371-8a9f-aec1fa799ea9
Report Status: 4
Hashed bucket: 
Cab Guid: 0
11/11/2018 23.20	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: fffff802b32e3378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\111218-4609-01.dmp
\\?\C:\WINDOWS\TEMP\WER-11828-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B24.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B35.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B43.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B54.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_c0f5677c959e16a92098a897b11ef425b4a4e2_00000000_cab_1b843884

Analysis symbol: 
Rechecking for solution: 0
Report Id: 02afff02-8ddd-4c63-ac02-7a03389ae1fb
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
11/11/2018 23.19	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: fffff802b32e3378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\111218-4609-01.dmp
\\?\C:\WINDOWS\TEMP\WER-11828-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B24.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B35.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B43.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B54.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_c0f5677c959e16a92098a897b11ef425b4a4e2_00000000_03ac3b63

Analysis symbol: 
Rechecking for solution: 0
Report Id: 02afff02-8ddd-4c63-ac02-7a03389ae1fb
Report Status: 4
Hashed bucket: 
Cab Guid: 0
24/10/2018 10.49	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: fffff803422eb378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\102418-7984-01.dmp
\\?\C:\WINDOWS\TEMP\WER-14531-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45B3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45C4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45D3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4602.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_764bc4fec05b6db26b5471cb3632e411373b44c3_00000000_cab_1ee44e2f

Analysis symbol: 
Rechecking for solution: 0
Report Id: c9d285e0-87d2-4af6-8e47-5300fcbcf775
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
24/10/2018 10.49	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: fffff803422eb378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\102418-7984-01.dmp
\\?\C:\WINDOWS\TEMP\WER-14531-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45B3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45C4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45D3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4602.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_764bc4fec05b6db26b5471cb3632e411373b44c3_00000000_03c44601

Analysis symbol: 
Rechecking for solution: 0
Report Id: c9d285e0-87d2-4af6-8e47-5300fcbcf775
Report Status: 4
Hashed bucket: 
Cab Guid: 0
04/11/2018 12.49	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: fffff8039dced378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\110418-4406-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10421-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34EA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34FB.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER350A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER352A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_773c515a08d4fec303897523c3ff8282b86545_00000000_cab_1bfc3596

Analysis symbol: 
Rechecking for solution: 0
Report Id: f406c72a-a58b-4471-9616-dff971cd3137
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
04/11/2018 12.49	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: fffff8039dced378
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\110418-4406-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10421-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34EA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34FB.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER350A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER352A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_773c515a08d4fec303897523c3ff8282b86545_00000000_03a03529

Analysis symbol: 
Rechecking for solution: 0
Report Id: f406c72a-a58b-4471-9616-dff971cd3137
Report Status: 4
Hashed bucket: 
Cab Guid: 0
19/10/2018 21.59	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: d1
P2: 23c
P3: 5
P4: 0
P5: fffff80c6a699360
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\101918-9562-01.dmp
\\?\C:\WINDOWS\TEMP\WER-15515-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48C1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48D1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48E0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48F0.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_a7742ffe1cce9b7d3ccde74e573639caded6c25b_00000000_cab_1b84494d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 998a5294-e584-4ca2-bdbe-0f57f2461098
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
19/10/2018 21.59	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: d1
P2: 23c
P3: 5
P4: 0
P5: fffff80c6a699360
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\101918-9562-01.dmp
\\?\C:\WINDOWS\TEMP\WER-15515-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48C1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48D1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48E0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48F0.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_a7742ffe1cce9b7d3ccde74e573639caded6c25b_00000000_03c448ef

Analysis symbol: 
Rechecking for solution: 0
Report Id: 998a5294-e584-4ca2-bdbe-0f57f2461098
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

Name	NVIDIA GeForce GTX 1070
PNP Device ID	PCI\VEN_10DE&DEV_1B81&SUBSYS_85DC1043&REV_A1\4&38AB2860&0&0008
Adapter Type	GeForce GTX 1070, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1070
Adapter RAM	(1.048.576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f4187dc256a67a6b\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f4187dc256a67a6b\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f4187dc256a67a6b\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f4187dc256a67a6b\nvldumdx.dll
Driver Version	25.21.14.1634
INF File	oem9.inf (Section108 section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	1920 x 1080 x 60 hertz
Bits/Pixel	32
Memory Address	0xF6000000-0xF70FFFFF
Memory Address	0xE0000000-0xF1FFFFFF
Memory Address	0xF0000000-0xF1FFFFFF
I/O Port	0x0000E000-0x0000EFFF
IRQ Channel	IRQ 16
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_f4187dc256a67a6b\nvlddmkm.sys (25.21.14.1634, 19,39 MB (20.337.064 bytes), 05/11/2018 18.14)

Code:

nvlddmkm.sys Wed Oct 10 15:33:24 2018 (5BBE7E34)

Code:

nvlddmkm	nvlddmkm	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_f4187dc256a67a6b\nvlddmkm.sys	Kernel Driver	No	Manual	Stopped	OK	Ignore	No	No

Code:

nvlddmkm     nvlddmkm               nvlddmkm               Kernel        Manual     Stopped    OK         FALSE       FALSE        10.010.624        7.794.688   0          11/10/2018 00.33.24    C:\WINDOWS\system32\DriverStore\FileRepository\n 36.864

This particular DPC Watchdog crash is more difficult to debug because it is a type 1 where the system has spent a long time cumulatively on all the deferred procedure calls (DPCs) with IRQL set at the DPC level. The driver causing it is not always visible in the stack at the time of the crash. There is guidance on debugging these crashes in this link. As pointed out in the article the 0x133 bugcheck with a first parameter of 1 needs a full kernel memory dump and one where the Circular Kernel Context Logger ETW traces are enabled.

The first step is to extract the list of ETW loggers found in the memory.dmp using the "!wmitrace.strdump" command in WinDBG. Once the ID of circular kernel context logger is identified you can extract the logfile using the "!wmitrace.logsave (ID) (path to ETL)" command. You can then load this file into the Windows Performance Analyser (available from the Windows ADK kit) and look for all the DPCs that are taking longer than the allowed 100µs. The analyser will show which drivers are associated with these long DPC times.

I have done this for the latest crash dump and the following result is obtained from the WPA.


Attachment 212140

This shows that the two drivers causing long DPC times are dxgkrnl.sys and tcpip.sys. As these are not third party drivers it is not easy to suggest the next steps to fix this but it would seem to be connected with the graphics processes or network. The highlighted address for the graphics DPC can be used to find the corresponding entry in the stack.

Code:

0: kd> .load pde;!dpx
=========================================================================================
 PDE v11.3 - Copyright 2017 Andrew Richards
=========================================================================================
Start memory scan  : 0xfffff8022abe3958 ($csp)
End memory scan    : 0xfffff8022abe4000 (ISR Stack Base)

0xfffff8022abe3978 : 0xfffff8022b262378 : nt!KeDpcWatchdogProfileGlobalTriageBlock
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
0xfffff8022abe39b8 : 0xfffff8022aef41ad : nt!KiUpdateRunTime+0x5d
0xfffff8022abe3a08 : 0xfffff8022aef5293 : nt!KeClockInterruptNotify+0x8f3
0xfffff8022abe3a88 : 0xfffff8022b1ca118 : nt!KiClockTickTraces+0x138
0xfffff8022abe3bd8 : 0xfffff8022aef41ad : nt!KiUpdateRunTime+0x5d
0xfffff8022abe3c18 : 0xfffff8022b057c5c : nt!KiAcquireSpinLockInstrumented+0x64
0xfffff8022abe3d00 : 0xfffff8022b7cad60 : hal!HalpKInterruptHeap+0x8b0
0xfffff8022abe3d18 : 0xfffff8022b769883 : hal!HalpTimerClockInterrupt+0x63
0xfffff8022abe3d48 : 0xfffff8022af41d75 : nt!KiCallInterruptServiceRoutine+0xa5
0xfffff8022abe3d50 : 0xfffff8022b7cacb0 : hal!HalpKInterruptHeap+0x800
0xfffff8022abe3d88 : 0xfffff8022afbfd4a : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
0xfffff8022abe3d98 : 0xfffff8022b7cacb0 : hal!HalpKInterruptHeap+0x800
0xfffff8022abe3db8 : 0xfffff8022afc0237 : nt!KiInterruptDispatchNoLockNoEtw+0x37
0xfffff8022abe3dd8 : 0xfffff8022afc13e1 : nt!KiIsrLinkage+0x2c0
0xfffff8022abe3de0 : 0xfffff8034ad72e62 :  Trap @ fffff8022abe3de0
0xfffff8022abe3df8 : 0xfffff8022aef26f5 : nt!EtwpLogKernelEvent+0x225
0xfffff8022abe3ee8 : 0xfffff8022ae9b21c : nt!PerfInfoLogInterrupt+0xfc
0xfffff8022abe3f20 : 0xfffff80348a5b580 : dxgkrnl!DpiFdoLineInterruptRoutine
0xfffff8022abe3f48 : 0xfffff8022afbf8d9 : nt!KiScanInterruptObjectList+0xc9
0xfffff8022abe3fb8 : 0xfffff8022b7cacb0 : hal!HalpKInterruptHeap+0x800
0xfffff8022abe3fd8 : 0xfffff8022afbf5f7 : nt!KiChainedDispatch+0x37

You have already tried updating the graphics drivers so it looks as if we need to look elsewhere. I can't find the tcpip.sys function in the stack but this is usually related to network functions so I would suggest you try to update the rt640x64.sys driver for the Realtek Ethernet.

Looking at the Interrupt dispatch table (IDT) I did indeed find this driver mentioned:

Code:

0: kd> !idt

Dumping IDT: fffff8022abc8000

00:    fffff8022b0e4100 nt!KiDivideErrorFaultShadow
01:    fffff8022b0e4180 nt!KiDebugTrapOrFaultShadow    Stack = 0xFFFFF8022ABCC9E0
02:    fffff8022b0e4200 nt!KiNmiInterruptShadow    Stack = 0xFFFFF8022ABCC7E0
03:    fffff8022b0e4280 nt!KiBreakpointTrapShadow
04:    fffff8022b0e4300 nt!KiOverflowTrapShadow
05:    fffff8022b0e4380 nt!KiBoundFaultShadow
06:    fffff8022b0e4400 nt!KiInvalidOpcodeFaultShadow
07:    fffff8022b0e4480 nt!KiNpxNotAvailableFaultShadow
08:    fffff8022b0e4500 nt!KiDoubleFaultAbortShadow    Stack = 0xFFFFF8022ABCC3E0
09:    fffff8022b0e4580 nt!KiNpxSegmentOverrunAbortShadow
0a:    fffff8022b0e4600 nt!KiInvalidTssFaultShadow
0b:    fffff8022b0e4680 nt!KiSegmentNotPresentFaultShadow
0c:    fffff8022b0e4700 nt!KiStackFaultShadow
0d:    fffff8022b0e4780 nt!KiGeneralProtectionFaultShadow
0e:    fffff8022b0e4800 nt!KiPageFaultShadow
10:    fffff8022b0e4880 nt!KiFloatingErrorFaultShadow
11:    fffff8022b0e4900 nt!KiAlignmentFaultShadow
12:    fffff8022b0e4980 nt!KiMcheckAbortShadow    Stack = 0xFFFFF8022ABCC5E0
13:    fffff8022b0e4a80 nt!KiXmmExceptionShadow
14:    fffff8022b0e4b00 nt!KiVirtualizationExceptionShadow
1f:    fffff8022b0e4b80 nt!KiApcInterruptShadow
20:    fffff8022b0e4c00 nt!KiSwInterruptShadow
29:    fffff8022b0e4c80 nt!KiRaiseSecurityCheckFailureShadow
2c:    fffff8022b0e4d00 nt!KiRaiseAssertionShadow
2d:    fffff8022b0e4d80 nt!KiDebugServiceTrapShadow
2e:    fffff8022b0e4e00 nt!KiSystemServiceShadow
2f:    fffff8022b0e4e80 nt!KiDpcInterruptShadow
30:    fffff8022b0e4f00 nt!KiHvInterruptShadow
31:    fffff8022b0e4f80 nt!KiVmbusInterrupt0Shadow
32:    fffff8022b0e5000 nt!KiVmbusInterrupt1Shadow
33:    fffff8022b0e5080 nt!KiVmbusInterrupt2Shadow
34:    fffff8022b0e5100 nt!KiVmbusInterrupt3Shadow
35:    fffff8022b0e53a8 hal!HalpInterruptCmciService (KINTERRUPT fffff8022b7ca4b0)

50:    fffff8022b0e5480 storahci!AhciHwMSIInterrupt (STORPORT) (KINTERRUPT ffffd600784dcc80)

71:    fffff8022b0e5588 *** ERROR: Module load completed but symbols could not be loaded for TeeDriverW8x64.sys
TeeDriverW8x64+0x10e6c (KMDF) (KINTERRUPT ffffd600784dc640)

90:    fffff8022b0e5680 serial!SerialCIsrSw (KINTERRUPT ffffd600784dca00)

91:    fffff8022b0e5688 USBXHCI!Interrupter_WdfEvtInterruptIsr (KMDF) (KINTERRUPT ffffd600784dc780)

a1:    fffff8022b0e5708 *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
rt640x64+0x4e50 (NDIS) (KINTERRUPT ffffd600784dc8c0)

b0:    fffff8022b0e5780 ACPI!ACPIInterruptServiceRoutine (KINTERRUPT ffffd600784dcdc0)

b1:    fffff8022b0e5788 dxgkrnl!DpiFdoLineInterruptRoutine (KINTERRUPT ffffd600784dc3c0)

HDAudBus!HdaController::Isr (KINTERRUPT ffffd600784dc500)

ce:    fffff8022b0e5870 hal!HalpIommuInterruptRoutine (KINTERRUPT fffff8022b7cadb0)

d1:    fffff8022b0e5888 hal!HalpTimerClockInterrupt (KINTERRUPT fffff8022b7cacb0)

d2:    fffff8022b0e5890 hal!HalpTimerClockIpiRoutine (KINTERRUPT fffff8022b7cabb0)

d7:    fffff8022b0e58b8 hal!HalpInterruptRebootService (KINTERRUPT fffff8022b7ca9b0)

d8:    fffff8022b0e58c0 hal!HalpInterruptStubService (KINTERRUPT fffff8022b7ca7b0)

df:    fffff8022b0e58f8 hal!HalpInterruptSpuriousService (KINTERRUPT fffff8022b7ca6b0)

e1:    fffff8022b0e5180 nt!KiIpiInterruptShadow
e2:    fffff8022b0e5910 hal!HalpInterruptLocalErrorService (KINTERRUPT fffff8022b7ca8b0)

e3:    fffff8022b0e5918 hal!HalpInterruptDeferredRecoveryService (KINTERRUPT fffff8022b7ca5b0)

fe:    fffff8022b0e59f0 hal!HalpPerfInterrupt (KINTERRUPT fffff8022b7caab0)

I would appreciate it if other BSOD analysts could take a look and see if they can confirm my findings (axe0 or cwsink ?)

@philc43 - I think it might be a problem with the GPU. Core 0 looks like it was jammed for at least 2 minutes (which is the DPC timeout period) and there are no calls into nvlddmkm.sys in that entire extracted trace. For comparison, I ran a 1 minute trace on my own system while it was just sitting idle on the desktop and there were 18,332 calls into nvlddmkm.sys with the DPCs mainly being processed on core 0 and most originating from a dxgkrnl.sys ISR. Statistically, I would also expect to see some amount of nvlddmkm.sys calls in the sampled stacks on the other cores when a DPC takes over the thread running on those cores but I don't see any. It looks like the GPU is jammed for some reason.

I looked at the trace in both WPA and MXA (Media eXperience Analyzer) and they show the same thing. I was able to confirm in MXA that dxgkrnl.sys hadn't been called prior to the small portion at the end and even then, those ISR's don't seem to have become nvlddmkm.sys DPC's which I'm sure at least some of them should have done. I believe a DPC can timeout because it took too long doing lots of work but it can also take too long because it's stuck. My guess is some

nvlddmkm.sys DPC's were created prior to the trace but couldn't get processed. Or perhaps some other driver DPC's were waiting on a synchronization object that was never released - possibly held by something queued to be processed on core 0. There are probably other possibilities but those are the only things I can think of based on my understanding of trace analysis.

@scruptus - Based on what I described above, I think the next thing I would recommend trying is removing the Nvidia GPU and using the onboard graphics to see if you can reproduce the problem. Is that something you've already tried?

@cwsink Thanks for taking a look at this and for your suggestions. Let's see what the OP can tell us after reverting to onboard graphics.

Thanks for the in-depth analysis guys.

I'll remove my GPU tomorrow and see if that helps.