Forum Discussion
New Contributorjtagserver.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
Super ContributorI am currently suspecting that the issue may be caused by either driver incompatibility or a USB‑Blaster III hardware‑related problem.
Could you help verify the following?
1. Driver installation
Have you installed the USB‑Blaster III drivers exactly as described in the user guide below, ensuring that both components were installed?
USB‑Blaster III driver (requires UART FTDI driver)
UART FTDI driver
User Guide:
https://docs.altera.com/r/docs/864466/current/usb-blaster-iii-fpga-development-cable-user-guide/connecting-the-usb-blaster-iii-fpga-development-cable
2. Try installing only the Programmer
Could you uninstall the entire Quartus Pro software suite and instead install only the:
“Quartus® Prime Pro Edition Programmer and Tools”
download link below (at "Individual Files" tab): https://www.altera.com/downloads/fpga-development-tools/quartus-prime-pro-edition-design-software-version-25-3-1-windows
3. Test with only the USB‑Blaster III connected. Please disconnect all other USB devices and hardware.
Then connect only the USB‑Blaster III to rule out interference from other peripherals.
4. Test a different USB‑Blaster III unit
Does the issue still occur if you try using another USB‑Blaster III cable?
5. Test on another Windows 11 machine
Does the same problem occur if you connect the USB‑Blaster III to a different Windows 11 PC?
I may need some additional time to reproduce this issue on my side.
Regards,
Richard Tan
New ContributorHi Richard,
thank you, for picking up this topic!
- yes, both were installed
- will try
- nothing else was connected before, just the Agilex3C evalboard, as soon as USB connection was made and JTAG server tried to communicate with it the system crashed
- It happens still, I tried with two evalboard
- It did not happen on a machine where Quartus was not installed (I know this is a too easy statement since jtagserver.exe was causing it according to minidump), I will try it on a different computer
So summary: 2,5: will be tried, 1,3,4: did not help further.
We have one more theory:
We are using the machine with products where there is FTDI chip inside (FT2232H and/or FT4232H), on the other hand since you program a custom VID/PID for USB Blaster III, theoretically it should pick up your own Intel signed driver and not a standard FTDI driver, since it will not know what it is exactly. (Unless there is an overlap in some .sys files between your intel signed driver and the standard FTDI driver package.)
For sure I will try it with a fresh computer and quartus installation too when we have more time, nevertheless there should be a way to make it work regardless of driver conflicts. Or at least it would be nice when it would fail gracefully and not with a BSOD.
Kind regards,
Peter
- RichardT_altera
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
