nixsrk caused system crash/reboot

[mcheatham]

I am using a PCI-6220 digitizer and DAQmx 8.6 to read input signals from a BNC-2090A board. After about an hour or so of recording/reading data from the digitizer, the system randomly rebooted and generated a memory dump file. I have attached the log file after running it through WinDbg.

The log file from this post a few months ago is very similar:
http://forums.ni.com/ni/board/message?board.id=170&message.id=293141

Has anyone else seen this kind of issue?

[Nathan_R]

Hi mcheatham,

Does this happen everytime you run your application or was this an isolated event? If it happens often try running an acquisition on the PCI-6220 using the test panel. This will remove your program from the equation and just test the driver installation and hardware. You can access the test panel for your card inside Measurement and Automation Explorer (MAX). MAX can be found under Start>>Programs>>Nationa Instruments>>Measurement and Automation. Once MAX is open you should find the PCI-6220 listed under Devices and Interfaces>>NI-DAQmx Devices. Right click and the PCI-6220 and select test panels. Setup the test panel with rates similar to your program. Let this run for several hours and see if it causes the computer to reboot also. Let me know if you have any questions and take care.

Thanks,

[Neil_S.]

mcheatham,

Thanks for bringing this crash to our attention.  Would it be possible for you to email me the crash dump?  Did you do a full memory dump, a small memory dump, or a kernel memory dump?  We can take a look at it with our symbols loaded in WinDbg and see what may have happened.  You can send it to me by sending the crash dump to mio.daq.pses at ni.com.  If it is too big let me know and we can probably see if we can have you upload it to our ftp server.

Thanks,

Neil S.
Product Support Engineer
Multifunction DAQ
National Instruments

[mcheatham]

Thanks for the replies. One of our sales reps happened to stop by yesterday, and we are also working with him to resolve this.

It seems to happen randomly, after about an hour+ of recording. I'll give the test panel run through a try.

The mini dump is also attached.

[Neil_S.]

M. Cheatham,

Thanks for posting the dump file.  Sorry for my delay in getting back to you on it.  I ended up also getting an email from your Sales Rep and have been working with Chris.  I took a look at the dump file yesterday and Chris D. should be getting back with you shortly to work with you on the issue. 

I figured I would also post my results here for other forum visitors.

A crash occurs if you try to start (actually reserve) a Digital Change Detection task that uses HWTimedSinglePoint timing mode and has channels that have already been reserved by another task.  I am not sure how this might happen in the your code, but looking at the crash dump and the DAQmx source code it seems like the most likely scenario.  Trying to reserve a resource that has already been reserved should generate an error and not a blue screen.  But in either case the code would not have run correctly.  Getting a bluescreen is definitely not expected behavior and should be fixed in a future version of NI-DAQmx.  I talked to Chris D. about filing a bug report to R&D.  In the meantime, I would recommend you work with Chris D. to see how the same resource can be reserved twice in your application and find ways to prevent this from happening.  This should prevent the blue screen from occurring.

Regards,

Neil S.
Multifunction DAQ PSE
National Instruments

[mcheatham]

We actually had one of our sales reps provide us with a different acquisition board (PCI-6221 I believe) and have not experienced any crashes since it was installed.

Pretty sure everything is resolved since the effects from before were detrimental to our recordings.

Anyway, thanks for your help!