Jump to content

Fiery

Administrators
  • Content Count

    10027
  • Joined

  • Last visited

  • Days Won

    448

Posts posted by Fiery

  1. On 4/26/2021 at 9:44 AM, masterdrew01 said:

    I've been using sensor panel to keep an eye on various bits of information about my PC, and I've had a big issue where virtually any time my PC is under a heavy load, my screen will freeze for a few seconds and then reboot suddenly. Sometimes this happens very early in an intense gaming session and sometimes it happens after an hour or two, but almost every time I do any heavy duty gaming, my PC freezes and then reboots. The same thing happens sometimes without my PC being under any load at all, or under very light loads like streaming a movie on Netflix or writing a paper on Microsoft Word. At times, I've gotten up from my PC while leaving it idle (with the sensor panel active), and when I've returned a few minutes later it will have rebooted. This occurrence is much less common when demanding games are not being played, but it still happens at least once every three or four days. Considering that the main times I want to have sensor panel running is while I am gaming, this is obviously a very big issue. I bought this software solely for its sensor panel functionality, and so not having use of it is very disheartening to me. I know that it is Aida causing this problem as a few weeks ago I stopped using it and all crashing problems have since been resolved. On a few occasions since then I have tested it out again and every time my PC has frozen and rebooted within a few hours of resuming use. I have all of the latest software downloads both for Aida and windows, so I don't think that is the issue. Any help in this area would be much appreciated.

    Please let us know what motherboard, CPU and video card(s) you have in your computer.

  2. 18 minutes ago, Exxpedition said:

    Hi,

    I would like to know your opinion in refer to your experience. How accurate is battery capacity info for Galaxy S20 Samsung.

    I'm a bit dissapointed cause, after unpack brand new S20 i checked battery declared by samsung as 3880 min capacity, but it appeard in AIDA, there is max circa 3620 mAh..

    Do you have any ecxxperience with that? I understand, that some differences are possible, but want to learn your opinion.

    BR

    Expedition

    We don't have experience on that, but maybe others would chime in having the same phone than yours.

  3. 13 hours ago, Andrew Pafitis said:

    Wow you guys are fast.

    The fan sensors are labeled and responding as expected, no issues with RPMs jumping sensors. However I'm not seeing the AIO_PUMP represented anywhere, and the "Power Supply" fan is no longer there. AIO_PUMP RPMs were previously reported, albeit with issues as described above. Is the Power Supply fan not able to be read from the motherboard?

    I have no idea why the issue comes about the AIO_PUMP RPM :(  We've renamed the PSU fan to Chassis #3 fan since we had no better idea than this on where the Chassis #3 fan RPM reading might come from :)

  4. On 1/29/2021 at 10:55 PM, davis said:

    So hwinfo just released an update as many already know - that allows us to monitor the memory temperature on 3080/3090 cards, as this seems to get pretty toasty on founders cards especially.. 

    I was just wondering if it's possible or planned in the near future to add the same possibility to aida64? Or is there any way I can haxx it in there, I can of course use hwinfo but I have everything else on my sensorpanel and don't want a floating window just for the sake of it.

    Here's the first AIDA64 beta to measure Hotspot and VRAM temperature for nVIDIA video cards:

    https://www.aida64.com/downloads/latesta64xebeta

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

    Let me know how it works.

  5. 5 hours ago, Andrew Pafitis said:

    I have the new NZXT B550 motherboard that was released a few weeks ago. Some of the cooling fans listed have oddly specific names in Aida64 (System, Chassis, GPU) when the motherboard pins are labeled CPU_FAN, AIO_PUMP,  SYS_FAN 1, SYS_FAN 2, SYS_FAN 3, SYS_FAN 4, and SYS_FAN 5. See here on page 15, items 2, 5, 16 and 29: https://nzxt-site-media.s3-us-west-2.amazonaws.com/uploads/download/attachment/1033/N7_B550-Digital_Manual-210315-EN.pdf

    For full context on my machine, it's the NZXT B550 motherboard with 5800x Ryzen, NZXT X53 AIO on the CPU, RTX 2080 (stripped for AIO), second RTX X53 AIO on the GPU, NZXT E850 power supply (connected via USB for smart monitoring in NZXT CAM), and a USB connected NZXT RGB & Fan Controller (although I have no fans attached to that, just using for additional RGB channels).

    I can map some of the motherboard headers to sensors in Aida64, but not all.

    CPU_FAN="Chassis", connected to CPU AIO Radiator Fans

    AIO_PUMP="CPU", connected to CPU AIO "AIO" cable

    SYS_FAN 1 = "System", connected to GPU AIO Radiator Fans

    SYS_FAN 2="Aux", connected to GPU onboard fan

    SYS_FAN 3=???, I don't have a fan connected to read outputs on A64

    SYS_FAN 4=???, connected to case exhaust near CPU, I can't find any sensor in A64 showing this fan's speeds

    SYS_FAN 5="Aux2", connected to case exhaust near GPU

    Also strange, the AIO_FAN/"CPU" sensor properly reads out the AIO pump speed from the motherboard, BUT only if the CPU_FAN is not running. If CPU_FAN fan is running and displaying "Chassis" RPMs, Aida64 then shows 0 RPM from "Chassis" and the pump's actual RPMs are displayed against the "Power Supply" sensor. This is the only time that "Power Supply" shows any RPMs, and doesn't actually ever show the PSU's fan speed.

    The only other cooling fan sensor showing in A64 is "GPU". This is likely reporting off the GPU's internal fan port, but I have that fan cable disconnected and instead control an aftermarket onboard fan for the card and the AIO fans through the motherboard headers (SYS_FAN 1 and SYS_FAN 2).

    So in my system, the Power Supply fan from the E850 and SYS_FAN 4 are definitely not showing RPMs on any sensors in A64. SYS_FAN 3 could also be missing but I don't have anything connected to it to confirm.

    I would have expected to see the 3 additional fan ports from the NXT usb fan controller, although I now see in another thread that support for the fan controller was added last month in a beta update. Just installed the beta and still not seeing them, assuming then that fans need to be connected before they're detected in A64. Besides that, latest beta still having all the same issues above with the motherboard ports and PSU fan.

    I'm also assuming that the only way to see the pump speed from the second AIO attached to the GPU would be to connect it to one of the fan ports, is that correct? Both AIOs are connected via USB and report pump speed to NZXT CAM as expected, just not sure if A64 is supposed to be able to read from the USB or needs to read discretely from the headers. Is it an issue that I have 2 of the same AIOs attached to the system?

    Attaching the ISA sensor and USB dumps as I've seen requested in other threads. I can do more testing if necessary, but my rig is mounted on the wall in a Thermaltake P90, so it's really a pain to disconnect and take down to work on. (It's so beautiful tho)

    We've fixed the labels for the fan readings measured by the Nuvoton SIO sensor chip of your motherboard in the following new beta update of AIDA64:

    https://www.aida64.com/downloads/latesta64xebeta

    Let me know how it works.

    As for the other NZXT USB-connected devices, AIDA64 can detect them (a Kraken X53/X63/X73 and an NZXT RGB & Fan Controller), but I suppose due to the fact that you've had NZXT CAM Software running in the background, it couldn't open them and handle them properly.  NZXT CAM doesn't really tolerate any other software gaining access to NZXT devices -- except for the motherboard sensor chip where it cannot lock other software from accessing it.

  6. On 3/20/2021 at 3:29 PM, Hittman said:

    Sorry to hijack thread, but I wanted to report that this hang event was not only impacting systems with odospace installed.   I have a new EVGA SR-3 with the Intel Xeon W-3175x.  When running the sensor panel on a 3rd HDMI monitor the system randomly hangs while idle.  I can run 3DMark for hours but as soon as the system is idle the system will hang at random intervals.  I have installed the latest Beta version downloaded this morning and the problem persists.  I am running a pair of EVGA Titans at the moment.  I will test again when the EVGA 3090 FTW3 Hydro Copper gets here next week.  The system seems stable with Aida64 running as long as the sensor panel is not running.

    Try to check it with AIDA64 v6.33 (latest version) as well.  Your motherboard uses a very particular sensor solution, so let's start with that.  Do you have any other monitoring software (either made by EVGA or a 3rd party) running in the background that may collide with AIDA64?

  7. 59 minutes ago, Anthony Rodriguez said:

    Anyone got any 480 x 800 fire dbz or dbs panels?

    I apologize for being slightly ignorant and clueless, but what's dbz and dbs? :)

  8. On 4/18/2021 at 4:12 AM, Ghryst said:

    "We used to offer the 1 PC license for the same starting price of $39.95.  So we haven't raised the price, but raised the number of licenses you get for the same price."
    now almost double that in only 4 years.
    you could be gaining SO MANY MORE CUSTOMERS, for the same development price, if you would price your product reasonably.
    most monitoring software is free, aid64 IS better, so it justifies a charge, but NOT almost the price of an AAA game that has 100's of developers working on it.
    in 2021, for the reasons above, $10-$15 IS reasonable, and the reason i will not purchase at the currently almost $60 pricetag, for home users, PER YEAR. 
    maybe you need to change your business model to fit the market?

    I appreciate your post, and you have a number of valid points there, but what you quote ("$60 pricetag ... PER YEAR") is not correct.  We reserve the right to set our prices at a level where we believe the value of our software is, and what justifies the efforts and resources we've been investing into this software since 1995.  You on the other hand have the right to choose a different software if you deem our prices unacceptable or unjustified.  The fact that you're so passionate about our pricing and you put time and efforts into posting into this forum however indicates to me that you actually like our software and dedicated to continuing to be a part of our journey.  Because of that reason I'll send you a private message about some further stuff ;)

  9. 4 hours ago, 1usmus said:

    Why do you block global PCI mutex during memory throughput testing? 
    Why do you always have the cache tested not by the best core, but always by the 0? Perfect pattern for Intel and disgusting for AMD.

    1) Do you mean the Global\\Access_PCI mutex?

    2) I'm confused. Do you mean the throughput (bandwidth) benchmark for the caches or the cache latency benchmark?  And what CPU do you think we measure an incorrect performance of and by what margin?

    3) Are you the author of Ryzen Tweaker? :)

  10. 7 hours ago, Largeone299us said:

    Why can I not get the panel lock size to just lock the damn size. Please help. I have done the DPI settings item. I have done the scaling for different monitors thing. Every time I get any sort of update to a driver any where on the damn PC this software destroys all the work I put into making the sensor panel. It shifts everything off the screen I spent hours making and changes the size to whatever number it feels like no matter what I set the lock to. In fact if I open a panel that I know I had saved as 1024 by 600, it resizes it to 1564 by something every time. Please can someone tell me what to do to fix it.

     

    Please avoid posting a single issue into multiple topics.  I've replied you in your other topic. This topic is closed.

  11. 7 hours ago, Chris Swann said:

    I know it's Aida64 because if I close the program down the problem stops. 

    The problems occurs when I right click anything to do with the desktop. So, an example, if I create a new folder on the desktop, the new folder icon normally automatically allows me to rename it. However when Aida64 is running it only allows me to type for a few seconds. It’s like someone is clicking off of the icon to cancel the renaming,

    I use Aida for the sensor panel.

    I have tried several things. I have uninstalled Aida64 and them reinstalled it. I have rolled back to a previous version and the problem is still there.

    That is caused by the always-on-top SensorPanel setting.  When you press a right-click on Windows Desktop, Windows 10 (for whatever reason) take away the always-on-top state of the SensorPanel window.  AIDA64 will then regularly have to check if the always-on-top setting is still enabled for the SensorPanel; and when it's no longer enabled, it will reclaim it.  That's when Windows 10 (again, for some mysterious reason) hides the right-click context menu.  Other than making the check for always-on-top setting less frequent, we couldn't find a workaround for this issue so far :(

  12. 7 hours ago, The Mac said:

    Which of the 3 CPU sensors is the one i should be watching for throttling (cpu, package or diode)?  They all report different temps.

    None of them seem to match what ryzen master reports.  Supposedly thats the one that throttles at 90 degrees.

    Ryzen 5800x....

    Ryzen Master uses averaging and post-processing of thermal readings while AIDA64 reports the direct and immediate temperature readouts.  We believe it makes no sense to process the thermal readings and make them artifically "feel" or look different to the immediate readings.

    AFAIK throttling in the sense we're used to that term on Intel processors is not implemented in AMD processors.  I suppose what you refer to is the way Ryzen processors alter their own CPU core clock frequency depending on the actual thermal state.  If you mean that, then it'd useful to try the AIDA64 System Stability Test and watch the 3 thermal readings along with the current CPU core clock frequency in order to find out which one is the one you're looking for.

    We've designed the Unified tab of the System Stability Test to let you put both thermal readings and clock frequency measurements on a single graph.

  13. 22 hours ago, Ridingmac said:

    Hi,

    I have a corsair H150i  has a CPU cooler. Aida64 show pump rpm and only 2 or the 3 fans. RTSS and HWinfo64 do however have all 3 fans and i would like my sensor panel to display all 3 fans. Is there a way to add either RTSS or HWinfo64 sensor data to Aida64 extreme? If so can someone point me in the right direction to a tutorial/documentation on how to do this?

    Thanks

    Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.


    Thanks,
    Fiery

×
×
  • Create New...