Skip to content

Recommendation

Leave as default

Leave the default state.

Before changing TSX for a game, you need to confirm that the program uses these instructions and that the result of the change is reproducible.

Scope
Intel TSX transactional instructions
FPS and memory
FPS is not affected

TSX (Transactional Synchronization Extensions) is an Intel extension for hardware transactions: a program executes a critical section as an all-or-nothing transaction and rolls it back on a conflict, instead of using traditional locks. This can reduce synchronization overhead in multithreaded code. Support depends on the processor generation, microcode and the application itself.

The tweak controls the use of TSX on the Windows side and requires a reboot.

Why the tick is under “Legacy”: Intel disabled the TSX instructions with microcode updates on vulnerable processor generations after vulnerabilities related to transactions were discovered. On most modern systems the instructions are unavailable, and the tick changes nothing. According to the visible BoosterX description, disabling reduces the attack surface and eliminates rare crashes of old games on certain old CPU generations.

On an unsupported processor the setting is not applied. The change affects security, so without a confirmed need, leave the default state.

Compare the default and modified states across several identical runs of the same workload and make sure that reverting restores the previous behavior.

In BoosterX, open “Optimization” → “Legacy” → “TSX”, move the toggle to the “On” position to leave the default state (the “Off” position applies the change), and click “Apply”. If “Instant apply” is enabled, a separate click is not required. Perform a reboot.

The public Intel page about the microcode disabling of TSX does not open as of the verification date, so the fact is stated cautiously and remains without a direct link. The visible BoosterX descriptions and the reboot requirement are confirmed.

Last check: 2026-09-20.