Understood, thanks, but is there a difference in the underlying mechanism by which FFS copies a file from my hard drive to my USB memory stick compared with me doing it manually in File Explorer? That might help me to identify the problematic driver.
Appreciate your help.
Search found 3 matches
- 07 Aug 2015, 15:43
- Forum: Help
- Topic: BSOD with Windows 10 and FAT32 memory sticks
- Replies: 6
- Views: 759
- 07 Aug 2015, 13:37
- Forum: Help
- Topic: BSOD with Windows 10 and FAT32 memory sticks
- Replies: 6
- Views: 759
Re: BSOD with Windows 10 and FAT32 memory sticks
Thanks. I had seen that page, and the two soultions are to run chkdsk /f /r on the drive (which I have done, with no errors), or to add memory (I have 12Gb RAM, and wasn't running anything else, so nonpaged pool memory depletion is unlikely to be the issue).
Also, a driver bug wouldn't explain why ...
Also, a driver bug wouldn't explain why ...
- 07 Aug 2015, 11:20
- Forum: Help
- Topic: BSOD with Windows 10 and FAT32 memory sticks
- Replies: 6
- Views: 759
BSOD with Windows 10 and FAT32 memory sticks
Recently upgraded to Windows 10 and running FFS 7.3.
Whenever I try to sync files from my hard drive to a memory stick which is FAT32 formatted, I get an immediate BSOD (FAT_FILE_SYSTEM) after I hit the Sync button. This is reproducible across multiple memory sticks and different USB ports on my ...
Whenever I try to sync files from my hard drive to a memory stick which is FAT32 formatted, I get an immediate BSOD (FAT_FILE_SYSTEM) after I hit the Sync button. This is reproducible across multiple memory sticks and different USB ports on my ...