Core Isolation affects CPU bus clock?

Until recently I'd never enabled Core Isolation in the security settings. I switched it on a few weeks ago for the first time.

Running HWInfo yesterday I noticed that the CPU bus clock was ~98.5MHZ, and not 100MHz meaning that the CPU never reached it's peak speed (3700). Also the RAM clock was ~1780Mhz and not 1800. RAM is using XMP but the CPU is stock, I'm not one to fiddle with CPU BIOS settings.

After a panic thinking I had a hardware issue, I switched Core Isolation off again - and sure enough the base clock and RAM now run at the full speed.

I'm guessing this is by design? An overhead created by using HVCI?

Hi,
Yep
Virtualization features need to be disabled in bios

If you don't want to do that you can try an older portable version 6.08 and the issue might not happen or it doesn't for me but those features you state do need to be disabled.
But with VM features enabled in bios you can still use vm of windows or linux just not core isolation

ThrashZone said:

Hi,
Yep
Virtualization features need to be disabled in bios

If you don't want to do that you can try an older portable version 6.08 and the issue might not happen or it doesn't for me but those features you state do need to be disabled.
But with VM features enabled in bios you can still use vm of windows or linux just not core isolation

HWiNFO

HWiNFO: Free software download for olderv versions of windows.

www.fosshub.com

Click to expand...

Virtualization is enabled in BIOS, I've disabled core isolation and now get full speed RAM and CPU bus. I've managed for years without it anyway.

By the way this is what I got even with core isolation/... disabled
Wish they would get with cpu-z this is a world record