Nick,
The EEPROM on your device stores some general information about your device as well as calibration information for it. The driver has detected that some value in this EEPROM have changed unexpectedly (this could be due to an access to it when the computer froze). What has changed however is not clear. Because of this you have several alternatives. The best thing you can do is externally calibrate the device. This will overwrite all calibration information stored in the EEPROM, and insure that all of your calibration information is valid. This operation should work regardless of the current state of the EEPROM. If this is not an option, then there are several DAQmx functions you can run that will have the side-effect of resetting the EEPROM sanity check. However, if you were to run one of these, although you will no longer get the error, if your calibration values have become invalid, then you will most certainly loose measurement accuracy. I believe that if you change user info (Calibration property node) or change the user calibration password the driver will reset the it's sanity check. However if you choose this route, make sure you thoroughly test your device to ensure that your measurements are correct.
So once again, my strong suggestion would be to externally calibrate the device. If it's really not an option, try one of the other function calls, then test your device thoroughly.
I hope this helps,
Dan