Skip to main content
Participant
November 16, 2022
Answered

(Win11 22H2) Lightroom Classic, Photoshop and Bridge are all crashing since recent Windows update

  • November 16, 2022
  • 1 reply
  • 2270 views

After latest (automatic) Windows 11 (22H2) Updates below, all installed (working) Lightroom Classic 2023 (12.0.1.0), Photoshop 2023 (24.0.0.59) and Bridge 2023 (13.0.0.562) are now crashing when loading Nikon NEF file. It actually crashes entire Windows OS and I have to power off to restart Windows OS. 

1. 2022-11 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5020622).

2. 2022-11 .NET 6.0.11 Update for x64 Client (KB5020743).

3. 2022-11 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5019980).

Today, I had tried to uninstall and reinstall Lightroom Classic 2023, Photoshop 2023 and Bridge 2023, but it do not fix any crashing issue. Can anyone help?

 

Two Lightroom's Windows system report are below:

Description
Faulting Application Path: C:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: Lightroom.exe
Application Version: 12.0.1.1
Application Timestamp: 6358cbe5
Fault Module Name: ui.dll
Fault Module Version: 12.0.1.0
Fault Module Timestamp: 6358ca88
Exception Code: c0000005
Exception Offset: 0000000000126a48
OS Version: 10.0.22621.2.0.0.768.101
Locale ID: 3081
Additional Information 1: ad3e
Additional Information 2: ad3ebaef0c582296709560c54298769f
Additional Information 3: bbb0
Additional Information 4: bbb059d4908a9d8487638c86e35807b6

 

Description
Faulting Application Path: C:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: Lightroom.exe
Application Version: 12.0.1.1
Application Timestamp: 6358cbe5
Fault Module Name: onnxruntime.dll
Fault Module Version: 1.11.22.318
Fault Module Timestamp: 62351fee
Exception Code: c0000005
Exception Offset: 00000000000377ce
OS Version: 10.0.22621.2.0.0.768.101
Locale ID: 3081
Additional Information 1: b1bf
Additional Information 2: b1bf8baffda55104261a94c32aba95e9
Additional Information 3: 2838
Additional Information 4: 28385993da9dcb32f83c16c585e889b0

 

 

 

{thread title updated by moderator}

This topic has been closed for replies.
Correct answer Bo Zhang

More info:

1. Once LrC or PS crashed, there is no way to start any applicartion with "out of memory" error!

2. I had already sent the Photoshop generated error report.


The root cause of "out of memory" crashing issue has now been identified and fixed in my PC. It is caused by disable "virtual memory" (page file) after Microsoft.NET update then repartitioning disk drive. 

Thanks for all your time and support.

1 reply

Sameer K
Community Manager
Community Manager
November 16, 2022

Welcome to the Lightroom Community. I'll help you with fixing this.


I've checked the crash reports & I could find one report for Photoshop & the above-shared information refers to Microsoft's machine learning API to be the cause. Follow the steps in this help article to submit crash reports for all the apps that crash: https://helpx.adobe.com/photoshop/kb/submit-crash-reports.html

 

You can also open Event Viewer from Windows Search.

  • Go to Windows Logs > Application Logs & look for Error & Warning logs.

     

  • Share the log related to Lightroom Classic or Photoshop's crash instance with us.

 

  1. Try booting up the Windows OS in Safe Mode to see if it still crashes.
  2. Try the troubleshooting steps to narrow down the issue: https://helpx.adobe.com/photoshop/kb/troubleshoot-crash-or-freeze.html

 

Keep me posted on how it goes from here. Thanks!

Sameer K

 

 

 

 

dj_paige
Legend
November 16, 2022

It actually crashes entire Windows OS and I have to power off to restart Windows OS. 

 

Entire computer crashing is almost always a symptom of a bad driver or a hardware malfunctions somewhere. You need to re-install/upgrade/downgrade all of your drivers for your computer (video driver is the most likely culprit but any other drivers such as motherboard or other could be the culprit). If that doesn't help then start looking for hardware malfunctions (disk drive, RAM, motherboard).