Whenever a process terminates without first stopping an output signal the PC locks up. The output waveform generation is started with a NI-DAQ WFM_Group_Control call.
This behavior is very consistent. It has been exhibited every time a process has initiated output and been terminated without stopping the output through another call to WFM_Group_Control.
In at least the two most recent instances the following was saved to the Event Log as part of the memory dump.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xbb4ec120, 0x0000001c, 0x00000000, 0xbb4ec120). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini10160
1-01.dmp. A previous instance had
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xbb48f120, 0x0000001c, 0x00000000, 0xbb48f120). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini100401-01.dmp.
Under Windows XP the lockup appeared to be deferred until the next NI-DAQ call following the offending processes termination.
Due to PC configuration problems having nothing to do with NI hardware or software ( network card ) NT 4 has not been tried yet.
It is never my intention to not stop the output signal but when debugging it can be difficult to avoid this situation. Additionally if a production user were to logout or terminate the process the lockup would be encountered.
Any suggestions or experiences shared are greatly appreciated,
Jack Metcalfe
