Jump to content
AIDA64 Discussion Forum

Leaderboard


Popular Content

Showing content with the highest reputation since 10/07/10 in Posts

  1. 4 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
  2. 4 points
    Hi guys I'm new here on forum, so... My name's Pav, i'm from Navan (Ireland).Today i've created my first sensor panel MIDNIGHT(based little bit on sunj's work. Thanx man ). Hope you like it. preview: And on my desktop: MiIDNIGHT.sensorpanel
  3. 2 points
    Ok cool I'll see what I can come up with for ya we can fine tune it later on ...
  4. 2 points
    Got a bit carried away with XCOM2 and hunting down a (possible) memory issue...
  5. 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.
  6. 2 points
    This is the sample SensorPanel used in AIDA64 2.50 what's new page. This utilizes the new gauges and graphs. 250release_sample.sensorpanel
  7. 2 points
    THX, it's a great Feature ;-) My Actual LCARS / BW setting, 1024x600 to Display on a GalaxyTab 7" via iDisplay:
  8. 1 point
    Make sure to upgrade to the latest beta version of AIDA64 Engineer available at: https://www.aida64.com/downloads/latesta64eebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.
  9. 1 point
    I was just asking because we've revamped the SMTP module to unlock support for Yandex and other mail services in AIDA64 v5.97. So you need that version or an even newer one to have proper SMTP support with SSL/STARTTLS.
  10. 1 point
    Thank you for the info. We'll remove the VRM temperature reading in the next AIDA64 beta update.
  11. 1 point
    Please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.
  12. 1 point
    Actually, the AIDA64 app doesn't need to be unconfined (even if it has some special permission) so you can upload it to the OpenStore without requiring a manual review, so without the need to publish the source code (but if you changed idea and want to publish, it's welcome ) and choosing a proprietary license (as said by @mateo_salta) Thanks
  13. 1 point
    Thank you for the data. We'll add the 2 missing temperature readings in the next AIDA64 update that is rolling out tomorrow. As for the Adaptec issue, have you tried to enable Adaptec RAID support in AIDA64 / main menu / File / Preferences / Stability? Make sure to restart AIDA64 after altering that option.
  14. 1 point
    When that happened to me (the lcd is black or the sensor panel i only half to view....) it was my screen resolution for my main screen that wasn't set to the game specs.
  15. 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 if it helps.
  16. 1 point
    Go to AIDA64 / main menu / File / Preferences / Stability, and enable both the following options: Embedded Controller (EC) support Embedded Controller (EC) bank switching After altering those options, make sure to restart AIDA64 to apply the changes.
  17. 1 point
    I've sent you a private message about this issue.
  18. 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.
  19. 1 point
    It's due to the difference in motherboard and CPU as well.
  20. 1 point
    It's not supported yet. We've just ordered a unit, and we'll implement support for the Commander Pro protocol as soon as it arrives. I'll let you know in this topic once a new AIDA64 beta -- with the protocol implemented -- becomes available for download. It shouldn't take more than 2 weeks approx.
  21. 1 point
    Please note that in order to detect the missing details, the camera ID information had to be previously encoded into the Android profile of the device. When the manufacturer of the devcie (in your case Sony) didn't encode the info there, then sysinfo apps cannot read or detect it.
  22. 1 point
    If the drive has a very smart controller that desperately tries to hide the fact that the capacity is less than the advertised value, then for a while the Random Write + Verify test may not report any issues. Especially when the performance is that freakishly low With such an underperforming drive you would have to let the Random Write + Verify test run for at least 2 days to draw any meaningful conclusion. Good old fraudulent pendrives which perform adequatly (like 20-30 MB/s) are usually caught by the test in a matter of minutes, sometimes few seconds only. But it's always best to let the Linear Write + Verify test to complete to 100%, since that's the only sure way of knowing that the drive can be filled 100% with data, and all data is fully retained (stored) by the drive.
  23. 1 point
    Thank you. 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
  24. 1 point
    Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know if it helps
  25. 1 point
    Thank you. The lack of proper sensor readings is due to the fact that AIDA64 is unable to use its kernel driver. That could be because the kernel driver file (KERNELD.X64 or KERNELD.X86) is missing, or your Windows user has no administrator privileges, or a Windows prevents to elevate the security privileges of AIDA64.
  26. 1 point
    Thank you! We don't have any presets available, but you can use some of the SensorPanel layouts other users posted to: https://forums.aida64.com/topic/667-share-your-sensorpanel/
  27. 1 point
    I'd start with: 1) Update motherboard BIOS to the latest one 2) Set memory module timings to a more relaxed setting, dictated by the classic SPD block rather than the XMP (Extreme Memory Profile). If that still doesn't help, then I'd try it with 2T Command Rate (tCR or tCMD) setting as well. If none of those help, it could still be a faulty memory module, a dying motherboard or a faulty PSU. Not easy to diagnose such issues though If you have a chance to borrow a reliable PSU, it would worth checking that too. Regards, Fiery
  28. 1 point
    Then I suppose the issue is that AIDA64 sets the fan speed to its default value (or the one you configured as Asetek fan speed), but then Corsair Link software will override that when it is running in the background. That's a collision that we cannot avoid on our end, and is caused by the improper USB API that some Asetek-6 based water coolers use. The problem is that you cannot detect water cooler temperature and fan RPM reading without altering the fan duty cycle (%) setting So you have to send a duty cycle value in order to get sensor readings back.
  29. 1 point
    Please don't mix PCH and PCH Diode temperatures. The first one comes from the onboard sensor chip, if it supports that readout. The latter comes from the PCH (chipset) itself, if it supports it. The latter doesn't need motherboard-specific support, so we cannot add it. Your PCH either supports the readout or not, and your BIOS either configures the PCH thermal controller properly or not.
  30. 1 point
    That's because AIDA64 currently supports "only" up to 14 misc fans We'll expand that to 20 fans in the next AIDA64 beta update
  31. 1 point
    I don't think so. What could happen is a faster battery discharge when you keep AIDA64 running in the background to monitor your notebook. Monitoring hardware uses a few percentage of CPU load, and that causes higher overall system power draw than without it.
  32. 1 point
    The issue will be fixed in the next AIDA64 beta update due in a few days from now Regards, Fiery
  33. 1 point
    That only means the Strike7 SDK causes a crash in its DLL, and that pulls AIDA64 main process down with itself I'd be happy to help you out, but at this point we both are at the mercy of Mad Catz. If they could try this out and find the issue in their SDK and fix it up, that would of course fix this whole thing. Or, if they can find an incompatibility between their SDK and AIDA64, then we would be happy to work with them to resolve it. The main problem is that we cannot reproduce the issue on our own Strike7 keyboard. If we could do that, things would probably be a bit easier. Please try to put a bit more pressure on Mad Catz, as a customer who's having issues using their product.
  34. 1 point
    Hello With this forum, I can't copy/paste the text when I post a message. And I can't "add to post" file in a message How tio fix it ? Thanks
  35. 1 point
    Thank you, we've fixed this issue 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. Regards, Fiery
  36. 1 point
    It depends on the actual protocol your LCD uses. In theory, AIDA64 is well prepared to support virtually any LCD devices that can display a bitmap image directly. It already supports over 50 different LCD protocols, and a wide range of connection options, including USB, WiFi, LPT (parallel), COM (serial). It would be important for us to understand what exactly needs to be done to push a bitmap image into your LCD screen, so please share any technical detail you've got on that. If it uses a proprietary protocol that you wouldn't wanna share with others, then please drop me a private message with your email address, and we'll continue discussing this in email. Thanks, Fiery
  37. 1 point
    It is Logitech's DLL, part of the Logitech G-Series driver package called LgLcdApi.dll. Try to reinstall the drivers, it should help.
  38. 1 point
    Th well e manufacturer makes the choice at manner a the maximum rate of manner a instinctively
  39. 1 point
    Nice 1st post, thank you And you've got quite a fleet of PCs
  40. 1 point
    For Italian users, we have a guide in Italian on how you can create a fully customized SensorPanel in AIDA64 Extreme Edition. (FYI: this is a pre-3.20 post so it does not cover area graphs and histograms, which have just been introduced, but these can be configured the same way as a line graph.) Come creare e personalizzare il SensorPanel di AIDA64? Hope it helps!
  41. 1 point
    You can try reinstalling Windows, updating drivers, updating BIOS, but I'm not sure if those would help at all in your case. It worth a try though.
  42. 1 point
    Thank you. I think the reason why we cannot find the sensor readings is that your motherboard has an IPMI BMC chip, and the sensor readings are only available via IPMI Sensor calls. Problem is: via direct IPMI KCS interface AIDA64 doesn't seem to be able to communicate with the BMC chip. Do you have an IPMI driver installed? If not, can you please try to install one? Maybe with the IPMI driver installed, you would be able to see the IPMI Sensor readings on the Computer / IPMI page.
  43. 1 point
    To make AIDA match the look of my Windows 8 box, I have spent some time designing a sensor panel. Here is the result (click here to download the sensorpanel config file).
  44. 1 point
  45. 1 point
    Thank you. If you have a chance to borrow two identical DDR3-1333 modules from a friend, then it would worth checking out whether it makes a difference. If you cannot do that, then it may worth playing around with the memory modules, because there may be one or two weak ones amongst the 4 modules you've got installed. Try removing two, and check out if it changes anything. If not, then try replacing the two installed modules with the ones you removed previously, etc. Make sure to have the 2 modules always placed in the DIMM slots that makes the chipset operate optimally (dual-channel; first DIMM slots usually). I apologize for not being able to provide better ideas on troubleshooting. Remotely it's usually quite difficult But what you did so far (installing a better CPU cooler and a new PSU) were both good steps in trying to hunt down the cause of the hardware issue.
  46. 1 point
    Yes, that's our suspicion too. We already have a theory about where the Shared Memory feature piles up the handles, but it's not easy to reproduce and verify it. We'll work on it in the upcoming days, collect feedbacks from other beta testers as well, and hopefully we can fix it up soon.
  47. 1 point
    The gadget requires AIDA64 to be running. You can hide AIDA64 main window by double-clicking on its System Tray icon. Regards, Fiery
  48. 1 point
    Hey, I know this thread is somewhat old, but I was looking to start a thread where everyone posts their sensorpanel display; apparently this one was already here, so I figured I would just join the party. I have had Aida 64 for some time, and have been using the OSD. I somehow caught wind of the sensor panel just last night (I didn't know about it), and after a few hours this is what my display looks like (this is my left monitor). I'm quite happy with how it came out, and I thought I would share.
  49. 1 point
    Do you have a Logitech G13, G15 or G19 gaming device with a built-in LCD screen? If so, then do you have the necessary Logitech drivers installed? Regards, Fiery
  50. 1 point
    1) Here is the Sensorpage: Informationsliste Wert Sensor Eigenschaften Sensortyp Winbond W83627DHG (ISA 290h) GPU Sensortyp Analog Devices ADT7473 (NV-I2C 2Eh) Motherboard Name Asus P5E3 Deluxe / Premium Gehäusezutritt gefunden Nein Temperaturen Motherboard 35 °C (95 °F) CPU 35 °C (95 °F) 1. CPU / 1. Kern 25 °C (77 °F) 1. CPU / 2. Kern 29 °C (84 °F) 1. CPU / 3. Kern 17 °C (63 °F) 1. CPU / 4. Kern 20 °C (68 °F) GPU1: Grafikprozessor (GPU) 38 °C (100 °F) GPU1: GPU Diode 35 °C (95 °F) GPU1: GPU Speicher 32 °C (90 °F) GPU1: GPU Umgebung 31 °C (88 °F) GPU2: Grafikprozessor (GPU) 43 °C (109 °F) GPU2: GPU Speicher 35 °C (95 °F) GPU2: GPU Umgebung 36 °C (97 °F) WDC WD3200AAKS-00L9A0 (WD-WMAV29347229) 17 °C (63 °F) WDC WD3200AAKS-00L9A0 (WD-WMAV29379843) 17 °C (63 °F) WDC WD3200AAKS-61L9A0 (WD-WCAV2V784550) 17 °C (63 °F) WDC WD3200AAKS-61L9A0 (WD-WCAV2V784369) 17 °C (63 °F) Kühllüfter CPU 620 RPM Gehäuse #1 1918 RPM Gehäuse #2 2220 RPM GPU1 40% GPU2 1427 RPM (40%) Spannungswerte CPU Kern 1.35 V +3.3 V 3.31 V +5 V 4.97 V +12 V 11.87 V +5 V Bereitschaftsmodus 4.99 V GPU1: GPU Kern 0.96 V GPU1: GPU Vcc 3.32 V GPU1: GPU +12V 12.05 V GPU1: GPU VRM 0.95 V GPU2: GPU Kern 1.05 V GPU2: GPU Vcc 3.32 V Strom Werte CPU 54.87 A GPU1: GPU VRM 17.50 A Leistungswerte CPU 68.69 W GPU1: GPU VRM 16.50 W 2) I can confirm, that there are 2 GPUs in my System. A GTX 480 for Graphics and a GTX 285 for Physx. In the NVidia Driverpanel it is also set, that the 285 only does physx and nothing else. 3) There is one external Drive connected, but it is switched off, most of the time, because its just a Backupdrive. Hope that these Data would help. Greetings Dune
×
×
  • Create New...