@wouter1971: Please check if the attached Core.dll solves the problem.
That's fast Marcus
Re-added the overscan parameters and tested the new core.dll and no issue seen. This solves the problem. Did a reverse check also and then it apeared again.
Nice work!