You can always reload the driver and see if that helps. Others are complaining about similar issues so this could be a wider problem with 3.4e on some machines. If it is, well have to try to find a commonality and find a workaround.. sigh..