Tweaking the computer
Modern systems with a fully updated Windows should not need any of the default settings to be modified. However, if certain drivers are not fully optimized and you experience audio drop-outs, it is worth having a closer look. Note that the following settings are often not accessible, especially on laptop systems.

• Disable Hyper-Threading (Intel)/Simultaneous Multi-Threading (AMD) in the UEFI BIOS if your CPU supports it and if your BIOS allows you to modify this setting.
• Disable advanced power-saving and dynamic performance options for your CPU if applicable. This usually needs to be done in the UEFI BIOS of your computer and includes ‘Enhanced Intel SpeedStep (EIST)’, ‘AMD Cool 'n' Quiet’, ‘Intel Turbo Boost’, and ‘AMD Turbo CORE’.
• Disable C-States in the UEFI BIOS if this is accessible. C-States allow your CPU to sleep when idle, which may interfere with real-time applications such as audio. This option is often called ‘Disable CPU Idle State for Power Saving’.

https://helpcenter.steinberg.de/hc/...t-up-and-optimize-a-Digital-Audio-Workstation

 

Actual configuration:
1) AMD IPU DPM - disabled
2) AMD fTPM switch - disabled
3) NX Mode - enabled
4) SVM Mode (AMD-V) - enabled
5) IOMMU (AMD-Vi) - enabled
6) AMD SMT (hyper-trading) - enabled
7) core performance boost - enabled
Internal sound card, webcam, Bluetooth and card reader are disabled.
8) secure boot - disabled
I’ve all cores manually unparked.

so I can disabel SVM Mode (AMD-V), IOMMU (AMD-Vi), AMD SMT (Simultaneous Multithreading) and also Core Performance Boost?

 

128 or 256 is more than enough for playing the keyboard.

 

Anything with boost should definitely be turned off.
It's more for gamers, etc., not musicians. Musicians want consistent performance to avoid dropouts: Please turn it off!

Core Performance Boost:
Allows the processor to run above the manufacturer's specified frequencies, as long as temperature, power consumption, and voltage are not exceeded. This option is set by default on most motherboards. This applies to both Intel and AMD. Intel calls this Multicore Enhancement. It's a type of automatic overclocking.

 

I’ve just turned off all those settings: SVM Mode (AMD-V), IOMMU (AMD-Vi), AMD SMT (Simultaneous Multithreading) and also Core Performance Boost

I’m running another Latencymon and let’s see!
Thank you everyone for the inputs

 

ok with this new settings, Latencymon looks even better:
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:36:22 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-M9R85AK
OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: SCHENKER VIA 14 Pro (M24), SchenkerTechnologiesGmbH
BIOS: 12.08
CPU: AuthenticAMD AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
Logical processors: 8
Processor groups: 1
Processor group size: 8
RAM: 16190 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 3801 MHz
Reported CPU speed (registry): 3793 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution
of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 281,0
Average measured interrupt to process latency (µs): 4,566215

Highest measured interrupt to DPC latency (µs): 276,0
Average measured interrupt to DPC latency (µs): 0,772842


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 186,954390
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0,006722
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0,006722

ISR count (execution time <250 µs): 3775516
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 340,146586
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total DPC routine time (%): 0,191973
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0,204183

DPC count (execution time <250 µs): 3811958
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 37
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk
while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: id.exe

Total number of hard pagefaults 15797
Hard pagefault count of hardest hit process: 12496
Number of processes hit: 27


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 63,121659
CPU 0 ISR highest execution time (µs): 186,954390
CPU 0 ISR total execution time (s): 0,915030
CPU 0 ISR count: 2740292
CPU 0 DPC highest execution time (µs): 340,146586
CPU 0 DPC total execution time (s): 35,497234
CPU 0 DPC count: 3751875
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1,701504
CPU 1 ISR highest execution time (µs): 8,155022
CPU 1 ISR total execution time (s): 0,068992
CPU 1 ISR count: 314990
CPU 1 DPC highest execution time (µs): 51,044028
CPU 1 DPC total execution time (s): 0,006779
CPU 1 DPC count: 3921
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1,645613
CPU 2 ISR highest execution time (µs): 24,925916
CPU 2 ISR total execution time (s): 0,051602
CPU 2 ISR count: 230221
CPU 2 DPC highest execution time (µs): 55,021355
CPU 2 DPC total execution time (s): 0,005638
CPU 2 DPC count: 3394
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 3,027098
CPU 3 ISR highest execution time (µs): 4,798840
CPU 3 ISR total execution time (s): 0,007501
CPU 3 ISR count: 20228
CPU 3 DPC highest execution time (µs): 68,035328
CPU 3 DPC total execution time (s): 0,041307
CPU 3 DPC count: 14457
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2,876502
CPU 4 ISR highest execution time (µs): 22,371210
CPU 4 ISR total execution time (s): 0,020249
CPU 4 ISR count: 56497
CPU 4 DPC highest execution time (µs): 113,929871
CPU 4 DPC total execution time (s): 0,033021
CPU 4 DPC count: 12128
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 3,004594
CPU 5 ISR highest execution time (µs): 6,301608
CPU 5 ISR total execution time (s): 0,023464
CPU 5 ISR count: 61355
CPU 5 DPC highest execution time (µs): 137,353019
CPU 5 DPC total execution time (s): 0,044028
CPU 5 DPC count: 17101
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 2,460248
CPU 6 ISR highest execution time (µs): 21,068811
CPU 6 ISR total execution time (s): 0,036584
CPU 6 ISR count: 137422
CPU 6 DPC highest execution time (µs): 117,065647
CPU 6 DPC total execution time (s): 0,011633
CPU 6 DPC count: 5353
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1,933513
CPU 7 ISR highest execution time (µs): 26,869496
CPU 7 ISR total execution time (s): 0,050158
CPU 7 ISR count: 214511
CPU 7 DPC highest execution time (µs): 99,693646
CPU 7 DPC total execution time (s): 0,008207
CPU 7 DPC count: 3766
_________________________________________________________________________________________________________

 

Try to test your workflow in Reaper. I think that problem is not in you computer [Ableton is the problem]

 

This is what I was talking about just from seeing many posts about Ableton, cpu spikes (especially when they first put out a major version number upgrade). The cpu jumping 10% is expected switching to the much smaller buffer with an empty project. Also, it's not exactly known for its' external hardware latency compensation accuracy. It's nearly perfect in Logic, and this is why I never even started using Ableton.

This is how I would test "Blame Ableton". That laptop is more than powerful enough for recording real-time audio. Better yet even, for recording Midi data for any minor quantization and editing, and then a render in a second pass. That way you can add all the VST plugin automation you want between playing and rendering steps.