@Inezant, @stuck & @Joanna I believe we have been here before, potentially the same or something similar, when DxO attempted to avoid the risk of a crash by pre-allocating GPU memory before actually attempting to use it and then downgraded many users to ‘CPU only’ and that is “fatal” if any images have DP XD, or now DP XD2s assigned.
Please see here DXO PL 6.10 and older GPU’s - #28 by Cecile-C
As a result of the problems other users had experienced, I changed my setting to ‘CPU only’ to see what the outcome might be. This brought my i7 4790Ks to their knees just browsing to an image with DP XD selected, the mouse stuttered, the performance monitor software I was running could not even keep plotting the CPU usage graph!!
DxPL was consuming every bit of CPU it could get whenever I browsed to an image with DP XD assigned!
Please note that this is browsing not exporting, DxPL “sips” a little GPU “juice” when rendering/re-rendering DP XD images and now does the same with Dx XD2s and I mean a tiny “sip”. But to replace that GPU “sip” with CPU results in chaos for less powerful CPUs.
If you have an onboard IGPU then it is worth trying to select that but that will make exporting even worse, if it works at all.
But during the problems that some other users experienced my two i7-4790K’s both worked fine (when I didn’t select ‘CPU only deliberately’), one with a 4MB GTX 1050Ti and the other with a 2MB GTX 1050 (not much different to your 2MB GTX 1030 @Inezant) and the 2MB card was not downgraded automatically to CPU only at any time, by “fine” I mean slow to export but fine for browsing.
You would think that a Beta tester might have suggested that DP XD should have been retained as an option alongside DP XD2(s) to avoid any risk of potential performance issues with low powered GPUs 
!?
In my tests I concluded that rendering the preview window was the culprit and if I moved the position of the preview around then each time the CPU would max out. The Loupe is no longer permanently on so browsing should be possible without the chaos I saw.
@Joanna but exporting with ‘CPU only’ is truly “horrendous”.
@Inezant please make a support request, the fact that it worked for browsing and (slowly) for exporting with PL7 means that you have an expectation that it would remain the case with PL8.
In truth DxPL doesn’t seem to require much GPU memory but the problem was caused by a design/coding change that sought to pre-allocate GPU memory to avoid problems but which actually caused problems.