Recent content by marcosscriven

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

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

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

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/threads/hwinfo-is-crashing-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...

Just an idea - as I’m not sure how the code works. But could you have a function that wraps all such register accesses, and debug logs if they aren’t there?

Doh - it’s right there in the error log, sorry. looks like something to do with boost state:https://github.com/cyring/CoreFreq/blob/master/amdmsr.h

May I ask which register? It may be useful feedback for the QEMU devs. I Googled “Ryzen FEE00900” and could only find something called “APIC base” Thanks again

@Martin - I just tried beta v6.25-4135 and it worked perfectly (without any changes to my setup). May I ask what you did please? And thanks!

Thank you @Martin - I’ll keep a lookout.

Sorry, it‘s not correct to for me to say it crashes the VM. When I check the Windows events afterwards it says something is crashing the kernel. From the host perspective everything is fine with the VM. I totally get it’s not the intended use case for HWiNFO here, however it really would be...

Please see full attached debug report. However, the error seems to be at the end: Log CPUs: 12, cores: 6 RdMSR[#0000001B] = 00000000:FEE00900 APIC ID[00]: PackageID=0, CoreID=0, ThreadID=0, M, BSP ExtCPUname: "AMD EPYC Processor (with IBPB)" RdMSR[#C0010293] ERROR RdMSRm: #C0010064 #C0010065...