Internal Error (Correction failed on the execute stage)

Internal Error (Correction failed on the execute stage) on DXO Photo Lab 8 and Canon R5 Mark II. Doing it almost all the time when trying to apply corrections.

Mac or Win, Robert … and, what’s your system configuration (Memory, CPU, GPU, etc) ?

PS. Welcome to the User forum.

2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | DxO.PhotoLab version: 8.0.0.417
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Platform: Win
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Operating system: Microsoft Windows 11 Pro (10.0.22631)
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Operating system language: en-US
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | RAM: 32456 MiB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Virtual memory: 98304 MiB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Total memory (RAM + virtual memory): 130760 MiB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | CPU(s) count: 1
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | CPU #1: 13th Gen Intel(R) Core™ i7-13700
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | CPU #1 manufacturer: GenuineIntel
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | CPU #1 frequency: 2.10 GHz
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | CPU #1 cores: 16
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU(s) count: 2
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #1: NVIDIA RTX A2000 12GB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #1 VRAM: 12110 MiB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #1 driver version: 32.0.15.5612 (6/24/2024)
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #2: Intel(R) UHD Graphics 770
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #2 VRAM: 128 MiB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #2 driver version: 31.0.101.4953 (11/6/2023)
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display(s) count: 2
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #1: Generic PnP Monitor
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #1 size: 2560 x 1440 @ 100%, 59 Hz (32 bits)
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #1 resolution: 96 dpi
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #2: Generic PnP Monitor
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #2 size: 2560 x 1440 @ 100%, 59 Hz (32 bits)
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #2 resolution: 96 dpi
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | .NET Framework version : 4.8.9261.0

Doesn’t look like it’s anything to do with your system capabilities !

Suggest you raise a request for support with DxO:
https://support.dxo.com/hc/en-us/requests/new

Since the latest program update I am having the same problem all the time. So the program as such is useless. Has anyone found any solution to this?

I’ve had these too and to me it seems it’s because of running out of RAM. I come from PhotoLab 6 and version 8 uses a lot more.

Minimum RAM is 8 GB, recommended is 16 and I have that 16, so maybe it is something else?

I have the same issue and sometimes it crashes totaly. I have a ticket at the DxO Support and wait hopefully for the solution before I buy.

I am also having occasional crashes. Please, let us know if You get a working solution from the support.

What happens if you disconnect the monitors connected to the mobo and only run the dedicated graphics card?

Any changes?

@RJM If you use the
image
<> from the above menu and put the text between the markers you get something that might be easier to read

[quote="RJM, post:3, topic:40277, full:true"]
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | DxO.PhotoLab version: 8.0.0.417
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Platform: Win
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Operating system: Microsoft Windows 11 Pro (10.0.22631)
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Operating system language: en-US
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | RAM: 32456 MiB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Virtual memory: 98304 MiB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Total memory (RAM + virtual memory): 130760 MiB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | CPU(s) count: 1
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | CPU #1: 13th Gen Intel(R) Core™ i7-13700
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | CPU #1 manufacturer: GenuineIntel
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | CPU #1 frequency: 2.10 GHz
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | CPU #1 cores: 16
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU(s) count: 2
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #1: NVIDIA RTX A2000 12GB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #1 VRAM: 12110 MiB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #1 driver version: 32.0.15.5612 (6/24/2024)
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #2: Intel(R) UHD Graphics 770
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #2 VRAM: 128 MiB
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | GPU #2 driver version: 31.0.101.4953 (11/6/2023)
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display(s) count: 2
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #1: Generic PnP Monitor
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #1 size: 2560 x 1440 @ 100%, 59 Hz (32 bits)
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #1 resolution: 96 dpi
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #2: Generic PnP Monitor
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #2 size: 2560 x 1440 @ 100%, 59 Hz (32 bits)
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | Display #2 resolution: 96 dpi
2024-10-03 12:43:52.025 | DxO.PhotoLab - 36888 - 4 | System - Info | .NET Framework version : 4.8.9261.0
[/quote]

I have encountered the problem recently but only on two exports from a batch of 60 and all previous exports with the RTX3060 and the subsequent export with the 2060 worked fine.

The 5900X in the machine that encountered the problem does not have an IGPU so all traffic to the monitors has to go via the GPU at the same time that PL8 is exporting and I got this at one point in the export process

There does appear to be a CPU “glitch” in the snapshot I took and DxO support made a comment about the possibility of a potential “glitch” occurring!?

The machine in question has 32GB RAM and the 6GB on the 2060 is barely being used

I have been supplied with a patch file to insert that will increase what is logged and that is what I feel you need.

Collecting some log information from Windows might help us. Please follow this procedure:

* * copy the attached file DebugLog.nlog into you DxO Photolab logs folder located in your documents (C:\Users\%username%\Documents\DxO PhotoLab 8 logs)
* * Start DxO PhotoLab and reproduce the problem
* * Make a zip file of DxOPhotoLab.txt and dopcor.txt
* * Send it to us
* * Delete file DebugLog.nlog

So please contact DxO support (and that goes for anyone else experiencing the problem) and request help to increase the logging of the situation, there is always a possible “risk” that the change in system activity for the logging and the insertion of additional logging in DxPL may well change things but if it does, that may provide a clue to the nature of the problem.