Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    You can ignore the negative values. We however will need to implement stronger workarounds to filter out negative/invalid readings
  2. Fiery
    Note that recent AMD GPUs use a different register access mechanism than previous generation GPUs, so as long as the other software does poll your GPU, a collision may just occur, and it would be different than how it worked on the previous HD7850 card you used to have.
  3. Fiery
    We only have control over the actual USB protocol as long as you're using our Samsung SPF drivers based on LibUSB. If you use Samsung's own mini-monitor driver, then USB transactions are controlled and governed by Samsung's driver.
  4. Fiery
    Do you have any other monitoring or overclocking software running in the background? The issues sounds like a collision between AIDA64 and another software that would poll the video adapter for sensor readings or clock measurement. Regards, Fiery
  5. Fiery
    I'm afraid it's currently not possible to accomplish any of the listed actions with AIDA64. Regards, Fiery
  6. Fiery
    Please upgrade to the latest beta version of AIDA64 Extreme available at: http://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 Thanks, Fiery
  7. Fiery
    You're right, and we've fixed it up in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Thanks, Fiery
  8. Fiery
    Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps about the fan labelling issue. Also, I'm not sure what CPU#1 do you mean. Where can you see that in AIDA64?
  9. Fiery
    Thank you for letting us know about the resolution Regards, Fiery
  10. Fiery
    Uncore power is calculated as package minus IA cores minus DIMM. However, in the second case that results into a negative value which triggers AIDA64 to not display the wrong uncore result. That also indicates that something goes wrong with the power measurement inside your CPU. It's not necesserily a hardware malfunction, more an anomaly that causes AIDA64 to measure the wrong values. Please note that AIDA64 follows Intel's power specifications, so it should work in all cases, but maybe yours is a special one. You may also want to check the measurements using HWMonitor, but I suppose it would yield to the same results... Regards, Fiery
  11. Fiery
    There's already a mechanism in place to filter out such values. Maybe you're not using the latest AIDA64 version of v5.00? If you've got multiple GPUs that support OpenCL, then AIDA64 will use all of them to stress the system.
  12. Fiery
    1) The negative uncore reading is just a temporary reading error, you can simply ignore that value. 2) The System Stability Test window turns quite red when it detects an error. Here's a sample screen shot: 3) To stress the GPU, AIDA64 uses OpenCL code. OpenCL however is a layer that is quite closely tied to the video display driver right now, and so putting a heavy OpenCL stress on the GPU causes the video driver to slow down. That issue will only be solved when GPU manufacturers will finally decouple OpenCL from the video driver. Regards, Fiery
  13. Fiery
    If it's possible, please check it with HD Sentinel too: http://hdsentinel.com Let me know if it reports it as an issue or not.
  14. Fiery
    Thank you for the videos. Quite frankly, we've never seen such issues to happen about external LCD displays, and my first thought was that it must be due to a hardware failure or USB communication issue. Maybe under heavy load the USB interface is not passing the whole JPEG image properly from AIDA64 to the SPF -- but that's just pure speculation.
  15. Fiery
    Only Intel knows what changes about power measurement when you disable Turbo Boost. Even without Turbo Boost the CPU must stay inside the power envelope, so I suppose the power measurement should still work as before.
  16. Fiery
    PhotoWorxx is a test that relies heavily on the memory subsystem and CPU caches. Probably with your overclocking setup, the internal workings of the CPU IMC (memory controller) issues further penalties on memory/cache transactions, and that causes the lower than expected performance.
  17. Fiery
    AIDA64 uses the standard method Intel provides to measure energy consumption of the CPU. It is never intended to be used by 3rd party applications. It was designed for Turbo Boost originally, to make sure the CPU knows how much energy it draws, to make sure it stays between the pre-configured TDP and TDC levels. But just like with the CPU core diode temperature measurement (which was designed to provide protection against overheating, and not to measure absolute temperature), Intel CPU owners demanded various software like AIDA64 to measure and show those readings. Even though in many cases the readings will not reflect anything useful
  18. Fiery
    Which SMART attribute fires the alert? Can you show me a screen shot, or copy-paste the full content of the Storage / SMART page into this topic? Thanks, Fiery
  19. Fiery
    I guess it could have been a temporary mixup between our servers. Hopefully it won't happen again
  20. Fiery
    Due to the overlapping (overlaying) visual elements, making a soft/rounded corner would be quite difficult to achieve, and would make the rendering much slower than now.
  21. Fiery
    Yes, during the test. Most unstable computers freeze under heavy load more frequently than when you leave them at idle. It's up to you. If you do more things during the stress test, it may or may not increase the possibility of finding the issue. If it has a faulty component that causes the freezing, but the component is not dead yet but only working unreliably, then a heavy stress test might cause the dying component to finally give in. But in case you have a perfectly fine computer with all reliable, working, faultless components, then the stress test will not damage the computer.
  22. Fiery
    Where can you see that phenomenon? At which URL? For me it looks and works fine at the AIDA64 Downloads page: http://www.aida64.com/downloads Try to press Ctrl+F5 in your browser, maybe it will help. Regards, Fiery
  23. Fiery
    That formula isn't quite scientific For example, your CPU has multiple clock planes and multiple voltage planes. Not to mention Turbo Boost, throttling and other factors that could ruin the validity of that formula. And also, how do you know the stock dissipation of your CPU? The value Intel publishes as TDP has nothing to do with the stock power draw of the CPU. It is only an informational value for motherboard manufacturers to help them design their motherboard PCB. Also, TDP is an average value, under regular usage scenario. It's not a peak value at all, not measured under heavy load. A 130W TDP CPU could easily draw over 160W, even at stock settings, if you put it under heavy stress (FPU subtest of AIDA64 System Stability Test for example). Of course, in order to measure such relatively accurate values, you would need a lot more than relying on the dissipation that the CPU reports for itself
  24. Fiery
    Modern AMD processors are not capable of measuring accurate core diode temperatures at idle. The measured temperatures only make sense when the CPU is under load. I'm afraid we cannot fix that hardware issue from our software. Regards, Fiery
  25. Fiery
    We tend to re-shuffle our plans as times goes by, since many times a particular feature request goes higher or lower on our list of things to do. When a certain feature gets requested by many users (either here on the forums, or on other forums, or via our tech support), such features get assigned a higher priority. Sadly, due to resource constraints, that also means that we have to shelve or postpone other planned features that seem to be less popular among AIDA64 users. Right now we're quite busy with some major things coming, which are unfortunately not related to either multiple SensorPanels or the alerting facility. In AIDA64, a lot of things would deserve, worth or require improving or revamping, but our resources are quite tight, so we cannot do everything that would interest or even excite us, which is a shame
×
×
  • Create New...