F5F Stay Refreshed Hardware Desktop is this how you turn off SMT on ryzen ?

is this how you turn off SMT on ryzen ?

is this how you turn off SMT on ryzen ?

M
Mr_Doom1023
Member
151
07-31-2019, 10:13 AM
#1
Sure! Turning off SMT on your Ryzen 5 3600 is possible, but it’s not recommended unless you’re certain about your needs. SMT (Simultaneous Multi-Threading) helps improve performance, especially under load. Disabling it might reduce performance on some tasks. Always back up your settings before making changes.
M
Mr_Doom1023
07-31-2019, 10:13 AM #1

Sure! Turning off SMT on your Ryzen 5 3600 is possible, but it’s not recommended unless you’re certain about your needs. SMT (Simultaneous Multi-Threading) helps improve performance, especially under load. Disabling it might reduce performance on some tasks. Always back up your settings before making changes.

I
Ich_Bin_Kuhl
Junior Member
25
07-31-2019, 04:25 PM
#2
I would configure it through the BIOS rather than Ryzen Master. It doesn’t pose any risks, though it may not offer significant advantages.
I
Ich_Bin_Kuhl
07-31-2019, 04:25 PM #2

I would configure it through the BIOS rather than Ryzen Master. It doesn’t pose any risks, though it may not offer significant advantages.

M
memee56200
Member
212
07-31-2019, 11:24 PM
#3
Neutral outcome.
M
memee56200
07-31-2019, 11:24 PM #3

Neutral outcome.

E
Epsylon16
Member
209
08-02-2019, 02:43 PM
#4
The difference will be noticeable. I've seen videos showing improved frame rates in games, and I plan to test it myself.
E
Epsylon16
08-02-2019, 02:43 PM #4

The difference will be noticeable. I've seen videos showing improved frame rates in games, and I plan to test it myself.

B
Batterbatter75
Junior Member
34
08-09-2019, 02:58 AM
#5
Tested fully accurate—even at full CPU load I felt stuttering.
B
Batterbatter75
08-09-2019, 02:58 AM #5

Tested fully accurate—even at full CPU load I felt stuttering.

R
Raqet
Member
222
08-10-2019, 02:59 PM
#6
Overall weaker performance across multithreaded applications. Very limited number of titles available. Many suffer reduced speed, especially in recent releases. This is largely because insufficient threading support.
R
Raqet
08-10-2019, 02:59 PM #6

Overall weaker performance across multithreaded applications. Very limited number of titles available. Many suffer reduced speed, especially in recent releases. This is largely because insufficient threading support.

S
SillyDragon
Senior Member
586
08-10-2019, 03:47 PM
#7
The improvement you notice might be inconsistent and not very reliable. You probably won<|pad|> a game won’t see better performance, and in some cases it could even slow things down. The only exception was Hitman 2 where turning off smt helped.
S
SillyDragon
08-10-2019, 03:47 PM #7

The improvement you notice might be inconsistent and not very reliable. You probably won<|pad|> a game won’t see better performance, and in some cases it could even slow things down. The only exception was Hitman 2 where turning off smt helped.

G
GhostyLite
Member
238
08-30-2019, 06:49 PM
#8
Turn off SMT in BIOS, verify the game will work afterward. Have fun!
G
GhostyLite
08-30-2019, 06:49 PM #8

Turn off SMT in BIOS, verify the game will work afterward. Have fun!

C
caseyjones223
Junior Member
18
09-03-2019, 01:50 PM
#9
Kind of an old post BUT... It is absolutely NOT pointless in certain situations. Infact, if you're asking how to disable it there is one VERY good reason you may be asking. Steinberg's Cubase and Nuendo (from v6 on) have a feature called ASIO-Guard. ASIO-Guard is meant to boost performance but, it often conflicts with Intel's Hyperthreading and AMD's SMT. If you're using a PC, you're able and may be looking to disable SMT if: You're using what seems like a rather light workload for your CPU yet you keep getting clicks, pops, or even freezing due to overloading on the VST meter. If you're experiencing issues due to the VST meter in Nuendo/Cubase showing spikes/peaking/overload but you've checked your CPU and RAM performance in task manager and it shows your CPU usage nowhere near 100%... You'll need to disable SMT/Hyperthreading in BIOS. Take it from me. I was experiencing this issue for months when I first updated from Nuendo 4 up to v9. It forced me to close the studio down for awhile because I had no idea what was causing it. The CPU exceeded the requirements, boosted RAM past the 64gb everyone says is the max any DAW will use, ran performance tests in other DAWs that far exceeded the workload in Nuendo; yet the issue remained. My workaround came by building a network of servers to offload plugin processing but, as soon as I started patching out through hardware audio processors (analog EQs/compressors, etc), the issue came right back. The reason is a conflict between ASIO-guard and SMT/Hyperthreading. Disable it, if you have this issue with Nuendo or Cubase. Hopefully posting this response will help anyone Googling this problem.
C
caseyjones223
09-03-2019, 01:50 PM #9

Kind of an old post BUT... It is absolutely NOT pointless in certain situations. Infact, if you're asking how to disable it there is one VERY good reason you may be asking. Steinberg's Cubase and Nuendo (from v6 on) have a feature called ASIO-Guard. ASIO-Guard is meant to boost performance but, it often conflicts with Intel's Hyperthreading and AMD's SMT. If you're using a PC, you're able and may be looking to disable SMT if: You're using what seems like a rather light workload for your CPU yet you keep getting clicks, pops, or even freezing due to overloading on the VST meter. If you're experiencing issues due to the VST meter in Nuendo/Cubase showing spikes/peaking/overload but you've checked your CPU and RAM performance in task manager and it shows your CPU usage nowhere near 100%... You'll need to disable SMT/Hyperthreading in BIOS. Take it from me. I was experiencing this issue for months when I first updated from Nuendo 4 up to v9. It forced me to close the studio down for awhile because I had no idea what was causing it. The CPU exceeded the requirements, boosted RAM past the 64gb everyone says is the max any DAW will use, ran performance tests in other DAWs that far exceeded the workload in Nuendo; yet the issue remained. My workaround came by building a network of servers to offload plugin processing but, as soon as I started patching out through hardware audio processors (analog EQs/compressors, etc), the issue came right back. The reason is a conflict between ASIO-guard and SMT/Hyperthreading. Disable it, if you have this issue with Nuendo or Cubase. Hopefully posting this response will help anyone Googling this problem.

I
ImXuliiPvp
Junior Member
25
09-04-2019, 02:21 PM
#10
I aimed to share my discoveries for future reference because I’m astonished at how quickly people made assumptions without solid proof. I’ve battled stuttering for as long as I can remember, especially during demanding CPU tasks. My current setup includes a Ryzen 9 3950X at 4Ghz, 80GB DDR4 RAM, and an X570 motherboard running the latest BIOS (October 2022). The RTX 3080 caused intense stuttering, prompting me to upgrade to the RTX 3090 Ti a month prior. The graphics card was extremely noisy, so I opted for an open-loop configuration. It features a 360mm 30mm radiator, a custom Corsair loop with an EKGW pump, and powerful fans (Phanteks T30-120). My system runs at 51°C under full load when the RTX3090 Ti clocks at 2070Mhz.

This background explains my situation and the solutions I implemented. I experienced significant lag spikes and microstuttering in several titles: Fortnite (FPS ~105, low ~22), Dying Light 2 (FPS ~59, low ~27), and Shadow of the Tomb Raider (FPS ~96, low ~46). Other games also suffered.

What I did was turn off SMT in the BIOS. Removing it not only stabilized my system but also improved overclocking potential. I could push the core clock up to 4.27 with a 1.26v boost at the same speed. This resulted in much better low-FPS performance across titles: Fortnite (FPS ~110, low ~68), Dying Light 2 (FPS ~61, low ~51), and Shadow of the Tomb Raider (FPS ~95, low ~58). The impact was dramatic, especially for games with high CPU demand.

I noticed better CPU utilization overall—Fortnite now uses up to 43% CPU compared to just 29% previously. The temperature stayed similar, indicating improved efficiency rather than higher power draw. Windows felt snappier too.

Currently, I have 16-core processors but prefer this configuration over a 32-thread machine that often disrupts my gaming sessions. It seems recent CPUs might be affected by SMT limitations, though I haven’t found many references confirming microstuttering. My hope is that this experience can help others facing similar challenges. For me, disabling SMT delivered immediate improvements: microstutter vanished, low-FPS dropped across most games, and I achieved higher overclocking potential. The experience also made Windows feel more responsive.
I
ImXuliiPvp
09-04-2019, 02:21 PM #10

I aimed to share my discoveries for future reference because I’m astonished at how quickly people made assumptions without solid proof. I’ve battled stuttering for as long as I can remember, especially during demanding CPU tasks. My current setup includes a Ryzen 9 3950X at 4Ghz, 80GB DDR4 RAM, and an X570 motherboard running the latest BIOS (October 2022). The RTX 3080 caused intense stuttering, prompting me to upgrade to the RTX 3090 Ti a month prior. The graphics card was extremely noisy, so I opted for an open-loop configuration. It features a 360mm 30mm radiator, a custom Corsair loop with an EKGW pump, and powerful fans (Phanteks T30-120). My system runs at 51°C under full load when the RTX3090 Ti clocks at 2070Mhz.

This background explains my situation and the solutions I implemented. I experienced significant lag spikes and microstuttering in several titles: Fortnite (FPS ~105, low ~22), Dying Light 2 (FPS ~59, low ~27), and Shadow of the Tomb Raider (FPS ~96, low ~46). Other games also suffered.

What I did was turn off SMT in the BIOS. Removing it not only stabilized my system but also improved overclocking potential. I could push the core clock up to 4.27 with a 1.26v boost at the same speed. This resulted in much better low-FPS performance across titles: Fortnite (FPS ~110, low ~68), Dying Light 2 (FPS ~61, low ~51), and Shadow of the Tomb Raider (FPS ~95, low ~58). The impact was dramatic, especially for games with high CPU demand.

I noticed better CPU utilization overall—Fortnite now uses up to 43% CPU compared to just 29% previously. The temperature stayed similar, indicating improved efficiency rather than higher power draw. Windows felt snappier too.

Currently, I have 16-core processors but prefer this configuration over a 32-thread machine that often disrupts my gaming sessions. It seems recent CPUs might be affected by SMT limitations, though I haven’t found many references confirming microstuttering. My hope is that this experience can help others facing similar challenges. For me, disabling SMT delivered immediate improvements: microstutter vanished, low-FPS dropped across most games, and I achieved higher overclocking potential. The experience also made Windows feel more responsive.