I agree with
PlaySound, there's no reason/benefit in producing to AVI. Generally speaking, you'll have the best results when producing to a similar format as your highest-quality source clips, so in this case choose 1920x1080/60p MP4 to match your GoPro clips.
As he also suggested, try using the Produce Range feature to have PD pre-produce the titles section so it doesn't have to try and process it every time your preview it. Another benefit is that you'll know right away if the glitch is gone without having to produce the whole project
Here's a quick
*video* from an older post that shows the steps. Note that there's also a Produce Range button just above the timeline that appears once you've selected a range, and you can click on that or right-click on the selected range, whichever is easier for you.
One last oddity is that your DxDiag results are missing some important details. A few sections down from the top you'll see where the details from your Radeon card are supposed to be, and yet the most important details (chipset, installed driver version) are blank. I've never seen that before and so I don't know how much of a problem that actually is or isn't. There are some other details missing at the very end of the report, but for now i'm focusing on the video driver which could
possibly explain the title glitch.
The very latest AMD Catalyst drivers are causing problems with PD, as seen in this
*thread* so you probably should make sure you have the previous drivers installed. Open Device Manager and find your card under Display Adapters and look at the driver details. I think the version you want was from late 2014.
Let us know what you find, and if any of these suggestions help!
YouTube/optodata
DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors
Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°