I have a WIN10 machine (2700x CPU) with a Nvidia 1060/6GB as well as AMD RX580 video card installed. I have been testing my new copy of PL4 and DeepPrime exports.
With the preferences set to using the Nvidia card I can export single photos as well as multiple photos in batch.
However, if I select the AMD RX580 card in the preferences I can only export single photos at a time. If I batch select multiple photos I get one successful export and for the rest I get the error message:
Save has Failed Internal Error (Correction failed on the execute stage)
I have WIN10 v 2004 and the latest drivers for NVIDIA and AMD installed. My monitor is connect to the NVIDIA card. The AMD card is installed but does not have a monitor attached.
I have a RX580 video card, and I’m have the same problem with batch exports. It works fine if I use CPU only, but it’s very slow. With the video card enabled, changing the maximum number of simultaneously process images to 1 also appears to solve the problem (but slows things down )
Note my trouble ticket #236989. DXO has forwarded this problem to the developers and I await a fix. You might open a trouble ticket and note my number to show them the problem is impacting more then one user.
For those that are following this thread, DXO continues to work on my troubleticket. They have been requesting additional log files and details as they attempt to solve the problem. Although the problem still persists, DXO appears to be actively working and escalating the troubleshooting with the developers.
An update, the error is still with me and DXO has recommended I downgrade my exports to one at a time. They believe the error will be resolved in the future at some point with an AMD driver update. However, I have given up and have swapped out my AMD card for a NVIDIA based card.
A new update, just to try a random idea, I loaded an old version of AMD drivers. AMD Drivers 17.12.2 Windows 10 64bit. With the older drivers, the export bug does NOT appear and seems to work fine. This is with an older RX500/400 series card.
Thank you for the information. It’s an interesting track. I’ve tried the same and also confirm that it fixes the stability issues with a RX 560 we have. We’ve forwarded the information to AMD engineers.
However I’m uncomfortable with recommending to do this for everyone having stability issues with AMD RX 500 series GPUs. This is a very old driver (December 2017), and although it looks to fix DeepPRIME exports, we don’t know what else it may break in PhotoLab or other programs.
So to other people reading this post, I’d say… you might try it but use at your own risk. There’s most likely no big deal trying it: in the worst case you’ll just need to reinstall usual drivers if you have issues with these old ones.
I picked the driver 17.12.2 because it was the last driver from 2 generations of drivers ago. For all I know, a more recent but older driver might also work. You could also try the last driver from the 18.xx generation of drivers to see if that works. I just wanted to go back far enough to avoid whatever bug is present in the current generation AMD driver release.
AMD Driver 20.12.1 correction failed on the execute stage error
AMD Driver 19.12.3 correction failed on the execute stage error
AMD Driver 18.12.3 exports never complete, spinning arrow runs forever without error and without complete
AMD Driver 17.12.2 works fine, exports error free with good performance.
DXO support recently contacted me and asked me try the latest AMD beta driver 21.2.3 optional recently released. Kudos to DXO for taking the initiative to continue working with AMD to resolve this driver issue.
I am happy to report that for me, the new driver 21.2.3 fixes the export error message with my RX series card. The performance is slightly improved from the 17.12.2 driver as well.
One important note, for some reason the AMD driver when selected under Driver-Settings-Graphics-Advanced-GPU Workload menu to “Graphics” mode (which is the default) I see 100% GPU utilization and high power draw on my graphics card with PhotoLab even when there are NO IMAGES being processed. Selecting “compute” mode however has the same export performance and a more normal 0% idle GPU load when idling and 100% load under export.
I recommend Photolab users try out the new driver and select “compute” mode in the driver settings menu.
It exports an image with DeepPRIME in about 24 secs - but, I do have to set WinMLUseGraphicQueue = True in the DxO.PhotoLab.exe.config file, to force it to be used by PL.
Regards, John M
Edit: Ooops !! I made that change, (CPU Workload = Compute) and my export time went out to 30 secs (from 24) - - changing it back, and rebooting, made no difference (still 30 secs) … Any suggestions ?
One more update, 21.2.3 has been working fine for me. I just let my system update itself to the latest 21.4.1 and the error is back. I have now regressed back to 21.2.3 and it is working again.
)
