• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
15

Lr closes on filmstrip use w/ AutoWrite XMP enabled (Thread is damaged-Contacting Forum Support)

Explorer ,
Dec 03, 2023 Dec 03, 2023

Copy link to clipboard

Copied

Help!

Just tried version 13.0.2 today (12-3-23)… same problem ... LrC still crashes when scrolling through filmstrip in Develop Module.

(Note: I do initial filtering with “stars”. Not sure if related >> Crashing happens even unfiltered, but seems to happen more quickly when images are filtered)

 

History...

Early Oct, I upgraded to 13.0 = crash ... when scrolling through images in filmstrip

Oct 15, tried 13.0.1 = crash ... when scrolling through images in filmstrip in Develop Module.

Oct 29 and Nov 28 tries, same crash result with trying the “second install” and “waiting 5 min” after install.

 

From Oct 15 to today I have needed to revert back to version 12.5 = no issues, old LrC is solid and works fine.

I must use to 12.5 to be able to work.

 

Today's System info:

 

Lightroom Classic version: 13.0.2 [ 202311290958-8ff975ea ]

License: Creative Cloud

Language setting: en

Operating system: Windows 10 - Business Edition

Version: 10.0.19045

Application architecture: x64

System architecture: x64

Logical processor count: 24

Processor speed: 3.1GHz

SqLite Version: 3.36.0

CPU Utilisation: 0.0%

Built-in memory: 32509.3 MB

Dedicated GPU memory used by Lightroom: 1220.9MB / 8032.0MB (15%)

Real memory available to Lightroom: 32509.3 MB

Real memory used by Lightroom: 1409.3 MB (4.3%)

Virtual memory used by Lightroom: 2849.4 MB

GDI objects count: 723

USER objects count: 2702

Process handles count: 3125

Memory cache size: 96.0MB

Internal Camera Raw version: 16.0 [ 1677 ]

Maximum thread count used by Camera Raw: 5

Camera Raw SIMD optimization: SSE2,AVX,AVX2

Camera Raw virtual memory: 130MB / 16254MB (0%)

Camera Raw real memory: 153MB / 32509MB (0%)

System DPI setting: 144 DPI (high DPI mode)

Desktop composition enabled: Yes

Standard Preview Size: 3840 pixels

Displays: 1) 3840x2160

Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

 

Graphics Processor Info:

DirectX: NVIDIA GeForce RTX 3070 Ti (31.0.15.4601)

Init State: GPU for Export supported by default

User Preference: GPU for Export enabled

 

TOPICS
Windows

Views

3.9K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
replies 102 Replies 102
Explorer ,
Dec 21, 2023 Dec 21, 2023

Copy link to clipboard

Copied

I have the exact same issue.  It started when v13.0/13.01 was released.  Looking through the event logs, LrC is the only App that has this issue. I would think if it was a OS issue other apps woud have this issue.  Also starting at the same time LrC was upgarded.   My Window's event log looks the same.  Really sounds like a LrC issue to me.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 21, 2023 Dec 21, 2023

Copy link to clipboard

Copied

There was an update this week and things seem to have gotten a bit more stable. I've done nothing except applied all updates to Camera Raw, Lightroom and Photoshop. LR doesn't crash nearly as much. But, there still  seems to be a lot of processing and drive I/O by merely traversing the film strip. It's odd that using the AI features don't present a problem.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 07, 2023 Dec 07, 2023

Copy link to clipboard

Copied

Bring up Google, and search on:

Faulting module name: ntdll.dll

 

Perhaps as a MS site discussion on that might help

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 21, 2023 Dec 21, 2023

Copy link to clipboard

Copied

Hi GoldingD and Rikk Flohr: Photography... With larger jobs out of the way, I finally had a chance to run the newest LrC version 13.1.0.8 and run "event viewer" after it crashed (same conditions as all previous version 13.xx crashes).

I have the "Application Error" data and the "Windows Error" data at the time of the crash. I am not sure what I'm looking for or what to do with the data. Would one of you or Adobe representative be interested in reviewing?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 22, 2023 Dec 22, 2023

Copy link to clipboard

Copied


@jeffm69483393 wrote:

Hi GoldingD and Rikk Flohr: Photography... With larger jobs out of the way, I finally had a chance to run the newest LrC version 13.1.0.8 and run "event viewer" after it crashed (same conditions as all previous version 13.xx crashes).

I have the "Application Error" data and the "Windows Error" data at the time of the crash. I am not sure what I'm looking for or what to do with the data. Would one of you or Adobe representative be interested in reviewing?


 

On the ntdll issue, another member with a similar problem had an additional dll issue, AcLayers.DLL, (in this very discussion) and that one leads to a Windows OS problem with Visual C++ and another members post: https://community.adobe.com/t5/lightroom-classic-discussions/error-api-ms-win-crt-convert-l1-1-0-dll... that show a need to reinstall Visual C++. I suspect that you may want to visit that. Otherwise probably contact Adobe, or perhaps Microsoft.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 22, 2023 Dec 22, 2023

Copy link to clipboard

Copied

I'm sure many other apps use the same Dll and don't have this issue.  This started with a version change to LrC.  IMHO it's an Adobe issue.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 11, 2023 Dec 11, 2023

Copy link to clipboard

Copied

Along with ntdll.dll errors in my Windows (10) log, I got another DLL error:

Faulting application name: Lightroom.exe, version: 13.0.2.1, time stamp: 0x6566d133
Faulting module name: AcLayers.DLL, version: 10.0.19041.3636, time stamp: 0x2ca84e8d
Exception code: 0xc0000374
Fault offset: 0x000000000000add6
Faulting process id: 0x1fac
Faulting application start time: 0x01da2c45995c3568
Faulting application path: C:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exe
Faulting module path: C:\WINDOWS\SYSTEM32\AcLayers.DLL
Report Id: e33f22b0-3ea7-4017-8911-e2924a554fe1
Faulting package full name:
Faulting package-relative application ID:

 

I never had this level of crashing until the move to version 13.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 21, 2023 Dec 21, 2023

Copy link to clipboard

Copied

quote

Along with ntdll.dll errors in my Windows (10) log, I got another DLL error:

Faulting application name: Lightroom.exe, version: 13.0.2.1, time stamp: 0x6566d133
Faulting module name: AcLayers.DLL, version: 10.0.19041.3636, time stamp: 0x2ca84e8d
Exception code: 0xc0000374
Fault offset: 0x000000000000add6
Faulting process id: 0x1fac
Faulting application start time: 0x01da2c45995c3568
Faulting application path: C:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exe
Faulting module path: C:\WINDOWS\SYSTEM32\AcLayers.DLL
Report Id: e33f22b0-3ea7-4017-8911-e2924a554fe1
Faulting package full name:
Faulting package-relative application ID:

 

I never had this level of crashing until the move to version 13.


By @HugeBob

 

 

see:

https://community.adobe.com/t5/lightroom-classic-discussions/error-api-ms-win-crt-convert-l1-1-0-dll...

 

Windows OS problem with Visual C++

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 17, 2024 Jan 17, 2024

Copy link to clipboard

Copied

I had this problem on version 13.1. Before that, I used the 12th version - no problem.
Version 13.1 crashed constantly. I have updated the C++ Runtime libraries (I have Win 11 23h2) - and I have been working without problems for two days now.
Download page for C++ libraries on the Microsoft website:
https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 18, 2024 Jan 18, 2024

Copy link to clipboard

Copied

Alexey M  , thanks for your input. 

Did your LrC 13.1 crash occur in development module, when moving from one images to another image on filmstrip?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 18, 2024 Jan 18, 2024

Copy link to clipboard

Copied

Yes, the LrC was constantly crashing when switching between images in the Develop module. I usually couldn't even scroll through ten photos. Of course, it was impossible to work like this - I went to look for a solution and read about C++ here.
Everything is working fine now.
By the way, C++ Runtime is the standard system components. If you update them using the link I wrote above (and it's from the official Microsoft website), nothing bad will definitely happen.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 19, 2024 Jan 19, 2024

Copy link to clipboard

Copied

Alexey M, thank you for the info. I downloaded the appropriate MS Visual C++ and installed. I'll give LrC 13.xxx another try, with the next small job.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 30, 2024 Jan 30, 2024

Copy link to clipboard

Copied

Alexey M, I finally had a chance to install the files from the link you provided. My LrC version 13.1 still crashes, when scrolling through images in develop module. Event Viewer still shows a ntdll.dll error.

Is your stystem working without crashes?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 31, 2024 Jan 31, 2024

Copy link to clipboard

Copied

Same here. Uninstalled every Visual C Runtime, installed the latest versions in x86 and x64, still lightroom crashes after a few photos. Deleting preferences also did not work. Or latest drivers. I'll try to uninstall it and reinstall it. (Windows 11 german, latest, GTX2080, 4096x2160, 128GB DDR4, i9 13900K, not overclocked. Nothing else crashes, just lightroom)

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 14, 2024 Jan 14, 2024

Copy link to clipboard

Copied

I'm running lightroom classic 13.1 and having the same issue.  Windows 11 for me, and I'm in the middle of a job so can't move back to version 12.xxx becaue the library was updated for 13.  

Thank you jeffm for the clarification that it only crashes when moving between filtered images, for me in Develop Mode.  I'll try making a collection of just the filtered images and see if that helps. 

I've done all the troubleshooting steps, with no success.  Crashes are instantaneous, with no close dialog.  

Event Viewer shows: 

AppPathC:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exe
  ModulePath

C:\WINDOWS\SYSTEM32\ntdll.dll

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 14, 2024 Jan 14, 2024

Copy link to clipboard

Copied

LrC 13.xxx (any version 13) is not stable on my system. Continual crashing as described above is an ongoing problem. 
The only way I can get work done is to revert to the stable LrC 12.5. 

An Adobe representative and a discussion board expert have been helpful in pointing to a direction to track down the cause of the error. They say "it likely a Windows OS issue".

When I get time, I can post the latest crash data... or send it to Adobe, if they desire. 

I don't understand why ONLY LrC 13.xxx is the ONLY app that crashes. 
All other apps including LrC 12.5 run with no issues. 

I can only spare the time to test/try LrC 13.xxx with tiny jobs, due to frequent crash interruptions. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 15, 2024 Jan 15, 2024

Copy link to clipboard

Copied

I might have an insight.  Check your catalog settings, and see if you're set to Automatically write changes into xmp, and/or to Write date or time changes into proprietary files.  I was, and unchecking them seems to make my machine more stable.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 15, 2024 Jan 15, 2024

Copy link to clipboard

Copied

Thanks Will. I'll take a look at that, with the next small job. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 22, 2024 Mar 22, 2024

Copy link to clipboard

Copied

Did anyone on this thread figure this out?  I went down the Windows OS error route and did all the .dll fixes, it was all clean and had one issue when re registering the ntdll.dll file saying no entry point found which is being said that is not an OS issue, that is a Lightroom error and to do all the .dll cleanup steps and uninstall/reinstall lightroom since Microsoft can't fix it on their end since the dll files are working. 

 

I have done the uninstall and reinstall many times the past 6-8 months this has been going on and no fix, but trying yet again after doing the command prompt cleanups.

 

If this doesn't work, then there is probably nothing we can do other than wait for Adobe to fix it.....but it's been 6-8 months since this has been happening and they have replied twice with zero input except saying they don't see our crash reports, because Lightroom isn't generating it, and then not even trying to look into it....

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Mar 22, 2024 Mar 22, 2024

Copy link to clipboard

Copied

I did find effective & expert help at Facebook "Adobe Photoshop Lightroom"

at https://www.facebook.com/lightroom/  .
In my case, it looks like my original (very large) V12.51 catalog was corrupted for use in version 13.x  (or was corrupted during original attempted upgrade to V13) ... something wasn't working correctly.
In any case … Adobe rep with initials " ^SK " was able to guide me through some fairly complicated (and logical) operations to correct. I have been running the latest 13.x version, ever since.
I would say that now, latest version of LrC 13.x is running much better than the “old reliable version 12.51” ... it was very much worth the time & & effort in listening to " ^SK ", on the Adobe link I mentioned above.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 23, 2024 Mar 23, 2024

Copy link to clipboard

Copied

I had gone through an entire day process with Adobe live support with this having me create a brand new Catalog for V13.  Which is the catalog I'm using now with the same issue as the previous one that was upgraded from 12 to 13   =/

 

Today, I seen someone else mentioning they had theirs stabilize after disabling the auto update metadata.  Which made me think about it, it might have been similiar timing of when I found that option and enabled it to when this whole issue started around V13 release.  So right now I'm testing it disabled and so far so good, but every time I say that, it crashes again.....so we'll see.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Mar 23, 2024 Mar 23, 2024

Copy link to clipboard

Copied

My remedy was much more involved than only creating a new catalog (I wanted to retain the data in my existing version 12.51 catalog).

As directed by Adobe support, I had to create a "new user" account on my PC (running Win10).

This new "user account" was used as a tool for diagnosis and correcting. The Adobe support and I communicated over a period of 3 weeks. We got back to each other as we had time.
My LrC is now running great with the latest version 13.2.

 

If your crashing issues are exactly as I had ... I could try to post the FB communication thread here that I had with a super patient and knowledgeable Adobe support staff.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 11, 2024 Apr 11, 2024

Copy link to clipboard

Copied

Oh yes, please do post that FB Thread. This problem is driving me crazy, 48 crashes alone today.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 18, 2024 Jan 18, 2024

Copy link to clipboard

Copied

This is exactly my problem. Since moving to LR 13.x. Never happened with any version before, doesn't happen with any other program (Creative Suite, Office). Windows 11, german, latest studio drivers (GTX 2080):

 

Name der fehlerhaften Anwendung: Lightroom.exe, Version: 13.1.0.8, Zeitstempel: 0x6576c53f
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.22621.2506, Zeitstempel: 0xbced4b82
Ausnahmecode: 0xc0000374
Fehleroffset: 0x000000000010c7a9
ID des fehlerhaften Prozesses: 0x0x9634
Startzeit der fehlerhaften Anwendung: 0x0x1DA49F3B3384690
Pfad der fehlerhaften Anwendung: C:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: 65f670d1-126b-4bc0-9aad-d230300a0ed5
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

 

And 20 minutes later:

 

Name der fehlerhaften Anwendung: Lightroom.exe, Version: 13.1.0.8, Zeitstempel: 0x6576c53f
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.22621.2506, Zeitstempel: 0xbced4b82
Ausnahmecode: 0xc0000374
Fehleroffset: 0x000000000010c7a9
ID des fehlerhaften Prozesses: 0x0x3200
Startzeit der fehlerhaften Anwendung: 0x0x1DA49F69FB469A9
Pfad der fehlerhaften Anwendung: C:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: cf6a59a8-d4d9-4d33-9e5e-64291ab26f66
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

 

it is unusable this way.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 01, 2024 Jun 01, 2024

Copy link to clipboard

Copied

I also have the exact same problem in version 13 until now, still in the develop module when I scroll through the photos in the filmstrip area, and while searching the web for the solution to the problem I arrived at this page, and reading what another user ( willwenzel) says at page 2, I finally arrived at the solution, simply by disabling automatic data writing in xmp. Every other attempt was in vain.
Since yesterday, trying to deactivate the check on the automatic writing of xmps, I have been working for many hours and I have never had a crash again, when previously after a few minutes the application inevitably crashed. Fingers crossed, the problem appears to be resolved.
I hope this can help someone.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines