Random BSOD mostly during idle usage - DPC_WATCHDOG_VIOLATION

@philc43 - I think which are running and enabling/disabling different providers can be done via perfmon. This is a screenshot of mine which are the defaults of the providers installed on my system, for example.Attachment 226523

cwsink said:

@philc43 - I think which are running and enabling/disabling different providers can be done via perfmon. This is a screenshot of mine which are the defaults of the providers installed on my system, for example.Attachment 226523

Thanks for the suggestion, I did ask the OP to check and according to post #14 he does have the logger running. My next thought was that he had an insufficient size of dump allocated and that logging was not being recorded with the dump file.

So I enabled Kernel memory dump and uninstalled the Corsair Link Software wondering if this was the source of the issues. Still got a BSOD. Link to the Kernel memory dump and diagnostic information
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

I've also got a new test GPU, it's not the same as mine but it's from the same series so I'll see if it happens with the second GPU.

The latest BSOD bugcheck was 133 with parameter 1.
All BSOD to date have had the same bugcheck.

The mini and memory dumps debugging displayed a recurrent misbehaving hardware driver: Nvidia dGPU nvlddmkm.sys

The driver version during the crash was: 25.21.14.1935

This driver version has had two BSOD and a prior driver version had multiple BSOD.

The hardware swap should be helpful in identifying whether the problem is dGPU, port, or motherboard.

Code:

Name	NVIDIA GeForce GTX 1060 6GB
PNP Device ID	PCI\VEN_10DE&DEV_1C03&SUBSYS_85B61043&REV_A1\4&38AB2860&0&0008
Adapter Type	GeForce GTX 1060 6GB, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 1060 6GB
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a8e74171e1b8492\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a8e74171e1b8492\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a8e74171e1b8492\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a8e74171e1b8492\nvldumdx.dll
Driver Version	25.21.14.1935
INF File	oem16.inf (Section108 section)
Colour Planes	Not Available
Colour Table Entries	4294967296
Resolution	2560 x 1440 x 59 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_7a8e74171e1b8492\nvlddmkm.sys (25.21.14.1935, 19.78 MB (20,736,208 bytes), 05/03/2019 20:09)

Code:

nvlddmkm  Fri Mar  1 01:36:41 2019 (5C78E109)

Agreed. It seemed stable last night but that is also the rough use case observed after it does BSOD. I'm thinking after this it's likely to be the motherboard if I get another BSOD with the 1080 card.

So having swapped out the GPU I got another BSOD today. Not really sure what to think now, motherboard at fault? Software issues?

Logs and memory dump at Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
I've also included a clip of what happens to the sound during this time, this happens whether it's playing through the monitor (via graphics) or through a headset plugged in via 3.5mm jack.

I have checked both your recent kernel memory dumps and the circular kernel context logger is still not showing up so I can't look any further into the DPC delays.

From your most recent crash I can extract the list of dpcs:

Code:

0: kd> !dpcs
CPU Type      KDPC       Function
 0: Normal  : 0xffff978205b8eda8 0xfffff8036e831010 HDAudBus!HdaController::NotificationDpc
 0: Normal  : 0xffff97820b0ce0e0 0xfffff80371591f6c nvlddmkm
 0: Normal  : 0xffff978202d53c70 0xfffff8070e153780 Wdf01000!FxInterrupt::_InterruptDpcThunk
 0: Normal  : 0xfffff80365275568 0xfffff80365c8f1b0 nt!KiEntropyDpcRoutine
 0: Normal  : 0xfffff8036601db80 0xfffff80365d36530 nt!PpmCheckPeriodicStart
 0: Normal  : 0xffff978202e41a88 0xfffff8070ed066b0 ndis!ndisInterruptDpc
 0: Normal  : 0xfffff8036602f280 0xfffff80365c8be50 nt!KiBalanceSetManagerDeferredRoutine
 0: Normal  : 0xffff978202b237c0 0xfffff8036e1c1010 vmbusr!ParentRingInterruptDpc
 0: Normal  : 0xffff978202cee8b8 0xfffff8070f4b5110 storahci!AhciPortSrbCompletionDpcRoutine
 0: Normal  : 0xffff97820c286670 0xfffff8036e3948e0 dxgkrnl!DpiFdoDpcForIsr

This suggests that there are graphics, audio, network, bus and storage drivers all involved in DPC waits.

Have you thought of doing an in-place upgrade of your system keeping all your files and apps. This might fix any corruption or other problems associated with the operating system in case there is a driver or software component to this problem.

Repair Install Windows 10 with an In-place Upgrade