uffe:
You seek...Yoda...Help you...I...will..
This is a kernel mode problem with your NIDAQ32.SYS driver. I believe
that you can pretty much rule out problems with LV5.1.1 or app
builder. Your problem
You have run into a classic BSOD message. It may not always occur so
it can be really frustrating to diagnose. There may be some
workarounds you can implement at the application level but it still
needs to be fixed at the kernel (O/S) level so you're going to need to
contact NI.
I've had this same problem error message in the past but not with DAQ
cards. As I recall, in one case there was a problem with a spinlock
in the SCSI driver (.sys) file which protected access to the hardware
I was using.
What is a spin lock? A spin lock is a special synchronization
construct used by device driver developers to protect access to
critical sections of their code usually for hardware access. It is
the kernel mode equivalent to a VISA resource lock or a semaphore in
LabVIEW.
For more on spin locks see:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/kmarch/hh/kmarch/k101_97hu.asp
Work-around Possibility #1: Do you have two different parts of your
code trying to access the DAQ card simultaneously? If so, providing
your own VISA resource locks or semaphores at the application level
may cure the problem even if the kernel mode driver is failing to
protect access to the card like it should.
Even if this fixes the problem PLEASE report it to NI so that they can
fix it properly in the .sys file and let other users know that the
workaround I suggested works.
See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/network/hh/network/103ndisx_7mk2.asp
Work-around Possibility #2: I don't know the details of setting up
your DAQ card so if this question doesn't make any sense don't worry
about it. Are you setting up the card with some empty array, zero
memory size, or empty string value or something? I had this problem
with a reflective memory card driver.
Sometimes this can screw up a driver that isn't checking for this sort
of thing with the result of it trying to reference a null ptr or
something. Again, even if you fix the problem by error checking the
values before you give them to the DAQ driver VI, make sure you tell
NI about it.
This explanation also jibes with what Microsoft has to say on
IRQL_NOT_LESS_OR_EQUAL. See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/w2kmsgs/6077.asp
3) There may be other explanations for your problem but these are two
that I've run into personally. Try going to www.microsoft.com and
doing a search on IRQL_NOT_LESS_OR_EQUAL if my two possibilities
aren't the cause of your problem.
4) Make sure you have the latest driver from NI for the NIDAQ. NI may
have already fixed your problem in a later version of the NIDAQ
driver.
5) Also I would recommend making sure that you have the latest service
pack (SP6A) installed or that you go ahead and upgrade to Win2000. As
I recall when I had my one of my driver problems it was with an
earlier SP release and upgrading SP's helped.
6) If none of these suggestions help, you need to call NI help line
(800-IEE-E488) and report this to see if they know about it so that
they can give you a work around and see if they can recreate the
problem and then fix it.
Doug De Clue
LabVIEW developer
ddeclue@bellsouth.net
uffe wrote in message news:<5065000000080000001B550000-1027480788000@exchange.ni.com>...
> I get IRQL_NOT_LESS_OR_EQUAL.
> Address fc792324 has base at fc6f8000 Nidaq32.sys and Address fc7028e3
> has base at fc6f8000 Nidaq32.sys.
>
> The system is running on Windows NT 4.0. The application is built
> using Application Builder and LabView 5.1.1. The NIDAQ 6.9.0 is used.
>
> Please help me.
