Plugging in Kindle is crashing Windows 10 after summer update
answers.microsoft.com
answers.microsoft.com
Andrew Tanenbaum's arguments for microkernels still ring just as true today as they always did.
A kindle is just a USB drive, though. And that driver is probably kernel mode for performance reasons.
I recall they did a major overhaul like that for audio drivers too.
As for micro-kernels, at least they have won in the embedded and real time space, with the likes of QNX, L4 and a few others.
BTW, beyond the exciting development stuff that they are releasing there are a lot of issues inside the company. For example, they made it almost impossible to renew my company MSDN Premium account after talking with support guys for weeks.
Perhaps it's not this time, but I personally think Microsoft should do a better job of naming and shaming when third party drivers/software are responsible for crashes. Maybe even form a special team that looks out for stuff like this on forums, does root cause analysis, and maintains a wall of shame (as well as fixing customer issues).
Luckily there's a work-around so I can still connect to the Kindle with Calibre; just connect the Kindle _before_ starting Windows, then it will not crash, and also still work as an USB drive. [1]
[0] http://www.tenforums.com/bsod-crashes-debugging/60314-bsod-c...
[1] https://www.amazon.com/forum/kindle?_encoding=UTF8&cdForum=F...
Is your system completely vanilla (mine were fresh installs onto empty drives from official media), or could your OEM have snuck something in?
I'm not saying you're wrong, or that Windows isn't to blame. There just must be more to it than Windows 10 anniversary update + Kindle Paperwhite. Maybe you and others affected have some other thing in common.
I do have iTunes installed which apparently was the issue for some users. Others have also reported the getting the crash without that though. But I don't intend to try uninstalling it and see if that resolves the problem, I connect the Kindle so seldom that the work-around will do for now.
EDIT: now that I think about it, Kindles don't come with power adapters anymore, do they? So users would probably still be connecting the Kindles for charging purposes.
My mouse would double click instead of click, had to drop enhanced power mode in using the device manger on every USB port.
I got BSOD when going full screen on youtube - had to disable hardware acceleration.
I got BSOD when pressing F5 in powerpoint....
I lost the ability to open the start menu after SP1 - a problem that exists since windows 8... I had to revert to the previous build.
If the new Microsoft means no QA... I'd rather have the old one....
These symptoms seem like something might be up with your hardware.
Grab something like WhoCrashed and you may be able to find the culprit
If there's anything Microsoft is consistent about, it's inconsistency.
Well, unless you fancy digging around in the Registry, but yeah, they removed the GUI-toggle for it.
More seriously, though, the biggest thing is that they added Ubuntu-support with this update. The rest of the features are pretty boring.
The first such sub-version release was 1511 (i.e. a build from 2015, November), and this Anniversary Update is version 1607 and happens to be one year after the release of Windows 10, which is why they called it "Anniversary Update".
That said, my household switched to a mix of Gentoo Linux, EdgeOS and iOS. We do not have things crash when USB devices are attached. :)
That said, my household uses a mix of Linux, Windows 10, various IOT, and Android. I don't have things crash when USB devices are attached; sometimes they just don't work on the *nix machines.
http://blog.davidelner.com/dual-booting-ubuntu-14-10-on-the-...
Anyway, for my own anecdote - I have a five year old Dell XPS L502X that has an Optimus style video card in it - Windows 7, 8 and 10 run beautifully on it with no drivers problems. Meanwhile, any Linux distro I've tried to install directly on the hardware just barfs itself.
An Asus Eeebook bought with Ubuntu pre-installed in 2012, everything should work out of the box, right?
Actually no, from the time I bought it until the wlan driver worked properly took around 6 months.
I just kept it and constrained myself to LAN during those months instead of returning the laptop, because I wanted to somehow support GNU/Linux on laptops.
So yeah, driver support. It still sucks, just not as bad as 96. Honestly, I remember it better in 96 since the hardware was simpler you could usually get everything to kind of work.
My NAS runs CentOS and I have Arch/Ubuntu on my home pc's, but I still dual boot Windows on one because gaming.
The 'I wonder who else will switch to Debian 8 like me' just struck me as comical.
I would be extremely surprised if MS lost any meaningful amount of marketshare from Win10, especially to linux distros.
Do Chromebooks count?
it was initially a pain to get working, however over the past 12 months the tooling has improved a great deal, in virt-manager you can now assign your graphics cards/sound card/... with 1 or 2 clicks, and it simply works!
MS are free to spy on me playing Starcraft II in a VM, and I try to support Linux with my new purchases wherever possible.
I might very well write a blog post, as quite a few people have asked
Besides games I'd love to be able to have a daw working well with asio and so on, as in virtualbox this does not work very well unfortunately (I guess realtime audio is not an easy problem to solve when vms are involved)
audio was the hardest thing to get working smoothly... I have two soundcards, pass one through to Linux, and have a 5cm cable from the output into the line-in of the second card, which has hardware mixing so comes straight out the speakers with no pulseaudio involvement. needed a few registry hacks too (which I can't recall)
quite a few people report success with HDMI audio output, but my monitors are too old for this, so I haven't tried it
Another popular option is Synergy (https://github.com/symless/synergy) but I never used it.
Here's what I feel about each Windows release I've used much (1=low, 10=high):
+-----------------+-------------+----------------+-----------+
| Windows Version | Expectation | Disappointment | Usability |
+-----------------+-------------+----------------+-----------+
| 3.1 | 5 | 2 | 8 |
| 3.11 | 7 | 3 | 6 |
| NT 3.51 | 7 | 5 | 7 |
| 95 | 6 | 3 | 7 |
| NT 4.0 | 7 | 3 | 9 |
| 98 | 7 | 2 | 8 |
| ME | 7 | 7 | 6 |
| XP | 8 | 3 | 8 |
| Vista | 5 | 5 | 4 |
| 7 | 4 | 3 | 6 |
| 8 | 6 | 8 | 2*|
| 10 | 8 | 6 | 4 |
+-----------------+-------------+----------------+-----------+
* - marred by experience w/Surface RTI would have expected that expectation would have started going down after each disappointment.
The freedom these operating systems give us is something I think should be emphasised more as people tend to focus on the technical challenge.
I was just waiting to see how Windows 10 would evolve, because I don't really want to use Linux at home but it seems that's the way I will have to go.
I am on MS OSes since MS-DOS 3.3. So far only skipped MS-DOS 4, Windows ME and Vista.