This is actually a bug in measuring the CPU BCLK in HWiNFO, which is currently discussed in another topic here too.
I'm working on fixing this right now. It would be helpful for me if you could capture this issue while running HWiNFO in Debug Mode and attaching/sending the resulting Debug File for analysis.
Please try to new v4.43-2295 Beta and let me know if it's fixed now.
Uhm, that's not normal. Is there maybe some application or component in the system that might interfere with the timers ?
In case you don't change BCLK on the fly, you might try to disable the "Periodic polling" option under "CPU Clock Measurement" in HWiNFO.
Disabling periodic polling seems to fix it, but...CPU-Z still shows BCLK under 95-94 MHz.
CPU-Z does use a very similar method to calculate BCLK as HWiNFO. You just won't notice rare peaks there, because it doesn't keep Min/Max values.
I assume it's a bad reading - something might be interfering with the timers or counters used to measure the actual BCLK.
Solved it, the culprit is Hyper-V manager, turning the feature off solves the issue.
But I still want to use Hyper-V though, hope you can maybe investigate this problem.
FYI Martin I very rarely see those out of range values in Core Clock and Bus Clock.
ASRock Z97 Extreme6 Intel Xeon E3-1276 v3 Scythe Mugen 4
16GB Samsung M3V 2000MTs 1.35V
SanDisk Extreme Pro 256GB Windows 8.1 UEFI boot
Samsung 840 Pro 256GB x 2 RAID 0 Windows 10 TP UEFI boot
Samsung 830 256GB x 2 RAID 0
EVGA GTX 760
Seasonic X660 XP2 PSU
Fractal Define R4