Copy link to clipboard
Copied
When I import files into the Lightroom Classic catalog, and it starts to generate previews, it crashes at some random time. I turned off the parallel processing of previews, but it still crashes. It stops crashing if I turn off the hardware acceleration. But I want to use it with hardware acceleration. My drivers are updated, as well as all Adobe apps on my machine. And what I found unacceptable with every Lightroom crash, it corrupts and damages my original photo files.
Copy link to clipboard
Copied
<moved from cc desktop bugs>
Copy link to clipboard
Copied
When I import files into the Lightroom Classic catalog, and it starts to generate previews, it crashes at some random time. I turned off the parallel processing of previews, but it still crashes. It stops crashing if I turn off the hardware acceleration. But I want to use it with hardware acceleration. My drivers are updated, as well as all Adobe apps on my machine. And what I found unacceptable with every Lightroom crash, it corrupts and damages my original photo files.
By @Tsvetelin Pavlov
More than likely, your hard disk is malfunctioning causing both LrC crashes and photo corruption.
Copy link to clipboard
Copied
Thank you. But it happened no matter where the image files are stored - I've tried with at least two drives, just because my photos' directories are on several drives.
Copy link to clipboard
Copied
It is a design feature of Lightroom Classic that it never writes to the image portion of your photo files. So LrC cannot be the cause of damage to the files. If it happens on multiple drives, there could be other hardware problems. But this is a hardware problem.
Copy link to clipboard
Copied
I know and I am surprised. 😕 But currently, I am using DNGs; it does not create sidecar files, and I guess when LR tries to set the preview back into the DNG, it corrupts them.
It also happens only when hardware acceleration is turned on. I already turned it off, but the whole point of upgrading my PC was to use the acceleration - it is several times faster and I really want to use it.
Copy link to clipboard
Copied
Please do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
"It stops crashing if I turn off the hardware acceleration."
"DirectX: NVIDIA GeForce RTX 3070 Ti (31.0.15.3667)"
You've got the most recent Studio driver installed. Based on reports here, the last six months of Nvidia drivers have seemed pretty stable. But you might try rolling back to a driver from 6-9 months ago to see if still happens (and thus might be related to the driver):
https://www.nvidia.com/Download/Find.aspx?lang=en-us
Copy link to clipboard
Copied
I have had this problem ever since I assembled my new machine - somewhere around February this year. I regularly update the drivers, and every time I check if the issue persists. So, I already tried the older versions.
I tried to switch to the Game ready driver, but the issue persists.
Copy link to clipboard
Copied
"When I import files into the Lightroom Classic catalog, and it starts to generate previews, it crashes at some random time."
Are you presented with the window asking to submit the crash report to Adobe? Are you entering the email address associated with your Adobe Id? If so, Adobe's Rikk Flohr is pretty good about doing an initial look at the crash reports and getting an internal bug filed if necessary.
Copy link to clipboard
Copied
No, when this crash happens, nothing is shown - just LrC kills itself.
I had two or three times when the dialog for crash report appeared, so I entered my e-mail and entered details, but I didn't receive a reply or further info.
Just to be honest, yesterday started a support case with Adobe's support; they made a remote session, witnessed the crash, collected logs, and scheduled a call with me tomorrow.
Copy link to clipboard
Copied
I hope Adobe Support is helpful, but beware that for all but the most routine issues, they can be pretty random and have a reputation for saying anything to close a case. If the call doesn't go anywhere, upload the before and after DNGs here, which could form the basis of an actionable bug report.
Copy link to clipboard
Copied
Thanks, I'll keep that in mind.
Copy link to clipboard
Copied
"it corrupts and damages my original photo files."
Upload an original DNG and its corrupted version to Dropbox, Google Drive, or similar and post the sharing link here. That will let us see precisely how the file is getting damaged.
Copy link to clipboard
Copied
Thank you. This was an intriguing suggestion.
I am attaching a photo from the original import, which was damaged - it's DNG and it is zeroed. I am attaching the corresponding NEF SOOC image.
It appears that the image gets zeroed -it is with the size of the original, but full of 'zero' bytes.
I tried several times to reproduce the problem (reimported the same photos several times with 'Copy As DNG' operation and rebuild the previews) and I got three BSOD and 5-6 crashes. But most interestingly, there was no damaged DNGs.
There was one time, I succeeded - but multiple NEF files got zeroed, not DNGs. So, I guess, while it was copying 'as DNG', it first copies the original file, and it is the one that gets corrupted while converting it to DNG. I am attaching example pairs of them too.
Edit: unfortunately, I can't upload the damaged files - the platform rejects them with error message "The attachment's * content type (application/octet-stream) does not match its file extension and has been removed." and I can't upload archives. But I will upload screenshots of the files side by side.
Copy link to clipboard
Copied
"I got three BSOD and 5-6 crashes."
A BSOD strongly indicates a hardware problem or buggy graphics driver. In general, an application itself can't directly cause the operating system to crash -- if the OS crashes due to something an application does, that's an OS bug that would be fixed at high priority by Microsoft or Apple, and such crashes are rare.
The issue doesn't happen when LR's use of the graphics processor is disabled, which suggests an issue with the graphics hardware or driver. Try rolling back to a 9-month old driver, as outlined above.
But I wouldn't rule out some other hardware problem that is only triggered when LR uses the graphics processor. Try running Windows memory and disk diagnostics.
Copy link to clipboard
Copied
You were correct - not hardware failure, but an overclocking setting in the UEFI.
Copy link to clipboard
Copied
Thanks to all for the support.
I am writing to help if someone else finds this thread.
Regarding the support of Adobe - I couldn't even join the call/meeting - it was in inconvenient hour, and I couldn't reschedule it.
I try to strip everything down from the motherboard, including taking out SSDs. In the end, I had to reset the UEFI back to the factory settings. And the problem was gone.
It appears when I set up the machine for the first time; I choose the medium at the auto overclocking setting and that was the reason for the crashes. I left it on UEFI defaults with the studio driver and everything is stable now.
Copy link to clipboard
Copied
Have you find any solution on this ? Currently i have the simlar issue but only recently after a random windows 11 update.
But ya during import it would crash if i get lucky it would still upload in the background with the pop up saying error LRC has crashed
Copy link to clipboard
Copied
Your "similar" issue should probably be placed in its own (brand new) thread, with full explanation of the problem you are having. People will be happy to try to help in a new thread.
Copy link to clipboard
Copied
As I wrote - In my case, semi-automatic overclock, enabled in the UEFI was the reason. When I reset the UEFI to factory defaults, LR became stable.
Good luck.