Barley wrote on Today, 15:44:Mumak wrote on Today, 15:17:Please provide HWiNFO Debug Files from both HWiNFO versions and I'll check that.
Thanks! Try to enable the "Low-level PCI Access" option in HWiNFO and let me know if that worked.
Mumak wrote on Today, 16:43:Thanks! Try to enable the "Low-level PCI Access" option in HWiNFO and let me know if that worked.
Sure did! Thank you! Is there a short and easy way to explain what the problem was? I'm especially curious about what was different with my chipset/motherboard to cause the issue.
Nothing is different with your system. It's due to certain security rules Microsoft introduced in kernel where they don't allow direct access to PCIe configuration space on some systems anymore.
Since this restriction resulted in BSODs on some systems, we have globally disabled the "Low-level PCI Access" option for all systems including legacy ones. But I didn't realize that the alternate function (via HAL) doesn't work as expected on XP and here the direct access is still required on systems like yours (where we need access to extended PCIe space). This will be fixed in the next HWiNFO build by enabling this option by default on such systems.
Mumak wrote on 39 minutes ago:direct access is still required on systems like yours (where we need access to extended PCIe space).
"extended PCIe space": do you mean systems with a plx chip, or a large number of native pcie lanes like my i7-4930K/Rampage IV Extreme?
Neither of those. It's the internal PCIe register space at offset 0x100 and above (so extended space from 0x100 in legacy PCI).
Mumak wrote on 15 minutes ago:Neither of those. It's the internal PCIe register space at offset 0x100 and above (so extended space from 0x100 in legacy PCI).
Thanks. I was curious because CPU-Z is having the same issues reading my memory, but unlike HWiNFO, there is no setting that I can find that will fix it, nor will downgrading to an earlier version fix it.
