I analyzed your dumps, and it seems to be the NdisFOidRequest error. A full memory dump helps me to locate the exact error position (NPF_GetDeviceMTU function). I think I have fixed it, but as this crash can't be reproduced, I didn't test my fix. You can try it:
Thanks for your tests for the first two versions of Npcap, I have fixed several problems as following:
1) Npcap causes BSoD if you uninstall Npcap when Npcap is still in use for capturing packets.
2) Npcap can't start the driver automatically when system reboots in 0.02, now I have added this feature back.
3) Npcap lose many packets for loopback capturing in 0.02, like TCP data packets. Now I have fixed it and tested against TCP data transmission, UDP data transmission and Apache HTTP server (XAMPP).
4) "Npcap Loopback Adapter" can be successfully renamed in Win10.
I have tested this version Npcap under Wireshark 1.12.6 x64, in Windows 8.1 x64 and Windows 10 Insider Preview 10240 x64.
Notice:
1) You need to try it under Win7 and later, and no need to change the installation options, just click the "Next"s. Npcap installed in "WinPcap Compatible Mode" is exclusive with WinPcap, so you must uninstall WinPcap first (installer will prompt you this).
2) If you have installed WinPcap, better to reboot the PC after uninstalling Winpcap and then install Npcap.
like Tyson I experienced crashes when launching Wireshark v1.99.9rc0-29-g65a1f60 with Npcap 0.03 installed on Windows 7 x64 (did not face it on my Windows 10 x64 virtual machine). You will find 2 minidumps and a full memory dump here: https://www.dropbox.com/sh/2oz00ox20kv3oe0/AACFQC83vyKS2dY7bI7hnZBOa?dl=0
