Jump to content
AIDA64 Discussion Forum

Leaderboard


Popular Content

Showing content with the highest reputation since 04/29/13 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. 7 points
    Here is my AIDA64 Sensorpanel, it was a heavy working:)image
  3. 6 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
  4. 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
  5. 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
  6. 4 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
  7. 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
  8. 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
  9. 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.
  10. 3 points
  11. 3 points
    Hello I heard/read that Windows 8.1 64-bit needs the following CPU support: - CMPXCHG16b - LAHF/SAHF - PrefetchW (http://windows.microsoft.com/en-us/windows-8/preview-faq) CMPXCHG16b and LAHF/SAHF I can find in the Aida64 CPU Instructions set list, but not PrefetchW. Does it have another name or ist it missing ?
  12. 3 points
    Finished mine. Transparency is fake Download
  13. 3 points
    This Industrial PC (Aaeon AHP-1081: http://www.aaeon.com...3_TW_UTF-8.html) is unknown for AIDA64 2.70.2112. Here is the report.htm. Hope this helps! Report.zip
  14. 3 points
    Hey guys, just thought you might like my Star Trek TNG sensor panel. I styled it like the control panels from The Next Generation. It's fully functional. I'm always tweaking though. It's a large size. 1024 x 972. I usually use it with 25% transparency on my 1600 x 900 desktop. I may do another design, just to switch up now and again.
  15. 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.
  16. 3 points
    Hi all, I'm new here... I just want to let you know that AIDA 64 can now be used through LCDHost (http://www.linkdata.se/). That way you can display almost everything from AIDA, as raw measures or graphs. Have fun!
  17. 2 points
    Introduction I like AIDA64, especially the logging functionality, but it's difficult to analyze this data. The diagrams within AIDA64 are very limited and there is no possibility to compare the influence of different settings (e.g. graphic) to the overall performance of a system. So I decided to implement a tool, which allows to illustrate AIDA64 log data in several diagrams and to compare multiple log-files side-by-side in one diagram ! User Guide Before you can use the tool, you have to generate an AIDA64 log file with at least the following marked settings: Log sensor readings to CSV log file UpTime The tool is very simple to use: no installation necessary, just start "GenericLogViewer.exe". At the top you can select how many diagrams with how many log-files should be presented by the tool. Open an AIDA64 log file by clicking the "Open File" button, select application type "AIDA64", select an AIDA64 log file and press "Open" (AIDA64 csv-log-files have typically the filename pattern: *_log.csv). After parsing the file, the logging duration of the file is shown and by default the "Timeline" diagram of the first log category. You can change the shown diagram with: Timeline/Statisic RadioButton Log Category ComboBox Change all buttons (changes category in every diagram) The Y-axis shows the values of the seleted Log Category in ComboBox (unit is within [..]) If an opened file is still updated with logging-data by AIDA64, you can simple update/refresh it by clicking on the "Reload"-Button: At the top left corner of every diagram you can find the arithmetic average of the corresponding curve: If there are too many different values on Y-axis in "Statistic" mode, the values are grouped into ranges. If this is the case, the following control is shown, which allows to increase of decrease the number of ranges (or to disable quantisation). Splitter between the diagrams allow you to adjust the height of all diagrams: After opening all log files you can hide the file area by unmarking "Show file area" to get more space for diagrams. New feature since version 2.1: Simple Mode I added a "two columns" feature, which doubles the number of diagrams. But if you use "two columns" with a high "number of diagrams" the diagrams are very small. That's why I introduced the "Simple mode" which: simplifies header and footer decreases line thickness Tip: use the "Tab"-key to toggle between 'Standard' and 'Simple' mode ! New feature since version 3.0: Time Window Definition If you click the "Edit"-button in the file area, a new window will be opened to define Start- and End-time of a time window for the logfile (see user guide at the top of this window). It allows you to show only a part of a single logfile or to synchronize multiple logfiles Attention: time window start-time is "normalized" to "00:00:00", otherwise synchronization of multiple log-files will not work ! Button description: "Set": defines Start/End time of time window "Reset": resets Start/End time to "file borders" "Zoom": zooms into diagram with the actual defined Start/End times for fine-tuning (from Start-10% to End+10%). Remark: works only in case of Start/End is more then 10% from "file Start/End times") "Cancel": closes window without any change "Apply": yes, take the actual defined Start/End times as the used time window for all diagrams ! New features since version 4.0 (August 2018): possibility to compare different categories of one file in one diagram possibility to present diagrams in a "dark style" If you have only file loaded, it's now possible to add up to two more ComboBoxes for category selection in any diagram. Addtional you can change the background color of the diagram section to black. New features since version 5.0 (July 2019): MSI Afterburner logs are now supported too (*.hml) "Statistic"-diagram got many improvements (now it works as it should) New diagram-type "Triple" implemented, which shows Minimum, Average and Maximum in a barchart: Requirements Microsoft Windows Microsoft Framework .NET 4.7.2 (at least, Windows Update from April 2018) no installation necessary, just start "GenericLogViewer.exe" Download The zip file (SHA-1 hash, Version 5.1: 3F00587F9019A8215BABDC8A55BE8264D60D7A9E) contains the binary files of the tool. Version history: 1.0: Initial version 1.1: "Change log category" buttons added 1.2: User Interface improvements 1.2: Switch to GenericLogViewer 1.3: Bugfix: depending on Windows Region Settings there could be a problem during DateTime conversion (older versions) 2.0: Many internal changes, new features see post below 2.1: New features see post below 2.2: Bugfix: log-files, created on a PC which was running > 24 hours couldn't be loaded -> fixed 3.0: New feature: Time Window Definition 3.1: Bugfix: sometimes log-files can't be opened after AIDA64 was stopped -> fixed 3.2: Bugfix: sometimes log-files can't be opened, case reported by mkos1 below -> fixed 4.0: New feature: different categories of one file in one diagram and dark mode 5.0: New feature: diagram-type "Triple" implemented 5.1: New feature: save screenshot GenericLogViewer - Version 5.1.zip
  18. 2 points
    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
  19. 2 points
    There must be something wrong about the OpenCL software stack. Try to uninstall and reinstall ForceWare.
  20. 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
  21. 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
  22. 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
  23. 2 points
    Ok cool I'll see what I can come up with for ya we can fine tune it later on ...
  24. 2 points
  25. 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.
  26. 2 points
    Got a bit carried away with XCOM2 and hunting down a (possible) memory issue...
  27. 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.
  28. 2 points
    Hi, im big fan of Fallout series so i made it pipboy like.
  29. 2 points
    Quick thought. It would be very useful to be able to have more than one sensor panel. ie, indefinite number (within reason ofcourse) independent of each other. Particularly for those of us using multiple monitors
  30. 2 points
    Here's my panel. Put a fair bit of effort into it lol. The gpu values are incorrect as i havnt installed my card yet but it'll be sweet once i do.
  31. 2 points
    Hey guys, just thought you might like my Star Trek TNG sensor panel. I styled it like the control panels from The Next Generation. It's fully functional. I'm always tweaking though. It's a large size. 1024 x 972. I usually use it with 25% transparency on my 1600 x 900 desktop. I may do another design, just to switch up now and again.
  32. 2 points
    Sensor panel that matches Win 8.1 stock theme: mikanoshi_HT.sensorpanel
  33. 2 points
    Yes, we do have plans about that, but unfortunately the current software stack for Corsair Link architecture doesn't allow multiple applications access the Link hardware simultaneously. Corsair said they will roll out a brand new software stack with 3rd party applications support sometime next year. As soon as their new software stack is ready, we'll get back to implementing Corsair Link support in AIDA64. Regards, Fiery
  34. 2 points
    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
  35. 2 points
    Hy, that is my construction
  36. 2 points
    That is great news! I have voted and shared
  37. 2 points
    When I run Aida64 Extreme v2.8, after a while the system reboots and the Asus Sabertooth z77 bios says, "asus anti-surge detected an unstable power supply unit on last start up." I have replaced the mother board, power supply unit, ram, hard drive, video card, case, pure sine wave UPS, and re installed from installation disk Win 7. I am running Intel i7 3770k at stock with Corsair H60 water cooler. Can Aida64 be triggering a "false" positive to the mother board about unstable psu? I have same problem with Asus p8z77-v Pro mother board.
  38. 2 points
    I just wanted to share the SensorPanel design I've been working on. Any suggestions are welcome! The mess of red lines in the CPU graph are the eight individual cores and the blue line is the overall load. The RAM bar is the RAM utilization and has the memory clock, rated speed, and timings as well. System temperatures are next, followed by the on-board fan speeds. The GPU graph shows GPU load in blue, MC in red, and VE in yellow (which seems to be 0% all the time), indicated by the labels beneath the graph. The GPU's current bus speed is above the graph, along with the GPU's current clock speed. Video RAM utilization and clock speed, GPU diode temperature, and GPU fan speed are at the bottom. Some thoughts: I wish there were a cleaner way of showing individual CPU cores on a graph - maybe showing only physical cores instead of all eight from HyperThreading? Sensor items that display hardware models would be nice for decorating the panel. Yes, I could just put a static label on there for my own personal use, but it wouldn't be very useful for someone else's system. Colors used on the panel should be able to have alpha values set. This could allow some great aesthetics, but would also allow for some easier-to-read graphs with multiple values (like the CPU cores in this example). Conditional coloring for sensor values would be great. For example, you can see above the CPU graph that the clock speed is lowered in an idle state; it would be nice to have this colored when not at max speed. One other addition that would make designing these panels more efficient would be a CSS class-like system where you could use a style class in place of a specific color so you could change the color used on multiple elements with one change. I've attached the SensorPanel file but I'd imagine you would need to have a similar board and CPU for it to work without some modifications. Here are my specs: i7-3770K at 4.3GHz Intel DZ77SL-50K board 16GB DDR3-1600 GSkill Ares memory EVGA Geforce GTX 670 with 2GB RAM Z77_i7-3770K_GF670.sensorpanel
  39. 2 points
    Hello, this is my sensorpanel: Dark Blue Black and Deep Black This is a screenshot of deep black with transparency This is the file of my settings Sunj.sensorpanel Sunj.sensorpanel
  40. 2 points
    Hello guys! Im tottaly new to this forum and dont even know what data would u need to help me., My pc is crashing(reboot) ,slowing down on daily basis .Ive checked it with Aida to find out i got warning signs in those sections,CPU Physical Info:Typical Powe,.CPUID Properties:CPU Thermal Design Power, North&South Bridge, SPD also have warning signs. I tried to highlite those "bad" values. Please help me, coz no way i can do it myself.My power supply is some cheap 650W.This pc was custom build by me. Do i have to get new power supply or isit faulty motherboard? I also atached full report .Sorry about my english. ------------------------------------------------------------------------------- Field Value CPU Properties CPU Type HexaCore AMD FX-6100, 3918 MHz (19.5 x 201) CPU Alias Zambezi CPU Stepping OR-B2 Instruction Set x86, x86-64, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, XOP, AES, AVX, FMA4 Original Clock 3300 MHz Min / Max CPU Multiplier 4.0x / 39.5x Engineering Sample No L1 Code Cache 64 KB per module L1 Data Cache 16 KB per core L2 Cache 2 MB per module (On-Die, ECC, Full-Speed) L3 Cache 8 MB (On-Die, ECC, NB-Speed) Multi CPU Motherboard ID ASUS CPU #1 AMD FXâ„¢-6100 Six-Core Processor, 3314 MHz CPU #2 AMD FXâ„¢-6100 Six-Core Processor, 3314 MHz CPU #3 AMD FXâ„¢-6100 Six-Core Processor, 3315 MHz CPU #4 AMD FXâ„¢-6100 Six-Core Processor, 3314 MHz CPU #5 AMD FXâ„¢-6100 Six-Core Processor, 3314 MHz CPU #6 AMD FXâ„¢-6100 Six-Core Processor, 3315 MHz CPU Physical Info Package Type 941 Pin uPGA Package Size 40 mm x 40 mm Transistors 1200 million Process Technology 32 nm CMOS, Cu, HKMG, SOI, Immersion Lithography Die Size 315 mm2 ===================================== Typical Power 95.0 W <=====Warning sign | ===================================== North Bridge Properties North Bridge AMD RS780L Revision 00 Package Type 528 Pin FC-BGA Package Size 21 mm x 21 mm Transistors 205 million Process Technology 55 nm ================================= Core Voltage 1.0 V<====Warning sign | ================================= South Bridge Properties South Bridge AMD SB710 Revision 00 Package Type 528 Pin FC-BGA Package Size 21 mm x 21 mm Process Technology 130 nm ================================== Core Voltage 1.2 V <====Warning sign | ================================== SPD Field Value Memory Module Properties Module Name Corsair Vengeance CMZ8GX3M2A1600C9 Serial Number None Module Size 4 GB (2 ranks, 8 banks) Module Type Unbuffered DIMM Memory Type DDR3 SDRAM Memory Speed DDR3-1333 (667 MHz) Module Width 64 bit ================================== Module Voltage 1.5 V<===Warning sign | ================================== Error Detection Method None Memory Timings @ 666 MHz 9-9-9-24 (CL-RCD-RP-RAS) / 34-107-5-10-5-5 (RC-RFC-RRD-WR-WTR-RTP) @ 592 MHz 8-8-8-22 (CL-RCD-RP-RAS) / 30-95-5-9-5-5 (RC-RFC-RRD-WR-WTR-RTP) @ 518 MHz 7-7-7-19 (CL-RCD-RP-RAS) / 27-83-4-8-4-4 (RC-RFC-RRD-WR-WTR-RTP) @ 444 MHz 6-6-6-16 (CL-RCD-RP-RAS) / 23-72-4-7-4-4 (RC-RFC-RRD-WR-WTR-RTP) Extreme Memory Profile v1.2 Profile Name Enthusiast (Certified) Memory Speed DDR3-1600 (800 MHz) ==================================================== Voltage 1.50 V (Memory Controller: 1.20 V)<====warning sign | ==================================================== @ 800 MHz 9-9-9-24 (CL-RCD-RP-RAS) / 41-128-2-6-12-6-6 (RC-RFC-CR-RRD-WR-WTR-RTP) @ 533 MHz 6-6-6-16 (CL-RCD-RP-RAS) / 27-86-2-4-8-4-4 (RC-RFC-CR-RRD-WR-WTR-RTP) Memory Module Features Auto Self Refresh Not Supported Extended Temperature Range Supported Extended Temperature Refresh Rate Not Supported On-Die Thermal Sensor Readout Not Supported Memory Module Manufacturer Company Name Corsair Inc. Product Information http://www.corsair.com/memory-3.html CPU Manufacturer Company Name Advanced Micro Devices, Inc. Product Information http://www.amd.com/u...ktop/processors Driver Update http://www.aida64.com/driver-updates CPU Utilization CPU #1 / Core #1 3 % CPU #1 / Core #2 0 % CPU #1 / Core #3 0 % CPU #1 / Core #4 0 % CPU #1 / Core #5 1 % CPU #1 / Core #6 0 % --------------------------------------------------------------------------- CPUID Properties CPUID Manufacturer AuthenticAMD CPUID CPU Name AMD FXâ„¢-6100 Six-Core Processor CPUID Revision 00600F12h Extended CPUID Revision 00600F12h Platform ID D8h (Socket AM3+) HTT / CMP Units 0 / 6 ============================================= CPU Thermal Design Power 95.0 W <===warning sign | ============================================= ------------------------------------------------------------------------------ Field Value BIOS Properties BIOS Type AMI BIOS Version 0801 System BIOS Date 11/30/11 Video BIOS Date 08/10/11 BIOS Settings (ATK) CPU Voltage 0.8000 V CPU/NB Voltage 1.200 V DRAM Voltage 1.460 V HT Voltage 1.200 V NB Voltage 1.100 V CPU Frequency 200.00 MHz CPU Ratio 20.5x BIOS Manufacturer Company Name American Megatrends Inc. Product Information http://www.ami.com/amibios BIOS Upgrades http://www.aida64.com/bios-updates HardwareReport.txt
  41. 2 points
    Im using AIDA64 1.60.1300 and temperatures are just weird and innacurate Motherboard:Asus P8P67 LE CPU:Core i7 2600 Field Value Sensor Properties Sensor Type Nuvoton NCT6776F (ISA 290h) GPU Sensor Type Diode (ATI-Diode) Motherboard Name Asus P8P67 LE Chassis Intrusion Detected No Temperatures Motherboard 29 °C (84 °F) CPU 63 °C (145 °F) CPU Package 35 °C (95 °F) CPU IA Cores 35 °C (95 °F) CPU GT Cores 35 °C (95 °F) CPU #1 / Core #1 5 °C (41 °F) CPU #1 / Core #2 5 °C (41 °F) CPU #1 / Core #3 5 °C (41 °F) CPU #1 / Core #4 5 °C (41 °F) GPU Diode (DispIO) 40 °C (104 °F) GPU Diode (MemIO) 42 °C (108 °F) ST3500418AS 32 °C (90 °F) Cooling Fans CPU 1959 RPM Power Supply 1259 RPM GPU 36% Voltage Values CPU Core 1.088 V +3.3 V 3.392 V +5 V 5.080 V +12 V 12.096 V +5 V Standby 5.139 V Power Values CPU Package 9.63 W CPU IA Cores 4.96 W on ASUS probe utility shows that cpu is 22Cº
  42. 2 points
    I will post a link, rather than the 1920x1200 screenshot. http://i291.photobucket.com/albums/ll305/Arctucas/Sensorpanel1-30-12.jpg
  43. 2 points
    I'd like an improved support for more products, including: -Main Adobe products (i.e. photoshop) -Nero -Main Slysoft products -Winpatrol / MBAM and SAS (to show in the security tab list) Some free system information tools can detect easily most of these license keys. Also, the audio/video codecs don't detect any external codecs (for example K-lite Codec pack). Thank you.
  44. 1 point
    I'm getting lost again, but ... the above 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 about the CPU temperature
  45. 1 point
    Please submit a report from the About page, and if possible, we will fix the reported issue in the next AIDA64 app update.
  46. 1 point
    It means either the CPU made a calculation mistake, or the memory or cache subsystem failed to load a value from your memory. It's such an issue that is impossible to track down any further, since all we can see during the stress test workload is that the calculation didn't end up with the right result. In such cases it's usually due to excessive overclocking or improper (too strict) memory timings setting. Regards, Fiery
  47. 1 point
    Hallo, Micha. Danke dafür. Thanks. I once served me and some adapted for me and my Samsung 800P. Resolution 800x480. Let's see what I would want to change at these times I like it quite well. see ya
  48. 1 point
    Please let me know the "RM" model ID of your phone, and we'll fix it up in the next app update. In your other post I can see "RM-822", but I'm not sure if that's the actual Lumia 920 model you mean. It works fine this way. The email icon is meant to be used to send the report to your email address of choice, while the other two email submit options are meant to be used to submit a report to us (FinalWire). The report submitted to us helps to fix bugs and improve the capabilities of the app, and that's why those reports include some degree of debug information. We cannot fix that, actually. The problem is that even though AIDA64 uses the same standard email sending API, Windows 10 (including Windows 10 for PCs and Windows 10 Mobile) fails to pass the whole report to the email client. So if you try to submit a report on a WP8.1 device, the whole report will be passed to the email client; but under Win10 the report will be truncated. Sadly, the same bug plagues universal Windows 10 apps as well. What we can do on our side as a workaround is to attach the report to the emails as a TXT file. That way the report included in the email body will be truncated, but the attached file will have the complete report. We never wanted to attach the report to emails, since we were certain Microsoft would fix this bug in one of the Preview builds. But since both Windows 10 RTM Build 10240 and the latest (and supposedly almost RTM) Windows 10 Mobile Preview build still has this issue, we gave up and attached the report to the emails. As soon as Microsoft fixes the email API bug, we will remove the attachment again. No, I'm afraid it can't. Regular apps have normal access to the API set of WP8.x and Win10 Mobile, while built-in apps like Settings and special apps developed by Microsoft can have special (broader) access to the Windows kernel. What is especially frustrating is that Microsoft doesn't provide a public API (not even a read-only one) to access more system details. The Windows kernel -- including the one used by Win10 Mobile and even WP8.1 -- can do a lot of very interesting tricks like SoC temperature and CPU core clock measurement, but Microsoft doesn't expose those features via a standard API call, so apps cannot access those readings.
  49. 1 point
    Please check the following forum topics: http://forums.aida64.com/topic/1328-aida64-v300-is-out/ http://forums.aida64.com/topic/1326-new-cache-and-memory-benchmarks-in-aida64-v300/
  50. 1 point
    I finished my first one, yay. 2012-12-01.sensorpanel
×
×
  • Create New...