|
@Kovid, if JeanPaolo booted in safe mode (he said he did) then A/V is out of the picture.
I am not willing to take video drivers out of the equation, or any other driver for that matter. It is easy to imagine that the first time some driver is used in a "different" way it could lock up, taking the machine with it. Later some system auditing thread (I think windows has one of these) could come along and reset the driver, after which it doesn't do the problematic "thing" again.
Another problem area could be IO bus scans triggered by some user-space event. Some device (or driver) could lock up, taking the system with it until the aforementioned auditor breaks it loose.
A third could be fonts. I think that fonts are rendered in kernel space. If this is true, and if something triggers a full font reload, and if some font is malformed in some way, then the reload could hang until it was broken loose.
All wild speculation, I admit.
Question: is there a way to start calibre without starting the device scanner? I looked at the code and didn't see anything already made. I tried commenting out lines 888 and 889 in gui2.device, which seemed to work in that the scanner didn't run and calibre didn't complain.
|