Jump to content

Fiery

Administrators
  • Posts

    12283
  • Joined

  • Last visited

  • Days Won

    541

Posts posted by Fiery

  1. PCH Diode is a temperature diode that is integrated in the motherboard chipset (also known as PCH for modern Intel platforms).  Some motherboards have no such diode connected, and some other motherboards may have the diode improperly implemented.  In the latter case the temperature readout may be stuck at a fixed value.  If that's the case, just ignore the reading ;)

  2. Thank you for the test.  It seems this mux is a bit tougher to crack than we anticipated :(  If it's possible, please do one more test for us:

     

    1) Restart your system, and make sure F-Stream is not auto-started when Windows loads up.

     

    2) Start AIDA64, check if both CPU fans are missing from the Sensor page

     

    3) Right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Super I/O Dump.  Copy-paste the full results into this topic.

     

    4) Close AIDA64

     

    5) Start F-Stream, check if both CPU fans are properly measured

     

    6) Close F-Stream

     

    7) Start AIDA64, check if any of the CPU fans is properly measured on the Sensor page

     

    8) Repeat step 3

     

     

    Thanks,
    Fiery

  3. My GA-Z77X-UP7 is also showing the wrong CPU voltage in CPUID, it shows 1.068 on an overclocked processor that EasyTune shows as 1.41.

     

    1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic.

    2) Also, right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic.

    Thanks,

    Fiery

  4. okay, thanks!

     

    P.S

    Just a quick question, would it help if I clear cmos I mean would that remove that Unknown whatever that is ?

     

    You can try, but I don't think that would help.

  5. Thanks for the dump.  If you would like us to improve AIDA64 to better support your motherboard, then please run the test for us.  Even if you don't upgrade to a newer AIDA64 release now, you may do that in the future, and by then you would have an AIDA64 release that has better support for your current hardware.  Of course by then you may have an even newer hardware, but that's another issue :) :)

     

    I've also sent you a private message.

  6. Then please try to do the following:

     

    1) Restart your system, and make sure F-Stream is not auto-started when Windows loads up.

     

    2) Start AIDA64, check if both CPU fans are missing from the Sensor page

     

    3) Right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump.  Copy-paste the full results into this topic.

     

    4) Right-click on the bottom status bar of AIDA64 main window --> System Debug --> ISA Sensor Dump. Copy-paste the full results into this topic.

     

    5) Close AIDA64

     

    6) Start F-Stream, check if both CPU fans are properly measured

     

    7) Close F-Stream

     

    8) Start AIDA64, check if any of the CPU fans is properly measured on the Sensor page

     

    9) Repeat steps 3 and 4

     

    Based on those dumps, we may be able to figure out how to set the mux into a state that allows you to at least monitor one of the CPU fans.


    Thanks,
    Fiery

  7. Please note that AIDA64 requires the driver of the Asetek/Antec water cooling system to be installed on the system.  So try to reinstall the ChillControl software (that also installs the drivers), but not have it running while you use AIDA64.

     


    Regards,

    Fiery

  8. Hello and thanks again for the fast reply.

    I perfectly understand the situation and the readings for the awesome AMD processor. Seems that Idle temps are going crazy, while the load temps are kinda normal.

     

    Anyway what can I do to fix this problem, because I took this platform so I can test CPU coolers and like this it is useless?

     

    I suppose the only reliable temperature measurement would be getting an external thermal diode that you could attach to the processor die.

  9. Please note that AMD Trinity processors implement a flawed temperature diode that is unable to provide correct temperature readings, especially when the CPU is at idle.  HWMonitor apparently implements a trick to correct the invalid temperature readings, but it's definitely not right even that way, since for example on our test system of Gigabyte F2A85X-UP4 + A10-5800K we get over 110 Celsius values using HWMonitor v1.21 while running the AIDA64 System Stability Test with FPU+GPU subtests enabled.  The processor would simply fry at such exceedingly high temperature, so the reading must definitely be incorrect.

     

    BTW, AIDA64 also implements a manual correction facility, so if you believe you know a formula to correct the core temperature readings on your system, to make them more realistic, you can try applying it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.

  10. the new disk usage is great! Is the program able to show a hard drive read and write percentage? Or something like page fault delta reading in the task manager?

     

    Currently such type of disk performance measurement is not supported by AIDA64.  We may implement it sometime later this year.

  11. Thank you.  Since the sensor chip's fan register corresponding to the muxed CPU_FAN1 and CPU_FAN2 headers indicates an invalid RPM reading, I suppose your motherboard by default would monitor CPU_FAN2 instead of CPU_FAN1.  Try to connect your fan to CPU_FAN2, and check if it appears in AIDA64 that way.

     

    As for Antec water cooling systems, unfortunately the way ChillControl software is designed, it's not possible to monitor the water cooling system from two or more different software :(  In other words, the access to the water cooling device is exclusive: either ChillControl accesses it, or AIDA64, but they cannot access it simultaneously.

  12. Certain video adapters use power management tricks that lower PCI-E speeds when the card is at idle.  Try to run a 3D application, and look at the bus speeds while that is running.  Alternatively, you can try using the GPU subtest of the AIDA64 System Stability Test (AIDA64 / main menu / Tools / System Stability Test).

     


    Regards,

    Fiery

  13. It's definitely not a virus.  BIOSes tend to use incorrect table signatures or completely corrupted tables to hide specific ACPI tables when you select such behavior in the BIOS Setup.  For example, if you disable the HPET table -- although in your case HPET is enabled ;)  Of course it could also be due to a BIOS bug, but such bugs fortunately doesn't cause any actual issues.

     


    Regards,

    Fiery

×
×
  • Create New...