Hi Pete, I’ve done all of the power options (and then some, using Power Settings Explorer) and the results were still the same. I’ve had C States and EIST disabled in the Bios (Gigabyte Z590 Aorus Pro AX, 64GB Ram) but I’m still having issues. It’s way worse when I Monitor a channel, as the VST Meter will jump from 50% to peaking and distorting. Meanwhile, Cubase in the Windows Task Manager is at 6.2%. Thanks for the suggestions!
Other than the power / c-state change, I’m not aware of anything else in 24h2 that changed that could impact this. (That doesn’t mean there couldn’t be something, just that I am out of ideas there.)
I mean, it could be things that would impact you across versions, like if you are using a sample instrument and haven’t excluded the sample folder from Defender real-time scans, or if your project folder is being managed by OneDrive.
Do you see anything else in the task manager taking up CPU cycles?
Pete
Microsoft
Interesting, but I would not block h2 because it seriously prevents some very cruel backdoors and protection it also stops to my knowledge the automatic screen recording of windows copilot which was forbitten by the EU back in December. So not installing is also not good in my humble opinion. Interestingly I made a post yesterday that the issues seem to be not because of windows 11 but because of 13 and 14 … Cubase 12 pro has non of the issues with windows 11
it also stops to my knowledge the automatic screen recording of windows copilot which was forbitten by the EU back in December
FWIW, the screen recording, called “Recall”, is only available on Copilot+ PCs (they have the Copilot+ key and a certain level of NPU on the processor package), and was only released to the public (except EU, where it is not yet available) this week.
Pete
Microsoft
If we tweak this one value to IDLESTATEMAX 2, which value is default if we want to revert back to default value? Thanks
It’s going to depend on your configuration. I recall that Cubase would kick in its own power configuration when running, but I haven’t looked into that in a long time.
Here’s how you see the configuration for your current power scheme
powercfg /query
Will give you all the information from the power scheme. I don’t have any setting for IDLESTATEMAX on my PC and current power scheme.
The max C-state is per processor. Intel descibes it as “C1-Cn” with “n” being whatever the max (most sleepy) state the processor supports is. Anecdotally, Intel processors in idle tend to be C3.
Some folks also set that max to 1.
scheme_current is an alias for the current power schemes. You can list them using
C:\Users\peteb>powercfg /list
Existing Power Schemes (* Active)
-----------------------------------
Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Balanced)
Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c (High performance) *
Power Scheme GUID: a1841308-3541-4fab-bc81-f71556f20b4a (Power saver)
Power Scheme GUID: e9a42b02-d5df-448d-aa00-03f14749eb61 (Ultimate Performance)
C:\Users\peteb>
To see just the configuration for sub_processor (the one referenced above), type this
C:\Users\peteb>powercfg /query sub_processor
The power scheme, subgroup or setting specified does not exist.
C:\Users\peteb>powercfg /query scheme_current sub_processor
Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c (High performance)
GUID Alias: SCHEME_MIN
Subgroup GUID: 54533251-82be-4824-96c1-47b60b740d00 (Processor power management)
GUID Alias: SUB_PROCESSOR
Power Setting GUID: 893dee8e-2bef-41e0-89c6-b55d0929964c (Minimum processor state)
GUID Alias: PROCTHROTTLEMIN
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0x00000064
Possible Settings increment: 0x00000001
Possible Settings units: %
Current AC Power Setting Index: 0x00000064
Current DC Power Setting Index: 0x00000005
Power Setting GUID: bc5038f7-23e0-4960-96da-33abaf5935ec (Maximum processor state)
GUID Alias: PROCTHROTTLEMAX
Minimum Possible Setting: 0x00000000
Maximum Possible Setting: 0x00000064
Possible Settings increment: 0x00000001
Possible Settings units: %
Current AC Power Setting Index: 0x00000064
Current DC Power Setting Index: 0x00000064
C:\Users\peteb>
powercfg is documented here.
To get help on any command, just type /? before the name of the command.
C:\Users\peteb>powercfg /? query
POWERCFG /QUERY [<SCHEME_GUID> [<SUB_GUID>]]
Alias:
POWERCFG /Q
Description:
Displays the contents of the specified power scheme. If neither SCHEME_GUID
or SUB_GUID are provided, the settings of the current active power scheme
are displayed. If SUB_GUID is not specified, all settings in the specified
power scheme are displayed.
Parameter List:
<SCHEME_GUID> Specifies a power scheme GUID. A power scheme GUID is
returned from the "POWERCFG /LIST" command.
<SUB_GUID> Specifies a power setting subgroup GUID. A power setting
subgroup GUID is returned from the "POWERCFG /QUERY"
command.
Examples:
POWERCFG /QUERY
POWERCFG /QUERY 381b4222-f694-41f0-9685-ff5bb260df2e
238c9fa8-0aad-41ed-83f4-97be242c8f20
C:\Users\peteb>
One way you can experiment is to create your own power scheme, set it current, and then mess with the values.
C:\Users\peteb>powercfg /? duplicatescheme
POWERCFG /DUPLICATESCHEME <SCHEME_GUID> [<DESTINATION_GUID>]
Description:
Duplicates the specified power scheme. The resulting GUID which represents
the new scheme will be displayed.
Parameter List:
<SCHEME_GUID> Specifies a power scheme GUID. A power scheme GUID is
returned from the "POWERCFG /LIST" command.
<DESTINATION_GUID> Specifies the new power scheme's GUID. If no GUID is
specified, a new GUID will be created.
Examples:
POWERCFG /DUPLICATESCHEME 381b4222-f694-41f0-9685-ff5bb260df2e
C:\Users\peteb>
Pete
Microsoft
4 Likes
My experience with 24H2 has been so-so. It was finally offered to my laptop here, and I have been using it for around a month now.
In almost all cases it was good, it was a long time since the last ‘upgrade’.
I had a bunch of custom settings for power management, all gone.. And had to redo my display driver. It’s really more ASUS fault, I think.
In Windows itself I have noticed a couple new bugs, but I think most of it is already patched…