HWInfo v6.27-4170 hanging in VM

[marcosscriven]

A while back I reported that HWInfo managed to completely crash my VM.

That was resolved by v6.25-4135 https://www.hwinfo.com/forum/thread...my-vm-while-reading-cpu-info.6279/#post-24218

While that was working for a while, I'm now finding a less serious bug where HWInfo hangs, but the VM is unaffected.

Debug log attached - but it ends in:

DPI 1.50 1.50
Completing: Comp
- Completing CPU data...
Completing: CPU Root
Completing: CPU 0
ERROR 0
AMD CPU_SMU_SVC[D][3]=ERROR 0
AMD CPU_SMU_SVC[D][4]=ERROR 0
AMD CPU_SMU_SVC[D][5]=ERROR 0
AMD CPU_SMU_SVC[D][6]=ERROR 0
AMD CPU_SMU_SVC[D][7]=

I've tried both the current release and the latest beta - I'm unsure exactly when it stopped working.

Thanks

 

[marcosscriven]

Update - given several minutes, it does eventually load. Not sure why the delay though.

 

[Martin]

This is a failure of VMM and given that it masks access to real hardware I don't understand the need to run a tool like HWiNFO there and expect proper reporting.
Under VM the hypervisor has full control of hardware and HWiNFO cannot report correct information unless the hypervisor allows this.

 

[marcosscriven]

It's handy for a few good reasons - however, unlike the first time you don't sound interested, so I'll leave it.

 

[Martin]

The entire VM system looks funny - AMD Ryzen 9 3900X on Intel P35 chipset.
How is a tool like HWiNFO expected to work there when the hypervisor totally messes access to real hardware - something is passed thru, something emulated...

 

[marcosscriven]

ok, I get it.I’m a fool for asking. Sorry.