Skip to main content

Some Windows 10 Anniversary Update PCs are crashing when connected to Kindles [Update]

Update: ZDNet received a statement from Microsoft on these crash reports.

"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."

A number of Windows 10 Anniversary Update PC owners are reporting Blue Screen of Death crashes when they connect them to Amazon's Kindle eReaders like the Paperwhite and Voyage.

Many Kindle owners have been trying to transfer ebooks to their PCs, but have instead been dealing with crashes on the latest major update to Windows 10. Some of those owners have posted their experiences to Microsoft's support forums (opens in new tab), (via The Guardian), such as the report from "Rick Hale"

On Tuesday, I upgraded to the Anniversary Edition of Windows 10. Last night, for the first time since the upgrade, I mounted my Kindle by plugging it into a USB 2 port. I immediately got the blue screen with the QR code. I rebooted and tried several different times, even using a different USB cable, but that made no difference."

So far, Microsoft has yet to comment on these issues. However, some Kindle owners are posting workarounds that have worked for some, but not everyone. One of them claims that just leaving the eReader plugged into the PC, and allowing it to reboot, solves the crashing problem. Another one states that plugging a Kindle into a USB 2.0 port, rather than a USB 3.0 port, can also work.

Are you experiencing any of these issues with the Windows 10 Anniversary Update crashing when connected to a Kindle eReader? If so, let us know in the comments, along with any workaround that have worked for you.

51 Comments
  • Ha, that sucks
  • That happens if you release too many builds too soon. Does not inspire confidence in the stability of windows OS. Every week my spectre is downloading something. And decouple the defender updates from OS update. Insiders can have patches to their heart's content, but spare others please, MS.
  • Um, Microsoft are providing monthly cumulative updates for production users, just as they did with previous versions of Windows. Also, this is just as much about the enormity of the Windows peripheral market as anything esle. Do you think that Microsoft are going to try connecting every possible eReader each time they have an update, regardless of how regular the updates are? Also, which build is causing the issue? If it's the original AU build then it how often they're releasing builds is even less relevant.
  • My Surface Pro 4 freezes every time a notification pops up. Can't dismiss it and then I have to reboot. I turned all notifications off hoping it resolves it.
  • That's weird... mine was getting frozen too, Transformer Book Flip TP300, especially when relating to network issues, and that was happened after I manually update it to Win10AU. But things are going to be okay after I refreshed that laptop, while having to install apps from scratch again. The thing is, resetting may help.
  • I've been experiencing the same issue with my Surface Book since the AU. Very frustrating because some times I have to keep hitting the Windows Key to get notification and action center unstuck (I know I made up a word :)  Another frustrating issue that I've been having since the AU; is audio and video playback. Sometimes Grove will not play audio or video will not play on websites whether I'm using Edge or Chrome or the Movies & TV App. Sometimes Cortana doesn't hear my commands or queries I have to reboot for the PC for it to work. The first time this happened; I took it to the Microsoft store and they installed some drivers. It worked well for a day but now it's back to the audio and video sporadically not working prompting me to do a restart. I did an online survey from Microsoft asking about my experience with Surface and I pointed out those issues. I also gave the opinion that when you pay a premium price for a Surface you'd expect that it wouldn't suffer from bugs from Windows update. You'd expect that Microsoft is using their own devices during programming and debugging for Windows builds and updates. That was part of the reason why I paid more for a Surface device over other OEMs or cheaper choices. I noted in the survey that when you buy Apple hardware for the most part vanity aside you buy it because you know or expect that it will work because Apple controls the OS and hardware and that I expect the same when it comes to Microsoft with Windows and their Surface devices. My Surface Book isn't the first time that I've had annoying issues with Windows 10. Last fall with my Surface 3 after Windows 10 was released last July their were issues that didn't get fixed until the "fall update" and then the "fall update" presented a new set of problems that didn't get fixed until December/January.  I understand that there are so many hardware out that runs Windows it's just that I expect Microsoft own devices to run Windows without issue. Maybe they'll get it together but these issues really make it hard for Microsoft to push Windows 10 and reach that 3 billion goal.  
  • I figured out a workaround: put PC to sleep before connecting kindle to it. Works like a charm.
  • Got my first Kindle today, connected to my Inspiron 13 7359, which has only usb3 ports, and had no BSOD. I've to try on others two pc's. They all have AU installed.
  • I get BSOD every time I plug in my Paperwhite 7th gen into any of the three USB ports on Anniversary Update Yoga 3 Pro. Workaround is to boot Windows with Kindle already plugged in.
  • Just tried plugging my boyfriend's Kindle to my XPS 13 and to my Venue 8 Pro (via the adapter). Nothing happened. Perhaps the fact that it can't be reliably reproduced is why it wasn't detected before.
  • I can reproduce every time, but some people have no problem.
  • Sounds to me like the device acts like a HDD, so plugging makes the system act like you did something you shouldn't do on a PC with HDD...so either new thing was made with old thing behaviors and it's just a product of consumer reluctance..? ;p
  • Same thing happens if you try to run a virtual machine.
  • Yea, can't seem to run Andy or Bluestacks anymore
  • Surface Pro 2 here and I'm running VMs daily without issues... Even from an external ssd drive. Fast ring, so I should have seen that before AU went global.
  • Have also been experiencing the same, VMs' just freezes and I have to restart. Happening since I got the AU
  • MS is doing a heckuva job. Sick "retrenching" in mobile too. Brilliant strategy to sell more phones by disappearing and selling fewer phones. /s
  • And ^^ THIS ^^ has what to do with the Thread/Topic... Move on !!!
  • We need a new post-release branch: "Release Prewiew" -> "Release" -> "Actually working thing"
  • Are you suggesting that previous versions of Windows and other OSes don't have any bugs?  If what you want is a perfect OS then you'll be waiting forever.  I haven't really had any significant issue with the Production build of Windows 10 AU so I'm rather glad that they didn't make me wait until they'd tested every possible eReader and every other Windows peripheral in existence for every possible scenario before releasing.  Fantastic suggestion though.
  • Happened to me with my gen2 Fire. Got the blue screen and code. Said looking for solution. The computer rebooted itself and has worked fine since.
  • My Surface 3 didn't recognise my Kindle Voyage at all...
  • Time to get a Kobo...
  • My lumia 830 camera crash after getting anniversary update, when i click in camera app its showing something went wrong, is there any solution?
  • Buy something with No Windows 10 Mobile in it.
  • Why don't you go to Android Central and stop whining here?
  • Because he's attention seeking. Just like all the other kids who slate Win10M on every article, even the ones with nothing to do with Win10m. It shows just how unoriginal they all are doesn't it? Lol. *All aboard the hate train! /s*
  • Try a hard reset. Go into Settings and search for 'back up' first and make sure you do it. You'll get the opportunity to restore during the reset process. Despite this you must still backup anything on your phone first to be safe. (Photos, saved downloads etc won't be backed up by the inbuilt software - just app settings for supported apps and what apps you had installed) Anoying, yes, but I've found that it fixed a number of problems for me.
  • It's not a common problem though
  • Really, people still buy Kindles? Posted via the Windows Central App for Android.. But waiting for the HP Elite so I can get rid of this junkie Galaxy S5...
  • They've sold way more Kindles than WPs...
  • They have sold way more WPs than Rolls royce cars. Your point?
  • Reading a book on eInk display is much easier on the eyes than reading from a tablet. I bought the Paperwhite just last year to replace the old 3G. If I could, I'd read WinCentral on the Kindle instead.
  • Yup...have a Kindle...love it...
  • How are issues like this slipping through all of the rings? Webcams and Kindles aren't uncommon devices, yet both of these are causing issues in the latest public release after being vetted by millions of Microsoft employees and Windows Insiders. Personally, I would like Microsoft do a public retrospective after the fix on why this happened and what they and we (as Insiders) can do to keep issues like this from getting through again.
  • Thats what happens when MS relies only on insiders for its testing
  • I'd love to hear YOUR suggestion. If even with the help of Insiders there are still bugs slipped through the release build, then there's not much else Microsoft could do, isn't it? Or you prefer the old way of Microsoft doing updates with one big update once every few years?
  • You have no idea how MS, or any company, works do you? MS have their own internal testing too. That's why insiders' don't receive every build (watch the build numbers. They don't always go up by 1, sometimes they can go up by 3, 5, 10 even). Insider's just help to find the hidden bugs that aren't as obvious as for example a "The start menu is buggy" bug in a fast ring build. (that's not actually a current bug, just an example). (And also help for suggestions for the OS etc)
  • When your upgrades become downgrades. Lovely.
  • Windows 10 is worst system ever
    Stay Windows 7 or 8.1
  • Compared to Windows 10, Windows 8 was flawless. Windows 10 such POS!
  • They need to bring Sinofsky back to clean this mess!
  • Good luck running W7 on Intel Kaby Lake then. Not supported.
  • They need to concentrate on fixing the bugs for a little while. No new features until bugs are squashed.
  • Works fine with my older Kindle Touch
  • Just don't plug it in.. why do you need to?  You can send things to your Kindle wirelessly...
  • Thats not the point
  • Maybe I should test mine
  • PowerShell was also broken recently. Apparently they forgot to add needed files to update pack. Incompetence of Nadella is staggering.
  • People will say it's not Nadella's fault. But when you're responsible for major cost "savings" by reducing QA and functional testing teams to bare minimum, and replace mostly with big data analysis via telemetry; yes, it is your fault.
  • My tablet is toast, not responding to touch, sound driver gone, would crash when trying to check or install update through windows update