bluescreen in win2K (nipalk.sys)

[baki]

STOP 0x0000001E (0xC0000005, 0xBFE3D8B8, 0x00000000, 0x00000014)
KMODE_EXCEPTION_NOT_HANDLED
Address 0xBFE3D8B8 base at BFE27000 DataStamp 3CD9AE48 nipalk.sys

All worked fine with installed NI-488.2 Version 2.0 and a PCI-GPIB card.

Two weeks ago I installed NI-DAQ Version 6.9.3f3 but yet no Hardware (The PCI1200 is waiting on my desk). Since this time I have often bluescreens caused by "nipalk.sys" while debugging with MSVC++.

thanks

Babak Pourat

[mikeb]

I am seeing the same thing after installing NI-CAN 2.0, but I do have a NI PCI-CAN/2 card installed already. I have tried to uninstall in safe mode (using Add/Remove programs) but, despite going through the motions of uninstalling the files, registry entries, and start menu entries are all still there.

[logman]

Babak,

Do you have anymore information about what you are doing when you receive the Blue Screens? NI-DAQ generally is very stable (especially if there isn't a DAQ card in the system), so my guess is that either your installation of NI-DAQ is corrupt, or something about Windows 2K is corrupt. I will lean toward NI-DAQ being corrupt, which means you will probably want to do a complete uninstall and reinstall of it. The uninstalls of NI-DAQ tend to leave a bunch of information behind, so you will probably need to delete the registry entries for NI-DAQ after you uninstall it. Here is a link to a KB which tells how to do this: Deleting NI-DAQ from R
egistry

Good Luck!

[Jeremiah Cox]

Hello Babak,
When you encounter a system crash while using National Instruments products (for example if the crash only happens when you are using NI hardware and/or software or the crash indicates a software module named "ni..."), I strongly recommend that you contact National Instruments Technical Support as they are best prepared to assist you in resolving this type of issue. The crash that you are experiencing looks to be a new issue that we have not seen before. However, the driver that you are using is a bit out of date. I would strongly recommend that you upgrade to NI-488.2 2.1 and/or NI-DAQ 7.0 by visiting http://www.ni.com/downloads/. Either one will upgrade you to a newer version of NI-PAL which I anticipate will solve this problem (the code where
your crash occurred has been rewritten and tested to new limits).

Sincerely,
Jeremiah Cox
Staff Product Support Engineer -- Platform Services
National Instruments -- http://www.ni.com