Is it possible for a 1394 camera to change driver association on its own?

[MS08]

I have a customer who experienced a strange problem with his LV application and Unibrain 1394 camera.  The program has typically worked fine, but on one occasion, it became unresponsive and had to be aborted (ctrl-al-del).  The operator vaguely remembers seeing a windows message that led him to believe windows had changed the driver associated with the device.  I realize this seems a bit vague, but it's all the information we have, and I thought I'd see if anyone had encountered similar problems.  If so, is there any way to disable the other drivers (listed as legacy and generic in MAX)?

Thanks

[Robert_Eastlund]

I have seen a similar situation.  Does your customer have the NI driver and the camera manufacturer's driver installed? 

[MS08]

Thanks for the reply, Robert.  I'll have to answer now (and confirm later) based on the development machine we have here, which I am confident matches the customer's.  It has NI-IMAQdx 3.1.0 but no driver for the camera that I can find in device manager or in the list of programs.

[Robert_Eastlund]

Although, I am not certain what initiates the problem, I have seen a camera manufacturer's driver activate on its own.  The occurance seems to be random.  The solution was to uninstall the camera manufacturer's driver.

[MS08]

I will ask the operator to check for the camera mfg driver.  Thanks again for the quick responses.

- M