Windows 10 Blue Screen Crash

[mrspaceman]

I have Calibre 2.71 install in windows 10 build 14931.

when I open Calibre. it works fine.
when I plug in , Kobo Aura One, I can mount and update it's storage.

But, If I start Calibre with the Kobo mounted, windows blue screens with a FAT_FILE_SYSTEM error.
if I plug the Kobo in with Calibre running it also blue screens.

Has anybody else seen this. it seems similar to the "Windows Anniversary Update blue screens when an ereader is plugged in" issue

[JSWolf]

Which version Windows 10 are you running?

[mrspaceman]

version 1607
build 14931.1002 (64 bit)

[gabaldini]

Try formatting your kobo device,or a factory resetting

[kiwik]

The Kobo will not work with a USB 3.0 port and Calibre.

If your laptop does not have USB 2.0 ports (like mine), simply purchase a USB 2.0 hub and use that.

For more info, see this thread:

https://www.mobileread.com/forums/sh...d.php?t=282881

[jackie_w]

Originally Posted by kiwik

The Kobo will not work with a USB 3.0 port and Calibre.

Whilst this may be your personal experience, it's certainly not universal. All my Kobos are working with calibre and USB 3 ports on my ASUS Windows 10 laptop.

[PeterT]

I wonder if there might be difference in USB drivers; Microsoft supplied in one case vendor in others for instance?

[gbm]

Originally Posted by PeterT

I wonder if there might be difference in USB drivers; Microsoft supplied in one case vendor in others for instance?

I do not know about the drivers but using the proper usb3 cables is a must.

See my post here

benie

[JSWolf]

Originally Posted by gbm

I do not know about the drivers but using the proper usb3 cables is a must.

See my post here

benie

That's USB C cables that need to be properly made. I've never had a cable problem with USB 1, USB 2, and USB 3. The cable that comes with a Kobo Reader works.

Cable issues with USB C is why when someone says we should have a USB C port on Kobo, I say no way.

[BetterRed]

Originally Posted by PeterT

I wonder if there might be difference in USB drivers; Microsoft supplied in one case vendor in others for instance?

But why is 'that' an issue only for calibre?

kiwik for example, is able to access his Kobo e-reader via the USB 3.0 ports on his Dell with the Kobo desktop application and File Explorer, but not via calibre.

Maybe he should try using the drivers from Dell, his Windows install was from MS media, so presumably he has MS source drivers.

BR

[PeterT]

All I can think is that calibre stresses the device. Would be interesting to stress the Kobo at the o/s level without calibre and see what happens.

[BetterRed]

Originally Posted by PeterT

All I can think is that calibre stresses the device. Would be interesting to stress the Kobo at the o/s level without calibre and see what happens.

Can the Kobo be used with calibre natively, i.e. without the extended driver, utilities, input/output etc plugins, or are one or more of them mandatory?

If it can, are we certain that the problem is not being caused by one or more of them rather than the calibre base.

BTW : I kicked myself when you suggested kiwik try a USB 2 hub. I should have thought of that, I acquired a Dlink 7 port hub recently, it's attached to a spare USB 3 port (Hitachi controller).

BR

[davidfor]

Originally Posted by BetterRed

Can the Kobo be used with calibre natively, i.e. without the extended driver, utilities, input/output etc plugins, or are one or more of them mandatory?

If it can, are we certain that the problem is not being caused by one or more of them rather than the calibre base.

BTW : I kicked myself when you suggested kiwik try a USB 2 hub. I should have thought of that, I acquired a Dlink 7 port hub recently, it's attached to a spare USB 3 port (Hitachi controller).

I can think of two ways this is happening. Calibre is discovering the device in such a way that it triggers a bug in a driver. The alternative is the way the driver reads the database on the device is putting stress on the driver or connection somehow. But, I can't really see it being either. The former I think would hit other devices as well, the latter should cause a problem when using the Kobo desktop application. And it doesn't seem to be any of the other plugins. At least one tester has removed them, and the crash happens to early for them to be involved.

The people who have reported this say they can access the device using explorer. And copy books to it. And they say the Kobo desktop application is OK.

[kiwik]

It failed (on Dell laptop with Intel chipset) with both the Windows certified drivers that were auto downloaded, and also with the Intel drivers that I manually installed. I can try the ones from the Dell site.

I set my USB ports to be 2.0 in the BIOS and that worked perfectly on the same install.

I work in IT with these same laptops every day (500 users), and the only time I have ever seen this fastfat.sys crash is with Calibre + Kobo. I mention this because we have a ton of USB devices, it seems that this is the only combo to make this problem appear. I just can't imagine what is causing it. Kovid confirms that Calibre doesn't use any low level calls, just normal filesystem operations.

But yes to confirm, absolutely no issues using the Kobo with Windows explorer and USB 3.0.

[davidfor]

Originally Posted by kiwik

It failed (on Dell laptop with Intel chipset) with both the Windows certified drivers that were auto downloaded, and also with the Intel drivers that I manually installed. I can try the ones from the Dell site.

I set my USB ports to be 2.0 in the BIOS and that worked perfectly on the same install.

I work in IT with these same laptops every day (500 users), and the only time I have ever seen this fastfat.sys crash is with Calibre + Kobo. I just can't imagine what is causing it. Kovid confirms that Calibre doesn't use any low level calls, just normal filesystem operations.

But yes to confirm, absolutely no issues using the Kobo with Windows explorer and USB 3.0.

I can't remember if you said before, but how quick is the crash? Is it as soon as calibre detects the device or does it happen as one or more of the device jobs are run? Is the behaviour different if the device is connected when calibre is started vs connecting when calibre is already running?

And which device and firmware? It's not in your profile and I didn't see it in your first couple of posts in the other thread (and yes, I'm sure it will jump out at me as soon as I press the post button.)