Same / similar problem with my 7D M2 on the first major shoot in Africa Dec 2014/ Jan 2015. Took the card back to the retailer for a refund. Lost around 12 shots I guess.
Upvote
0
East Wind Photography said:Andris said:The same for me with Lexar 3400x CFast. From 1000 shots there were about 10 - 12 coruupted raw still image files. Also interesting that 4K .mov file size for some files ir 0 B. In camera clip is playing, when view or copy on computer, size is 0 B.
The 0B files are due to the Windows driver not being able to read large files using the camera driver. You need to use the EOS utility to transfer the file (slow) or use a cfast card reader which uses its own driver and can read large files.
Photo282 said:I'm a 1DX ii user who has been talking to Canon about the loss of data in the bottom right hand corner. The camera was returned to canon service with Sandisk CFast card with problem files still on the Cfast card. I've since picked up my camera from canon with the recommendation to use a supplied CF card. Was advised that firmware was in pipeline to solve the problem with CFast card. The Sandisk CFast card supplied with 1DX ii does not have serial numbers that I can see.
Sandisk reply in Dutch said:Hartelijk dank voor ons op de hoogte te brengen dat u deze producten gebruikt!
Canon en SanDisk werken momenteel samen om een nieuwe firmware vrij te geven voor de camera om het kaart problem op te lossen, deze zal spoedig beschikbaar zijn. We willen ons verontschuldigen voor het ongemak dat dit veroorzaakt.
We zullen u een e-mail notificatie sturen wanneer de Canon firmware wordt vrijgegeven.
dilbert said:The firmware update will likely do one of two things:
1) add a pause between flushing the data to the card and removing power, giving the card time to write out the data from its buffers
2) update the way in which the camera talks to the card to ensure that the card has committed all data to "disk" before declaring it to be safe to remove power from
jd39 said:We may get SLOWER capture rates with this new firmware. I don't know how to go back to an old firmware, so I am going to avoid upgrading to the new firmware when it comes out. I'm not willing to test the upgrade...
...Why can't we just all not use Sandisk and not change the firmware? Am I worried for nothing?
dilbert said:This isn't Sandisk's problem, it is Canon's.
dilbert said:Look at it from another perspective: are there any reports from owners of cameras made by other manufacturers (e.g. Nikon) that are reporting the same problem?
This isn't Sandisk's problem, it is Canon's.
kaihp said:dilbert said:This isn't Sandisk's problem, it is Canon's.
Actually, we can't tell whether it's Canon or SanDisk having a problem.
It may be that the problem only occurs in the 1Dx2, but if it occurs because the SanDisk card is violating a spec, it's SanDisks problem.
It could also be the 1Dx2 that is violating a spec; then it's Canon problem.
And we can't tell the difference without looking at the specs, signals and timing diagrams to determine what happens.
+1East Wind Photography said:Look at it this way. Both companies may have just decided that a firmware update was the least expensive resolution to the problem. We dont really know who is at fault. My lexar card works fine so is it canon?
kaihp said:+1East Wind Photography said:Look at it this way. Both companies may have just decided that a firmware update was the least expensive resolution to the problem. We dont really know who is at fault. My lexar card works fine so is it canon?
Do we really care who is at fault, as long as we can get the problem fixed?