Hi.
Please refer to this document for high CPU troubleshooting:
Hope the information is helpful.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />
<EventID>2</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2023-05-21T01:58:21.703565000Z" />
<EventRecordID>83117699</EventRecordID>
<Correlation ActivityID="{f99b800c-d922-427e-b58f-c83741b3e29c}" />
<Execution ProcessID="2104" ThreadID="3164" />
<Channel>System</Channel>
<Computer>VMPOSSUM</Computer>
<Security UserID="S-1-5-19" />
</System>
- <EventData>
<Data Name="Length">880</Data>
<Data Name="RawData">435045521002FFFFFFFF0300020000000200000070030000153A0100150517140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F89080782BDC0589D901000000004552000000000000000000000000000000000000580100005000000000030000010000001411BCA5646FDE4EB8633E83ED7C83B100000000000000000000000000000000020000000000000000000000000000000000000000000000A8010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000068020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E800000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000057010000000000000002000000000000E4060300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000390000000000000000000000000000000000000000000000000000000000000000000000000000000200000001000000249025B8878BD90127000000000000000000000000000000000000000700000090000100000500CCC09AC7022800000000D01242010000000000000039000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
</EventData>
</Event>
Hi.
Please refer to this document for high CPU troubleshooting:
Hope the information is helpful.
Hello there,
Did you upgrade your cluster from 2016 to 2019?
This is a problem with Hyper-Threading when you upgrade your cluster from 2016 to 2019. You need to make sure to upgrade your VM's configuration version when the VM's are off from 8.0 to 9.0. You may also need to set the VM Processor settings to HwThreadCountPerCore to 0 from 1.
In Windows Server 2019, Hyper-V now defaults to a more secure “core scheduler” where previous versions used “classic scheduler” for CPU scheduling and isolation. What this means, is that when you migrate a VM over to Hyper-V on WS2019, you need to update the VM configuration and change some settings, or it will only use a single hardware thread per core.
Get-VMHostSupportedVersion
Get-VM | FT Name, Version
Get-VM | Update-VMVersion
Get-VM | Get-VMProcessor | FT VMName,HwThreadCountPerCore
Get-VM | Set-VMProcessor -HwThreadCountPerCore 0
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer–