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

zbook said:

Please upload DM log collector

Requested DM log.

The first V2 log collector did not collect the mini dump file.
The DM log collector was able to collect it.
Please upload another V2

zbook said:

The first V2 log collector did not collect the mini dump file.
The DM log collector was able to collect it.
Please upload another V2

New V2 log.

The misbehaving driver while Windows driver verifer was used was Netwbw02.sys.

Code:

NETwNb64     ___ Intel(R) Wireless  ___ Intel(R) Wireless  Kernel        Manual     Running    OK         TRUE        FALSE        741,376           2,138,112   0          29/04/2019 16:02:27    C:\WINDOWS\system32\DRIVERS\Netwbw02.sys         4,096

Code:

Name	[00000001] Intel(R) Dual Band Wireless-AC 3160
Adapter Type	Ethernet 802.3
Product Type	Intel(R) Dual Band Wireless-AC 3160
Installed	Yes
PNP Device ID	PCI\VEN_8086&DEV_08B3&SUBSYS_81708086&REV_CB\E4F89CFFFF508B7E00
Last Reset	08/06/2019 21:56
Index	1
Service Name	NETwNb64
IP Address	192.168.1.65, fe80::f0ba:24b5:a6be:6c0d, fdaa:bbcc:ddee:0:49b4:5906:e177:e6dc, 2a00:23c6:a10f:3a00:49b4:5906:e177:e6dc, fdaa:bbcc:ddee:0:f0ba:24b5:a6be:6c0d, 2a00:23c6:a10f:3a00:f0ba:24b5:a6be:6c0d
IP Subnet	255.255.255.0, 64, 128, 128, 64, 64
Default IP Gateway	192.168.1.254, fe80::a608:f5ff:fe67:b249
DHCP Enabled	Yes
DHCP Server	192.168.1.254
DHCP Lease Expires	09/10/1932 12:26
DHCP Lease Obtained	08/10/1932 12:26
MAC Address	‪E4:F8:9C:50:8B:7E‬
Memory Address	0xB1100000-0xB1101FFF
IRQ Channel	IRQ 4294967289
Driver	c:\windows\system32\drivers\netwbw02.sys (18.33.17.1, 3.36 MB (3,521,016 bytes), 12/10/2018 15:25)

Code:

netwnb64	___ Intel(R) Wireless Adapter Driver for Windows 8.1 - 64 Bit	c:\windows\system32\drivers\netwbw02.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes

Code:

Netwbw02.sys Mon Apr 29 10:02:27 2019 (5CC71203)

This misbehaving driver was the same version as the earlier misbehaving version.
See post #41.

Make sure Windows updates of non-Microsoft drivers is off:

Enable or Disable Driver Updates in Windows Update in Windows 10

See if you find a different version than prior misbehaving versions.

If you can find another version then the driver can be tested.

If a third driver fails then replace the hardware.
If the hardware is built into the motherboard the find a USB wireless card.

I have had the WU driver update disabled for some time now.

Ok I'll try going back to 18.20.0.9 again (the "latest" (2015) one from the Toshiba site).

It puzzles me though, why does rolling back to 1803 fix the problem? Is the way 1809 handles drivers different somehow? Also this would suggest it's not a hardware fault?

See if turning off core isolation memory integrity makes any difference: (see post #6)
Turn On or Off Core Isolation Memory Integrity in Windows 10


An additional option is to upgrade to 1903 to see if it makes any difference.

Just checked, core isolation memory integrity is already off.

OK so I've gone up to 1903, and after a day, same deal. However, this time on checking the memory dump, it appears to contain the circular logger trace (at ID 0x02), if examining that could help?
Below: memory and ndis dumps.
Attached v2 and DM logs.

MEMORY13.zip - Google Drive
NDIS-20190613-1119.zip - Google Drive

The NDIS dump was bugcheck 15E.
The misbehaving driver was again Netwbw02.sys

If the hardware can be swapped or replaced then swap or replace.
If the hardware is attached to the motherboard and cannot be swapped or replaced the find a USB option.

Code:

Netwbw02.sys Mon Apr 29 10:02:27 2019 (5CC71203)

Code:

Name	[00000002] Intel(R) Dual Band Wireless-AC 3160
Adapter Type	Ethernet 802.3
Product Type	Intel(R) Dual Band Wireless-AC 3160
Installed	Yes
PNP Device ID	PCI\VEN_8086&DEV_08B3&SUBSYS_81708086&REV_CB\E4F89CFFFF508B7E00
Last Reset	13/06/2019 23:00
Index	2
Service Name	NETwNb64
IP Address	192.168.1.65, fe80::f0ba:24b5:a6be:6c0d, fdaa:bbcc:ddee:0:29a4:5386:1094:ed8a, 2a00:23c6:a10f:3a00:29a4:5386:1094:ed8a, fdaa:bbcc:ddee:0:f0ba:24b5:a6be:6c0d, 2a00:23c6:a10f:3a00:f0ba:24b5:a6be:6c0d
IP Subnet	255.255.255.0, 64, 128, 128, 64, 64
Default IP Gateway	192.168.1.254, fe80::a608:f5ff:fe67:b249
DHCP Enabled	Yes
DHCP Server	192.168.1.254
DHCP Lease Expires	19/10/1932 14:33
DHCP Lease Obtained	18/10/1932 14:33
MAC Address	‪E4:F8:9C:50:8B:7E‬
Memory Address	0xB1100000-0xB1101FFF
IRQ Channel	IRQ 4294967289
Driver	C:\WINDOWS\SYSTEM32\DRIVERS\NETWBW02.SYS (18.33.17.1, 3.36 MB (3,521,016 bytes), 30/04/2019 17:31)

Code:

netwnb64	___ Intel(R) Wireless Adapter Driver for Windows 8.1 - 64 Bit	c:\windows\system32\drivers\netwbw02.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes

Code:

NETwNb64     ___ Intel(R) Wireless  ___ Intel(R) Wireless  Kernel        Manual     Running    OK         TRUE        FALSE        741,376           2,138,112   0          29/04/2019 16:02:27    C:\WINDOWS\system32\drivers\Netwbw02.sys         4,096

I have now found another old wireless driver, 17.5.0.5. Trying that now.

As I've said before though, w10 1803 works flawlessly with all the drivers I have used so far. There is a problem with a driver(s) compatibility with 1809 and onwards.

Have you been able to extract the ckcl trace from the last memory dump?