Microsoft Surface Book Plagued With GPU Issues
It has only been a few days since Microsoft’s latest Surface Book, which the company claims to be the ultimate laptop, launched and there are already reports coming in from users about issues that plague the extremely expensive device and end up turning it into nothing more than a paperweight.
Among the many issues, one that has been reported by most users involves the notebook to suddenly stop working, randomly and the only solution right now seems to be a complete power cycle of the device. Although that still doesn’t fix it and the Surface Book will stop responding again pretty soon.
Microsoft has yet to issue a fix for the problem or clarify that what exactly could be causing the problem but some inquisitive users have taken it upon themselves to figure that out and it seems to stem from the October 23rd update, KB3097617, which added support for Windows Hello technology.
On the other hand, Microsoft representative are advising users to install any and all updates that the company releases in order to avoid such issues.
Another prevalent issue involves the screen of Surface Book to continuously flicker and turn off, especially when Hyper-V virtualization is enabled; something the machine should be able to handle easily given its specification.
Some users are also reporting that the Windows as well as Nvidia’s software fail to detect a discrete GPU for the device until the clipboard is undocked and then redocked. What’s even funnier is that sometimes the device even fails to register the clipboard having been detached.
Microsoft has positioned the Surface Book as the “ultimate laptop,” amid reports that company is apparently wrestling with a problem of keeping Book units stocked within stores. And bugs are not exactly uncommon where Microsoft devices are concerned.
Even though the Surface Pro 3 helped drive Microsoft’s Surface sales to hundreds of millions of dollars per quarter, the tablet was plagued by overheating bugs soon after its launch. But like those issues were resolved, let’s hope Microsoft gets a handle on these as well, and soon.