Thats indeed a driver issue, I just produced this error
with a couple of machines here under various conditions.
But it might be also related to the .Net Framework.

Success is walking from failure to failure with no loss of enthusiasm.