IRQL_NOT_LESS_OR_EQUAL

[suni]

Hi

I have labview application which use visa functions, data aquisition functions, acquire joystick data fuctions. All i am doing is acquiring data form joystick, scale them and write it to serial port. In the same loop i am acquiring data from sensors and diaplay it in the front panel. I created executable for this application. It was working fine for a while. All of sudden exe made the computer crash. After running Microsoft (R) Windows Debugger test it said

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.

 Is it the daqmx driver that caused it?

Can somebody help me with this issue?

Thanks

[Steven_T]

Hello Suni,

Have you contacted anyone from NI Support about this problem?  If you have, what is the service request number?

One of the first things that will be necessary is a kernel memory dump.  This may tell us what driver caused the crash.  Once we kow the driver, we would need the exact version of the driver installed on your system.  From your description, it could be any of the drivers on your system that are in use by this application.

Use this KB for tips on getting a memory dump.

http://digital.ni.com/public.nsf/allkb/581127525C80606A862570BE0003111D 

Once you have the memory dump, you can place it on our ftp site (ftp.ni.com/incoming).  You can then let us know the name of the file through phone, email, or forum support.

Thanks,

Steven T.

Message Edited by Steven T on 08-19-2009 04:15 PM

[suni]

Hi Steven,

Thanks for the reply.

I have attatched the kernal memory dump file. I tried to place it in ftp.ni.com/ncoming. But I couldn't. Could you tell me how to do it? Thanks

[Steven_T]

Hello Suni,

The memory dump indicates that no NI drivers are directly causing this crash.  To narrow down what could be causing the problem, what NI hardware is being used with this application?

Specifically I am interested in any NI GPIB, NI Serial, or NI DAQ interfaces.

Thanks,

Steven T.

[suni]

Hi Steven,

I am using NI 6225M daq device. I am not using any Ni serial hardware. But I am writing to serial port using VISA function. Also I am using acquire joystick data function.

Thanks

[Steven_T]

Hello,

Since you are not using any NI hardware accept DAQ, that seems to be the only NI driver that could cause this problem.  I will alert someone from that group to look into this.

Steven T.

[Doug_L._Bear]

While I investigate this issue further, could you try running another application built with DAQmx and see if that causes the same results.  Try one with just serial.  That may be an easier way to narrow down the issue, can you run a VI on this machine, does that crash the computer, or just the executible?

[Seth_B.]

Hello Suni,

I had some of our DAQ R&D engineers look at the kernal dump and they weren't able to find any DAQ releated function calls.  If you are able to reproduce this, could you get us a complete memory dump instead of just the kernal dump and submit the file to ftp://ftp.ni.com/incoming?  This will allow us to run the memory dump file through a debugger to see if we can get more information.

Thanks,

[suni]

Hi Seth,

I've been running the exe program after this happened and it is working so far. If it happes again I will get the complete memory dump. BTW could you tell em how to get the complete memory dump? I don't have full LabView installed in this computer therefore I can't run any VI's in this machine.

Thanks,

Suni

[Seth_B.]

Hello Suni,

To set up your computer to give you a complete memory dump, do the following:

1. Select Start, right-click on My Computer, and select Properties. (You can also do this with the shortcut WindowsKey+Pause)
2. Switch to the Advanced tab and select Settings under Startup and Recovery
3. Under Write Debugging Information, select Complete Memory Dump.

This will put a complete memory dump in the C:\ drive if your computer BSODs again.

Regards,