Windows 10: BSOD Since Win10 1809 update, 0x133(1) DPC Watchdog Violation

Hi Guys,
Getting random yet sometimes frequent 0x133 (1) Bugcheck on my laptop since the win10 v1809 update. I had this several months ago, and the only way to fix it was to roll back to v1803, problem solved.
Forward to now, and I recently allowed it to update again, and again the bugcheck is back. Seems youtube aggravates it somewhat, or intensive web pages.
As I say, going back to 1803 everything is fine, it only happens in 1809. I just don't really want to have to keep rolling back. A friend suggested trying 1903, but I'm not sure.

Things I've done so far:
- Disabled fast startup.
- Upgraded graphics driver to intel v5063, made things worse.
- Downgraded graphics driver to the latest offered by Toshiba, v4300. Still happening, but not as often.
- Disabled windows update from updating drivers.

I've had a look at the dump in Windbg preview, and it's not very informative, more often than not it names acpi.sys, which is a bit vague. Also tried bluescreenview, which names hal.dll and igdkmd64.sys as suspicious.
I have included a link below to the most recent Memory dump which I believe has the circular logger information included in it. Perhaps if anyone could be so kind as to have a pick through it?
System specs filled in on profile.

Dropbox - MEMORY2.DMP - Simplify your life

Many thanks

:)

 

BSOD- DPC Watchdog violation

BSOD - DPC watchdog violation how to fix?

 

BSOD DPC WATCHDOG VIOLATION

According to what I found from your minidump file, ndis.sys is caused this
DPC WATCHDOG VIOLATION BSOD error on your Windows computer.It's a
NDIS 6.20 Wrapper Driver and installed onto your computer through Windows Update. As far as I know, you have installed new Windows updates lately.

You can uninstall those updates out of your computer, restart your PC and check again the result. Remember to do these steps in Safe Mode.

For more solutions to fix DPC watchdog violation BSOD error in case the above method doesn't work, check it out the following link below:

https://usefulpcguide.com/17082/dpc-watchdog-violation/

 

DPC Watchdog violation (0x133, 1) with Win10 1809

Hi -

I'm having sporadic blue screens, with stop code 133, 1 DPC WATCHDOG VIOLATION. Anecdotally this seems to have become an issue with Windows 10 1809. It only seems to occur with web browsing, most often when looking at media heavy pages - interestingly the
system will play CPU/GPU/memory intensive games absolutely rock-solid.

Some system details:

Intel i7-6700K (8 core)

32 Gb RAM

Gigabyte Z170X Gaming 3 motherboard

Gigabyte GeForce GTX 1070 G1 Gaming 8G

Intel SSD 600p 512Gb boot

Western Digital WD2003FZEX 1.8Tb data drive

Killer E2200 ethernet (part of motherboard)

Windows 10 Pro, x64, 1809 - Hyper-V enabled

Running Windows Defender, default settings

I have crash dump(s) available, including one with kernel circular logging enabled, happy to supply to MS. WinDbg !analyze points to nvlddmkm (see below), but as I understand it, these DPC watchdog violations are tricky to diagnose since Windows is complaining
of a cumulative error and the DPC itself could be servicing frequent interrupts.

I've tried just about everything I can think of - updating BIOS, removing/downgrading/upgrading NVidia drivers (now back to latest), updating SSD firmware, updating network drivers, disabling HDMI audio driver to no avail.

Note dumps vary, I have one where pretty much the only DPCs in the queue are ndis, dxgkrnl and nvlddkm. The ETL trace shows dxgkrnl flatlining CPU 0 prior to the bugcheck.

I'm at the point of thinking I need to change the graphics card, but before going down those lines it'd be great to get some confirmation of whether I'm looking at genuine hardware problem or not.

!analyze -v dump:

Code:

0: kd> !analyze -v

Code:

 0: Threaded: 0xfffff802329a30d8 0xfffff8023330f480 nt!KiDpcWatchdog

Thanks in advance,

Damian