Windows 10 Computers Crash When Amazon Kindles Are Plugged In (theguardian.com)

It appears that many users are facing an issue with their Windows 10 computers when they plug in an Amazon Kindle device. According to reports, post Windows 10 Anniversary Update installation, everytime a user connect their Amazon Paperwhite or Voyage, their desktop and laptop lock up and require rebooting. The Guardian reports:Pooka, a user of troubleshooting forum Ten Forums said: "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." On Microsoft's forums, Rick Hale said: "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."

Comments

Even tried a different USB cable

[Anonymous Coward]

Best results will be obtained by using Monster (tm) brand USB cables.

Re:Lets...

[npslider]

Did you try rebooting your speakers?

Re:Lets...

[sirber]

You can: choose Linux.

Study finds that 75% people pushing Linux on others aren't actualy using Linux.

Take action

[karmawarrior]

I'm probably not the only one here who's getting sick and tired of hearing about yet another major Windows bug that we can't do anything about. While Microsoft makes their operating system even less stable, update to update, it also makes it harder for us to even pick the updates that we know work and leave those we don't aside.

That's a serious problem, and downtime due to computers crashing, needing to be reformatted and their operating systems re-installed, together with the time taken for users to learn about these problems and investigate workarounds, costs the world economy trillions every year. In this case the user loses whatever functionality lead them to wanting to plug a Kindle Fire into their Windows PCs in the first place, again having a real cost associated with it.

Yet while we waste time waiting for our computers to reboot, we feel helpless, unable to investigate workarounds or other ways to achieve the results we want.

This quagmire of people being unable to fix the problems caused by bugs and other issues will not disappear by itself. Resources need to be devoted, and unless people are prepared to actually act, not just talk about it on Slashdot, nothing will ever get done. Apathy is not an option.

You can help by getting off your rear and writing to your congressman or senator. Tell them your concerns about bugs in Windows 10. Warn them that trillions of dollars are being lost because of these issues. Tell them this is important to you. Tell them that you appreciate the work being done by organizations like Microsoft and Amazon to fix the bugs, but that without better QA and more reliable drivers, you will be forced to use less and less secure and intelligently designed alternatives. Explain the concerns you have about freedom, openness, and choice, and how vicious, angry, arguments undermines all three. Let them know that this is an issue that effects YOU directly, that YOU vote, and that your vote will be influenced, indeed dependent, on their policies on bugs in Windows 10.

You CAN make a difference. Don't treat voting as a right, treat it as a duty. Remember, it was thanks to ordinary people like YOU that we are now seeing such innovations as SMP in OpenBSD. Keep informed, keep your political representatives informed on how you feel. And, most importantly of all, vote.

Taking Care of the Competition

[Sperbels]

Does this mean MS has a competing e-reader coming to market?

Re:Signed drivers?

[squiggleslash]

So you're saying there's code in there along the lines of:

void usb_insertion_handler(string vendorid, string modelid, usbcontext context) {
. Driver d = DriverDB.find("usb/" + vendorid + "/" + modelid);

. if(d.signed()) {
. . d.load();
. . d.init(context);
. } else {
. . // alert("Driver not signed, device inserted in " + context.description + " cannot be used at this time"); -- 02/03/16 ska - not Microsofty enough

. . // Events.WriteEvent("usbsubsystem", "Driver unsigned, not loaded 0x80039193"); -- 02/10/16 jrh - good, those idiots will probably search for that number, sucks to be them when there's nothing on our website about it, hahahaha! -- 02/11/16 ska - not good enough, try again

. . System.BSOD(); // Crash, because clearly there's no better way to handle this problem
. }
}