Copy link to clipboard
Copied
Hey guys,
pretty much during a editing session and after days of editing (meaning no manual(!) changes to the system -> Win 10) Lightroom crashed and since then keeps crashing appr. 10s after startup. The crash log always looks similar to the attached one. What's weird: The program stays fully responsible and works fine behind the crash window. I can switch and use each and every module, edit and changes are saved.
Tried the classics (Reinstall, different versions 9.2 and 9.1, no GPU, deactivated anti virus etc.)
Any idea what the report is trying to tell me and what I should do? Very lost and on a schedule..
Thanks a lot.
Let me know if you need the full message.
<?xml version="1.0"?>
<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">
<crashreport serviceVersion="2.0.3" clientVersion="2.0.3" applicationName="Adobe Lightroom Classic" applicationVersion="9.1" build="[201911291132-64cf80b4]" source="Windows-Client">
<time year="2020" month="3" day="25" hour="15" minute="18" second="32" timeoffset="60" timezone="Mitteleuropäische Zeit"/>
<user guid="...."/>
<system platform="Windows 10 Home" osversion="10.0" osbuild="18363" applicationlanguage="de-de" userlanguage="de-DE" oslanguage="de-DE" ram="8078" machine="Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz" model="Intel64 Family 6 Model 142 Stepping 10" cpuCount="8" cpuType="8664" cpuFreq="1800 MHz"/>
<crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x00007FFF65EAB038">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x00007FFF65EAB038" symbolname="FxPluginMain"/>
<stackStatement index="1" address="0x00007FFF65EAF9E0" symbolname="FxPluginMain"/>
<stackStatement index="2" address="0x00007FFF65EAFCD5" symbolname="FxPluginMain"/>
<stackStatement index="3" address="0x00007FFF65EB9D75" symbolname="FxPluginMain"/>
<stackStatement index="4" address="0x00007FFF65EB410F" symbolname="FxPluginMain"/>
<stackStatement index="5" address="0x000000000DE5D825" symbolname="AgNativeGdiPlusImage::operator="/>
<stackStatement index="6" address="0x000000000DE5F4F5" symbolname="AgNativeGdiPlusImage::operator="/>
<stackStatement index="7" address="0x00007FFF72A27BD4" symbolname="BaseThreadInitThunk"/>
<stackStatement index="8" address="0x00007FFF734CCED1" symbolname="RtlUserThreadStart"/>
</thread>
</backtrace>
<registerSet>
<register name="RAX" value="0x000073258F054B78"/>
<register name="RBX" value="0x00000000522000C4"/>
<register name="RCX" value="0x0030003600320033"/>
<register name="RDX" value="0x000000003C4DD420"/>
<register name="RSI" value="0x00000000522000A0"/>
<register name="RDI" value="0x00000000522000C4"/>
<register name="RSP" value="0x000000003C4DD3E0"/>
<register name="RBP" value="0x000000003C4DD439"/>
<register name="RIP" value="0x00007FFF65EAB038"/>
<register name="EFL" value="0x0000000000010246"/>
<register name="LastExceptionToRip" value="0x0000000000000000"/>
<register name="LastExceptionFromRip" value="0x0000000000000000"/>
</registerSet>
<binaryImageSet>
<binaryImage start="0x0000000140000000" end="0x0000000141362000" path="adobe\Lightroom.exe"/>
<binaryImage start="0x00007FFF73460000" end="0x00007FFF73650000" path="ntdll.dll"/>
<binaryImage start="0x00007FFF72A10000" end="0x00007FFF72AC2000" path="kernel32.dll"/>
<binaryImage start="0x00007FFF70A00000" end="0x00007FFF70CA3000" path="KERNELBASE.dll"/>
<binaryImage start="0x00007FFF70710000" end="0x00007FFF70859000" path="crypt32.dll"/>
<binaryImage start="0x00007FFF70410000" end="0x00007FFF7050A000" path="ucrtbase.dll"/>
<binaryImage start="0x00007FFF470D0000" end="0x00007FFF47127000" path="adobe\CRClient.dll"/>
[...]
Daniel
Copy link to clipboard
Copied
For now a good nights sleep seems to have fixed the issue. Weird as it was reproductable 100% even after rebooting yesterday.
Copy link to clipboard
Copied
There was a time when earlier versions of Lr would crash and stay in memory (visible in Task Manager) and could not then be re-opened. I have not seen reports of this problem recently, but your problem sounds similar.
You could try the procedure below if the problem persists for you.