Following the issues related to webcams on Windows 10 Anniversary Update, now some users are reporting that plugging in their Kindle to their PC running Windows 10 Anniversary Update is causing BSOD. This issue is affecting both regular Windows 10 Anniversary update users and those on the Windows Insider program.
“I recently the summer anniversary update for Windows 10 on both my laptop and my desktop which went without any errors. Today I plugged in a Kindle Paperwhite and it immediately crashed my laptop to a blue screen with a QR code regarding the sys_part_mgr or something similar. I figured it might be a driver issue even though my laptop is fairly new so I plugged it into my desktop and got the exact same thing. A blue screen of death. Just for more info’s sake it is a Kindle paperwhite being plugged into usb 3.0 ports on a HP laptop and Dell desktop both running the latest windows,” said Tucsat on Microsoft Support Forums.
There are several other similar reports from users across the web. “I’ve had a Kindle paperwhite for a few years no and never had an issue with connecting it via USB. However, after the recent Windows 10 updates, my computer BSOD’s [blue screen of death] and force restarts almost as soon as I plug my Kindle in,” said an user on Ten Forums.
Some users have suggested an workaround for this issue. You need to plug-in your Kindle when your PC is in sleep mode or before switching on your PC. After doing this, when you wake up your PC or switch it on, your Kindle will get connected to your PC without any issue and you can even transfer books to Kindle if you want.
Microsoft is yet to respond to this issue and we will update the post once we hear it back from Microsoft.
Update: Microsoft has confirmed the issue and they are working on a fix. Read their statement below.
We are aware of an issue with a small number of Kindle Voyager and Paperwhite e-Readers causing an unexpected behavior when plugged into Windows 10 devices after installing the Anniversary Update. We are currently working on an update to address this issue.