Amazing, this is still an issue even after I bug reported it during the tech test back in May. Microsoft blew me off and said it was any number of random driver interactions. I do not have a fix yet....