Lightroom: Recent update causing instant crashes

  • 2
  • Problem
  • Updated 2 years ago
  • (Edited)
updated 15 min ago.  LR instantly crashes OS on every start now.  something is badly broken.  Of course, support is not available now.  Has anyone actually heard of a cure or am I out of business for some weeks now?
Photo of Richard Clary

Richard Clary

  • 4 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 2
Photo of Ignacio Barrientos

Ignacio Barrientos, Employee

  • 84 Posts
  • 6 Reply Likes
Any information about OS version would help, if on macOS please attach crash log.
Photo of Richard Clary

Richard Clary

  • 4 Posts
  • 0 Reply Likes
After hours (2.5) of trying to figure out the horrible adobe website that is nothing but buy this damn thing in circular fashion I finally remembered I used thunderbird for this an so find this email.  I am putting in some information here.  If you can help it would be fine as adobe is not usable at all.  Around 65 hours now of internet reading and not a bit of help.  I can find not one ~lock anything on this system.  Every catalog I have opened other than the first one opens, and after closing is "locked by me". 

System Config:

Mobo EVGA Z-77 FTW 151-IB-E699 1155 LGA

CPU Intel i7 3770K 3.5Ghz no OC

Ram 32 GB GSkill 9 9 9 24 2T @1866mhz no OC

Video EVGA 660Ti (Nvidia) rev A2

Win7 Ultimate/LinuxMint 18 Dual boot. Works fine for years this way.


Very sorry to you all for not putting in relevant data. I was at end of a 23 hour work when that happened.

 What went on: I saw a notice of upgrade online, stupidly clicked and told it to update from LR CC. At end of update I restarted LR, clicked on the picture, instant white screen, had to use windows to turn it off. Tried again, clicked on picture, okay, pushed arrow key to go to next photo, instant white screen.    I turned off machine and went to bed. Turned machine on some hours later, clicked on LR to go to work, it instantly froze to a white covered screen saying not responding. Hit X in corner, re-click to start again, it came on, i moved the mouse to a photo, instant freeze again to the white screen, not responding. Restart machine, try to start LR again, it began, I moved through a couple pictures w/ the arrow keys, then,same result and no responding. So mad now I just take next of day off. Turn it on again today @ 5 PM CST 24 September, 2016, it promptly informs me that the catalog Africa is not writable and crashes again.  Over the last week this has never opened a catalog again and PS is now BSOD on first mouse click.  Nothing adobe will work.  The CC red update thing seems gone from the machine.  I did not do anything, it is just gone.


My direct need is to undo this last update. How? Or, can it be fixed? Just info, the machine has been stable for years in its current state. The update began a cascade of fail. I do not know how to find a log if one exists so, I would need that instruction. I do thank anyone who is willing to help. Thanks to all, Richard Clary

Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14190 Posts
  • 1787 Reply Likes
What does the event viewer say the faulting module is?

This behavior sounds like the result of an old/bad video driver.

Determine what video card you have and go *directly to the manufacturers website (nVidia or ATI/AMD)* and download the latest driver.

Just doing Windows Update won't give you the latest and greatest drivers. You must go directly to your card manufacturers website to check for driver updates.

If that doesn’t solve it, go to the Preferences in Lightroom and uncheck “Use Graphics Processor” under the Performance tab and restart Lightroom: https://helpx.adobe.com/lightroom/kb/lightroom-gpu-faq.html

If you still need to rollback, you can do that by following the instructions here: https://helpx.adobe.com/lightroom/kb/roll-back-to-prior-update.html
(Edited)
Photo of Richard Clary

Richard Clary

  • 4 Posts
  • 0 Reply Likes

I do not know of an event viewer.  I suspect likely in computer management?  What would I look for?  Will do so if I know what is needed.

Let me be clear here.  Going to LR and setting anything is not going to happen because the program will not start now!  It says the catalog is "not writable" is locked or open.  When I opened an earlier date of that catalog, it worked until I closed it and that version is now "not writable" Locked or open or I don't have permission.   The whole CC master program just disappeared with this upgrade.  is that expected?  That is the one I used to start the update as always before. 

at the risk of being testy, after now near 6 days of no ability to even start a program that worked perfectly until an update I find video driver way down my list of suspects.  Never the less, I use a 368 series driver for a card that started w/ a 320 series driver.  Why on earth would a driver fault cause a catalog to be locked?  why would it cause  the next catalog to do the same thing?  Photoshop is now acting up.  Every other thing runs fine on the machine as always have. 

To be fair, nvidias drivers seem to be game update oriented instead of performance oriented.  I shall now get and install the latest thing just to make that checkbox.  DONE.  378.90 installed. that one is only a few days old. I will restart now right after sending this.

  Please know, I do appreciate that you will try and help I am just insane mad now.  Not you, just this situation is not tenable.  Thank you for your effort.  I will see how reboot goes.  If I do not hear back today I will try the rollback thing.

Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14190 Posts
  • 1787 Reply Likes
You are describing two different things. If the file is locked, then see this document: https://helpx.adobe.com/lightroom/kb/lightroom-error-catalog-cannot-be-opened-lrcat-lock.html

If Lightroom is crashing when you go to the develop module, that's likely an unsupported card or a bad GPU driver.
Photo of Richard Clary

Richard Clary

  • 4 Posts
  • 0 Reply Likes

I have spent ~40 min trying to send a very long reply.  This system is near useless,  Is it possible to have an exchange where it may work and not make me endlessly resign in everytime I "submit"? 

Short note, I just opened PS and did one simple operation and it did not crash for that tiny test.  While I respect you believe that this is hardware, I submit if it was every program would suffer equally from that big a defect.  Remember, I have stated this started from the instant of a upgrade effort.  The likelihood of a hardware or driver fail coinciding with the download while a non zero number is never the less incredibly small.  LR original crash was on the first click after an upgrade and it has now done this to two catalogs. 

Addin:  I just spent 1:47:44 on phone w/ india.  The nice kid messed around doing the same things over and over w. zero results.  The message is not a locked catalog it is about a catalog that is either damaged now or not workable.  The worry is now that having seen it do this to every catalog it opens I think the update is in fact doing this.  Any engineer types who might give a go at analysis?
(Edited)