I just returned from a trip where I took approximately 14,000 images. Probably 20-30 images turned our similar to this one. Does anyone have any ideas of what is causing this or what the solution might be.
In 2005 (I was using either a D80 or D300) I did a day's shooting at Grand Canyon. I was using a top of the line--at the time--Lexar CF. Most of the files on that CF were corrupt. The ones that I could read showed parts of multiple shots on one image. I sent the CF to Lexar, and they recovered most of the images.
I did not have the funky color problem. To me that would suggest either a failing CF, buffer problems, connection problems, etc. Not sure that there is any software that could reconstruct your images without the color striations.
I am assuming from the image content that you were not using a high frame rate, which might eliminate buffer problems being the culprit.
How many actuations on this D300. What is the brand and model of your CF?
I always use either top of the line SanDisk or Lexar CF/SD/SDHC, etc. It amazes me how much many on here spend for their camera bodies, lenses, tripods, heads, brackets, grips, etc. and then scrimp on memory cards. I have never had another problem since 2005. Just knocked on wood.
Several years ago I had a similar issue with colored streaks
on a Nikon 5700. My local camera store sent it in to Nikon
for repair and they replaced the shutter. I had a D70s also
exhibiting this problem and again they replaced the shutter.
Both cameras started out with a few random frames and
eventually all were bad. Hope this helps.
Are your card's on nikons approved list of cards mentioned in the manual? As a last resort you can try formatting the cards via your computer, and run the windows error checking utility presuming you're running windows. Then being sure to reformat the cards in camera. Cards not tested and approved can sometimes have intermittent problems as can a failing card.
____________________________________________________________________ When no one is looking, Pigs can walk on they're hind legs
I talked about a similar problem of image file corruption here.
My case was a little different, and turned out to most likely be a bad eSata cable between my file server PC and an external storage box. My problem was a random flipped bit here and there in just a very few image files. In your case, you appear to be missing a string of bits, which is offsetting the image in addition to the RGB color transpositions that raw file corruption tends to create. I assume these are raw files?
Anything in between the camera buffer and the final disk storage could corrupt a file (in principle). If it were me, I would first determine if the image on the card is corrupted. It may not be corrupted, it may just be the image on your hard drive.
As I mentioned in my thread, I use a Windows app called BeyondCompare (BC). I would copy the contents of the card to the hard drive, then use BC to bit compare the contents of the hard drive folder(s) to the actual card. You may need to modify your workflow to avoid renaming files or adding IPTC or XMP data, for example.
There are other bit comparison tools out there; this is just the one I use. If you are on a MAC then you need to find some other tool.
If images are corrupted but the hard drive files are identical to the camera card files then you know it is happening in camera. Otherwise you need to start investigating the hardware chain.
Thank you all for your replies. They have brought up many interesting possibilities.
I went to Africa on this trip taking 17 4GB and 8GB cards. I had expected that they would last the entire tip and I had a NEXTO 500GB has a backup. Unfortunately, I filled up the cards after the first week and then started reusing the cards (yes, I know I lost my redundancy).
All of the scenarios presented are possible because of the above. Does anyone know if Opanda or any other software records a serial number or any other ID of the original card that it gets recorded on? That would make it easy to see if a card has went bad.
Thanks to everyone for their help and suggestions.
>I went to Africa on this trip taking 17 4GB and 8GB cards. I >had expected that they would last the entire tip and I had a >NEXTO 500GB has a backup. Unfortunately, I filled up the >cards after the first week and then started reusing the cards >(yes, I know I lost my redundancy). >
I had asked previously how many actuations you had on this D300. Someone on here mentioned problems with the shutter. I have seen other D300's with high actuations suffering shutter problems.
I have never had a problem with a shutter that I know of, so not sure of how they might be tested. It just sounded like your count might be high with all the memory cards that you were going through. The folks that I have known with shutter problems on D300's knew for sure that they had shutter problems.
At 1st 87,000 sounded like a lot, but I can easily shoot 1,000 photos in a couple of hours. Shooting track meets, I usually shoot the highest frame rate, and keep my finger down sometimes for 15-20 seconds at a time. Don't even want to look at the shutter count on my D7000.
you said that you went on a trip to Africa, but the pic in your original post is of Venice if I am not mistaken? Maybe the card (s) did not format correctly after a previous shoot? After downloading your images do you delete your images from your card or do you format?
I have nothing important to add to your problems with possible corrupted files, but I’m very interested in what your final conclusion will be.
I’ve been struggling with printing problems that are similar to your photo attached to this topic. Much of the time my prints look very much like your photo. I have found that my old Epson printer is still very capable of outstanding prints, but I’ve been unable to determine why this is happing most of the time.
My current thinking is that I’m printing from a corrupted RAW file. Please keep me in mind, as you solve your issues.
I am having currently similar issues. Every 500 pictures i am having aprox. 1 corrupt file. I hope the shutter is ok. I have currently 43000 shutter actuations. The cards I have been using were formated on a nikon but a different model camera. I don't know if it could be the problem.
I forgot to say that my corrupt file is a NEF. On the camera the NEF seems to be ok, I can zoom in and out and i can see the picture correctly on the camera screen. But if I convert it to jpg on the camera the jpg gets corrupted as yours. If I try to open in CaptureNX2 the program crashes.
>It's always a good idea to format a card in the camera >you'll be using before starting to shoot.
I was bitten by this last weekend. The card was formatted in the D700 and used in the D200. Lots of weirdness happened on the file system. Could be coincidence, maybe not. Lexar's card utility was able to recover all the photos.
---------+---------+---------+---------+ Joseph K Seattle, WA, USA
>I was bitten by this last weekend. The card was formatted in >the D700 and used in the D200. Lots of weirdness happened on >the file system. Could be coincidence, maybe not. Lexar's >card utility was able to recover all the photos. >
Next time i will take in consideration. Thank you for your reply.
>Welcome to Nikonians! > >>The cards I have been using were formated on a nikon but a >>different model camera. > >It's always a good idea to format a card in the camera >you'll be using before starting to shoot.
Thank you for the information. I will try this next time.
As I mentioned on this trip I took a lot of pictures and had to reuse some of my cards. All cards were backed up from the CF cards to a NEXTO eXtreme (ND2700) 500GM memory storage device. At the end of the trip, those files were then imported into Lightroom4 and the issue was then discovered.
Since I had renamed the files on import, I decided to re-import them into a Test catalog for lightroom4 to see if the bad images were grouped close enough together that they could have been taken with one "bad" card. Had I discovered a bad card, I then would have determined the file number through lightroom4 and then manually checked each card to find the bad CF card.
When I re-imported the files from the NEXTO device into a new catalog in lightroom4, all of the images imported perfectly with no exceptions! I was able to find corrupted pictures in the first import and match them to non corrupted pictures in the 2nd import.
This leads me to the following conclusions; 1. The camera shutter is working fine. 2. The CF cards are all working fine. 3. The NEXTO device itself is working fine during its CF import process,
BUT; 4. Based on comments people have left, there may be a problem with the cable used between the NEXTO device and my computer. 5. There could we an issue with Lightroom4.
Since I have never had this issue with Lightroom before, to me the logical cause then seems to be the interface cable or some issue with the NEXTO communicating with the PC.
Thanks to everyone for their help on this issue. If anyone disagrees with my logic or conclusions please let me know.
>Since I have never had this issue with Lightroom before, to me >the logical cause then seems to be the interface cable or some >issue with the NEXTO communicating with the PC.
I think you are right. I think it must be the cable or the NEXTO communication with the PC. I'm glad you solved your problem.
My similar problem is not solved yet.
Yesterday I was shooting about 300 pictures. Exactly 4 pictures were wrong. 4 Corrupted NEFs. Like my previous bad pictures : On the camera the NEF seems to be ok, I can zoom in and out and i can see the picture correctly on the camera screen. But if I convert it to jpg on the camera the jpg gets corrupted as yours. If I try to open in CaptureNX2 the program crashes.
I will try to give you more data: - Like Brian said, previous to the shots, I formatted the card with the D300. - The card was empty so I didn't delete any of the pictures to save space. - I detected the issue was on some (not all) rapid sequence shots. First shot, less than 1 second, another shot. 1st shot corrupted. 2nd shot ok. - The card used is a 8GB Kingston SDHC class 4. I use a 15$ SDHC to CF Adapter purchased on ebay.
I think the card is ok. I have used it a lot of times with my old d3000. But I am beginning to think if there is a problem with the SD-CF adapter. I hope the shutter and the buffer of the camera are both ok.
Do you think the sd-cf adapter could be the problem? Thank you in advance for your responses.
I was researching to use an eye-fi (only available in SD format, I believe) card on my D300 and I read several posts stating that SD-CF adaptors did not work very well. I ignore ithough whether it was only related to use with eye-fi or with normal storage. Maybe you could research archived posts.
>I was researching to use an eye-fi (only available in SD >format, I believe) card on my D300 and I read several posts >stating that SD-CF adaptors did not work very well. >I ignore ithough whether it was only related to use with >eye-fi or with normal storage. >Maybe you could research archived posts.
Billcavanagh says: "In general, putting any adapter in any data path increases the chance of corruption and is likely to slow the transfer rate. The time you most need high speed is the transfer from the camera's digital processor to the memory chip in the camera."
It says: "increases the chance of corruption". On this I suppose it could be or it could not be.
I think I have my similar to Bulgakov's issue solved too.
Last week i was on a travel. Total pictures: 1300. Cards used: actual CFs 32GB, 2Gb, 512MB. No CF to SD adapter used. No corrupted files. I tested slow & fast burst shots. All ok.
I conclude the corruption was caused by the adapter. The adapter I used previously was exactly this: http://www.amazon.com/SD-CF-II-Type-Adapter-Supports/dp/B000YZGCIU . I used with different SDs & had corrupted files aleatory with all of them. I don't know if other adapters can corrupt files too, but I think this does. Be careful.
I will invest in actual CFs and I will forget SDs and adaptors with my D300.
Thank you to Bulgakov for his post and to all that helped with this issue that has solved mine too.
Thanks for all of the followup to my initial post. I guess the lesson to be learned, at least for me, that is anytime you add to the complexity of a system (transferring files, adapters, cables, etc.) you increase the likelihood of any error occurring.