I can confirm that this seems definitely to be a laptop-related problem. Kirben's and Dark-Star's workaround seems to work here too. Gonna try updating the drivers too. Thanks to the posters in this thread (and the search-button )!