Overclock.net banner
3,781 - 3,800 of 9,078 Posts
That's just what MSI AB reports as requested clock speed. Actual clock speed is lower but not reported by MSI AB.

For true clock speeds, you can use Ryzen Master Tool. Refer to the two BF2042 videos I posted. One with MSI AB overlay running, one with MSI AB overlay disabled and Ryzen Master Tool running showing the true clock speed, and it's lower than 5.25Ghz.

Note, Ryzen Master Tool has a performance cost, so I don't recommend using it long term.
Ok im running afterburner overlay aswell, i guess mines reporting actual clock speed then.
Ive run hwinfo while gaming and reset the values during sessions and its showing that my afterburner clock speed is pretty close
I was thinking u had a golden chip boosting like that
Thanks for the reply
 
Ok im running afterburner overlay aswell, i guess mines reporting actual clock speed then.
Ive run hwinfo while gaming and reset the values during sessions and its showing that my afterburner clock speed is pretty close
I was thinking u had a golden chip boosting like that
Thanks for the reply
Look for effective clock speed in HWINFO64, it should be the same or similar to what Ryzen Master Tool reports.
Image
 
Some theory crafting while the game downloads. If Process Lasso makes it stutter less, then it is probably a game issue not liking Ryzen dual CCD X3D CPU. Probably could be fixed with a game update, but I'm guessing the game has not been updated since X3D launch?

If my theory is correct, then Process Lasso will not be needed to make the game run better, all you will need to do is use the Windows High Performance power profile.

I'll share my findings soon and hopefully a YT video to boot.
@ghiga_andrei

Here is the game running without Process Lasso installed, using Ultra RT without any stuttering when running the default Windows High Performance power profile.
Video is converting now, give it a few minutes for better quality.

If I switch to the Balanced Windows Power Profile (which is required for GameBar/Chipset driver assignment support) the game stutters every few seconds.

My theory crafting is correct. The game needs to be updated to properly support dual CCD X3D parts. Thankfully, switching the power profile is relatively easy.

So, you could use Process Lasso and manually assign the affinity/CPU sets yourself. Or you could just switch to the Windows High Performance Profile and not bother with any of that.

If Metro Enhanced was a game I played a lot, maybe using Process Lasso to automatically assign the Windows High Performance Profile when the game is launched, rather than manually assigning affinity yourself ,would be the optimal solution with the least effort required on your part.

I think there are other apps available that can do something similar too. However, I can see your reasoning for using it for Metro at least having seen how the game behaves using the balanced power profile.
 
Discussion starter · #3,784 ·
@ghiga_andrei

Here is the game running without Process Lasso installed, using Ultra RT without any stuttering when running the default Windows Performance power profile.
Video is converting now, give it a few minutes for better quality.

If I switch to the Balanced Windows Power Profile (which is required for GameBar/Chipset driver assignment support) the game stutters every few seconds.

My theory crafting is correct. The game needs to be updated to properly support dual CCD X3D parts. Thankfully, switching the power profile is relatively easy.

So, you could use Process Lasso and manually assign the affinity/CPU sets yourself. Or you could just switch to the Windows Performance Profile and not bother with any of that.

If Metro Enhanced was a game I played a lot, maybe using Process Lasso to automatically assign the Windows Performance Profile when the game is launched, rather than manually assigning affinity yourself ,would be the optimal solution with the least effort required on your part.

I think there are other apps available that can do something similar too. However, I can see your reasoning for using it for Metro at least having seen how the game behaves using the balanced power profile.
Which power plan did you choose when you switched away from Balanced?
 
Which power plan did you choose when you switched away from Balanced?
I use Balanced, always. However for some reason it seems like this particular game performs better using the Windows High Performance profile.

For dual CCD X3D parts best results are 99.9% achieved with the default Balanced Profile set to Best Performance.
Image


Image
 
@ghiga_andrei

Here is the game running without Process Lasso installed, using Ultra RT without any stuttering when running the default Windows High Performance power profile.
Video is converting now, give it a few minutes for better quality.

If I switch to the Balanced Windows Power Profile (which is required for GameBar/Chipset driver assignment support) the game stutters every few seconds.

My theory crafting is correct. The game needs to be updated to properly support dual CCD X3D parts. Thankfully, switching the power profile is relatively easy.

So, you could use Process Lasso and manually assign the affinity/CPU sets yourself. Or you could just switch to the Windows High Performance Profile and not bother with any of that.

If Metro Enhanced was a game I played a lot, maybe using Process Lasso to automatically assign the Windows High Performance Profile when the game is launched, rather than manually assigning affinity yourself ,would be the optimal solution with the least effort required on your part.

I think there are other apps available that can do something similar too. However, I can see your reasoning for using it for Metro at least having seen how the game behaves using the balanced power profile.
Hmm, did not know that just changing the power plan would fix it, I'm glad we had this talk and you tested it.
Thanks, maybe I will go back to Gamebar default setup.
 
Discussion starter · #3,788 · (Edited)
The 'Balanced' power plan is REQUIRED for the AMD 3D driver to switch exclusively to the cache CCD. Just as much so as Game Bar recognizing it as a game. So switching off Balanced disables the 'smart' CCD switching and allows the game to run across all cores, which is necessary for this game to avoid the massive FT spikes that comes with forcing it to CCD0 only. I haven't tested myself but I'd imagine keeping it on Balanced and then going into Game bar and unchecking 'this is a game' would have the same results.

edit: well apparently you can't 'uncheck' the box if game bar detects it as a game, you can only check it if game bar doesn't detect it as a game. there's probably a file somewhere that lists all the executables game bar has determined is a game, or it's contained in the AMD 3D driver itself, but I'm too lazy to look for it
 
The 'Balanced' power plan is REQUIRED for the AMD 3D driver to switch exclusively to the cache CCD. Just as much so as Game Bar recognizing it as a game. So switching off Balanced disables the 'smart' CCD switching and allows the game to run across all cores, which is necessary for this game to avoid the massive FT spikes that comes with forcing it to CCD0 only. I haven't tested myself but I'd imagine keeping it on Balanced and then going into Game bar and unchecking 'this is a game' would have the same results.

edit: well apparently you can't 'uncheck' the box if game bar detects it as a game, you can only check it if game bar doesn't detect it as a game. there's probably a file somewhere that lists all the executables game bar has determined is a game, or it's contained in the AMD 3D driver itself, but I'm too lazy to look for it
Actually that would be a great feature that Microsoft should add to the gamebar, the ability to manually disable it for a game (like the reverse of checking This is a game). Would be really simple for them and useful for us.
 
Actually that would be a great feature that Microsoft should add to the gamebar, the ability to manually disable it for a game (like the reverse of checking This is a game). Would be really simple for them and useful for us.
Agreed, that’s the one thing that’s missing.
 
...more quick questions as I continue to prep for the 7950X3D build...Does a fresh Windows 10 Pro 21H2 install work/work well with the 7950X3D and its unique requirements re. CCDs, Cache etc. ? How about Win 11 Pro 21H2 (I don't like 22H2), or even a Spectre Ghost ISO (slimmed down Win 11) ? Tx :)
Yes should be fine, however it’s worth considering that 21H1 is not too far away from EOL though so if you can I’f make the switch to 22H2. I’m using the latest build of Win 11 22H2 without any issues.
 
Yes should be fine, however it’s worth considering that 21H1 is not too far away from EOL though so if you can I’f make the switch to 22H2. I’m using the latest build of Win 11 22H2 without any issues.
Thanks much ! I'm prepping for a > dual-boot setup but aren't there yet because of a lack of proper 'free' time right now.
 
It forces the game to use one CCD only. That's exactly what GameBar/Chipset driver does, unless CPU utilisation is high enough in which case GameBar/Chipset driver can utilise one or more of the cores on the second CCD. Can this app do that? I doubt it if it's forcing apps to use only one CCD or the other. And in those scenarios, in my testing that = reduced performance.
View attachment 2625499

For games with low CPU utilisation that's fine btw, it's only in games that really push the utilisation high enough that this method of using third party (and unneeded apps) falls down. I don't recommend using them, but people will do it anyway and get lower performance (in some games) without even realising.
It says "by dynamically parking the second CCX". The paragraph seems to be saying "we disable the second CCX, that's how the game is restricted to the first CCX", but once the second CCX is unparked the Windows thread scheduler has no idea it's supposed to keep the game on the first CCX. If it knew that, then you wouldn't need to park the second CCX in the first place.
 
I uninstalled the new chipset driver, and performance is back. Then I installed the new "3d v cache" only. Performance is still the old. My conclution; Only install 3d v cache for my 7800x3d :p

Easy BF 2042 benchmark: Main menu fps:
Cpu bound settings
Stock 7800x3d + B650E-F
7600c34 2x16
3090 stock
View attachment 2625329
Do you have a config file I can use to compare?
 
Trying to dial in PBO for my 7950x3d w/ Taichi X670E motherboard. I'm having an issue where adding a frequency offset breaks the AMD driver preferring the higher frequency cores for things like Cinebench, resulting in very poor single core performance. If I don't use the frequency offset, PBO doesn't do much.

I know there is a workaround by forcing the freq cores all the time then using process lasso for games, I was just hoping to try the AMD native solution first. Is there a fix for this that I'm not aware of?
 
Trying to dial in PBO for my 7950x3d w/ Taichi X670E motherboard. I'm having an issue where adding a frequency offset breaks the AMD driver preferring the higher frequency cores for things like Cinebench, resulting in very poor single core performance. If I don't use the frequency offset, PBO doesn't do much.

I know there is a workaround by forcing the freq cores all the time then using process lasso for games, I was just hoping to try the AMD native solution first. Is there a fix for this that I'm not aware of?
PBO MaxBoost is (nearly) disabled and ineffective on X3D models anyway.
 
3,781 - 3,800 of 9,078 Posts