Copy link to clipboard
Copied
Hello Adobe-Support,
I have .NEF files. If I open them in Photoshop, the picture is displayed in strange colors, like in the first screenshot. If I open the same file with GIMP (darktable), it is displayed correctly (second screenshot). I tried it on different PC´s and it is still wrong in Photoshop. I use the newest version of Photoshop and Camera Raw. I also tried different versions. Camera is: NIKON D5600.
How to fix this problem?
Copy link to clipboard
Copied
<moved from enterprise&teams>
Copy link to clipboard
Copied
First, try disabling GPU in the preferences (Performance) or alter the settings. Any better?
If turning OFF the GPU works, it's a GPU bug, and you need to contact the manufacturer or find out if there's an updated driver for it. This is why disabling GPU is an option as more and more functionality moves to the GPU in newer versions of many Adobe products. Disable third-party graphics accelerators. Third-party GPU overclocking utilities and haxies aren't supported.
Also see: https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html
Check to see that your GPU meets system requirements.
Copy link to clipboard
Copied
I dont´t use Lightroom Classic, the .NEF file opens via Camera Raw. I don´t think it´s a GPU bug, I tried the same picture on 4 different PC´s, on 3 PC´s there is this problem I mentionted above. When I open the .NEF picture with a other software, it is displayed correctly, as I already mentioned. I also completly reinstalled Photoshop a few times and tried different GPU settings. Nothing worked.
Copy link to clipboard
Copied
I think this looks like a corrupt file. Not what you want to hear, I know.
Many viewers will not show the full raw data, but the embedded jpeg preview. This preview is just a very small part of the file, so it may be fine even if the main file is corrupt.
One shot in the dark you can try is to convert the file to DNG. It will be the same sensor data, but the file will be repackaged, so just maybe.
File corruption is always caused by failing hardware. There is no reason to look for other causes. That can be machine components like a failing disk or bad RAM, but it's just as likely to be the card reader, cables or connectors.
If you have file corruption it's essential to have backup. If you don't, do it ASAP before it spreads and destroys more files. Don't open the files to check; just copy them somewhere directly.
Copy link to clipboard
Copied
Upload the problematic raw to something like Dropbox. Then the actual raw data can be evaluated in RawDigger. If the raw not preview is corrupted, that will show it.