Copy link to clipboard
Copied
For the past 6 months or so LR Classic has been crashing on my desktop intermiitently when I crop dng files (which are large, source is a Nikon Z9). This happens about once per 25 attempts and is not reproducible - i.e. it will crash for an image and then after restarting LR it will work for that same image.
I have the very latest drivers for my graphics card, an RTX6030. I have done updates for LR and Windows. Nothing helps. All other operations work fine. E.g. denoising using the graphics card works fine, etc.
Here is the System Info:
@johnm59973136
My recommendation is to contact nVidia and report the crash. Even though you have the latest driver and a clean install, that does not mean the driver is still at issue. There is always the possibility the card is defective, but I doubt that.
You should have the Crash Report in your system that you can use to refer to your issue.
I see that you made a request earlier for a Stack Trace. If you cannot find the local crash report, the Unique Stack ID reported is 70833915
To be clea
Copy link to clipboard
Copied
Is it possible to configure LR to generate a dump next time it happens instead of displaying that dialog that blames it on the graphics card? So Adobe can see the stack trace, etc to better grok what's happening.
Copy link to clipboard
Copied
Is it possible to configure LR to generate a dump next time it happens instead of displaying that dialog that blames it on the graphics card? So Adobe can see the stack trace, etc to better grok what's happening.
By @johnm59973136
Do you have a screenshot of that error message? Can you repeat?
Perhaps something like:
or perhaps:
And as to that Adobe crash report dialog, Rikk Flohr was inquiring about, you received something like thus, correct?
Copy link to clipboard
Copied
Attached is the dialog I get when it crashes. Also attached is the list of Adobe processes running when it happens. The "Adobe Crash Reporter Service" runs for over a minute while LR is non-responsive. Am I correct in assuming that this is gathering crash information and sending it up to Adobe?
The link in the dialog is this: Lightroom Classic crashes on Windows (adobe.com)
Copy link to clipboard
Copied
1. When you click on that button "click here" you then get info about the GPU? Do you have a screenshot of that.
Oh is that link, that I will include below what shows up?
https://helpx.adobe.com/lightroom-classic/kb/crash-gpu-directx-enabled.html
2. When LrC crashes, and when the crash processor acts upon that, you may get a Error Report screen to show up, the last one in my previous reply.
You fill that out, you include your e-mail address (same e-mail address you use to sign in to Adobe with) and you send that on to Adobe. I do not think the crash processor automatically flags Adobe to look at it. And apparently, not all crashes trigger the error screen to show up
If you get that screen, when filling the info about what you were doing, include a link to your discussion, that might help.
Now, as to that error screen for the crash not showing up, read the following link, you might have an option turned off
https://helpx.adobe.com/photoshop/kb/submit-crash-reports.html
Copy link to clipboard
Copied
Yes, when I click "click here" I just get that link to the Adobe web page.
I used to get the dialog about sending the error report, but I haven't seen it in ~months. Now I repeatedly just get the link to the web page. Is there any way to configure LR to show the error report dialog? Or is there any way to collect the error report data on my computer?
Copy link to clipboard
Copied
In the link I included in the reply above
https://helpx.adobe.com/photoshop/kb/submit-crash-reports.html
For MACOS and for Windows, their are instructions on how to enable that dialog. For Windows, basically you use REGEDIT to make sure a value is set. (instruction actually tells you how to set it without entering the registry)
I am sure a user would have answered a prompt for this to have been changed to Never Ask. Probably something like Click here to never ask again.
Entering REGEIDIIT is not for the novice on computer management. Small text scripts to alter the registry is usually safe.
Looks like Adobe wants the value to be 0. If you simply view the registry, and look for that key, and it is set to 0, than probably nothing to do.
And once again, If you are not comfortable with looking around in the registry, then Don't. One error, and your computer is a mess. Looking Ok, Editing and saving, careful...
When you contact an Adobe Tech, they may in fact remotely look at this.
Copy link to clipboard
Copied
Thank you! Will try that and hopefully capture a crash.
Copy link to clipboard
Copied
I've been notified by Adobe that my case is to be closed. But the probem persists. The diagnosis by Rikk Flohr is "The crash report from today indicates a problem with your nVidia card's driver. "
I have the very latest drivers from Nvidia with a clean install, and the problem persists.
So what am I to do? Buy another video card? I've already done that for a prior problem I had with LR. I have a modern, common video card (RTX3060) which is well above the performance requirements specifed by Adobe. Adobe apparently will not open a case with NVidea about this "problem with driver", nor will it provide me will sufficient information to open a case myself.
I've been a loyal, paying customer for many years. Surely Adobe owes it's users some recourse beyond "tough luck sucker".
Copy link to clipboard
Copied
@johnm59973136
My recommendation is to contact nVidia and report the crash. Even though you have the latest driver and a clean install, that does not mean the driver is still at issue. There is always the possibility the card is defective, but I doubt that.
You should have the Crash Report in your system that you can use to refer to your issue.
I see that you made a request earlier for a Stack Trace. If you cannot find the local crash report, the Unique Stack ID reported is 70833915
To be clear:
Engineering (not Rikk Flohr) has diagnosed and advised that this crash mode is due to an Nvidia GDS crash, and the help doc that refers to this issue is https://helpx.adobe.com/lightroom-classic/kb/crash-gpu-directx-enabled.html.
Which, based on this thread, it looks like it exhausts your options save for disabling the GPU.
No one has said, " Adobe apparently will not open a case with NVidea about this "problem with driver","
No one has said, "nor will it provide me will sufficient information to open a case myself."
No one has said, "tough luck sucker"
I understand you are upset with your inability to use Lightroom as you expect to, but Adobe can only be responsible for its software and must cede some concerns to other software, hardware, OS, platform, and, ultimately, the individual customer.
Other areas you might explore (but I am betting on an updated driver from nVidia):
I wish you success in resolving your issue.
Copy link to clipboard
Copied
Doing a "clean install" of the very same driver I've had the crash with seems to have fixed the problem.
Thanks for your help and sorry for the rant.
Copy link to clipboard
Copied
JohnM, I have also had continual crashes (when moving from one image to another, in develop module) with LrC any version 13.xx. The only way I can get any editing work done is to revert to LrC version 12.51.
The help I have received on this Adobe Community board has led me to a "ntdll.dll" error. The suggested corrections offered here have not helped ... all I get is "not an Adobe issue".
LrC all versions 13.xx is the only app that crashes.
No other applications crash on my system, none.
LrC 12.51 does NOT crash.
I wish that Adobe support would point to a solution.
Feeling stranded … as I continue to pay for my subscription.
Copy link to clipboard
Copied
Sorry Rikk, I was replying to John. Just getting frustrated in my attempts to run LrC version 13.xx since last October.
My last few days of trying to run v13 ... still crashes.
Getting ready to revert to 12.51 again.
Copy link to clipboard
Copied
I have experienced crashes caused by overclocking tools, system monitoring tools, etc.
Check to see if you are using any of these tools.