I used to have this problem on one of my machines.
With V5, I would get the same error on the drives used by a media card reader - even when they were empty.
Just checked again, and with 6.0.1044, this does not happen. So maybe it was a bug in version 5 that Pondus mentioned. I thought it was something to do with the card reader and windows…