Looking at drwatson logfile, can you tell me why my app crashed?

[RudyRed]

I recently updated one of our PC test systems to SP4 (WIN2kPro). It has AMD cpu > 1 GHz, 256 MB RAM. It ran a test for the past 13 days then my LabVIEW app crashed this morning. The drwatson logfile pins the rap on my LV app. I wonder if it had something to do with the recent update of the OS (just before starting the test). The event log shows there was not a reboot, and the drwatson log shows the same time as the last entry in the data file the test was producing. Does anyone at National Instruments know how to use the drwatson log file to discover the direct cause of the crash?

[Jeremy Braden]

For questions like these, you are better off contacting NI directly. Goto www.ni.com/ask for directions. It has been my experience that Dr. Watson error logs are only useful as sublimentary information. It is best for support and for the forum if you can provide a clear description on how to cause the error consistantly.

[RudyRed]

Thanks for the response, Jeremy. Actually, I've not had this situation before with this app, so I don't know how to cause it...I'm just wondering if it might be related to the latest MSWIN2k updates--after which windows informed me that I had improperly unplugged a USB device called, "NIPAL"!!! I'll try to find the time to pursue this matter, as you've suggested.

ER