jtagserver.exe causing BSOD together with ftdi driver

Does the BSOD still occur if you never power‑cycle the eval board?

I’m asking because the behavior you’re seeing is consistent with a mixed‑FTDI driver environment, which is a plausible root cause.
Even though the USB‑Blaster III uses an Intel‑signed INF with a custom VID/PID, both Intel’s package and the standard FTDI CDM packages typically load the same kernel‑level bus driver: ftdibus.sys. This SYS file is shared across many FTDI‑based devices.

If Windows has multiple FTDI packages staged (e.g., one from Intel’s USB‑Blaster III and others for FT2232H/FT4232H products), the system can:

-Select a different FTDI package on re‑enumeration (after a reboot or cable power cycle).
-End up loading a different ftdibus.sys build (older or incompatible) for the same hardware instance.

This aligns with your observation that a clean reinstall temporarily resolves the issue, but the crash returns later.
Could you check whether multiple versions of ftdibus.sys exist on the machine?

Regards,
Richard Tan