Tektronix Technical Forums are maintained by community involvement. Feel free to post questions or respond to questions by other members. Should you require a time-sensitive answer, please contact your local Tektronix support center here.
i think i have a serious driver issue with the KUSB-488B GBIP Adapter.
prior to my problem description, my environmental data:
OS: Windows 10 Pro
GPIB-Adapter: KUSB-488B (VID:05E6, PID:488B)
Driver: SCPI Command Compatible One
Driver-Version: 188.8.131.527 (as stated in Device Manager)
IDE-Platform: c# / Visual Studio 2015
Indicated Problem: Blue Screen (BSOD) / Source: usbxhci.sys
We developed a multi-device calibration Software which utilizes your Model 2002
for reference Measurements and several other devices as DUT's,
here especially mentioned several PXI-Measurement Cards from National Instruments within a PXI Chassis
which are connected via ExpressCard Bus and a Controller within that Chassis.
The Software uses Threading and works fine and stable whenever i only use one of the instrument interface-types.
But whenever i try to access both in parallel i have a BSOD occuring randomly.
The Blue Screen tells there is an IRQL_NOT_LESS_OR_EQUAL - Error caused by the File usbxhci.sys which is the
driver for the USB 3.0 extensible Host controller.
Whenever i only use the Model 2002 via GPIB Adapter alone or in parallel with other than NI Devices via ExpressCard everything is working fine.
Even the NI Stuff in Parallel with others than the GPIB Adapter connected Device works fine.
The Reason i tell it here in your forum is because i got to the conclusion that it only can be the Driver for the KUSB-488B.
I know that it can be a lot of all else usb-stuff connected, but disabling, removal, ... let me came to this assumption.
I even tried to connect via an old usb 2.0 Hub - but no changes using the generic usb hub.
After Hours of Investigation and Try-Outs where everything works fine (with other USB-connected Devices!) i can't
figure it out.
I read about your topic viewtopic.php?f=13&t=138576 concerning a beta-version of Windows 10 Driver
and recognized that there even is no official Support for Windows 10 or yet a download available for that beta-version.
I really don't know how to go on. Does anyone know if there's a Problem with it since Microsoft changed the USB Stack with the involvement of Windows 8.1?
I am only able to test on Windows 10 ... and we need it! I can't switch back to windows 7 for several reasons.
Is there a hotfix from Microsoft available concerning this issue? Do you have a newer driver version for me .. even beta?
Does there exist a work-around or known windows 10/8 issue with the driver?
A lot of posts for this BSOD exists on the internet. But all come down to kick-out the faulty drivers.
Common errors there are due to old drivers using the usb 3.0 extensible interface (usbxhci.sys)
My Chipset Drivers are up-to-date. Everything works fine, but not in parallel usage of the NI ExpressCard Controller interface.
Maybe someone discovered similar behaviour with the ni-pxi-stuff?
The last one chance that actually seems to may work for me is to use another gpib adapter. But i thought to have a good one!
The driver for the national instruments adapter provides actual drivers and are whql certified.
But I don't want to switch from SCPI to the NI Commands and have to change my adapter. In general i'd always prefer
non-NI solutions for several personal concerns.
Please give me any suggestions or hints where to search on. Everything seems to work well but not in parallel with the NI-Stuff.
I think there is a severe windows 10 driver problem.
Do you see any chances to fix it by using your announced beta-version of the driver?
if so, where can i get it?
Thanks to any answers ...
(Also I will send you a private message to get your contact info, send me a response if you would like a beta copy of the new driver)
- Keithley Applications
- Posts: 108
- Joined: September 22nd, 2010, 12:27 pm
- Country: United States
In the meantime, are you installing the KUSB-488B driver as "Keithley Command Compatible" or "NI Command Compatible"?
For what it is worth, my own experience has proven that "NI Command Compatible" works better with other NI drivers.
A Greater Measure of Confidence
Who is online
Users browsing this forum: No registered users and 1 guest