Answered

Light room error

Forum|Forum|7 months ago
December 13, 2025
2 replies
182 views

Good day for all,
How can I solve the following problem? thanks very much.

<?xml version="1.0"?>
<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">
<crashreport serviceVersion="29.0.0.202506270808_710830c" clientVersion="29.0.0.202506270808_710830c" applicationName="Adobe Lightroom" applicationVersion="9.0" build="20251017-1944-414afc8" source="Windows-Client" crashType="n/a">
<time year="2025" month="12" day="13" hour="13" minute="49" second="14" timeoffset="480" timezone="å°åŒ—æ¨™æº–æ™‚é–“" crsessionduration="21"/>
<user guid="285885d2-55b7-4c5e-8175-1a2cdb296ad6"/>
<system platform="Windows 10 Home" osversion="10.0" osbuild="19045" applicationlanguage="en-us" userlanguage="zh-TW" oslanguage="zh-TW" ram="65303" machine="13th Gen Intel(R) Core(TM) i9-13900K" model="Intel64 Family 6 Model 183 Stepping 1" cpuCount="32" cpuType="8664" cpuFreq="2995 MHz" processorArchitecture="9"/>
<gpu>
<gpuinfo availability="Running/Full Power" adapterCompatibility="Advanced Micro Devices, Inc." adapterRAM="24.0 GB" caption="AMD Radeon RX 7900 XTX" description="AMD Radeon RX 7900 XTX" driverDate="20251203000000.000000-000" driverVersion="32.0.22029.9039" videoModeDescription="1920 x 1200 x 4294967296 è‰²å½©" pnpDeviceID="PCI\VEN_1002&DEV_744C&SUBSYS_240D1458&REV_C8\6&13FD3BF3&0&00000008" installedDisplayDrivers="amdxc64.dll,amdxx64.dll,atidx9loader64.dll"/>
<gpuinfo availability="Off Line" adapterCompatibility="Intel Corporation" adapterRAM="128 MB" caption="Intel(R) UHD Graphics 770" description="Intel(R) UHD Graphics 770" driverDate="20241018000000.000000-000" driverVersion="32.0.101.6129" videoModeDescription="" pnpDeviceID="PCI\VEN_8086&DEV_A780&SUBSYS_D0001458&REV_04\3&11583659&0&10" installedDisplayDrivers="igd10iumd64.dll,igd12umd64.dll,igdumdim64.dll"/>
</gpu>
<crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x00007FFF7136F3EC">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x00007FFF7136F3EC" symbolname="luaopen_math"/>
<stackStatement index="1" address="0x00007FFF7136F3CE" symbolname="luaopen_math"/>
<stackStatement index="2" address="0x00007FFF71388A2A" symbolname="luaopen_table"/>
<stackStatement index="3" address="0x00007FFF71366174" symbolname="lua_resume"/>
<stackStatement index="4" address="0x00007FFF713B5149" symbolname="AgThrowProgramError"/>
<stackStatement index="5" address="0x00007FFF7136621E" symbolname="lua_resume"/>
<stackStatement index="6" address="0x00007FFF71358823" symbolname="luaopen_base"/>
<stackStatement index="7" address="0x00007FFF7136538D" symbolname="lua_getstack"/>
<stackStatement index="8" address="0x00007FFF7138855E" symbolname="luaopen_table"/>
<stackStatement index="9" address="0x00007FFF71366174" symbolname="lua_resume"/>
<stackStatement index="10" address="0x00007FFF713B5149" symbolname="AgThrowProgramError"/>
<stackStatement index="11" address="0x00007FFF7136621E" symbolname="lua_resume"/>
<stackStatement index="12" address="0x00007FFF71358823" symbolname="luaopen_base"/>
<stackStatement index="13" address="0x00007FFF7136538D" symbolname="lua_getstack"/>
<stackStatement index="14" address="0x00007FFF7138855E" symbolname="luaopen_table"/>
<stackStatement index="15" address="0x00007FFF71366174" symbolname="lua_resume"/>
<stackStatement index="16" address="0x00007FFF713B5149" symbolname="AgThrowProgramError"/>
<stackStatement index="17" address="0x00007FFF7136621E" symbolname="lua_resume"/>
<stackStatement index="18" address="0x00007FFF71358823" symbolname="luaopen_base"/>
<stackStatement index="19" address="0x00007FFF7136538D" symbolname="lua_getstack"/>
<stackStatement index="20" address="0x00007FFF7138855E" symbolname="luaopen_table"/>
<stackStatement index="21" address="0x00007FFF713B5149" symbolname="AgThrowProgramError"/>
<stackStatement index="22" address="0x00007FFF7136600F" symbolname="lua_resume"/>
<stackStatement index="23" address="0x00007FFF71357EAD" symbolname="luaopen_base"/>
<stackStatement index="24" address="0x00007FFF71357CA0" symbolname="luaopen_base"/>
<stackStatement index="25" address="0x00007FFF7136538D" symbolname="lua_getstack"/>
<stackStatement index="26" address="0x00007FFF713885C8" symbolname="luaopen_table"/>
<stackStatement index="27" address="0x00007FFF71366174" symbolname="lua_resume"/>
<stackStatement index="28" address="0x00007FFF713B5149" symbolname="AgThrowProgramError"/>
<stackStatement index="29" address="0x00007FFF7136621E" symbolname="lua_resume"/>
<stackStatement index="30" address="0x00007FFF71358823" symbolname="luaopen_base"/>
<stackStatement index="31" address="0x00007FFF7136538D" symbolname="lua_getstack"/>
<stackStatement index="32" address="0x00007FFF7138855E" symbolname="luaopen_table"/>
<stackStatement index="33" address="0x00007FFF71366174" symbolname="lua_resume"/>
<stackStatement index="34" address="0x00007FFF713B5149" symbolname="AgThrowProgramError"/>
<stackStatement index="35" address="0x00007FFF7136621E" symbolname="lua_resume"/>
<stackStatement index="36" address="0x00007FFF71353670" symbolname="lua_pcall"/>
<stackStatement index="37" address="0x00007FFF6F0DB333" symbolname="WFLuaMessagingProcessor_scheduleFunctionWithLightUserdataInLuaState"/>
<stackStatement index="38" address="0x00007FFF7136538D" symbolname="lua_getstack"/>
<stackStatement index="39" address="0x00007FFF71366165" symbolname="lua_resume"/>
<stackStatement index="40" address="0x00007FFF713B5149" symbolname="AgThrowProgramError"/>
<stackStatement index="41" address="0x00007FFF7136621E" symbolname="lua_resume"/>
<stackStatement index="42" address="0x00007FFF71353670" symbolname="lua_pcall"/>
<stackStatement index="43" address="0x00007FFF6F0DBA95" symbolname="WFLuaMessagingProcessor_scheduleFunctionWithLightUserdataInLuaState"/>
<stackStatement index="44" address="0x00007FFF6F0DB1FD" symbolname="WFLuaMessagingProcessor_scheduleFunctionWithLightUserdataInLuaState"/>
<stackStatement index="45" address="0x00007FFF6F0D54D8" symbolname="WFMessaging_Processor_weakReleaseAndClear"/>
<stackStatement index="46" address="0x00007FFF6F0DF26B" symbolname="WFMessagingImpDispatch_Queue_retain"/>
<stackStatement index="47" address="0x00007FFFF5933730" symbolname="TpAllocPool"/>
<stackStatement index="48" address="0x00007FFFF591D79A" symbolname="TpReleaseCleanupGroupMembers"/>
<stackStatement index="49" address="0x00007FFFF4747344" symbolname="BaseThreadInitThunk"/>
<stackStatement index="50" address="0x00007FFFF591CC91" symbolname="RtlUserThreadStart"/>
</thread>
</backtrace>
<registerSet>
<register name="RAX" value="0x000002B03C038550"/>
<register name="RBX" value="0x0000000000000028"/>
<register name="RCX" value="0x000000007FFE0380"/>
<register name="RDX" value="0x0000000000A0013E"/>
<register name="RSI" value="0x0000000000000000"/>
<register name="RDI" value="0x0000000000000000"/>
<register name="RSP" value="0x000000ED0E6FE080"/>
<register name="RBP" value="0x000002B03C038550"/>
<register name="RIP" value="0x00007FFF7136F3EC"/>
<register name="EFL" value="0x0000000000010206"/>
<register name="LastExceptionToRip" value="0x0000000000000000"/>
<register name="LastExceptionFromRip" value="0x0000000000000000"/>
</registerSet>

</hbLogSessionDllStatus>
</crash>

Windows

Correct answer Keidran

I've finally had a breakthrough, and got Lightroom Desktop working again! I tried again for several hours last night to find a fiix for my problem. I'm not sure if it will work for you - I notice you have an AMD GPU, while I have a Nvidia GPU, but I'll tell you what fixed it for me, and maybe there's a parallel you can do for your AMD?

The fix was me was rooted with the drivers, in the end. Nvidia offers two different drivers for my GPU: a "Game Ready" drivers (marketed more for gaming), and a "Studio" driver (marketed more for creative suites, like Lightroom, Blendr, Video Editing, etc.). I primarily game, so thought I should get the one that I thought would be more optimised for that experience.

Long story short: I finally through I should try the other driver. For Nvidia, in it's driver management and game settings tool, you can select to use the other driver, it then downloads it, and prompts the installation. For me, it will uninstall the Game Ready driver, then replace it with the Studio one. It was recommended to tick the option to perform a "Clean Install", which I did. It ran the uninstaller/installer, I restarted my computer, and a Christmas miracle happened: Lightroom, finally, opened again, after many months!

I have no idea what the AMD drivers situation is, but I think, for me, re-installing my driver as a clean installation, might have gotten rid of a bug I picked up in an old driver update months ago, that never got cleaned out in subsequent updates, because I never did a full "Clean" re-install. I think if I did a clean re-install of my "Game Ready" driver, that would have fixed my issue as well, but I'll stick with the Studio driver for now (since it seems to play games just as well).

Maybe there could be something there for you?

tl;dr - see if you can perform a complete "clean" uninstall of your graphics driver, and re-install the latest one.

K

KeidranCorrect answer

I've finally had a breakthrough, and got Lightroom Desktop working again! I tried again for several hours last night to find a fiix for my problem. I'm not sure if it will work for you - I notice you have an AMD GPU, while I have a Nvidia GPU, but I'll tell you what fixed it for me, and maybe there's a parallel you can do for your AMD?

The fix was me was rooted with the drivers, in the end. Nvidia offers two different drivers for my GPU: a "Game Ready" drivers (marketed more for gaming), and a "Studio" driver (marketed more for creative suites, like Lightroom, Blendr, Video Editing, etc.). I primarily game, so thought I should get the one that I thought would be more optimised for that experience.

Long story short: I finally through I should try the other driver. For Nvidia, in it's driver management and game settings tool, you can select to use the other driver, it then downloads it, and prompts the installation. For me, it will uninstall the Game Ready driver, then replace it with the Studio one. It was recommended to tick the option to perform a "Clean Install", which I did. It ran the uninstaller/installer, I restarted my computer, and a Christmas miracle happened: Lightroom, finally, opened again, after many months!

I have no idea what the AMD drivers situation is, but I think, for me, re-installing my driver as a clean installation, might have gotten rid of a bug I picked up in an old driver update months ago, that never got cleaned out in subsequent updates, because I never did a full "Clean" re-install. I think if I did a clean re-install of my "Game Ready" driver, that would have fixed my issue as well, but I'll stick with the Studio driver for now (since it seems to play games just as well).

Maybe there could be something there for you?

tl;dr - see if you can perform a complete "clean" uninstall of your graphics driver, and re-install the latest one.

K

Keidran

I have this same issue. I click to open Lightroom. It starts opening, then crashes during boot-up. It has done this for MONTHS now. I have tried so many different ways to uninstalll and re-install. Today I ran the AdobeCreativeCloudCleanerTool. Removed everything. Restarted my computer. Re-installed Creative Cloud Desktop and Lightroom. Lightroom still crashes during boot-up.

PLEASE HELP.

K

Keidran

Hello - I'll reply to my own post, and repeat the reply as a seperate reply on your original post - I don't know how the post notifications work on these forums.

I've finally had a breakthrough, and got Lightroom Desktop working again! I tried again for several hours last night to find a fiix for my problem. I'm not sure if it will work for you - I notice you have an AMD GPU, while I have a Nvidia GPU, but I'll tell you what fixed it for me, and maybe there's a parallel you can do for your AMD?

The fix was me was rooted with the drivers, in the end. Nvidia offers two different drivers for my GPU: a "Game Ready" drivers (marketed more for gaming), and a "Studio" driver (marketed more for creative suites, like Lightroom, Blendr, Video Editing, etc.). I primarily game, so thought I should get the one that I thought would be more optimised for that experience.

Long story short: I finally through I should try the other driver. For Nvidia, in it's driver management and game settings tool, you can select to use the other driver, it then downloads it, and prompts the installation. For me, it will uninstall the Game Ready driver, then replace it with the Studio one. It was recommended to tick the option to perform a "Clean Install", which I did. It ran the uninstaller/installer, I restarted my computer, and a Christmas miracle happened: Lightroom, finally, opened again, after many months!

I have no idea what the AMD drivers situation is, but I think, for me, re-installing my driver as a clean installation, might have gotten rid of a bug I picked up in an old driver update months ago, that never got cleaned out in subsequent updates, because I never did a full "Clean" re-install. I think if I did a clean re-install of my "Game Ready" driver, that would have fixed my issue as well, but I'll stick with the Studio driver for now (since it seems to play games just as well).

Maybe there could be something there for you?

tl;dr - see if you can perform a complete "clean" uninstall of your graphics driver, and re-install the latest one.

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.