GPIB Crashes XP

[cjholding]

We have recently updated our lab PCs to Windows XP SP2 from NT4.

In the past we would routinely run several applications on a single PC to control the various GPIB devices connected to it, for example one application to control a mainframe PSU and another to control a spectrum analyser. This software is both proprietry (e.g. WinCAL) and developed in-house, with CVI.

Since upgrading to XP the above scenario is no longer possible, if we do as suggested in my previous example and both applications attempt to communicate over GPIB simultaneous; to read the current from the PSU and the measurement from spectrum analyser for example; the PC will crash with a blue screen and the following error:

STOP: 0x0000008E (0xC0000047, 0x8051D1B8, 0xEE1ED658, 0x00000000).

This is completely repeatable.

I have made a kernel memory dump, as suggested in other topics, but at 68MB it is too big to attach here.

Windows XP SP2   5.01.2600

CVI Run-Time         8.0.1.356

NI-DAQ                    7.4.1f4

NI-488.2                   2.20

IVI Compliance        2.5

NI-VISA                    3.0.1

[Steven_T]

Hello cjholding,

It would be nice to get some more information regarding this crash.  I will need the version of the NI-488.2 driver you are using.  You can find this by checking in Measurement and Automation Explorer (MAX).  After opening MAX expand Software in the My System tree on the left.  Find NI-488.2 and click it to read the version number.

Also what type of interface are you using.  Is this a PCI, USB, Enet, etc?  

What types of commands are running on these applications?  Is serial polling involved are is it mostly reads and writes?  Are you using VISA API for communication or the gpib functions?  Are both applications using the same GPIB interface?

Thanks for any information you can provide.

Steven T.

Message Edited by Steven T on 09-21-2007 02:38 PM

Message Edited by Steven T on 09-21-2007 03:05 PM

[Steven_T]

Sorry for not seeing the version before.  You should probably upgrade to v2.5.  There have been many bug fixes that would prevent bluescreens.  Also, do you see any indication about the offending driver in the bluescreen?

Thanks,
Steven T.

[cjholding]

Upgrading to NI-488.2 v2.5 seems to have cured the problem, thank you.