This is exactly the same that happens to me.
Consequences of registering a kobo aura edition 2 windows#
To work around the problem I am closing Calibre before I want to copy books across, and dragging-and-dropping manually in Windows Explorer. I have reset the Kobo to factory settings twice, but it didn't help. I also have a Kindle Paperwhite Gen 3 which does NOT exhibit the problem on the same laptop. It's only after Calibre opens that the blue screen happens. It happens with all three ports, and with any USB cable that I've tried.Īgain, the connection works perfectly without any issues using Windows Explorer. This laptop only has USB 3.0 ports so I cannot test it on USB 2. This happens whether I have Calibre running first and then connect Kobo, or if I open Calibre after the Kobo is connected. When I run Calibre with Kobo connected (and without any other apps open), after 30 seconds or less I get a blue screen of death with this error: Using the Kobo Windows app also works without issues. I can leave it connected indefinitely without any issues. I can browse the file structure, copy on new files, delete files etc. So whether it was Intel chipset specific, or just resolved, I couldn't say.Ĭalibre 2.77 (problem has existed with all older versions too)Īccessing the Kobo via USB without Calibre running works perfectly. I now have a new Lenovo laptop (also with only USB3 ports), and the problem is gone. You can also copy all the files on the device when connected and restore them after the factory reset and checking things are working. If you do this, you lose the reading status for sideloaded books, and have to reload them. There is a fair chance that a factory reset on the device will be needed. When does it crash? Straight away or after a bit of time? Can you see which of the connect jobs are running?.Are you up to date with the Windows fixes?.What version of calibre? 32bit or 64bit?.Have you restarted the computer and device?.Have you tried a different USB port or cable? Or another computer?.It probably won't find any problems, but if it does, this might be the solution. If the problem is that Windows wants to run a check on the disk, do it. And if it isn't, then it needs to be eliminated as the cause. What is the problem that Windows is reporting? My guess would be whatever that is is the real problem and causing the later crash. It is not happening here with any of mine. I don't think I have heard of anything similar with a Kobo device.
0 kommentar(er)
