We are currently using two different NI boards the USB6215 and USB6002, we use the same software with both boards but are seeing intermittent blue screens with the USB6002 only (at the moment)
The blue screen details are
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.
If kernel debugger is available get stack backtrace.
Arg1: ffffbe0094d746e4, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80513b43dfb, address which referenced memory
At the moment we are un able to locate which DAQmx call may be causing the issue, It appears to happen when the system is starting up, but we have had reports that it has happened after the system has run for a little while.
we have tried NI versions from 18.0 to 2022 Q3 and all cause the same blue screen.
We have seen the crash on Windows 10 and Windows 11
Our application is a 32bit application written in C++
If anyone could give us some ideas of how to track this down and fix, it would be greatly appreciated
The question would be whether this is reproducible with any DAQmx example or soft front panel or just your application.
If reproducible with any DAQmx example or soft front panel, it would be worth raising a support ticket for NI Engineers to take a look at.
Unfortunately it varies a lot as to how often it happens, we have just had a week pass with out a blue screen but then had two in one day.
I could sit there opening and closing the examples for a week and it might not happen, but will spend some time trying this.
So I guess what I was after is if anyone else had seen anything similar with a crash coming from nifslk.dll?
If this dll narrowed down which calls could be causing the issue and hence maybe a bad parameter we are passing?
Any other wisdom on tracking down blue screen crashes.
Sorry only just seen your message.
We have reinstalled the drivers multiple times, used a number of different versions and seen it on multiple systems so I don't believe it's a problem with the install