Skip to main content
antti_t
antti_t
Participating Frequently
October 23, 2017
Answered

LR crashes after been updated to Classic CC

  • October 23, 2017
  • 1 reply
  • 896 views

I just updated LR 6 to Classic.

After updated I was able start it ones. The library conversion was successful but LR crashed right after that.

Now LR crashes every time I start it.

How to recover?

    This topic has been closed for replies.
    Correct answer Sean McCormack

    LR 6 crashed too. Here is the error:

    I started LR6 again this time with CTRL button. I selected the current library and successfully run integrity check. Then LR crashed again.

    Error 10/24/2017 15:17:26 Application Error 1000 (100)

    Log Name:      Application

    Source:        Application Error

    Date:          10/24/2017 15:17:26

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      nnn

    Description:

    Faulting application name: lightroom.exe, version: 6.0.0.10, time stamp: 0x5523190c

    Faulting module name: nvoglv64.DLL, version: 21.21.13.7653, time stamp: 0x5865011a

    Exception code: 0xc0000005

    Fault offset: 0x0000000000882451

    Faulting process id: 0x1e85c

    Faulting application start time: 0x01d34cc203c9c315

    Faulting application path: C:\Program Files\Adobe\Adobe Lightroom\lightroom.exe

    Faulting module path: C:\WINDOWS\SYSTEM32\nvoglv64.DLL

    Report Id: eed862a1-07eb-4d4c-b5b4-201d4afd7bfc

    Faulting package full name:

    Faulting package-relative application ID:

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Application Error" />

        <EventID Qualifiers="0">1000</EventID>

        <Level>2</Level>

        <Task>100</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2017-10-24T12:17:26.508198800Z" />

        <EventRecordID>110193</EventRecordID>

        <Channel>Application</Channel>

        <Computer>nnn</Computer>

        <Security />

      </System>

      <EventData>

        <Data>lightroom.exe</Data>

        <Data>6.0.0.10</Data>

        <Data>5523190c</Data>

        <Data>nvoglv64.DLL</Data>

        <Data>21.21.13.7653</Data>

        <Data>5865011a</Data>

        <Data>c0000005</Data>

        <Data>0000000000882451</Data>

        <Data>1e85c</Data>

        <Data>01d34cc203c9c315</Data>

        <Data>C:\Program Files\Adobe\Adobe Lightroom\lightroom.exe</Data>

        <Data>C:\WINDOWS\SYSTEM32\nvoglv64.DLL</Data>

        <Data>eed862a1-07eb-4d4c-b5b4-201d4afd7bfc</Data>

        <Data>

        </Data>

        <Data>

        </Data>

      </EventData>

    </Event>


    Google basically says the defaulting DLL is an NVideo OpenGL ICD..

    Are you graphics card drivers up to date?

    1 reply

    Akash Sharma
    Akash Sharma
    Legend
    October 23, 2017

    Hi antti_t,

    Did the app crashed right after the catalog conversion or were you able to work through few images before it crashed?

    What is the operating system in use on your computer? Also, try the troubleshooting steps listed in this article Adobe Lightroom GPU Troubleshooting and FAQ and update this discussion with the outcomes.

    Thanks,

    Akash

    antti_t
    antti_tAuthor
    Participating Frequently
    October 23, 2017

    It crashed right after conversion.

    I'm running Win10.

    I tried disabling GPU. No difference.

    Just checked the logs and found these to events:

    Log Name:      Application
    Source:        Adobe Setup
    Date:          10/23/2017 13:51:20
    Event ID:      1
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      nnn
    Description:
    The description for Event ID 1 from source Adobe Setup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    Installing Adobe Lightroom 6.0.0.0 {8048A5DF-8A70-5BE1-954B-E0FDE1BD0D0D}

    the message resource is present but the message is not found in the string/message table

    Event Xml:
    <Event xmlns="">
      <System>
        <Provider Name="Adobe Setup" />
        <EventID Qualifiers="16386">1</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2017-10-23T10:51:20.322492600Z" />
        <EventRecordID>109167</EventRecordID>
        <Channel>Application</Channel>
        <Computer>nnn</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Installing Adobe Lightroom 6.0.0.0 {8048A5DF-8A70-5BE1-954B-E0FDE1BD0D0D}</Data>
      </EventData>
    </Event>

    Log Name:      Application

    Source:        NVIDIA OpenGL Driver

    Date:          10/23/2017 14:03:27

    Event ID:      2

    Task Category: None

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      nnn

    Description:

    The NVIDIA OpenGL driver has not been able to initialize

    a connection with the GPU. This might be due to out of memory error,

    an exhaustion of system resources or too many graphical applications running.

    The application will not render correctly.

    Event Xml:

    <Event xmlns="">

      <System>

        <Provider Name="NVIDIA OpenGL Driver" />

        <EventID Qualifiers="32768">2</EventID>

        <Level>3</Level>

        <Task>0</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2017-10-23T11:03:27.126234400Z" />

        <EventRecordID>109169</EventRecordID>

        <Channel>Application</Channel>

        <Computer>nnn</Computer>

        <Security />

      </System>

      <EventData>

        <Data>The NVIDIA OpenGL driver has not been able to initialize

    a connection with the GPU. This might be due to out of memory error,

    an exhaustion of system resources or too many graphical applications running.

    The application will not render correctly.</Data>

      </EventData>

    </Event>

    Sean McCormack
    Community Expert
    Sean McCormackCommunity Expert
    Community Expert
    October 23, 2017

    Can you hold down the Control key when starting Classic? This should bring up a catalog picker. See if it runs okay with a new catalog. You may be able to import the updated catalog into this-it will lose publish services records though.

    Sean McCormack. Author of 'Essential Development 3'. Magazine Writer. Former Official Fuji X-Photographer.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices