Inspiring

Question

LR Classic doesn't open any exsisting catalog anymore

Forum|Forum|1 year ago
August 10, 2024
3 replies
889 views

Hi all, I have moved onto a new machine, so it's a completely new installation of Windows 11 Pro and LR Classic. Katalog and Data are on existing harddrive with same drive letters. With any existing catalog LR crashes while or shorty after opening the catalog. I can create a new catalog, but also can't import from any other existing catalog.

As I said, I have started from a clean fresh install from creative cloud, and meanwhile I have deinstalled and re-installed LR Classic several time - but the result is the same. I can't open any existing catalog (which is years of work).

Any ideas or does the crash report point to and indication?

Thanks, Christa

Crash report starts like this; I have tried to attach the file but wasn't successfull.

Windows

This topic has been closed for replies.

GoldingD

Legend

 drivers are updated Armoury Crate

Excellent, that nails that issue down as not the problem. Many people do not understand the MB Driver update issues. So I had to ask. For any member wondering what Armory Crate is, that is a ASUS application for checking and upgrading the MB drivers (and a bit more) on ASUS Motherboards.

Nivida is on latest version;

Some would ask if you selected a custom install type, but I assume you did. Also as your GPU is fairly new model (4000 series) as opposed to very old (say 800 series) I doubt if their is any left over bad code or files from older driver versions.

 I can create a new catalog,

I should have asked earlier. This new catalog, does it crash?

<crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x0000000077A7C38A">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x0000000077A7C38A" symbolname="luaopen_string"/>

So symbolname="luaopen_string"

I do not have a clue, A couple of similar earlier postings did not appear to get solved. Probably time to give Adobe a Chat/Call

_________________________________________________________________________

So, that crash report, when it showed up, did you fill it out, put in your e-mail, and send it on to Adobe?

If not, does it appear again, and then fill out the description of what you were doing, and I recommend including a link to your post in the LrC community (this post), include your e-mail address, and send it.

Christae10130384Author

Inspiring

Nvidia: Indeed, did a custom install, only installed the Nvidia driver and did unselect the two otthers (this time). Is this correct?
I had also intalled via custom install the graphics card driver and the other twos (don't remember them, sorry).

GoldingD

Legend

So, at this point:

If you can fill out that crash report dialog, and send to Adobe
Give Adobe a Chat/Call, perhaps tomorrow (not sure if they are available today). If you start a Chat, then include a link to your posting. And you may need to be assertive to have them arrange for a phone call (I suspect a Chat will not be all that helpful, but typically you start with a chat)

JohanElzenga

Community Expert

Update your GPU driver (if I read the crash report correctly it is from 01/15/2023, so way too old) and make sure you use the Studio driver, not the Game Ready driver.

-- Johan W. Elzenga

Christae10130384Author

Inspiring

Thanks Johan, Studio driver is updated to latest version, yet behaviour still the same. Sometimes worst now: no more crash report from Adobe und Bluescreen instead. Have attached another crash report from yesterday that shows the updated driver.

Christae10130384Author

Inspiring

Seems the crash report file doesn't go through, trying to copy paste it in.

<?xml version="1.0"?>
<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">
<crashreport serviceVersion="13.2.0.202308091502_65b8636" clientVersion="13.2.0.202308091502_65b8636" applicationName="Adobe Lightroom Classic" applicationVersion="13.4" build="[202406181129-60d181b7]" source="Windows-Client" crashType="n/a">
<time year="2024" month="8" day="10" hour="16" minute="59" second="53" timeoffset="60" timezone="W. Europe Daylight Time"/>
<user guid="18a2cfb0-b78b-4ba7-b590-c4f1adb5684f"/>
<system platform="Windows 11 Pro" osversion="11.0" osbuild="22631" applicationlanguage="de-de" userlanguage="de-CH" oslanguage="en-US" ram="65276" machine="Intel(R) Core(TM) i9-14900K" model="Intel64 Family 6 Model 183 Stepping 1" cpuCount="32" cpuType="8664" cpuFreq="3187 MHz" processorArchitecture="9"/>
<gpu>
<gpuinfo availability="Running/Full Power" adapterCompatibility="NVIDIA" adapterRAM="4095 MB" caption="NVIDIA GeForce RTX 4070 Ti" description="NVIDIA GeForce RTX 4070 Ti" driverDate="20240730000000.000000-000" driverVersion="32.0.15.6081" videoModeDescription="5120 x 2160 x 4294967296 colors" pnpDeviceID="PCI\VEN_10DE&DEV_2782&SUBSYS_88DD1043&REV_A1\4&256A0AA8&0&0008" installedDisplayDrivers="nvldumdx.dll"/>
</gpu>
<crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x0000000077A7C38A">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x0000000077A7C38A" symbolname="luaopen_string"/>
<stackStatement index="1" address="0x0000000077A7CBC9" symbolname="luaopen_string"/>
<stackStatement index="2" address="0x0000000077A8120C" symbolname="luaopen_table"/>
<stackStatement index="3" address="0x0000000077A5FA74" symbolname="lua_resume"/>
<stackStatement index="4" address="0x0000000077AA2BC9" symbolname="AgThrowProgramError"/>
<stackStatement index="5" address="0x0000000077A5FB1E" symbolname="lua_resume"/>
<stackStatement index="6" address="0x0000000077A52123" symbolname="luaopen_base"/>
<stackStatement index="7" address="0x0000000077A5EC8D" symbolname="lua_getstack"/>
<stackStatement index="8" address="0x0000000077A81E5E" symbolname="luaopen_table"/>
<stackStatement index="9" address="0x0000000077AA2BC9" symbolname="AgThrowProgramError"/>
<stackStatement index="10" address="0x0000000077A5F90F" symbolname="lua_resume"/>
<stackStatement index="11" address="0x0000000077A517AD" symbolname="luaopen_base"/>
<stackStatement index="12" address="0x0000000077A515A0" symbolname="luaopen_base"/>
<stackStatement index="13" address="0x0000000077A5EC8D" symbolname="lua_getstack"/>
<stackStatement index="14" address="0x0000000077A81E5E" symbolname="luaopen_table"/>
<stackStatement index="15" address="0x0000000077A5FA74" symbolname="lua_resume"/>
<stackStatement index="16" address="0x0000000077AA2BC9" symbolname="AgThrowProgramError"/>
<stackStatement index="17" address="0x0000000077A5FB1E" symbolname="lua_resume"/>
<stackStatement index="18" address="0x0000000077A4CF70" symbolname="lua_pcall"/>
<stackStatement index="19" address="0x00000000775FECDA" symbolname="private_load_AgEventLoopUtils"/>
<stackStatement index="20" address="0x0000000077A5EC8D" symbolname="lua_getstack"/>
<stackStatement index="21" address="0x0000000077A81E5E" symbolname="luaopen_table"/>
<stackStatement index="22" address="0x0000000077A5FA74" symbolname="lua_resume"/>
<stackStatement index="23" address="0x0000000077AAE489" symbolname="AgLua_callWithAutoReleasePool"/>
<stackStatement index="24" address="0x0000000077A5EC8D" symbolname="lua_getstack"/>
<stackStatement index="25" address="0x0000000077A81E5E" symbolname="luaopen_table"/>
<stackStatement index="26" address="0x0000000077A5FA74" symbolname="lua_resume"/>
<stackStatement index="27" address="0x0000000077AA2BC9" symbolname="AgThrowProgramError"/>
<stackStatement index="28" address="0x0000000077A5FB1E" symbolname="lua_resume"/>
<stackStatement index="29" address="0x0000000077A4CF70" symbolname="lua_pcall"/>
<stackStatement index="30" address="0x000000007760027F" symbolname="AgMainThreadAction_trigger"/>
<stackStatement index="31" address="0x00007FF869F0257D" symbolname="BaseThreadInitThunk"/>
<stackStatement index="32" address="0x00007FF86BAEAF28" symbolname="RtlUserThreadStart"/>
</thread>
</backtrace>
<registerSet>
<register name="RAX" value="0x00000001522FA9C0"/>
<register name="RBX" value="0x0000000000000000"/>
<register name="RCX" value="0x000000007FFE0380"/>
<register name="RDX" value="0x00000000005B0129"/>
<register name="RSI" value="0x0000000000000010"/>
<register name="RDI" value="0x0000000000000010"/>
<register name="RSP" value="0x0000000029A9F160"/>
<register name="RBP" value="0x0000000000000004"/>
<register name="RIP" value="0x0000000077A7C38A"/>
<register name="EFL" value="0x0000000000010206"/>
<register name="LastExceptionToRip" value="0x0000000000000000"/>
<register name="LastExceptionFromRip" value="0x0000000000000000"/>
</registerSet>

</hbLogSessionDllStatus>
</crash>

<sessionId>
56b40dbb-39ec-485c-99bd-0435c6dca437
</sessionId>
<dunamisConfigGuid>
b521ffc8-5267-46ac-bf6b-51b6a798b840
</dunamisConfigGuid>
<imsUserGuid>
449D2EF947A8C3EE992016B6@AdobeID
</imsUserGuid>
</crashreport>

GoldingD

Legend

I have moved onto a new machine,

What is the make/model of that computer. Or if a custom computer, the make/model of the Motherboard?

I ask because I am wondering what support the Mfg provides to assist you in updating the various drivers that support the various components on the Motherboard. The Intel Chip Set, the Video (separate from GPU), the Ethernet, the WiFi, the Sound, Bluetooth, SATA, special ports, etc.

And of course, what about your GPU, assuming that is a card. What is it's make/model and driver version?

I had a similar issue, turns out my Chipset driver was out of date, and that one driver update fixed my LrC crash. Although I did not get a crash report.

Naturally I assume you have brought up your Windows Update, but that does not do such a good job on these sort of drivers. Searching on the instructuion appears to be a no go.

<crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x00000000773F8CEC">

In that crash report, further down their will be a section listing instruction="0x00000000773F8CEC" , can you post that?

And I assume you have used Google to search on this, that exceptionCode appears to have lots of causes.

exceptionCode="0xc0000005"

If you search in this community on that bit of info. Many postings will show up. Not sure if any got solved. You might want to try that.

Oh, and P.S. from one of those postings, do you perhaps have an Android Device attached to your computer? Old odd issue LrC sometimes has. That odd one from:

And if yu use google on "0xc0000005" you will probably see some instructions on Running sfc /scannow, One post in the community addresses that:

No longer can export JPEG images without LrC crashing

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded