Hey Ward,
Does your computer happen to have an AMD processor? If so, which model specifically?
We’re aware of a very rare issue with a recent Windows update that causes this OS-level error when trying to run FireControl. It seems like the Windows update introduced a bug that is affecting certain processors. One user was able to resolve the issue by simply uninstalling and reinstalling FireControl - other have found success by updating their CPU drivers or computer’s BIOS. Keep in mind that the latter two are relatively drastic steps.
Unfortunately, due to the rare nature of the issue combined with the fact that it stems Windows - not FireControl itself - at this time all we can do is provide suggestions that might work and collect data that may help us formulate a consistent fix.
There’s also an ongoing thread about this issue that I’ll be keeping updated whenever we get new information: