Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12004

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    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
  2. Fiery
    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...
  3. Fiery
    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.
  4. Fiery
    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.
  5. Fiery
    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
  6. Fiery
    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...
  7. Fiery
    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
  8. Fiery
    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.
  9. Fiery
    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.
  10. Fiery
    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
  11. Fiery
    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
  12. Fiery
    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.
  13. Fiery
    We've just rolled out the first public beta of the new mobile device LCD monitoring feature. We've come up with 2 different solutions: http://forums.aida64.com/topic/2610-logitech-arx-control-lcd-for-smartphones-and-tablets/ http://forums.aida64.com/topic/2636-aida64-web-server-lcd-for-smartphones-and-tablets/
  14. Fiery
    We've fixed the issues in 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 how it works
  15. Fiery
    Along with the Logitech Arx integration, we've also come up with a new LCD module that basically acts as a web server. You can use your main computer to run AIDA64 on it and maintain its built-in web server, and you can use your other computers or mobile devices to monitor your main computer's status remotely, using nothing but a web browser. You can activate it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / RemoteSensor. Once you activated it, you can enter the IP address in virtually any web browsers to connect to the RemoteSensor. You can check the primary IP address of your computer on the Computer / Summary page in AIDA64. If it is e.g. 192.168.1.123, then enter the following in the address bar of your web browser: http://192.168.1.123 Or, in case you use a different TCP/IP port than the default http port of 80, then enter the address like this: http://192.168.1.123:8080 (if you use a TCP/IP port of 8080) Or, in case you try to use a web browser on the same computer where AIDA64 is running, you can simply use "localhost" instead of the IP address, like this: http://localhost Once you did that, you should see the AIDA64 splash screen in your web browser. It will provide you with information on the resolution that you need to use to get the most out of the LCD layout designer. On iOS devices the default setting should be close to the actual value to use, while on Android and other devices it may not match at all, so you need to change both the width and height. Please note that the Preview Resolution usually will not match the native screen resolution of your device. It's not a problem at all, and that discrepancy is due to the way web browsers manage the pixels of your screen, so don't be surprised that e.g. an iPhone 5 would report a Preview Resolution of 980 x 1360 pixels After the Preview Resolution is updated on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD page, you can use the same LCD layout designer that you would use for other LCD devices or the SensorPanel. Known issues and limitations: 1) Graphs and gauges are not implemented yet. We're planning to add them in the next few weeks. 2) RemoteSensor uses HTML5 SSE (Server-Sent Events) to refresh the web page, without having to reload it all the time. SSE is supported by almost all major web browsers, including Android Browser, BlackBerry 10 Browser, Chrome, FireFox, Opera, and Safari. However, it is sadly not yet supported by Internet Explorer. AIDA64 implements a trick to get around that limitation, but it sometimes will result in a mixup of the browser. If you notice that after changing the LCD layout in the AIDA64 Preferences, a strange log replaces the LCD layout in your browser, just refresh the web page. Hopefully Microsoft will finally implement SSE support in Internet Explorer 12 3) In order to prevent your mobile device from going to sleep while having the web browser open, you may need to install special apps on your mobile device. RemoteSensor has absolutely no control over the power management behavior of your mobile device. In case this is a deal breaker for you, and you've got a Logitech Gaming hardware, consider using Logitech Arx instead of the RemoteSensor. You can try the RemoteSensor in the following new AIDA64 beta update: http://www.aida64.com/downloads/latesta64xebeta Please let us know how it works on your mobile devices Thanks, Fiery
  16. Fiery
    In the past few weeks we've been working closely with Logitech developers to make this happen. Super nice guys, great professionals working there BTW. So, here's the first AIDA64 beta to implement Logitech Arx smartphone and tablet LCD integration: http://www.aida64.com/downloads/latesta64xebeta You can activate it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Logitech Arx. Once you activated it, the AIDA64 applet will appear in the Arx app's bottom row of icons. Tap on the AIDA64 icon, and the AIDA64 splash screen should be displayed on your mobile device. It will provide you with information on the resolution that you need to use to get the most out of the LCD layout designer. On iOS devices the default setting should be close to the actual value to use, while on Android it may not match at all, so you need to change both the width and height. Please note that the Preview Resolution usually will not match the native screen resolution of your device. It's not a problem at all, and that discrepancy is due to the Arx app using an embedded web view. Hence, AIDA64 and other Arx-ready software will need to render a HTML page, and the Arx framework will display that on your mobile device. And the embedded web view has its own ideas on how to manage the pixels of your screen, so don't be surprised that e.g. an iPhone 5 would report a Preview Resolution of 980 x 1140 pixels After the Preview Resolution is updated on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD page, you can use the same LCD layout designer that you would use for other LCD devices or the SensorPanel. On phone devices you can use a wider and/or taller LCD Preview Resolution than what your phone supports. So effectively you can have a much larger space to drop sensor readings on, and use scrolling to move around the big virtual "desktop" on your phone. Known issues and limitations: 1) Graphs and gauges are not implemented yet. We're planning to add them in the next few weeks. 2) The current Android Arx app (Version 172) may not display the AIDA64 applet properly, but instead throw an error message that is almost impossible to read, due to an unfortunate choice of colour scheme by the Arx app. If that happens, just kill the Android app, and start it again. Logitech is already working on a fix. 3) The current Android Arx app (Version 172) will not update the AIDA64 applet when the LCD layout is changed in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items. After applying a change on the layout, you need to switch to another Arx applet and then switch back to the AIDA64 applet. Logitech is already working on a fix. 4) Both the iOS and Android Arx app supports screen orientation change only on tablet devices, and page scrolling only on phone devices. We've notified Logitech about this pecularity, but we're not sure in which way would they remedy this. BTW, if you've got no Logitech Gaming hardware and so you cannot use Arx, check out the new RemoteSensor feature: http://forums.aida64.com/topic/2636-aida64-web-server-lcd-for-smartphones-and-tablets/ Please let us know how it works on your mobile devices Thanks, Fiery
  17. Fiery
    Thank you for the bug report. Both issues will be fixed in the next AIDA64 beta update due in a few days from now. I'll drop a message into this topic once the new beta is available for download. Regards, Fiery
  18. Fiery
    ISA in this case refers to the ISA Sensor Dump of AIDA64.
  19. Fiery
    Thank you for the dump. I'm afraid the missing values are only available via EC indexed register access. And performing such register access is quite dangerous, it could easily collide with Asus AI Suite or the BIOS, and would cause a BSoD or system lockup. So it's best not to risk that. If it's possible, try connecting the Extension Fans to other fan headers.
  20. Fiery
    I'm not sure how big are you looking for. LCDInfo makes gorgeous 4.3-inch colour TFT with very fast update rate: http://www.lcdinfo.com/products/usbd480-wq43.html The only problem is, that's an OEM device, so it has no frame or stand. You can integrate it into your case side or front though, and it would make a terrific addition to your existing chassis. If you're looking for even bigger external displays, then your only option is either going for a DisplayLink USB connected LCD monitor, e.g. Mimo 720S ... http://www.mimomonitors.com/products/mimo-720-s ... or Samsung SPF digital photo frames: http://forums.aida64.com/topic/2424-new-lcd-device-support-samsung-spf-digital-photo-frames/ DisplayLink monitors have a huge advantage that they can be used as a classic secondary display under Windows, so you can display any windows, and use any software on them. Samsung SPF DPFs on the other hand can be picked up at reasonable prices at eBay for example. If you go for Samsung SPF, then make sure to use our own drivers for it. Regards, Fiery
  21. Fiery
    Few years ago PNG completely replaced GIF as a still image format, and AIDA64 already supports PNG as well as JPEG. As for animated images/clips, they cannot be put on the SensorPanel or LCD anyway, so it's not a matter of the media format. Regards, Fiery
  22. Fiery
    That's normal for modern AMD processors. Their core diode only provides a meaningful readout when the processor is under load. Regards, Fiery
  23. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic. Thanks, Fiery
  24. Fiery
    The only thing that may cause such issues is when HDD/SSD drives report an incorrect (or unstable) temperature readout. When a certain temperature readout crosses the predefined limits, like they report 1000 Celsius, AIDA64 will remove the readout from the OSD Panel. What sort of SATA controller do you have your drives connected to? Do you use a RAID array? What kind of Windows do you have installed? Regards, Fiery
  25. Fiery
    It should be the CPU VRM voltage. But it's only available on Haswell CPUs. Regards, Fiery
×
×
  • Create New...