Runtime Error R6025 and DAQ-Driver

[Salvator]

Operating System Windows2000

Teststand  Version 3.0
DAQ-Driver  6.9.3f5
Serial Driver  1.7
LabvIEW RTE build with LabVIEW 6.1

hello,

we have build a testsytem based on LabVIEW and Teststand.
We use the NI-PCI boards 6713, RS232/16 and MIO-164E. We dont use any operator interface, only the
original Teststand sequence-Editor and the Single-Pass Prozess-model.
It works very fine for  e.g. a whole week running and then

,suddenly, the ERROR Window pops up :

"Window-Head: Microsoft Visual c++ Runtime Library

RUNTIME ERROR

Programm ...\National Instruments\Teststand3.0\Bin\SeqEdit.exe
R6025
- pure virtual function call"

After pressing the OK-Button, the Computer will boot and generate a memory-dump.

We have analyzed the dump-file with the Microsoft WINdbg Tool.

The Bugcheck Analysis reported an error with the Nidaq32k-Driver !!

What should/can we do ?

See below the analysis report:

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

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for Nidaq32k.SYS -

OVERLAPPED_MODULE:  kmixer

FAULTING_IP:
Nidaq32k!mdsSimpleDIGPortPrimitive::_accessCheck+600
bc4370a0 c745fcffffffff   mov     dword ptr [ebp-0x4],0xffffffff

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0xCB

LAST_CONTROL_TRANSFER:  from 804bce30 to 80440665

STACK_TEXT: 
bc175c54 804bce30 80064bd4 00000000 804bd199 nt!MmCleanProcessAddressSpace+0x421
bc175d04 804bd1b3 00000000 84973a28 80431261 nt!PspExitThread+0x4e1
bc175d10 80431261 84973a28 bc175d48 bc175d3c nt!PsExitSpecialApc+0x1a
bc175d4c 80465bfa 00000001 00000000 bc175d64 nt!KiDeliverApc+0x158
bc175d4c 77e017da 00000001 00000000 bc175d64 nt!KiServiceExit+0x58
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f7a4 00000000 00000000 00000000 00000000 0x77e017da

STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
Nidaq32k!mdsSimpleDIGPortPrimitive::_accessCheck+600
bc4370a0 c745fcffffffff   mov     dword ptr [ebp-0x4],0xffffffff

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  Nidaq32k!mdsSimpleDIGPortPrimitive::_accessCheck+600

MODULE_NAME:  Nidaq32k

IMAGE_NAME:  Nidaq32k.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  3f39592e

FAILURE_BUCKET_ID:  0xCB_Nidaq32k!mdsSimpleDIGPortPrimitive::_accessCheck+600

BUCKET_ID:  0xCB_Nidaq32k!mdsSimpleDIGPortPrimitive::_accessCheck+600

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

[RobertH]

hello frank,

do you have older versions of the LV RTE installed on your system?

take a look at this thread. maybe the removal of an older LV RTE solves the problem.

regards,

robert h
national instruments

[Salvator]

Hello Robert,

the windows 2000 system control shows only two LV RTE`s:

- Version 7.0 ( i think needed, an installed during Testand installation process...)

- Version 6.1 , installed for our application by me

I before already deleted old versions (I dont know from where they are ... ?) , because I knew the older thread with the R6025-Error ...

But:  the MAX (Version 3.0) shows additionally the LV RTE Version 6.0 !

Could this be the problem ?

thanks for help and best regards

[RobertH]

hello,

could you try to remove this old version with the msiBlast tool, which is also linked in this thread?

regards,

robert h
national instruments

[Salvator]

hello,

unfortunately the msiBlast tool dont indicate the LV RTE 6.0 !, too.

See attachment  .pdf file for all installed applications

So it seems to be a other problem of the MAX Version 3.0, showing a LV RTE, which does not exists.

(The expected folder ...\shared\LabVIEW Run-time\6.0 is not present, too.)

Nevertheless i dont have any idea to solve the problem with the R6025 Error ?

Note: In case of manually killing the LV TS RTE within the windows system control (testsequence is running) , a blue screen with error indication for nidaq32k.sys arises !?

regards