Sorry for the further spam, but this is an interesting (and annoying!) development...
After rebooting from the last BSOD, I tried running Wireshark, and received the usual error about the NPF server not running. However, after quitting it, I decided to try disabling the "Microsoft Network Monitor 3 Driver" (which seems to coexist with regular WinPCap, without problems), and ran "sc start npf":
C:\WINDOWS\system32>sc start npf
SERVICE_NAME: npf
TYPE : 1 KERNEL_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 0
FLAGS :
C:\WINDOWS\system32>
After waiting a little while, I started wireshark-gtk.exe, and discovered that the interface list was populated. However, after about 45 seconds, I received yet another BSOD:
==================================================
Dump File : 071915-30828-01.dmp
Crash Time : 19/07/2015 07:18:16 pm
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000099
Parameter 2 : ffffe001`e8f04148
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tm.sys
Caused By Address : tm.sys+e29ef9
File Description : Kernel Transaction Manager Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16384 (winblue_rtm.130821-1623)
Processor : x64
Crash Address : ntoskrnl.exe+150ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\071915-30828-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 9600
Dump File Size : 281,520
Dump File Time : 19/07/2015 07:20:06 pm
==================================================
Would be interesting to know why the BSOD occurs in the Kernel Transaction Manager, this time...
Tyson.
