LabVIEW
Remote PC Experiences BSOD when issuing reboot command to Real Time Controller
During development of my Real Time LabVIEW application I need to reboot my PXI-8106 embedded controller several times a day to check the built application after deployment. I usually reboot by right clicking on the RT target in my project and selecting Utilities>Reboot. This works very well, but once in awhile I have experienced the dreaded "Blue Screen Of Death" (BSOD) on my development PC as a result of the RT target rebooting! After much research and some reasoning I think I have discovered the problem and am presenting my solution here for any of you that experience the same problem.
It seemed to me when I first saw the BSOD, in this case more accurately described as stop 0x00000044, "MULTIPLE_IRP_COMPLETE_REQUESTS", that there was something wrong with my development laptop, as typically the resolution of stop error 44 usually points to a device driver that is at fault. However, a few minutes spent thinking this through led me to believe that this should not be the case, since the BSOD coincided with the reboot of the RT target, and the only link (in theory) between the two devices was either TCP or UDP messaging (or some other NI-VISA layer). For reference, I am connected to the RT target by a cross over cable and a USB to ethernet adapter that always has the same address assigned to it to prevent conflicts with my company's ethernet network. A deep dive into the problem on the NI website was not much help, and the one link I could find turned up one article that might have applied, and that article can be found at http://digital.ni.com/public.nsf/allkb/922DDC440FCB15048625719D006FCB97 . Basically, my reasoning was that whatever was causing this was being sent from the RT Target to my development PC as a result of the rebooting process and whatever that was, was the cause of the BSODs (I can make this happen pretty frequently without the fix).
The article sited above says that the gateway setting should be left blank - and here is where I think the problem came in. I had the gateway set to the address of my USB to ethernet adapter. My theory is that somehow, something that is included in the blast of TCP / UDP message traffic or other communications used by NI-VISA, etc., during the reboot of the RT Controller was causing the problem and subsequent BSOD. By disabling the gateway setting in MAX, I may be avoiding being the target of whatever messaging goes out on a reboot to the gateway. It seems to be working so far in that I haven't seen a BSOD since implementing my fix.
Hopefully posting this will save someone else the trouble I went through to find an explanation (and fix) for the problem.
Bill
Bill,
Thanks for sharing your solution with others.
Happy Holidays!
