Lightroom Classic: Crashes Windows every time started

  • 1
  • Problem
  • Updated 3 months ago
  • (Edited)
Lightroom Classic CC causes an immediate windows crash (blue screen) every time the program is started. The error is WHEA_UNCORRECTABLE_ERROR, which has an error Code of 124.

The good news is that _disabling_ Intel Speedstep in my Bios (Dell Alienware 18-core i9). Fixes this problem. No more crashing, and I can use LR. But this is only a partial fix, because without speedstep, the PC runs at a fixed 1.2 GHz, whereas with it, it runs at 2.6 to 3.4 GHz.

Anyway, this needs attention, since it's so consistent, I can't be the only one with this problem.

FWIW, Camera One also does this. In my desperation, I thought I could use it while you guys figured it out, but it also crashes in exactly the same way. (Lightroom cloud based also crashes.)

Bottom line is that Microsoft changed something and that's causing you problems. (I think.)
Photo of David Littleboy

David Littleboy

  • 5 Posts
  • 0 Reply Likes

Posted 3 months ago

  • 1
Photo of David Golding

David Golding

  • 117 Posts
  • 15 Reply Likes
So you are over clocking your rig? Seen that as an issue before. Nope, I do not have a link.


Can Titles in this blog be changed? If so, perhaps a title more akin to overclocking....

Oh, this is LR CC, my bad, Past info would have been for LRC
(Edited)
Photo of David Littleboy

David Littleboy

  • 5 Posts
  • 0 Reply Likes
Nope, no overclocking. And since the crash is instant, it's not overheating. The PC runs all 18 cores at 3.4 GHz for extended periods just fine.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1665 Posts
  • 571 Reply Likes
User mode applications such like Lightroom cannot be the root cause of BSOD. It is just a red-herring indicating some lower level hardware or driver failures.
Photo of David Littleboy

David Littleboy

  • 5 Posts
  • 0 Reply Likes
Sure, it's not _Lightroom_ that's the _root_ cause of the crash.

But Lightroom and Capture One are the only way to cause the crash, and they do so reliably. No other apps, no hardware diagnostics have any problems whatsoever.

"It's not our fault" may keep lawyers happy, but it shouldn't keep a computer scientist happy.

Photo of David Golding

David Golding

  • 117 Posts
  • 15 Reply Likes
Not over Locking? you stated that an app “without speedstep, the PC runs at a fixed 1.2 GHz, whereas with it, it runs at 2.6 to 3.4 GHz.” forcing a 2.6 GHz CPU to run at 3.4 GHz is overclocking
Photo of David Littleboy

David Littleboy

  • 5 Posts
  • 0 Reply Likes
Well, I wouldn't mind running LR at 2.6 GHz, but haven't figured how to yet, so thanks to (presumably) LR's aggressive attempts at improving performance, I get to run my PC at less than half speed. So I'm irritated. (If I sound irritated, it's because I am.)

FWIW, using Intel provided clock control is not called "overclocking". Overclocking is when you go outside manufacturer defined/recommended limits. It's what game folks do. I don't do that. I wouldn't complain if LR found problems under conditions outside manufacturer defined normal operation.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1665 Posts
  • 571 Reply Likes
BSOD clearly indicates a hardware/driver issue at play here. I am not sure what Lightroom or CaptureOne can do to fix that. I just don't want you wait for a solution from the wrong source instead of troubleshooting the hardware/driver.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1674 Posts
  • 576 Reply Likes
BSOD? It looks like Windows does not like overclocking under heavy load. Maybe it is overheating? 
Photo of David Golding

David Golding

  • 117 Posts
  • 15 Reply Likes
Following link is old, and not your exact model. But it reminds people to check for BIOS updates. This involved an Alienware rig, speedstep, Lightroom, and a BIOS update

https://forums.adobe.com/thread/2466582
Photo of David Littleboy

David Littleboy

  • 5 Posts
  • 0 Reply Likes
Thanks. I'll see if I can get the attention of the folks at Alienware. This appeared suddenly, after a _Windows_ upgrade, so there are lots of people involved in this glitch.