LR 4.3RC crash in ntdll.dll when switching modules

  • 1
  • Problem
  • Updated 6 years ago
  • (Edited)
It just halted and disappeared... this is from the event log. Other than that it has been running great.


Log Name: Application
Source: Application Error
Date: 11/19/2012 7:59:32 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Kennel_1-PC
Faulting application name: lightroom.exe, version:, time stamp: 0x5090f332
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x117c
Faulting application start time: 0x01cdc66b6e00dad4
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3 RC\lightroom.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 1b305572-3262-11e2-850a-485b390a32f9
Event Xml:



C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3 RC\lightroom.exe
Photo of DuhX


  • 17 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 1
Photo of Becky Sowada

Becky Sowada, Adobe Employee

  • 508 Posts
  • 105 Reply Likes
what were you doing in Lightroom when this happened? Can you make it happen again if you follow the same steps?
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2657 Posts
  • 341 Reply Likes
In my experience, ntdll.dll handles system memory allocation. Did you run LR out of memory by working on a large number of images, or doing a large number of edits to an image? You can watch LR's memory allocation in Task Manager, Processes tab. If you are running the 32-bit version of LR memory will run out faster.

if Adobe can replicate the problem they might be able to fix it; otherwise, if it doesn't happen again for you or for them, then the chances of it getting fixed are slim, unless, of course the issue manifests itself in another way and is diagnosed and fixed, then.
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
0xc0000374 is a heap corruption. This usually means that the ntdll library is corrupt in some manner. It will be hard to pin-point or even reliably reproduce because it was probably just chance the Lightroom failed -- it could just as easily have been any of the many other apps that need the library for allocations.

For example, it could be a driver that went sideways, taking out part of the heap. Have you introduced any new hardware lately? Even stuff like new USB devices can cause the execution profile of this library to change a lot.
Photo of DuhX


  • 17 Posts
  • 0 Reply Likes
I have not been able to reproduce the problem. It occurred when switching between develop and book modules. At the time I was working on very small projects of about 250 pictures.

I have a very stable system. I have not added any new hardware for awhile. Running Win 7 home premium on a Intel 930, 64 bit, 6GB ram and ATI Radeon HD 5800 video with 1 GB memory.

It has been a long time since I have had LR fail. LR 4.2 started out slow but now it works great with out crashes. With this new RC version I thought I would pass along this information should other have a similar problem.
Photo of Dorin Nicolaescu-Musteață

Dorin Nicolaescu-Musteață, Champion

  • 703 Posts
  • 38 Reply Likes
If this only happens (happened) when entering the Book module, take a look at his topic: .