Jump to content

Fiery

Administrators
  • Posts

    11186
  • Joined

  • Last visited

  • Days Won

    475

Posts posted by Fiery

  1. On 4/20/2024 at 1:39 PM, Tobi7854587458 said:

    Hello everyone. Unfortunately I cannot see my T-sensor under Aida64. It is displayed correctly in HWInfo64. Embedded controller is switched on.
    Can someone help?

    Cheers

    Make sure to enable both EC related options in AIDA64 / Preferences / Stability:

    Embedded Controller (EC) support
    Embedded Controller (EC) bank switching

    Let me know if it helps.

  2. 8 hours ago, fuf42 said:

    Is it possible to configure the Epson DM-D110 Device? This is a 2x20 VFD attached via USB FTDI Driver. This is the USB Dump:

     

    <DESC>DM-D110-XXX</DESC><DEVPATH>\\?\usb#vid_1208&pid_0780#00012775#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_1208&PID_0780\00012775</INSTANCE><PARENTINST>USB\VID_05E3&PID_0610&ASMEDIAUSBD_HUB\14000830</PARENTINST><BUSNUM>00000000</BUSNUM><ADDR>0000001F</ADDR><REV>0400</REV>
    
    ------[ FTD2xx Devices ]------
    
    Device Description : USB Edition of DM-D110
    Device ID          : 1208-0780
    Device Index       : 0
    Device Location    : 0
    Device Type        : FT232BM
    Serial Number      : 00012775
    
    

    It's working under Linux with the ftdi_sio kernel module and a ttyUSB-device is created with

    echo 1208 0780 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id

    where you can simply "cat" Text into it.

    regards,

    Christian

    Try to use the POS module of the AIDA64 LCD feature on the virtual COM port that the device allocates.  Set protocol to Epson.  Let us know how it works out.

  3. 9 hours ago, Dudleydogg said:

    I went back to previous version, then a Fix was published, I installed that fixed update and it was fine.

    Although I do have a 2nd device that I had to Wipe, and now when ever I try to enable the Beada Panel it just hangs. Previously prior to the Wipe/Reinstall it was working just fine.

    I am unable to leverage the Beada panel now.

    suggestions?

    Make sure to upgrade to the latest beta version of AIDA64 Extreme available at:

    https://www.aida64.com/downloads/latesta64xebeta

  4. 7 hours ago, ChaosAD said:

    Im afraid it still doesnt work. As soon as i power off my main monitor, sensoprpanel close from the second one, although i pin it to the second display. 

    By powering off, do you mean you press the power button on your primary monitor?  Please note that pinning only works in case the number of monitors are constant.  If you pin your SensorPanel to display #2, and display #1 (primary monitor) vanishes from the list of monitors as managed by Windows, the whole concept stops working.  We've designed the pinning feature to mitigate issues rising from changing primary monitor resolution as well as relations between the primary and secondary displays (e.g. when displays are moved around).  It's not been prepared to be aware of display #2 (secondary display) becoming display #1 (primary display) because of the main (primary) display suddenly disappearing from the system...

  5. 1 hour ago, MatthijsNL said:

    Hello,

    I'm a newby and just wonder if there are any other options for displaying in the taskbar?
    I configured AIDA64 to display the CPU temperature in the taskbar but find the font to small and too thin.
    Compared to the date and time, also displayed in the taskbar, these are much larger and bolder.

    taskbarAIDA64.jpg.45aafcd1d67f24b233c152f40de172d7.jpg

    Any ideas on this? Because I only can configure background and text colour 😞

    Thanks,

    Matthijs

    Unfortunately sensor icons can do whatever they can in a very constrained 16x16 pixel space.  By making the text bold, it may not fit into the 16x16 pixel space reserved for System Tray icons :(  If you need more flexibility, you may want to check out the OSD Panel, SensorPanel and RemoteSensor LCD modules of AIDA64.

  6. 3 hours ago, Edu V2MC said:

    Good morning, I ran the test on my memories and received an error warning: MTMBW: memory allocation timeout [BenchDLL v4.6.889.8-x64] please, does anyone know what it means and how to fix it?

    Try to restart Windows, and try it again.  It may have come up because of a temporary lack of physical memory that AIDA64 could allocate in order to execute its memory benchmarks.

  7. 16 hours ago, bobg2222 said:

    I recently cloned one of my PCs to a mini PC with an Intel Celeron N5105 processor (GMKTec Nucbox 5 with all the hardware recognized by AIDA64). This worked perfectly so the mini PC starts up with Windows 10 and all my stuff installed, including AIDA64.

    But CPU temp is just not right. It's always stuck on 28C when the individual cores are (at idle) in the mid-30s. It NEVER changes. I've tried uninstalling and reinstalling AIDA64 but nothing helps. hwinfo64 shows a "CPU Package" temp which DOES vary and seems reasonable (higher than the individual core temps but similar)--but the only CPU Package in AIDA64 is a power in watts.

    How do I get a useful CPU temp?

    In AIDA64 please press Ctrl+Alt+D --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

    Thanks,
    Fiery

  8. On 3/14/2024 at 7:41 PM, Loyd said:

    the fan control program uses a plugin to interface the razer with FC.  The razer does not commutate naturally with FC, It needs this plug in. there are a lot of plug ins available for all sorts of items on the FC github site. have fun.

    We've implemented support for Razer PWM PC Fan Controller in the latest AIDA64 beta version available at:

    https://www.aida64.com/downloads/latesta64xebeta

    Let us know how it works.

  9. On 4/1/2024 at 12:41 AM, rinaldop said:

    I am running Aida64 v7.20.6811 Beta and my hard drive temperature used to be reported but I no longer see that listed.

    Motherboard Name    Asus ROG Strix B650E-F Gaming WiFi

    Driver Description    WD_BLACK SN850X 2000GB

    I am running the latest driver 

    What dump do you want to troubleshoot it?

    In AIDA64 please press Ctrl+Alt+D --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

    Also, in AIDA64 press Ctrl+Alt+D --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

    Thanks,
    Fiery

  10. On 1/25/2023 at 6:17 PM, Crashtest said:

    :lol: you're joking:

    ACPI0010 = ACPI Processor Container Device (see C:\Windows\Inf\Machine.Inf of Windows 10 or newer)

    MSFT0101 = Trusted Platform Module 2.0 (see C:\Windows\Inf\tpm.inf of Windows 10 or newer)

     

    OK some AMD devices are "strange"

    GPIO0010, AMD0030, AMDI0030, AMDI0031 = AMD GPIO Controller (see amdgpio2.inf)

    AMDF030, AMDIF030, AMDIF031 = AMD GPIO Controller (see amdgpio3.inf)

    AMDI0052 = AMD PPM Provisioning File (see amdppmpf.inf)

     

    Thank you, we will fix the listed issues in the next AIDA64 beta update.

  11. On 8/4/2021 at 2:51 PM, Crashtest said:

    Here are some more minor "cosmetic" Updates for the PNP Database, esp. with the Windows 11 sysreq. :

    MSFT0101 - Trusted Platform Module 2.0 - ICON_Z_079

     

     

    ACPI0010 - ACPI-Processor Container Device - ICON_Z_066 or ICON_Z_009

    AMDI0005 - AMD MicroPEP - ICON_Z_009

    AMDI0010 - AMD I2C - ICON_Z_009

    USBC000 - UCM-UCSI - ICON_Z_101 (or 102/103)

     

    Thank you, we will fix the listed issues in the next AIDA64 beta update.

  12. 4 hours ago, Crashtest said:

    AIDA64 still cant identify same "basic" PnP devices 😟

    It only displays the "?" (ICONS_Z_099)

     

    So again (and again) a help for you to add:

     

    PNP ; Source, Inf, Device Desc, possible ICON

    ACPI0010 ; Windows 10, machine.inf, ACPI Processor Container, ICONS_Z_009

    MSFT0101 ; Windows 10, tpm.inf, Trusted Platform Module 2.0, ICONS_Z_079

    MSFT0200 ; Windows 11, hsp.inf, Microsoft Pluton Processor, ICONS_Z_079

    MHSP0001 ; Windows 11, hsp.inf, Microsoft Pluton Processor, ICONS_Z_079

     

    AMD:

    AMDI0052 ; AMD Chipset Drv, AMDPPMPF.inf, AMD PPM Provisioning File, ICONS_Z_009

    AMDIF031 ; AMD Chipset Drv, amdgpio3.inf, AMD GPIO Controller, ICONS_Z_009

     

     

    Bug.PNG

    tpm.inf 11.15 kB · 0 downloads hsp.inf 3.55 kB · 0 downloads amdgpio3.inf 3.68 kB · 0 downloads AMDPPMPF.inf 1.54 kB · 0 downloads

    Thank you, we will fix the listed issues in the next AIDA64 beta update.

    • Like 1
  13. 1 hour ago, Ali-S said:

    The Finals got updated late in 2023, and every time I try to launch the game, it detects Aida64 as a debugger tool by easy anti-cheat.

    Is there anyway to fix this issue?

    The only option I found for now is to close it, open the game, and reopen Aida64 again.

    Unless developers of The Finals could let us know why they detect AIDA64 as a debugger, we cannot do much on our end.  Please report the issue to them, and ask them to fix the issue in their detection method, or contact us directly in email to find a resolution involving both them and us.

  14. 12 hours ago, MadMartin said:

    ------[ Versions ]------

    Program Version : AIDA64 Extreme v7.20.6802
    LLKD Version    : 2
    BenchDLL Version: 4.6.889.8-x64
    Windows Version : Microsoft Windows 11 Pro 10.0.22631.3374 (64-bit)
    GetProductInfo  : 0x00000030

    ------[ Video Adapters ]------

    AMD Raphael [1002-164E / 1043-8877 / Rev CA]
    Sapphire RX 7800 XT [1002-747E / 1DA2-475D / Rev C8]

    Thank you!  According to that dump, you should have GPU fan RPM reading on the Computer / Sensor page of AIDA64.  If you cannot see it there, maybe it's because the fan is not spinning right now.

×
×
  • Create New...