Jump to content

Fiery

Administrators
  • Posts

    11334
  • Joined

  • Last visited

  • Days Won

    476

Everything posted by Fiery

  1. Strike7 API has quite a few weird issues. Sometimes implementing a workaround fixes it, but the major problem lies in the SDK that Mad Catz designed. Please report the issue to them, and we'll also ping them to find out how can we work together to fix this issue, and also the touch-related other problems. Thanks, Fiery
  2. Hard to diagnose such issues remotely My best guess would be that the low-level hardware detection module of AIDA64 collides with another diagnostics, overclocking, tweaking, or monitoring software. Or, a wild guess: maybe your security software kills the AIDA64 process due to it making some "funny" things like talking directly to the hardware.
  3. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3242kwn2zf6gyqzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. That should fix the fan RPM calculation issues. Note that the sensor chip of your motherboard is only capable of measuring no more than 3 fans. Hence, the 4th fan (NB fan) is not measured, but only powered.
  4. We've added graphs and gauges to both the Logitech Arx and RemoteSensor LCD module in the latest beta release of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta Note that the new gauges featured in these modules are called arc gauges. They do not have the same look & feel as the classic AIDA64 gauges (featured in the SensorPanel), but they offer much more flexibility.
  5. It looks great We've added graphs and gauges to both the Logitech Arx and Web Server LCD module in the latest beta release of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta Note that the new gauges featured in these modules are called arc gauges. They do not have the same look & feel as the classic AIDA64 gauges (featured in the SensorPanel), but they offer much more flexibility.
  6. I've just sent you a private message about this Regards, Fiery
  7. Our contact at Logitech says that they will look into it.
  8. Most notebooks can only control fan speeds, based on temperature readouts, but monitoring the current fan speed RPM is not supported. Are you sure your notebook is capable of measuring its fan speed(s)?
  9. Thank you. I've sent you a private message about this.
  10. Thank you. That indeed looks quite odd. What update frequency did you select for the OSD Panel? When the OSD Panel gets "confused", do the date and time items (at the bottom) drop out?
  11. We've recently revamped the OSD Panel and SensorPanel window positioning scheme, so make sure to upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3237vy9hqdrx7czip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. BTW, in the Registry you can set SensorPanelPosX and SensorPanelPosY to change the position of the SensorPanel.
  12. We haven't got any programming information on those devices. We've sent a request to Aquacomputer, hopefully they would help us out. I'll post updates on this issue into this topic.
  13. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero Dump. Copy-paste the full results into this topic. Thanks, Fiery
  14. Thank you for the test runs. It means one of the MSR register readouts cause the DPC latency spikes on your system. On your processor AIDA64 requires a lot of MSR readouts to detect/measure various values, like CPU multiplier, CPU BCLK (FSB), NB (uncore) clock, memory clock, CPU power measurement, etc. Not easy to get rid of the MSR readouts, you would lose too many vital information then
  15. Thank you. Since the Memory Timings and Memory Speed drop out, the issue may be related to your Haswell-E CPU. Is your CPU overclocked or otherwise specially tweaked? Can you see the drop outs only when the CPU is idle, or only when it is under heavy load? Can you see the drop out of the Memory Clock or DRAM:FSB Ratio items as well? BTW, we've tried to reproduce the issue on our own Core i7-5820K based test system, but without a luck. Maybe it's because our test system is not overclocked or tweaked from default settings...
  16. I've forwarded your request to them. However, please note that providing backwards compatibility in Android could be quite complicated and burn a lot of resources. Most Android developers focus on the latest & greatest few iterations of Android, and only provide backwards compatibility if it can be accomplished without too much overhead.
  17. Are you running the latest version of Logitech Gaming Software? (v8.57.145) If yes, then please report the issue to Logitech. As for graphs and gauges, as I wrote in my previous post, they are under development. We're planning to roll out gauges next week, and graphs a bit later on.
  18. Arx only supports a single set of applets, but it supports showing the same applets on multiple devices. So the layout you make with AIDA64 can be viewed on a phone and a tablet at the same time, but it has to be a single layout. You can however use e.g. Arx for your phone and the AIDA64 RemoteSensor for your tablet, or vice versa
  19. Thank you for the feedback. It's a bit odd that something was using port 8080, but then again, so many background processes and services are running under Windows these days...
  20. 1) What kind of items keep dropping out and then appear again? CPU Clock, CPU Multiplier? Or one of the temperatures? 2) Do you have any other hardware monitoring modules enabled, besides the OSD Panel? 3) Do you use Correction? (main menu / File / Preferences / Hardware Monitoring / Correction) Thanks, Fiery
  21. Sounds like it may be an issue related to your local (software) firewall, like Windows Firewall. In case your firewall software fails to pop up a warning message about AIDA64 trying to use the configured TCP/IP port for network traffic, you will need to add it manually to your firewall settings.
  22. First, try it with a different browser, not IE if possible If it doesn't help, then try to use a different TCP/IP port, like 8080.
  23. Can you please check it with DPC Latency Checker? It would be important to confirm whether this is caused by DPC spikes. Also, in a situation when the audio drops occur, please try to right-click on the bottom status bar of AIDA64 main window --> HWMon Modules, and disable first the GPU module. Then check if it fixes the issues. If not, then one by one try to disable the Motherboard module, and then the HDD module, and then the rest of the modules. Let me know how it goes. Thanks, Fiery
  24. No, tweaking system settings and overclocking using XTU wouldn't cause an issue with AIDA64. Have you tried the latest AIDA64 beta? http://www.aida64.com/downloads/aida64extremebuild3237vy9hqdrx7czip Will it throw the same hardware errors? BTW, generally speaking about the AIDA64 System Stability Test. Please note that it puts a more demanding workload on the PC than most other stress testing solutions. We've put great efforts in filling up all the processing pipelines, to keep all components of the CPU, memory and GPU busy all the time. So it's no surprise if issues about a certain "too optimistic" overclock setting is only revealed using the AIDA64 System Stability Test Regards, Fiery
  25. They both use the same HTML rendering engine, so their output should be similar. The AIDA64 Web Server solution, more specifically mobile web browsers in general have the unfortunate limitation about power management. While you're viewing AIDA64 sensor values in a mobile web browser, the phone or tablet will go to sleep after a while. Logitech Arx has no such limitation: it will stay active forever and prevent the mobile device from going to sleep.
×
×
  • Create New...