Jump to content
AIDA64 Discussion Forum

Leaderboard


Popular Content

Showing content with the highest reputation since 04/12/17 in all areas

  1. 8 points
    My Custom sensor panel, in the style of Asus' AI suite. It's 800 x 460 as this will be displayed on an in-case LCD-screen. The dials on top are dynamic, as well as the animated fan icons. I'm quite pleased with it. In case anyone's interested, I'll post a picture with the final result!
  2. 3 points
    Although I have made some detailed panels that looked ok to me I have come to realize that because I'm using a 5" LCD as my panel monitor I can't see the sensors because everything is just way too small so I decided to use only what I think would be helpful to my situation this round. Thank you StealthDefender for helping me realize this I would also like to thank Stupe9968 for the killer gauge templates . My new panel (I'm still kinda messin with it) So I just finished my new long awaited rig, specs are as of the following: PC Name - Jedi Assassin Motherboard - Gigabyte GA Z370 Aorus Gaming 7 CPU - Intel i7-8700k @ 5.0 MHz, 1.350 V CPU Cooler - NZXT Kraken X52 RAM - G-Skill Trident Z RGB 16G (2x8) DDR4-3000 MHz 16-18-18-38 CR2 SSD - Samsung M.2 960 EVO 500 MB (Temp) Portable HDD - Seagate Expansion 2 TB GPU - Gigabyte GeForce GTX 1060 Aorus Extreme Gaming 6GB Main Monitor - Viotek GN34C 34" curved 3440 x 1440 100Hz + O.C. Sensor Panel Monitor - 5" LCD attached to case PSU - EVGA SuperNova 850 G2 Gold Case - Phantek Enthoo Pro 2x NZXT 5x USB hub Speakers - Logitech Z623 200watt 2.1 THX Certified LG Blu-Ray DVD/Burner FANS 5x 120mm Thermaltake Riing plus RGB 2x 120mm NZXT 2x 140mm Corsair High Volume Purple LED
  3. 3 points
    Thank you for sharing your creation I copied your idea to create a similar panel for spf-87 if this a problem for you. I'm sorry and I delete this post spf-87h.splcd.axlcd
  4. 3 points
    We wanted to wait to tell final judgement on this issue until we have more info and more input. It's a Windows 10 bug indeed that plagues Windows 10 Insider Build 16273 and 16275, but only the 64-bit editions. It prevents certain software to install and use its otherwise perfectly fine kernel driver. The issue affects several software, not just AIDA64. We're already working on a workaround, but we also expect Microsoft to fix this up soon. I'll post a message into this topic once we have an update.
  5. 3 points
    After buying a new comp i was started with modding. More info - http://nl.hardware.i...irus_59-edition SilverStone Fortress FT03 Black + MIMO 720F Touchscreen USB Monitor (7" 800x480) He was supposed to be better than the old one. Lian Li PC-A05NBF Black + Alphacool LC-Display 240x128 I was looking for software to use the built-in monitor as my old Alphacool LC-Display. And I found AIDA64. The first attempt / v1 The second attempt / v2 - v2.sensorpanel The third attempt / v3. I use now v3 BW 128 v2 - v3.sensorpanel - v3 BW.sensorpanel - v3 BW 128.sensorpanel - v3 BW 128 v2.sensorpanel Possible future - v4.sensorpanel I can't upload anymore, the limit is reached Now I'm waiting for the appearance of the possibility to monitor hard drives and wireless signal strength.
  6. 2 points
    There must be something wrong about the OpenCL software stack. Try to uninstall and reinstall ForceWare.
  7. 2 points
    Thank you. Here's the fix for your motherboard as well as other motherboards that are affected by the same anomaly. https://www.aida64.com/downloads/latesta64xebeta
  8. 2 points
    New Text Version, uses on Desktop > text_v2.sensorpanel Adapted to 5 Inch Dispaly with 800x480 Pixels > PiDisplay.sensorpanel PiDisplay.sensorpanel text_v2.sensorpanel
  9. 2 points
    Here is how it's coming along ... the gauges will be in green (still have to make them) check your email and get back to me.... also the background file is in the zip file below. I am doing this for free so please keep my "branding" in the bottom lower right of the panel Red - MSI - background 2 test.zip
  10. 2 points
    Ok cool I'll see what I can come up with for ya we can fine tune it later on ...
  11. 2 points
    You're right, 16278 carries on the issue. We need to release one more AIDA64 hotfix to get around it again. We'll do that tomorrow or worse case Friday. I'll post a message into this topic once the new AIDA64 beta build is available for download.
  12. 2 points
    new set of gauges , If some like it, leave coment and i sent you on you email. I have for LCD and sensor panel in ( Large and medium sizes ) in png
  13. 2 points
    Some new gauges. LOAD and IDILE. If some like it, leave coment and i sent you on you email. I have for LCD and sensor panel in ( Large and medium sizes ) in png
  14. 2 points
    This is a real layout GA-Z77X-UD5H. Panel size 1000x792 GA-Z77X-UD5H.2015-11-20.sensorpanel I have layered .psd file.
  15. 2 points
    Thanks for the quick fix. All working fine now. Here is my custom panel. System Idle Example System Load Example Desktop Example If any one wants to use it you can download it from my blog - http://blog.psine.com/sensorpanel.html
  16. 1 point
    I'm using a 7" MiMo USB-Display with a resolution of 800x480 for my sensorpanel. I modified the medium standard gauges a little bit, hope you enjoy it. Custom_Gauge.zip
  17. 1 point
    State #0 should display the state where the range is zero, so it shows for example 0 RPM or 0 degrees Celsius. State #15 should display the state where the range is at its maximum. So it shows like 5000 RPM (if your cooler can spin up to 5000 RPM) or 100 degrees Celsius (if you deem your thermal readings will never exceed that value). All the other states should show an intermediate step. Since State #0 = 0%, and State #15 = 100%, for example State #5 should show the range as if it was 33%.
  18. 1 point
    It is detected using various detection methods and built-in hardware databases. It's not possible to edit that string.
  19. 1 point
    Hi, Aida64 now provides support for the Odospace Remote Panel app: Reuse your old android device to display sensor values of a Windows PC. A WiFi connection is not (!) required, Remote Panel works even when the device is connected to the PC via USB only. However, an SDK for Remote Panel is provided also. Sensor values are provided by the industry-leading system information tool Aida64 which must be purchased separately. Please note that Remote Panel is not affiliated with Aida64 or FinalWire in any way shape or form and no support can be provided by the Aida64 team for this app. Requirements - Aida64 version 5.20.3414 or heigher must be installed on the Windows PC. - Remote Panel (for Windows) version 1.16 must be installed and running, it can be downloaded with the following link http://apps.odospace.com/RemotePanelSetup.exe - Microsoft .Net framework 4.5 must be installed on the Windows PC. This will be done during the installation of Remote Panel (for Windows). - The android device vendor's drivers must be installed on the Windows PC. - USB debugging must be enabled on the android device. This is described in detail here. Enable Aiada64 plugIn - After installation of Remote Panel (for Windows) Aida64 must be restarted. - Within Aida64 open the preferences page, navigate to LCD and enable "Odospace". Add items within the LCD items page. Settings - A long press within the view opens the settings dialog. Troubleshooting - In general the settings dialog of Remote Panel (for Windows) can be opened from the popup menu of its tray icon. - Remote Panel (for Windows) uses port 38000 and 38001 for local communication, if you experience problems because another PC program is using one of this ports, change the port number within the Remote Panel (for Windows) settings dialog and within the Aida64 Odospace LCD plugin. - Remote Panel (for Windows) uses the Android Debug Bridge (adb.exe) for communication. If you experience problems with other Android synchronization programs, try to use another adb.exe file - it can be changed within the settings dialog of Remote Panel (for Windows). - On default, Remote Panel (for Windows) checks every 30 seconds for new devices, decrease this value within the settings for faster device recognition, increase this value for less CPU usage. Alternative usage - If an additional PC should send its sensor values to the android device, set the IP address within the Aida64 Odospace LCD plugin to the address of the PC where the android device is connected. For every PC specify a different panel position parameter. Remote Panel (for Windows) must be installed on every PC, however the Remote Panel (for Windows) executable must only be started on the PC where the Android device is connected. - Remote Panel can be used within a WiFi network also, in such case set the IP address within the Aida64 Odospace PlugIn to the device's address. The port must be set to 38000. The Remote Panel (for Windows) executable can be stopped in this case. Advanced topics - To automatically start Remote Panel you can use AutoStart. - To power off the device on PC shut down you can use AutomateIt Pro - use the USB disconnect trigger. - If the device battery discharge even connected via USB, try to set the CPU speed to a lower level. For example you can use Tickster MOD. - To power on the device on PC startup the device firmware must be modified (follow this AT YOUR OWN RISK, tested with Cyanogenmod 10.2 on LG P760/P880 and may not work with all devices): General 1. Download the device firmware - it can be the original or custom ROM. 2. Use Boot/Recovery Repacker to extract the boot.img file of the downloaded ROM. 3. Within the file init.rc, in the section beginning with "on charger" replace the string "class_start charger" with "trigger boot" or "trigger late-init". Ensure that your editor writes the file in UNIX format. 4. Use the repacker to compress the boot.img file. 5. Apply the new firmware. Nexus 7 (2012) 1. Boot in fastboot mode 2. Issue the following command within a command prompt: "fastboot oem off-mode-charge 0" Version 1.14 - Now sensor data of multiple PCs can be displayed on one android device - The android device can be connected to any PC (not only to the PC where Aida64 is running) - Requires Aida version 5.20.3414 or higher and Remote Panel (for Windows) version 1.14a Version 1.15 - Fullscreen mode (long press for settings) - RemotePanel (for windows) version 1.15: Verbose mode for better problem handling, fixes a rare ADB hang when multiple PCs are connected to one android device. Version 1.16 available - New option added: Keep screen on (long press for settings) Many thanks to the Aida64 team for the great support! Best regards odospace
  20. 1 point
  21. 1 point
    Thank you, but that dump doesn't include EC registers. Please enable status bar in AIDA64 / main menu / View, and on the status bar (which will appear on the bottom of the AIDA64 main window) do a right-click --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.
  22. 1 point
    Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://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.
  23. 1 point
    HDDs have different measurement units for the SMART attribute 09, so it's not possible to implement a generic solution that would cover all HDDs out there. Do you think your HDD measures power-on time in hours? In other words, do you think 15986 hours which is 666 days would be correct for your HDD? If you can let us know what the measurement unit for your particular HDD is, we can add that model to the SMART module of AIDA64 in order to show you the remaining drive lifetime information. If you have multiple HDDs, and you can send measurement unit information for all of them, that would be even more cool In such case don't forget to specify the full model ID of your HDD, like for this case Hitachi HDT721010SLA360. Thanks, Fiery
  24. 1 point
    We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems. The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component. Most likely that component is used for GPU profiling. And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable. We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted. Here's the new AIDA64 beta build that includes the workaround: https://www.aida64.com/downloads/latesta64xebeta
  25. 1 point
    We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems. The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component. Most likely that component is used for GPU profiling. And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable. We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted. Here's the new AIDA64 beta build that includes the workaround: https://www.aida64.com/downloads/latesta64xebeta
  26. 1 point
    nice gauge! Is better if color of indicator is red or orange... what kind of fonts are you using?
  27. 1 point
    As long as Mad Catz offers a similar SDK for RAT9 that it has for Strike7, we can implement that feature in AIDA64. But I haven't seen any such SDK offered by Mad Catz...
  28. 1 point
    Your notebook features an Intel Sandy Bridge class iGPU that doesn't support OpenCL. AIDA64 GPU stress test and GPGPU benchmarks require a GPU that supports OpenCL.
  29. 1 point
    Hey man this is just an idea of what I have so far , I need a little more info from you like how many fans/water pumps are you going to monitor and just what you want to monitor in general so I have a little more to go on......I assumed red in color cause MSI is usually red....
  30. 1 point
    Hello everyone ... I've been working on designing eye candy for the sensor panel backgrounds and came up with this idea for those of you who want to add a lil bling to your panel. Please tell me what you think ...The electrical sphere in this background moves, to see it in action click this link https://www.dropbox.com/s/4hs9b6nzw2bcg9h/2018-01-11_00-39-51.mp4?dl=0
  31. 1 point
    Please upgrade to the latest beta version of AIDA64 Extreme available at: 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.
  32. 1 point
    Thank you. It seems to be due to a motherboard BIOS bug about handling the MMIO (memory-mapped I/O) portion of the motherboard sensor chip (IT8655E). Please report the issue to Asus, I'm sure they will know how to fix it in an upcoming BIOS update for your motherboard.
  33. 1 point
    It's hard to provide proper feedback on that. On the one hand, 45-50% throttling is quite a lot, so I'd take it as alarming. However, since it's a brand new notebook, there shouldn't be any cooling issue due to hardware failure or dust clogging up the exhaust ports, etc. So it may just be normal the way it is. It may be worth checking what happens if you restart your computer, open AIDA64, open System Stability Test, but don't start any test there. Just let it sit and watch as the throttling is monitored. Now, start a game, play for 30 minutes, and check back to the System Stability Test whether it indicates that the computer was overheating without running a stress test but while playing a game. If throttling exceeds 25% while playing a game, I'd take it back to the shop and inquire the sales persons about it.
  34. 1 point
    It could mean that the memory frequency is too high, the memory timings are too tight, or the memory modules aren't compatible with your motherboard. Try to run other memory tests as well, to confirm that the memory modules aren't working properly across different tests.
  35. 1 point
    Thank you for your reply ... after i upgraded the driver ... the issue is fixed ... Best regard ... wish you having a nice day.
  36. 1 point
    The video driver reset takes a second or two, and after it is done everything should go back to normal. Except for the GPU subtest of the AIDA64 System Stability Test which will be stopped after the video driver reset. So in case a permanent blackscreen is exhibited, it may be due to a video driver reset issue in the first place, but then the video driver cannot recover due to -- in most cases -- a hardware stability issue. In other words: if you cannot get the display output working after the video driver reset, it's a hardware malfunction. Such malfunction can be due to a number of reasons, including excessive overclocking (and/or overvoltage), overheating, video memory stability issues (or overheating), PCI Express communication breakdown, etc.
  37. 1 point
    The mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please let us know how it works on your system.
  38. 1 point
    IMHO you need to contact MSI (the maker of your motherboard) to find out more about the voltage issue as well as for the purpose and meaning of the red LED.
  39. 1 point
    Maybe these URLs would help? They always point to the latest stable and beta build, respectively. https://www.aida64.com/downloads/latesta64xe https://www.aida64.com/downloads/latesta64xebeta
  40. 1 point
    We've implemented preliminary EVGA iCX sensor support in the latest beta version of AIDA64 Extreme available at: 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. Note that the iCX related readings will only appear on the Computer / Sensor page at this time. As the new sensor module gets more mature, we'll add the readings to the LCD, SensorPanel, OSD Panel (etc) modules as well. Please note that currently it supports a single video card model: EVGA GTX 1080 Ti FTW3 iCX. If it doesn't work on your video card, or in case you have a different video card that features iCX sensor, please submit a fresh nVIDIA SMBus Dump.
  41. 1 point
    We've checked, and unfortunately we haven't found any classic ways of obtaining those values from the video card iCX must use a custom communication protocol, but we have no idea how it works and how to handle it.
  42. 1 point
    We do have plans, but not for the near future. We're watching the market, the evolution of the Windows PC ecosystem, and we'll make our move to 64-bit once it will become necessary or mandatory. The 32-bit main binary is there because that's the best compromise. Having a 64-bit main binary wouldn't be a major benefit, but on the other hand it would raise a lot of issues. One such issue would be a considerably bigger distribution package, more than twice the size of the current ZIP and EXE package. That's because when you have a 64-bit main binary, you need to have all DLLs compiled to 64-bit as well -- while retaining the existing 32-bit DLLs for compatibility reasons. Another issue is that many interfaces and APIs that AIDA64 relies on have no 64-bit support. And so when you want to use such an interface/API from AIDA64, it works now, but it would stop working if the user switched to the 64-bit main binary. As for the name itself: it's there to separate the software from its predecessors, namely AIDA32 and AIDA16. While it's true that the main binary is still 32-bit, but the critical parts (modules) that truly benefit from porting 64-bit are already available in both 64-bit and 32-bit flavours. Those modules are the benchmarks and the stress test (AIDA64 System Stability Test).
  43. 1 point
    It seems when vram usage passes 4GB, the aida64 values for the used GPU begin showing very low numbers. This i what i see in Aida64, where GPU-Z and Nvidia Inspector show >4.8GB used. Utilization GPU 98% Memory Controller 46% Video Engine 0% Bus Interface 5% Dedicated Memory 609 MB Dynamic Memory 699 MB DirectX Video info shows Direct3D Device Properties Total / Free Video Memory 8192 MB / 3385 MB
  44. 1 point
    Hi, i also downloaded this Beta Version you Suggested but it says that i dont have a licence for that version. My current Version 5.80.4000 doesn't support my 1080ti. Any help would be appreciated. Ah ok...i see now, support for my AIDA64 Ended on 11.12.2016 :(... Regards Simon
  45. 1 point
    Thank you, I'm glad things are going in the right direction
  46. 1 point
    Hi, im big fan of Fallout series so i made it pipboy like.
  47. 1 point
    I know I'm not the OP but I'll give some feedback anyway. This works fine on my Toshiba Satellite P50t - the Nvidia GPU is always detected now, whether I have a 3D application open or not.
  48. 1 point
    Thank you. Does the HD8750M show up on the following pages in AIDA64? - Display / PCI/AGP Video - Display / Windows Video - Devices / Windows Devices
  49. 1 point
    Here is the updated SensorPanel sample to the AIDA64 v3.20 release to show you the new area graph and histogram in action. Please note that if you want to use this graph as is, you need a CPU that is capable of measuring and reporting its power draw. 320release_sample.sensorpanel
  50. 1 point
    I often undertake IT audits for clients. I'm looking to automate this task and my research led me to Aida64. Is this product able to allow me to install Aida64 Business on a standalone client PC, and have the findings written to an Access database (perhaps stored on a USB drive)? I've installed it as a trial on my PC, and modified the DB preferences to point at the DB - Access.mdb file, but no data is written. Is there something I'm missing in the process or abilities of this software?
×
×
  • Create New...