We did nothing, but it's good to hear that it works now. If the bug occurs again, the next thing would be trying a different driver as suggested above.