Slow conversions after moving to 2.5.x

Your logs show that it’s using your Intel hardware encoder but for some reason it’s running really really slow.

2020-01-21T23:54:52 MCEBuddy.AppWrapper.Handbrake → Encoding: task 1 of 1, 0.05 %[23:54:52] qsv_enc_init: using ‘hardware (1) via D3D11’ implementation, API: 1.11
2020-01-21T23:54:56 MCEBuddy.AppWrapper.Handbrake → Encoding: task 1 of 1, 0.10 % (10.62 fps, avg 10.62 fps, ETA 01h09m10s)
2020-01-21T23:54:56 MCEBuddy.AppWrapper.Handbrake → Encoding: task 1 of 1, 0.10 % (10.62 fps, avg 10.62 fps, ETA 01h09m10s)
2020-01-21T23:54:56 MCEBuddy.AppWrapper.Handbrake → Encoding: task 1 of 1, 0.10 % (10.62 fps, avg 10.62 fps, ETA 01h09m10s)
2020-01-21T23:54:57 MCEBuddy.AppWrapper.Handbrake → Encoding: task 1 of 1, 0.10 % (6.42 fps, avg 9.47 fps, ETA 01h17m34s)
2020-01-21T23:54:57 MCEBuddy.AppWrapper.Handbrake → Encoding: task 1 of 1, 0.10 % (6.42 fps, avg 9.47 fps, ETA 01h17m34s)

It’s likely your graphics driver. Try using one of the recommended version from the Hardware FAQ page and see if that makes your hardware conversion go faster.

You mentioned that you tried using a different machine with an i5 processor which was fast, check the graphics driver version on that machine and try to use the same one.

Usually when the speed changes suddenly it’s because the windows update may have updated your graphics driver and the new one is buggy.