apart from trial-and-error (or trying another PC), it's tricky - I suppose we could try to capture a list of the DLLs loaded into the SharpCap.exe process and see if there is anything in the list that looks unusual (ie not normal Microsoft/Windows stuff, not stuff that SharpCap itself wants).
We could try using procdump (https://learn.microsoft.com/en-us/sysin ... s/procdump) to make a crash dump of the process when it hits the error (or when it exits) - you could then send me the crash dump and I can see if I can spot anything unusual loaded up in the DLL list.
Download procdump from the page linked above, unpack it and then run the following from a command prompt window:
Code: Select all
"c:\path\to\procdump.exe" -e -t -w sharpcap
thanks,
Robin