Jump to content
AIDA64 Discussion Forum

mumak

Members
  • Content Count

    22
  • Joined

  • Days Won

    1

Everything posted by mumak

  1. Could you please also make a dump when fans are running at max speed?
  2. As I said before, it's a bug in NVIDIA drivers, so NVIDIA must fix it.
  3. AFAIK this was a problem of recent NVIDIA GeForce drivers (r397).
  4. This can happen if SVID is disabled in BIOS - in such case CPU power monitoring cannot work. Please check the BIOS settings.
  5. Some older HP Envy series (based on Quanta ODM design) used to have fan speed at EC [0xB2-0xB3], [0xD2-0xD3] (FAN_FEEDLo / FAN_FEEDHi). Not sure if that might apply here, but it's rather unlikely as the above models were notebooks using ENE ECs. An Embedded Controller dump (with known high and low fan speeds) might shed some light... And maybe a DSDT dump too...
  6. It's the highest temperature among all diodes on the CPU (cores, GT).
  7. I believe not all voltages you see in E-LEET can really be monitored. That screen is used to set values only, for values really monitored check the "Monitoring" tab.
  8. Please post the ISA and SMBus sensor dumps.
  9. It still might be a B3 chipset. There's a feature in Intel chipsets called Chipset Compatibility Revision ID. If this feature is activated by the BIOS, then the chipset reports a Compatible Revision ID (which is not the true hardware revision of the chip). On the 6-series chipsets this would cause all the identifiers on a B3 chipset to report a B2 value ! Unfortunately in this case there is NO UNIVERSAL WAY how to determine the true Hardware Revision ID - the only possible method would be if the BIOS saves the original ID in some register, then activates this feature and offers the reading of this ID to its own tools (which might be the case of the Acer tool). When this issue came out some vendors have released BIOS updates which obviously do not enable this feature anymore and so allow a proper reading of the ID - the result was that machines with a B3 chipset have been reporting B2 in all tools unless the user performed such BIOS update.
  10. Thanks. Note for Fiery: VIN1 = DIMM VIN2 = NB VIN3 = +3.3V (*2)
  11. Please post a photo of the BIOS System Health screen, or write down the values it displays.
  12. Indeed that could be the issue. The BIOS is unable to inform ME of POST end and that can cause several issues. Possible solution: BIOS upgrade (with ME) or RMA
  13. mumak

    DPC Latency

    I don't see a relation between HPET or C-States and a badly written driver which spends more time at IRQL >= DPC_LEVEL than allowed.
  14. The question is whether they would be willing to release that info. If yes, an NDA would solve the confidentiality concern. It might be worth a try..
  15. I'm not sure whether HWMonitor really supports DES, but in many cases the CPU Power Consumption reported there is not really measured, just totally estimated (guessed) based on TDP and current P-State. Such values are practically useless.
  16. Could you post a pohoto of BIOS Health monitoring page?
  17. Or does he see any other reading in the BIOS that's not covered by AIDA64?
  18. The PCH sensor might not be configured/calibrated properly and in such case it seems to be stuck at 59 C. This is common on many mainboards. You might want to ignore the PCH Temperature in case TBAR[0x03] is >= 0x80, which is what I do..
  19. Yeah, of course, I forgot this litte detail
  20. HWMonitor doesn't really monitor CPU Power Consumption, it just reports a rough estimatation basen on current P-State (voltage) and maximum TDP/TDC. And that's the reason it doesn't report the power consumption here, because this SKU doesn't specify max TDP/TDC (it's unlimited). There are other tools able to really monitor CPU power consumption on Nehalem and later CPUs based on Energy Counters (independant on Max TDP/TDC values, but requires platform enabling in PCH/BIOS).
  21. That means, the TDP/TDC is unlimited on that SKU.
×
×
  • Create New...