Quote:
Originally Posted by NullNix
What does this mean? While it is possible to determine how physical memory is fragmented, or how any one process's virtual memory is fragmented, neither of these things are particularly meaningful, nor is either a persistent thing: both are cleared on reboot.
...
Never, ever defragment flash. It cannot help and is sure to prematurely age your flash chip -- and since the Kindle's flash is not user-replaceable, that means prematurely aging the Kindle itself.
(Disk fragmentation cannot cause bluescreens anyway. It's routine and ubiquitous and, even on rotating storage, is only harmful to performance when there's a lot of it.)
|
It is the Windows pagefile which was fragmented into over 60,000 fragments. A user managed pagefile of fixed size is persistent, and not cleared on reboot. Even if it were system managed, clearing on reboot was an option to be chosen, at least up to Windows 8.1. I avoid a system managed pagefile as these are prone to fragmentation. The fixed size user manage pagefile only fragments on BSOD, which was not a problem until this Kindle connection issue.
The Kindle is not being defragmented. The BSOD occurs immediately the USB connection is plugged in. I am reluctant to try fixes such as plunning in before boot or while sleeping. I reboot infrequently, and even one BSOD is more hassle than I need.