Unfortunately it is hard to tell what's causing this. It may be the driver that is a part of Connection Emulator, though it is unlikely as we have not heard about BSODs for years. More likely it is some other driver in your system that is "surprised" by the removal of our driver from the networking stack.
Theoretically you could try unbinding the driver manually from network connections. For this, please access the Properties of each network connection and uninstall the driver as shown in the screen shot below. Then remove the software itself via Add/Remove Programs.
If that does not help, it may be easier just to keep the software in the system. It does not consume any resources when not used, and takes very little space.