Windows XP crashes with NI-488.2 2.4 Driver.

[maximo]

Our Windows XP systems crashes when our application tries to get SRQ status.

The systems have a PCI-GPIB board and connected to a prober.
NI-488.2 Driver is version 2.4. We found that it works with version 2.2 and 2.5.

Does anyone have any clue about what difference between drivers causes the crash?

Below is a bug check analysis done with the dump file.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {f7a65000, 0, b4bc39d6, 0}

*** ERROR: Module load completed but symbols could not be loaded for gpibprtk.sys
Page 1907a not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : gpibprtk.sys ( gpibprtk+49d6 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: f7a65000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: b4bc39d6, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------

Page 1907a not present in the dump file. Type ".hh dbgerr004" for details

READ_ADDRESS:  f7a65000

FAULTING_IP:
gpibprtk+49d6
b4bc39d6 8a1410          mov     dl,byte ptr [eax+edx]

MM_INTERNAL_CODE:  0

IMAGE_NAME:  gpibprtk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  42b998e7

MODULE_NAME: gpibprtk

FAULTING_MODULE: b4bbf000 gpibprtk

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  production_v305

TRAP_FRAME:  b4f768a0 -- (.trap 0xffffffffb4f768a0)
ErrCode = 00000000
eax=00000000 ebx=f7a64f00 ecx=0012b001 edx=f7a65000 esi=0012b004 edi=b4dbc068
eip=b4bc39d6 esp=b4f76914 ebp=00000001 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
gpibprtk+0x49d6:
b4bc39d6 8a1410          mov     dl,byte ptr [eax+edx]      ds:0023:f7a65000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 80528f24 to 8053738a

STACK_TEXT: 
b4f76838 80528f24 00000050 f7a65000 00000000 nt!KeBugCheckEx+0x1b
b4f76888 804e0944 00000000 f7a65000 00000000 nt!MmAccessFault+0x77e
b4f76888 b4bc39d6 00000000 f7a65000 00000000 nt!KiTrap0E+0xd0
WARNING: Stack unwind information not available. Following frames may be wrong.
b4f76944 b4bd0fba f7a65000 b4db9798 f7a67000 gpibprtk+0x49d6
b4f7698c b4bcffaf f7a67000 b4509204 b4db92e0 gpibprtk+0x11fba
00000000 00000000 00000000 00000000 00000000 gpibprtk+0x10faf


STACK_COMMAND:  kb

FOLLOWUP_IP:
gpibprtk+49d6
b4bc39d6 8a1410          mov     dl,byte ptr [eax+edx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  gpibprtk+49d6

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x50_gpibprtk+49d6

BUCKET_ID:  0x50_gpibprtk+49d6

Followup: MachineOwner
---------

[Steven_T]

Maximo,

Thank you for all of this information.  Has this application worked in the past?  If yes, what changed?

Do you happen to have a simple application that can reproduce the problem?  Does this problem happen on multiple systems?

I will be looking into this problem to determine the cause if we can reproduce it here.

Steven T.

[maximo]

Hi Steven,

Thank you for your post.
I wish I had a simple application that can reproduce the problem.
This involves our own application and the NI's GPIB driver.
It depends on the version of our application and the version of GPIB driver.
It happens when we combine the recent versions of our application with GPIB v2.4 driver.
It happens consistently on multiple systems.
It does not happen with GPIB v2.2 and v2.5.
The difference between the versions of our application is too big to look into.

We have concluded that the only way to find the cause is to ask NI to analyze the kernel memory dump.

-Masami

[JasonSmith]

What is the exact version of NI-488.2 v2.4 installed on your system when you see the failure?  I would recommend that you check the properties of C:\windows\system32\drivers\gpibprtk.sys to determine the exact version number, since that is the file listed in your dump.

Thanks,

Jason S.

[maximo]

The exact version of NI-488.2 v2.4 is 2.4.0307. Thanks, -Maximo