Hello slim1976,
It sounds to me that your device ended up in a bad state somehow. This can be caused by a large number of situations varying from your USB lost power for a second to not handling tasks properly (closing resources for example). It sounds like resetting your device fixed the issue, whatever it was. Instead of unplugging it, you can reset the device from Measurement and Automation Explorer directly or even programatically in your code.
If this is the first time you have seen this, I would not be too worried. If you can reproduce the behaivior, then the first thing I would suggest is to try and run an example program. If this does not cause the problem, then most likely it is something in the code. If it does occur in the example program, then that leads us to a driver/hardware issue. After that, we would go down the route of trying different computers/etc to try and isolate the issue.
Again, there are many causes for this, so I cannot tell you exactly what happened. Please post back if you have any questions or further concerns.
Neal M.
Applications Engineering National Instruments www.ni.com/support