5.x.x wrong processor ( with screen shots)

[z1nonly]

[If you are posting a new bug, please include the following]

1. The bug / behavior you have encountered
   While benchmarking the latest 5.2.1 version on my 5800X3d / 4090 rig, the program stops using the GPU on one or more tests, puts all load on the CPU…but does not even use SMT (hyperthreading).
   After taking forever on that test and producing a ridiculously-low score, the next test will be fine and then a couple tests later, it does it again.

2. Your system profile
   

   

3. Your log files (Help > Logging > Get Logs for Support)
   logsForSupport.zip (212.3 KB)

4. Any screenshots as necessary
   

Topaz Video AI  v5.2.1
System Information
OS: Windows v10.22
CPU: AMD Ryzen 7 5800X3D 8-Core Processor             31.925 GB
GPU: NVIDIA GeForce RTX 4090  23.576 GB
Processing Settings
device: 0 vram: 1 instances: 1
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 	36.29 fps 	2X: 	13.37 fps 	4X: 	03.21 fps 	
Iris		1X: 	38.00 fps 	2X: 	15.77 fps 	4X: 	03.89 fps 	
Proteus		1X: 	42.97 fps 	2X: 	15.64 fps 	4X: 	04.02 fps 	
Gaia		1X: 	15.74 fps 	2X: 	10.53 fps 	4X: 	03.40 fps 	
Nyx		1X: 	19.61 fps 	:face_with_monocle:**2X: 	00.16 fps** 	
Nyx Fast		1X: 	33.56 fps 	
Rhea		4X: 	03.31 fps 	
4X Slowmo		:face_with_monocle:**Apollo: 	00.42 fps** 	APFast: 	56.10 fps 	Chronos: 	31.97 fps 	CHFast: 	30.43 fps 	
16X Slowmo		Aion: 	29.08 fps 	

[z1nonly]

I don’t see the “edit” pencil so I will put additional info in a reply: [now it’s showing lol]

My 13900K / 4080 S rig sometimes picks the wrong processor as well on 5.2.1. I thought it was a P-core E-core issue or something and have just been stopping the process and restarting…and the correct processor is usually chosen after that.

Back to the AMD rig: I created a restore point while 4.x.x was installed and, after getting the same issue on 5.0, I restored to 4.x.x and did three benchmark runs with zero weirdness.

I then re-downloaded and reinstalled 5.2.1 and got the same issue as before.

This bug doesn’t appear to be an Intel / AMD issue and it’s present on both of the 5.x.x versions I tried.

[margaux.topazlabs]

The AI processor resetting to ‘auto’ is a known bug in 5.2.0-5.2.1. It has been resolved in the beta version and should be resolved in the next update!

[z1nonly]

I think I have always left that setting on “auto”. Or at least I don’t change whatever the default is.

[margaux.topazlabs]

I would recommend switching it to the GPU