Legend

Question

D750 "unexpected end of file" for NEF that loads fine into Capture NX-D

Forum|Forum|11 years ago
December 11, 2014
15 replies
33389 views

I have a NEF that produces an "unexpected end of file" error in both Lightroom 5.7 and PS CC (both with Camera Raw 8.7). The same NEF loads and converts fine in Nikon's Capture NX-D V1.0.2. The NEF also converts fine into a JPEG using the D750's in-camera NEF processing function. I can provide the NEF to Adobe for analysis.

This topic has been closed for replies.

W

wilsonjlam

Participant

Sorry to grave dig, but I just wanted to check that my EOF issues are the same as OP's.

I'm currently shooting on a new D750 with a Transcend 32 GB 45 MB/s 300x SDHC card. I'm also using Lightroom 5.7 and don't know what ACR (don't even really know what ACR is in the first place).

Here are the files: Transfer Big Files Free - Email or Send Large Files

J

jamesd43947165

Participant

Hi all. I'm getting similar issues across Lexar and Sandisk, and around the same amount of issues, 2500 images for last wedding with 15 - 20 EOF errors. Latest FW and LR 6.1 with PS CS6. Having issues with LR and PS crashing out too. Tried files with LR5.7 and still seeing the issues. Following your thread with interest. Thanks, James

HorshackAuthor

Legend

OP here - I just noticed that the current/latest version of ACR (8.8) is now able to successfully process D750 NEFs that exhibit the duplicate-data corruption issue I outlined in this thread...vs previous versions such as 8.7.1 which could not. I'm guessing Adobe modified the software to ignore any potentially corrupt data that exists beyond the normal processed dimensions of the NEF. I also noticed that ACR 8.8 can also process NEFs that have other types of corruption inside the actual image area itself (ie, typical CF/SD card corruption vs the D750-specific issue); now instead of reporting an EOF error, ACR actually lets you load and process the file but with any corruption visible in the image (typically as colored bands, depending on the type and location of corruption). Both changes are great news. I don't believe Adobe has made ACR 8.8 available to Lightroom users as of yet, so to take advantage of this fix you'll need to use Photoshop / Camera Raw.

ssprengel

Inspiring

Does it work to convert the premature-EOF NEFs to DNGs using the DNG Converter 8.8? In others words does the DNG Converter 8.8 fix the data slightly? If so that would be a way to get the bad-EOF NEF raw data into LR, already.

HorshackAuthor

Legend

Yep, DNG converter 8.8 can be used as a temporary alternative for LR users until Adobe puts ACR 8.8+ in the next LR release. Here's an EOF conversion attempt with converter 8.7.x vs 8.8.x:

D

dangramit

Participant

Hi - Sorry to come in on an older thread. I am experiencing the same problem on a new D750 and wondered if any progress had been made or answers from Nikon. Many thanks - Daniel

markoj2252089

Participant

Hello, i have the same problem on my Nikon D750.... Did anybody send it on Nikon service? Thanks

D

dangramit

Participant

Yep - I have an open case with Nikon Europe ref 150404-000005

mickp76958285

Participant

Guys, I found a solution! I also had the Unexpected End of File Occurred problem. Using a brand new Nikon D750 and latest lightroom for time lapse.

It was bugging me all day so I had to solve it. All I did was separate the corrupt NEF files into a separate folder, load them into Aperture, export unchanged as NEF to a new folder. Now they load properly in Lightroom without the Unexpected End of File Occurred problem!

TaDa...

Plus I now know that the Unexpected End of File Occurred problem only happens on 1 memory card I used, cheaper Integral 64GB.

Let me know if this works for you please.

Regards

HorshackAuthor

Legend

mickp76958285‌, thanks for sending one of your corrupt NEFs. Your corrupt NEF is similar to the issue discussed in this thread in that the encoded section runs out of data right at the final row of data. However your NEF does not have the replicated data corruption that is seen on the other files, which means your file(s) are corrupted somewhere in the middle of the NEF and is likely the result of the SD card rather than the D750 issue discussed here.

P

Pink Mink

Participating Frequently

I'm having the same problem with my D750's. Never had this issue prior to the firmware upgrade at the end of December. I shoot around 1500 to 2000 shots per wedding and around 10 images per shoot have the 'unexpected end of file' error when loading into Lightroom or Photoshop. Happening on both D750's with an assortment of SD cards (Lexar and Sandisk). I've sent the files off to Nikon for review to see what's happening and to try and get a resolution (hopefully!).

C

climbbike@gmail.com

Participating Frequently

My problem files open fine in Capture NX-D which is why I didn't think it was normal file corruption. But who knows . . . I'll try a new card and see if I get any new problem files.

S

sunilthakkar82

Participating Frequently

I just shot my first wedding with the D750... out of the 1120 images taken using the camera 10 of them gave the mentioned error in Lightroom (unexpected end of file)

The error was there in both files - Card Slot 1 and 2 (Backup Mode)... I tried fixing the NEF using the application mentioned, which did not work...

After reading this thread I tried opening them in NX-D, which works... but it sucks that these random errors show up in Lightroom... It gave me a real scare initially... at least the images are not lost...

Hopefully Nikon and/or Adobe sort this out soon...

S

sunilthakkar82

Participating Frequently

Forgot to mention... This was on the upgraded D750 firmware... 1.01

C

climbbike@gmail.com

Participating Frequently

I uploaded one of my problem files: Transfer Big Files Free - Email or Send Large Files up to 20 GB

Transfer Big Files Free - Email or Send Large Files up to 20 GB

engerim

Participating Frequently

Your sample file has the same issue (in row 4032) as my files.

Row: 4032 Col: 5921

dcraw has it as "Corrupt data near 0x1a881fd"

So the error also appears in 12 bit raw, lossless.

I updated the ticket at Nikon that you also have this error.

You may want to open a ticket there yourself and refer them to my case ID "141229-001985":

Title: "D750 bad huff data in last row of RAW file (14 bit) (row 4032)"

I doubt Adobe will do anything to circumvent the error as its clearly a camera bug.

I may open a ticket with Adobe Support...

ssprengel

Inspiring

As far as opening a ticket with Adobe, you may not need to. Adriana Ohlmeyer, from a few replies above, is an Adobe staff member who usually jumps on the forums after a new Camera Raw release to look for issues being reported. I assume she's either a developer or a QA person. There must have been enough replies to have caught her attention after the multiple-holiday week just ended.

A

adriana ohlmeyer

Adobe Employee

I am curious to know if you format the card in camera before shooting? If not, could you try and see if you can reproduce this issue, please?

Lattefarsan

Participating Frequently

I've formatted both cards in the camera

A

adriana ohlmeyer

Adobe Employee

Thank you!

HorshackAuthor

Legend

I was able to reproduce the EOF on my D750. This time I populated both SD slots - the first slot had my original Sony 32GB 94 MB/s card that produced the first EOF NEF from two weeks ago, the second SD slot had a Sandisk 32GB 45 MB/s. Unlike engerim setup, my two NEFs didn't match when I reproduced the EOF - the Sony card produced another EOF NEF but the Sandisk's equivalent/"backup" NEF in the other slot could be read by ACR/LR without error. To isolate the problem to the card vs the specific D750 slot, I then swapped the cards between the two slots and reproduced the EOF NEF again - the EOF issue followed the Sony card to the other slot. To isolate the problem to the specific copy of this Sony card vs this model of card, I then replaced the Sony card with another of the same make and the new card did not produce an EOF NEF. So it looks like my original Sony SD card is bad.

I then analyzed the EOF by comparing the EOF NEF from the Sony card to to the equivalent good NEF from the Sandisk and found that the Sony card has data corruption near the end of the file. Because the corruption is at the end of the file it appears Capture NX-D (and the D750's in-camera NEF->JPEG conversion) is not encountering during its decoding, perhaps because it's converting a smaller image dimension from the NEF vs ACR/LR.

Here is an analysis of the data corruption. Based on the data-replication I see it appears one of the parallel NAND channels within the card is incorrectly sourcing data from another NAND channel.

HorshackAuthor

Legend

I've continued playing around with the suspect Sony card and have reproduced the EOF NEFs a few more times. What's interesting is that each repro has the same signature - corruption near the very end of the file (within last 1KB), with corrupt data replicated across the corrupt area. This implies that whatever is wrong/marginal with my Sony SD copy is sensitive to the D750's media timing for the last write(s) of the image data. Because of this I'm still interested in analyzing other users' D750 EOF NEFs, to see if there's a unique timing sensitivity of the D750 with certain SD cards. When you attempt to reproduce please use both card slots because both NEFs are required to do the differential analysis to find the corruption. Please also report which model cards you are using.

I also tried the suspect Sony card in my similarly-configured D800 (14-bit lossy compressed raw) using the same 100-shot intervalometer sequence I used on my D750 and did not see an EOF NEF. Not conclusive by any means but an interesting data point.

Lattefarsan

Participating Frequently

Any particular settings that reproduces the EOF?

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded