NI 488.2 Software V2.4 Cause BSOD but not V2.5

[NaoIri]

Hi
We have seen BSOD(blue screen of death) when we use SRQ under NI488.2 V2.4 environment.
If we installed V2.5, BSOD disappered.
We also found some statements on V2.5 readme file

--------------------------------------------------------

SRQ

If an event handler was installed to handle service request (SRQ) events, the events could fail to trigger if the session was currently locked exclusively. This has been fixed.

--------------------------------------------------------

Could you please give us more info on this bug information?

[Steven_T]

Hello Naolri,

The particular bug fix you are talking about has to do with locking a GPIB session using iblck.  When the lock was on when SRQ events happened, the handler could fail to launch or would not run.  This particular bug had nothing to do with a BSOD. 

I would like to get some more information about this crash.  What type of system are you running (manufacturer, model, os)?  Has this application worked in the past?  If yes, what changed in the system?  Can you reproduce the problem with a simple application (and possibly provide that application)?  What GPIB interface are you using?

Thanks for any information you can provide.

Steven T.

[NaoIri]

Hi Steven

This issue is same as what maximo submitted
    http://forums.ni.com/ni/board/message?board.id=140&message.id=25143

1. What type of system are you running (manufacturer, model, os)?
    ---> We are using two type of PC (Hitachi and PFU). Both PCs are not consumer model.
           We saw this same BSOD on both PC. so we believe this is not PC related issue.
           And OS is WindowsXP Professional (32bit)

2. Has this application worked in the past? 
    ---> Yes. NI488.2 Software V2.2 does not occur this BSOD.

3. If yes, what changed in the system? 
    ---> Yes. We just upgrade NI-488.2 software from V2.2 to V2.4

4. Can you reproduce the problem with a simple application
    (and possibly provide that application)?
    ---> Now this issue is occur under our software environment,
           it is bit difficult to simplify this application for now.
           However, we collected MiniDump file (see attached file).
           So we could give you more detail information.

5. What GPIB interface are you using?
    ---> PCI-GPIB


Below is the MiniDump data we collected.

----------------------------------------------------------------------------------
Microsoft (R) Windows Debugger  Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [\\XXXXX\XXXXX\DriverTrouble\TerPCInfo_PCshutdown\Auto\MiniDump\Mini080307-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Fri Aug  3 10:50:56.500 2007 (GMT+9)
System Uptime: 0 days 13:47:21.484
Loading Kernel Symbols
..........................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {f7a8f000, 0, b5aa09d6, 0}

Unable to load image \SystemRoot\System32\drivers\gpibprtk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for gpibprtk.sys
*** ERROR: Module load completed but symbols could not be loaded for gpibprtk.sys

Could not read faulting driver name
Probably caused by : gpibprtk.sys ( gpibprtk+49d6 )

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

0: 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: f7a8f000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: b5aa09d6, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS:  f7a8f000

FAULTING_IP:
gpibprtk+49d6
b5aa09d6 ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

TRAP_FRAME:  b548f8a0 -- (.trap 0xffffffffb548f8a0)
ErrCode = 00000000
eax=00000000 ebx=f7a8ef00 ecx=0012b001 edx=f7a8f000 esi=0012b004 edi=b6108068
eip=b5aa09d6 esp=b548f914 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:
b5aa09d6 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 805296be to 80537832

STACK_TEXT: 
b548f838 805296be 00000050 f7a8f000 00000000 nt!KeBugCheckEx+0x1b
b548f888 804e0f07 00000000 f7a8f000 00000000 nt!MmAccessFault+0x77e
b548f888 b5aa09d6 00000000 f7a8f000 00000000 nt!KiTrap0E+0xd0
WARNING: Stack unwind information not available. Following frames may be wrong.
b548f910 b61058d8 0012b004 00000000 f7a8efff gpibprtk+0x49d6
b548f9dc 804dc8da 8a0c4ad8 ffdff538 804dcc8b 0xb61058d8
b548f9e8 804dcc8b 8a0c4a00 804dca4f 8a2f7b08 nt!KiAdjustQuantumThread+0x68
b548f9f0 804dca4f 8a2f7b08 b548fa78 00000000 nt!KiUnlockDispatcherDatabase+0x1c
b548fab8 804dcc8b b5aba251 00000000 02783298 nt!KeWaitForSingleObject+0x2fe
b548fb74 80570593 b548fc30 805705c9 b548fc04 nt!KiUnlockDispatcherDatabase+0x1c
b548fbd0 00000000 804e62de 897baf40 897baf00 nt!KeUserModeCallback+0x87


STACK_COMMAND:  kb

FOLLOWUP_IP:
gpibprtk+49d6
b5aa09d6 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  gpibprtk+49d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: gpibprtk

IMAGE_NAME:  gpibprtk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  42b998e7

FAILURE_BUCKET_ID:  0x50_gpibprtk+49d6

BUCKET_ID:  0x50_gpibprtk+49d6

Followup: MachineOwner


------------------------------------------------

[NaoIri]

Sorry I forgot to attach the file

Message Edited by NaoIri on 08-15-2007 07:25 AM