Skip to main content
January 1, 2026

P: Lightroom Classic Freezes (Black screen, UI glitch) after Using Object Select on Intel Arc 140T

  • January 1, 2026
  • 11 replies
  • 2758 views

Hello,

I recently posted on Intel's forum regarding problem with heavy gpu tasks on my laptop.
They asked me to post here to see if people on Adobe's side have any idea on how to fix this, and to cooperate.

My laptop is an Asus Zenbook (UX3405CA) :


- I9 285H

- Intel Arc 140T 16Go updated with the latest available driver (32.0.101.8331)

- The problem is still there with older drivers

- Windows 11 pro up to date

- Lightroom classic version 15.1

- Tried with older versions of Lightroom

- The BIOS has been updated
- Cleanded drivers with DDU in recovry mode then reinstalled through intel utility tool

- Recleaned them with DDU in recovery mode then reinstalled through MyAsus

The problem persists.
I get a LiveEventKernel with the code 141 in the event viewer every time the problem arises.

I have attached some relevant files, but can't add the dump because the format is not accepted.

I need your help to fix this problem permanently.

Thank you

11 replies

CSBTMAuthor
January 27, 2026

I just downloaded it and the problem still persists for me. Denoise and select object still crash the driver.

January 26, 2026

Sí, es lo que puse yo en el último mensaje. 

Participant
January 26, 2026

I just wanted to provide an update on this issue. On 1/16/2026, Intel released driver version .8425. This seems to have fixed the initial crashing and resetting of the GPU driver. I havent done any advanced edits yet, but the menu can load, detect objects and sub-objects (like eyes). Intel did not mention anything about this issue in their changelog, but for me, on first glance the issue seems to be fixed. Can someone else please confirm this isn't just me?

January 23, 2026

Hola, queria decir que hace 2 dias actualicé los drivers a la version 32.0.101.8425 y parece haberse arreglado el problema. Active el GPU en lighroom y editando utilizando IA no se tildó mas. 

 

Esperemos que sigua funcionando asi y espero que a todos le haya pasado. 

Participant
January 20, 2026

I am SOO glad I found this thread. This is EXACTLY what I am expereincing is incredibly frustrating and disheartening. I am running a Dell Pro Max 16 Premium (MA16250) with the ARC 140T 16GB model mentioned in this post. I just purchased this computer less than a week ago, and while everything else I need to do, such as cropping and color grading, works reasonably well. This is a huge issue that is making me regret my nearly $2300 purchase.

 

My machine shipped with driver version .8132  this was the version I was on when I originally discovered the crash. I have since updated to .8331, and the issue has improved ever so slightly, but it is still extremely unstable. I have had some luck with turning GPU acceleration off and trying to edit a 32.5MP file. (EOS R7) I also have some 45MP files (EOS R5), and those seem to instantly crash the driver and lock up Lightroom to a point where it needs to be restarted. The only way I have had any luck with masking on .8331 is exporting the picture in question (In this case, a 45MP one) in a lower resolution than re-importing the lower-res file, and it working as expected on the smaller file. This is just what I have been able to find after a few hours of trial and error, and your mileage may vary. This is not a viable solution for me, as I have already paid a significant amount for all the equipment involved (Computer, Lightroom, Camera, etc.), and I should not be forced to lower the resolution when I don't want to. The crash seems to be at least somewhat dependent on the size and context of the file, as well as whether GPU acceleration is on or off. Strangely, I tried using the AI erase feature, and that worked perfectly. Not even a momentary stutter. All other settings in this tab worked as intended, too.

As far as I can tell, enough documentation has been provided, but if need be, I will be happy to provide whatever is needed to get this problem fixed. Best of Luck Adobe team. Please keep us posted!

Participant
January 18, 2026

Bonjour à tous, 

 

Je viens aujourd'hui vers vous parce-que je suis au bout des solutions déjà explorées. 
J'ai un soucis avec mon nouvel ordianteur portable (vous trouverez ci-joint les informations système détaillées).

-Intel core Ultra9 285H

-Intel ARC 140T

-32Go RAM

 

Dès que j'utilise un masque IA (détection de personnes notamment), mon logiciel plante, parfois en affichant un message de plantage, d'autres fois en mettant un écran noir, puis en figeant l'affichage (exemple ci-joint).

J'ai essayé de mettre à jour mes pilotes, revenir à une ancienne version et même faire un reset Windows, rien n'y fait. 

 

J'avais trouvé une solution : limiter lightroom dans l'utilisation du GPU et restreinte l'utilisation au CPU. 
Cependant, cela me dérange dans mon travail puisque je note nettement le ralentissement. 

 

Lightroom V15.1


J'espère que vous pourrez m'aider à régler ce problème. 

 

Cordialement,

Tristan

johnrellis
Legend
January 19, 2026

"DirectX: Intel(R) Arc(TM) 140T GPU (16GB) (32.0.101.6554)"

 

That graphics driver appears to be a year old. Update to the latest driver here:

https://www.intel.com/content/www/us/en/download/785597/intel-arc-graphics-windows.html

 

However, if updating the driver doesn't help, note that Adobe has acknowledged problems with LR and the Intel Arc 140T and is investigating:

https://community.adobe.com/t5/lightroom-classic-bugs/p-lightroom-classic-freezes-black-screen-ui-glitch-after-using-object-select-on-intel-arc-140t/idi-p/15648937

 

 

Anshul_Saini
Community Manager
Community Manager
January 12, 2026

Hi Everyone,

 

Thank you for the detailed repro steps and for sticking with us through all the testing.

 

Here’s the current status, straight from the product side:

• The product team has logged this as a tracked bug affecting Intel Arc 140-series GPUs

• Engineering is actively investigating the root cause, based on the reproducible steps you shared

 

At this point:

• No additional troubleshooting is required from you

• The bug is under active investigation

 

I’ll keep this thread updated as soon as we have something concrete to share.

 

Thank you again for the thorough reporting and patience; it genuinely helped move this forward.

 

Best regards,

Anshul Saini

Anshul_Saini
Community Manager
Community Manager
January 12, 2026

updating status.

January 12, 2026

Wanted to hop in here and add that I am having similar issues, and came across this thread but very little else online. For me, Camera Raw fails to apply denoise when using my Samsung Galaxy Book 5 with a Core Ultra 256V and Arc 140V graphics. I select the option, and then it will say that "Graphics acceleration has been disabled due to an error." I followed the usual troubleshooting steps, DDU, driver updates, new profile, etc. but I get the same problem. I also then followed the recommended additional steps in this thread. I rolled back to Camera Raw 15.5 at the suggestion of a thread on Reddit which seems at least more stable, but doesn't have the newest features of course and still sometimes crashes and says "Graphics acceleration will be disabled for the rest of this session." I don't have any of these issues on my older Galaxy Book 2 with a core i7 1255u and the same amount of RAM, nor on my desktop. Thanks to those working on resolving, I look forward to hearing updates! 🙂

Anshul_Saini
Community Manager
Community Manager
January 7, 2026

Hi @CSBTM,

 

Thank you for running those controlled tests and for confirming the results. That was very helpful.

 

The additional testing shared by @almvang is especially valuable here. Their driver-by-driver breakdown clearly shows the issue. This aligns with your results and explains why disabling “Use GPU for image processing” avoids crashes, even though performance is reduced.

 

At this point, this is no longer a configuration or catalog issue. The behavior indicates a compatibility problem between Lightroom Classic’s GPU image processing pipeline and current Intel Arc drivers on certain systems.

 

I’ll reach out to the engineering team internally. I’ll update this thread as soon as engineering shares next steps or requests additional data. Thanks again to everyone for the thorough testing and clear reporting.

 

Best regards,
Anshul Saini