My desktop computer is spontaneously rebooting when Lightroom is open. This happens anywhere from 2-30 minutes after Lightroom is open. The computer does not crash or reboot for any other program. The only message that appears in Event Viewer is the following.
Log Name: System
Date: 9/17/2019 7:52:11 PM
Event ID: 41
Task Category: (63)
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
I have updated to the latest version of Windows, Lightroom and all of my motherboard BIOS and drivers. I'm running out of ideas for things to check and any help would be greatly appreciated.
1. Search the web (google) using ;
Lots of incidents, but not involving Lightroom Classic.
Perhaps a hardware issue, perhaps a driver issue
Do not forget that Lightroom Classic uses lots of resources. Phtoshop for one is a lot tamer in this regard. Lightroom Classic can be even nastier than high level games. So Lightroom Classic may be stumbling onto a hardware problem.
However, some items to consider
1. Do you have use GPU acceleration on or off. If on turn it off, see if that helps
2. Is this a desktop PC? Could the GPU (card) be loose, could an auxiliary power cable to the GPU be loose?
3. Are you overclocking the CPU?
And, you might, if you have not already, post your problem at :
Where actual Adobe techs hang out
However, the issue still occurred when opening Lightroom. I narrowed it down to Lightroom Sync. The machine would reboot whenever Sync was enabled. I deleted the entire mobile sync from the web and how Lightroom runs without the machine rebooting. It's quite disappointing to learn that this could be caused by Sync. No software should cause a machine reboot without throwing an error.
What is the Lightroom version?
Adobe Photoshop Lightroom Classic
I was able to use Lightroom for about a week after deleting all sync data. Now, the computer has again started spontaneously rebooting when Lightroom is opened.
I am facing the same problem, my friend. Please let me know if you have any better news.
Mine turned out to be a bad motherboard. Replacing the motherboard fixed this issue.