Problem with PCI-e card USB-C 20Gb/s card, with certain specific files only.

David689

Gold Level Poster
It may just be a slightly dodgy card.

The only other thing I can think to try is try it in a different PCIe slot.
Ooh - good thought.
It's weird how it objects to the same file each time, even though that file is OK on the MoBo connection and then if I delete that file it moves on to objecting to another one.
 

ubuysa

The BSOD Doctor
I would suggest that you open an elevated command prompt or PowerShell session and run a chkdsk /f /x on both the USB attached drive and the internal source drive. What you describe could easily be a filseystem corruption.
 

SpyderTracks

We love you Ukraine
I would suggest that you open an elevated command prompt or PowerShell session and run a chkdsk /f /x on both the USB attached drive and the internal source drive. What you describe could easily be a filseystem corruption.
But it works fine off the motherboard USB, it's only off the pcie card it struggles
 

ubuysa

The BSOD Doctor
But it works fine off the motherboard USB, it's only off the pcie card it struggles
If the problem is not where you're looking then it' somewhere else. Since it's a file copy problem I would start with the storage devices at each end and work in - hence the chkdsk suggestion.
 

David689

Gold Level Poster
I would suggest that you open an elevated command prompt or PowerShell session and run a chkdsk /f /x on both the USB attached drive and the internal source drive. What you describe could easily be a filseystem corruption.
Done, with the external disk plugged in to the MoBo 10Gb/s USB-C socket. No problems found.
 

David689

Gold Level Poster
I have the external drive formatted in exFAT (at one time I may have needed to access it on a Mac, but not any more). I don't suppose that could be relevant?
 

David689

Gold Level Poster
And it's just that one image file you have a problem with?
Not exactly. I was copying a folder comtaining nearly 40,000 images. When it got to one specific image the process halted with the error message described, the J: disk (the external one) having disappeared from "This PC". And it was consistently the same image, a TIFF.

However, I deleted that TIFF and then the problem moved on to another TIFF which then became, consistently and reproducibly, the file at which point the J: disk disappeared.
 

ubuysa

The BSOD Doctor
Not exactly. I was copying a folder comtaining nearly 40,000 images. When it got to one specific image the process halted with the error message described, the J: disk (the external one) having disappeared from "This PC". And it was consistently the same image, a TIFF.

However, I deleted that TIFF and then the problem moved on to another TIFF which then became, consistently and reproducibly, the file at which point the J: disk disappeared.
What happens if you copy that folder in sections, say 10,000 images at a time? Will it copy them all in the four 'runs' it will take?
 

David689

Gold Level Poster
What happens if you copy that folder in sections, say 10,000 images at a time? Will it copy them all in the four 'runs' it will take?
I'm away from my computer at the moment. I don't know if this helps - when using the PCI-e card socket to look at the problem file via "This PC" it just showed a generic "image" (paint brush) icon and would not open the image in Windows Photo Viewer whereas when using the MoBo socket the image's icon was a preview of the actual image and I could open it in Windows Photo Viewer. So it seems that for some reason the PCI-e card "objects" to those files in a way that the MoBo one does not.
 

ubuysa

The BSOD Doctor
I'm away from my computer at the moment. I don't know if this helps - when using the PCI-e card socket to look at the problem file via "This PC" it just showed a generic "image" (paint brush) icon and would not open the image in Windows Photo Viewer whereas when using the MoBo socket the image's icon was a preview of the actual image and I could open it in Windows Photo Viewer. So it seems that for some reason the PCI-e card "objects" to those files in a way that the MoBo one does not.
Hmm. My reason for asking for the copy in smaller blocks was because what you were describing sounded like some sort of buffer issue. Now it's sounding more like a dodgy PCIe card. Unless proven otherwise I would suspect that card....
 

SpyderTracks

We love you Ukraine
Hmm. My reason for asking for the copy in smaller blocks was because what you were describing sounded like some sort of buffer issue. Now it's sounding more like a dodgy PCIe card. Unless proven otherwise I would suspect that card....
Yeah, that was my thought too.
 

David689

Gold Level Poster
I wonder why it was only specific files that seemed to cause the problem?
I tried to copy only the folder that contained the "rogue" file but the same problem occurred when it reached that file. But then I deleted that .tiff and was then able to transfer all 40,000 images in one go with no problem, via the PCI-e card socket. And there are several .tiff files that are larger than the last two "rogue" files.
It was an oddly consistent problem - a few specific files that caused problems via the PCI-e card socket but not via the MoBo socket.
 

Bigfoot

Grand Master
I had a not dissimilar issue with a multi format USB card reader. Each card slot appeared as a separate drive letter in MS Explorer. When I tried to transfer raw files from my camera some of the pictures were corrupted when viewed on the PC. If I connected my camera directly via USB cable to the same USB port.with the card in the camera, the files transferred without corruption. My conclusion was that the card reader was faulty, even though I couldn’t work out how it could corrupt some files (only a small percentage) but not the rest. It does look like there might be a problem with your card.
 
Top