Lightroom Desktop Freezing/Flashing when in detail view, moving photos, or attempting to edit

[ArchersParadox]

I have been having issues with Lightroom Desktop. Initially, I thought it was an issue with my PC's CPU (previously over 10 years old), but after making significant hardware upgrades, I am still having this issue, and the desktop version is unusable, outside of importing photos for me to edit on my tablet. 

While opening any photo in the detail view, clicking on anything causes the screen to flash and the program to go unresponsive for several minutes. I'm not able to change any sliders, access presets, or change photos without this occurring. While in grid view, if I go to copy settings or change galleries, it will also freeze, but it seems to be alright when navigating the UI, creating or organizing galleries/folders, importing photos or exporting to SmugMug. 

Given the significant upgrades to my PC, I would think the program should run even better than it does on my tablet, and I would love to have that functionality back. 

Below are my LR and system specs, and I've also attached a copy of the diagnostic log and the more detailed, exhaustive report. 

Lightroom version: 8.2 x64 [ 20250201-0700-1b12095 ] (Feb 1 2025)
NGL Version: 1.39.0.9
WF Version: 7.2 963a5a9
VF Version: 1.0.154
HIL Version: 40501
CAI Version: adobe_c2pa/0.9.3 c2pa-rs/0.31.0
PH Version: 5.0

Operating system: Windows 11
OS Version: Windows 11 Pro (2009)
Application architecture: x64
System architecture: x64
Computer model: ASUS System Product Name / Intel(R) Core(TM) i9-14900K
Logical processor count: 32
Processor speed: 3.1 GHz
Real memory available to Lightroom: 130788.8 MB
Real memory used by Lightroom: 45551.0 MB (34.8%)
Virtual memory used by Lightroom: 93608.6 MB
Memory cache size: 13484.9 MB

Internal Camera Raw version: 17.2 [ 2155 ]
Maximum thread count used by Camera Raw: 17
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 648MB / 63346MB (1%)
Camera Raw real memory: 649MB / 130788MB (0%)

Displays: 1) 3840x2160, 2) 1920x1080
System DPI setting: 144 DPI (high DPI mode)
Dark Mode: Yes
Desktop composition enabled: Yes
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: DirectX: NVIDIA GeForce RTX 3050 (32.0.15.6094) - 8 GB
Graphics Processor Detail: loaded: Yes, supported: Yes, compute: Yes, init: I4_GPU4, hard: success, soft: success, al: Yes, dl: No
OS Media Capability: true

Application Folder: C:\Program Files\Adobe\Adobe Lightroom CC
Settings Folder: C:\Users\Conno\AppData\Roaming\Adobe\Lightroom CC
Library Folder: C:\Users\Conno\AppData\Local\Adobe\Lightroom CC\Data

[moved from bugs to discussions according to the community rules - Mod.]

[F. McLion]

First, please update the driver of your graphic card, as v560.94 is rather old.

https://www.nvidia.com/en-us/drivers/details/242207/

[ArchersParadox]

Thank you for recognizing this. I've updated the driver, however doing so has had no impact on improving Lightroom's performance. 

[ArchersParadox]

I'm adding an update that I'm ALSO seeing a significant slowdown in Lightroom on my iPad now as well. Even with switching to storing my albums I'm actively editing locally, switch between photos still hangs up and is not performing to the speed I'm used to. 

I've also updated my internet speeds to 10GB thinking my network was causing sync slowdown, but have not seen an improvement. 

[ArchersParadox]

I've now switched to edit on my phone, which is not ideal but was working decently for much of the day. Now, it crashes evey time I start applying a mask. 

[ArchersParadox]

Yet another update that this is still an ongoing issue across platforms for me. I did contact support, they ultimate did a remote access on my PC, cleared the cache, changed some settings, reinstalled my graphics driver, then disconnected. None of this resolved the problems. 

I have over 20,000 photos from several events going back to the beginning of March that have been significantly delayed due to these ongoing issues. At this point, I really feel my only course of action will be seeking refunds on my subscriptions and finding alternative software.