Jump to content

Crashtest

Members
  • Posts

    32
  • Joined

  • Last visited

Posts posted by Crashtest

  1. :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)

     

  2. Well AIDA64 reports DDR4 on the K19.6 IMC:

     

    "Supported Memory Types    DDR4-1333, DDR4-1600, DDR4-1866, DDR4-2133, DDR4-2400, DDR4-2667, DDR4-2933, DDR4-3200 SDRAM"

     

    aida_bug.PNG

     

    There are some known PnP Devices shown as "unknown" (using ICONS_Z_099):

    ACPI0010 -> ICONS_Z_009
    AMDIF031 -> ICONS_Z_009
    AMDI0052 -> ICONS_Z_009
    MSFT0101 -> ICONS_Z_079

     

    Regards,

    [P3D] Crashtest
     

     

    Report.txt

  3. One of the problems is Borland ähm Embarcadero and its Delphi.

    AIDA64 is written in Delphi - Delphi 64 Bit compiled apps are huges (sometimes 25mb vs 2mb) and some functions wont work as in 32bit...

  4. Hi,

     

    AIDA64 6.33.5749 has several problems with ASRockRack X570D4U Mainboard:

     

    1st it cant identify the MainboardAIDA_BUG_MB.png

     

    2nd it cant access the IPMI (ASpeed AST2500)

    AIDA_BUG_IPMI.png

     

    3rd it cant read the Memory SPD (maybe because of the IPMI mutex)

    AIDA_BUG_SPD.png

     

    4th some basic PCI-Devices (1022:790b & 1022:790e) cant be identified

    AIDA_BUG_PCI_790B.png

    AIDA_BUG_PCI_790E.png

     

     

    I tested it with Windows 7 PE (x32), Windows 10 (19044.1200) and Windows 11 (22000.160)

     

    Report.txt

    smbusdump_full.txt dmi_29.bin

  5. 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)

     

  6. AIDA should identify the PCI-Devices of the current AMD Chipsets (3xx/4xx/5xx for Zen/Zen2/Zen3) inside the PCI-Device-Page but it doesnt!

     

    Problem:

    On a system with AMD B450 or X470 Chipset, AIDA shows the parts of the Chipset as "AMD Low-Power Promontory Chipset" instead of B450.... or X470

    On a system with AMD A520 or B550 as "AMD 500-Series Chipset".

     

    Its "very" easy to display the right things - the first device of the chipset (USB XHCI) helps to identify the chipset:

     

    A320/B350/X370/X399:

    43B9 - X370 USB XHCI

    43BA - X399 USB XHCI

    43BB - B350 USB XHCI

    43BC - A320 USB XHCI

    This could/should be used for the other parts of the chipset

    43B5/43B5/43B7/43B8 - SATA

    43BD - SATA RAID

    43B0/43B1/43B2/43B3 - SUP

    43B4 - SDP

     

    B450/X470:

    43D0 - X470 USB XHCI

    43D5 - B450 USB XHCI

    This could/should be used for the other parts of the chipset

    43C8 - SATA

    43C6 - SUP

    43C7 - SDP

     

    A520/B550:

    43EC - A520 USB XHCI

    43EE - B550 USB XHCI

    This could/should be used for the other parts of the chipset

    43EB - SATA

    43E9 - SUP

    43EA - SDP

     

    SUP = Switch Upstream Port

    SDP = Switch Downstream Port

     

    So instead of 

    Bus 2, Device 8, Function 0    AMD 500-Series Chipset - GPP-Switch Downstream Port
    Bus 1, Device 0, Function 1    AMD 500-Series Chipset - SATA AHCI Controller
    Bus 1, Device 0, Function 2    AMD 500-Series Chipset - Switch Upstream Port
    Bus 1, Device 0, Function 0    AMD 500-Series Chipset - USB 3.1 xHCI Controller
     

    AIDA should show:

    Bus 2, Device 8, Function 0    AMD B550 - GPP-Switch Downstream Port
    Bus 1, Device 0, Function 1    AMD B550 - SATA AHCI Controller
    Bus 1, Device 0, Function 2    AMD B550 - Switch Upstream Port
    Bus 1, Device 0, Function 0    AMD B550 - USB 3.1 xHCI Controller
     

    For the "missing" chipset 43ED AIDA should continue to use "AMD 500-Series Chipset"

     

    In Delphi this could look like:

    // AMD Promontory 3xx Chipsatz
            $43B0 : begin
                    Result:=SubPCIName2('SB PCIe Port (Switch USP)','AMD PCIe USP', iH_BUS_PCIE);
                    if _SBAMD<>'' then Result:=SubPCIName2(_SBAMD + PCICL_BUS_PCISWU, _SBAMD + 'USP', iH_BUS_PCIE);
                    end;
            $43B1 : begin
                    Result:=SubPCIName2('SB PCIe Port (Switch USP)','AMD PCIe USP', iH_BUS_PCIE);
                    if _SBAMD<>'' then Result:=SubPCIName2(_SBAMD + PCICL_BUS_PCISWU, _SBAMD + 'USP', iH_BUS_PCIE);
                    end;
            $43B2 : begin
                    Result:=SubPCIName2('SB PCIe Port (Switch USP)','AMD PCIe USP', iH_BUS_PCIE);
                    if _SBAMD<>'' then Result:=SubPCIName2(_SBAMD + PCICL_BUS_PCISWU, _SBAMD + 'USP', iH_BUS_PCIE);
                    end;
            $43B3 : begin
                    Result:=SubPCIName2('SB PCIe Port (Switch USP)','AMD PCIe USP', iH_BUS_PCIE);
                    if _SBAMD<>'' then Result:=SubPCIName2(_SBAMD + PCICL_BUS_PCISWU, _SBAMD + 'USP', iH_BUS_PCIE);
                    end;
            $43B4 : begin
                    Result:=SubPCIName2('SB PCIe Port (Switch DSP)','AMD PCIe DSP', iH_BUS_PCIE);
                    if _SBAMD<>'' then Result:=SubPCIName2(_SBAMD + PCICL_BUS_PCISWD, _SBAMD + 'DSP', iH_BUS_PCIE);
                    end;
            $43B5 : begin
                    Result:=SubPCIName1('SB SATA Controller','SATA');
                    if _SBAMD<>'' then Result:=SubPCIName1(_SBAMD + PCICL_STOR_SATA, _SBAMD + 'SATA');
                    end;
            $43B6 : begin
                    Result:=SubPCIName1('SB SATA Controller','SATA');
                    if _SBAMD<>'' then Result:=SubPCIName1(_SBAMD + PCICL_STOR_SATA, _SBAMD + 'SATA');
                    end;
            $43B7 : begin
                    Result:=SubPCIName1('SB SATA Controller','SATA');
                    if _SBAMD<>'' then Result:=SubPCIName1(_SBAMD + PCICL_STOR_SATA, _SBAMD + 'SATA');
                    end;
            $43B8 : begin
                    Result:=SubPCIName1('SB SATA Controller','SATA');
                    if _SBAMD<>'' then Result:=SubPCIName1(_SBAMD + PCICL_STOR_SATA, _SBAMD + 'SATA');
                    end;
    
            $43B9 : begin _SBAMD:='X370 '; Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end; //ASM2016A
            $43BA : begin _SBAMD:='X399 '; Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end; //ASM2016B
            $43BB : begin _SBAMD:='B350 '; Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end; //ASM2016C
            $43BC : begin _SBAMD:='A320 '; Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end; //ASM2016D
    
            $43BD : begin
                    Result:=SubPCIName2('Promontory SATA RAID Controller','Promontory', iH_DISK_RAID);
                    if _SBAMD<>'' then SubPCIName2(_SBAMD + PCICL_STOR_SATA_R,'Promontory', iH_DISK_RAID);
                    end;
    
    // Low Power Promontory 4xx Chipsatz
            $43C6 : begin
                    Result:=SubPCIName2('SB PCIe Port (Switch USP)','AMD PCIe USP', iH_BUS_PCIE);
                    if _SBAMD<>'' then Result:=SubPCIName2(_SBAMD + PCICL_BUS_PCISWU, _SBAMD + 'USP', iH_BUS_PCIE);
                    end;
            $43C7 : begin
                    Result:=SubPCIName2('SB PCIe Port (Switch DSP)','AMD PCIe DSP', iH_BUS_PCIE);
                    if _SBAMD<>'' then Result:=SubPCIName2(_SBAMD + PCICL_BUS_PCISWD, _SBAMD + 'DSP', iH_BUS_PCIE);
                    end;
            $43C8 : begin
                    Result:=SubPCIName1('Promontory SATA Controller','Promontory');
                    if _SBAMD<>'' then Result:=SubPCIName1(_SBAMD + 'SATA Controller','Promontory');
                    end;
    
            $43D0 : begin _SBAMD:='X470 ';   Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43D1 : begin _SBAMD:='B550A ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43D2 : begin _SBAMD:='Pro560 '; Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43D5 : begin _SBAMD:='B450 ';   Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
    
            $43D3 : begin _SBAMD:='?43D3 ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43D4 : begin _SBAMD:='?43D4 ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43D6 : begin _SBAMD:='?43D6 ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43D7 : begin _SBAMD:='?43D7 ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43D8 : begin _SBAMD:='?43D8 ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43D9 : begin _SBAMD:='?43D9 ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43DA : begin _SBAMD:='?43DA ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43DB : begin _SBAMD:='?43DB ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43DC : begin _SBAMD:='?43DC ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43DD : begin _SBAMD:='?43DD ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43DE : begin _SBAMD:='?43DE ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43DF : begin _SBAMD:='?43DF ';  Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
    // AMD 5xx Chipsatz
            $43E9 : begin
                    Result:=SubPCIName2('SB ' + PCICL_BUS_PCISWU,'AMD PCIe USP', iH_BUS_PCIE);
                    if _SBAMD<>'' then Result:=SubPCIName2(_SBAMD + PCICL_BUS_PCISWU, _SBAMD + 'USP', iH_BUS_PCIE);
                    end;
            $43EA : begin
                    Result:=SubPCIName2('SB ' + PCICL_BUS_PCISWD,'AMD PCIe DSP', iH_BUS_PCIE);
                    if _SBAMD<>'' then Result:=SubPCIName2(_SBAMD + PCICL_BUS_PCISWD, _SBAMD + 'DSP', iH_BUS_PCIE);
                    end;
            $43EB : begin
                    Result:=SubPCIName1('SB SATA Controller','SATA');
                    if _SBAMD<>'' then Result:=SubPCIName1(_SBAMD + PCICL_STOR_SATA, _SBAMD + 'SATA');
                    end;
            $43EC : begin _SBAMD:='A520 ';   Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43ED : begin _SBAMD:='???? ';   Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;
            $43EE : begin _SBAMD:='B550 ';   Result:=SubPCIName1(_SBAMD + PCICL_USB_XHCI31, _SBAMD + 'XHCI'); end;

     

    Report_B550.txt Report_A520.txt Report_B450.txt Report_X470.txt

  7. AIDA64 incl. v6.25.5400 has some problems with my EPYC system:

     

    - wrong identification of EPYC integrated XHCI

    - no access to IPMI onboard

    - no sensor data (FANs)

    - no DIMM data

     

    System:

    AMD EPYC 7251

    ASRockRack EPYCD8-2T/Rev 2 (BIOS P2.50)

    Windows 20H1 (19041.172)

     

     

    Problem 1:

    PCI Database problem - PCI\VEN_1022&DEV_145F is shown as "AMD K17 - Reserved" but it's the EPYC integrated XHCI

     

     

    Problem 2:

    The ASRockRack EPYC8D-2T(Rev 2) has onbaord IPMI based on ASPEED AST2500 but AIDA64 cant get any data from it

     

    Problem 3:

    AIDA64 wont display any FAN data from the sensor chip

     

    Problem 4:

    AIDA64 cant read DIMM Data (SPD)

    bug_dimms.png

    bug_dimms2.png

    bug_fans.png

    bug_ipmi.png

    bug_usb.png

    epyc.txt

  8. Maybe this is because of reading the wrong file for its version!

     

    If you just get the version of C:\Program Files\Windows Defender\MsMpEng.exe - on my system it get 4.18.1902.5

    But if I follow the path from Registry ( HKLM\SOFTWARE\Microsoft\Windows Defender\

    String "InstallLocation"

    I get an other path -> "C:\ProgramData\Microsoft\Windows Defender\platform\4.18.1906.3-0\"

    Inside this "C:\ProgramData\Microsoft\Windows Defender\platform\4.18.1906.3-0\" is an other "MsMpEng.exe" with version 4.18.1906.3 - same version is reportet by Windows Defender Info Box

     

    BUT:

    AIDA64 displays correct file version at the Anti-Spyware page !?!?!

     

    AIDA64_BUG_WinDef_2.png

    AIDA64_BUG_WinDef_3.png

  9. On ‎7‎/‎9‎/‎2019 at 9:35 AM, Fiery said:

    Thank you for the bug report.  I'm not sure if it's possible to detect Windows Defender on recent Win10 builds, but we'll improve on it in the next AIDA64 beta in order to show some details on the Windows Defender installation.  The virus database date seems to be off though, so we need to do more research on that matter.

    It is possible to access Windows Defender Status using WMI ….

    https://docs.microsoft.com/de-de/previous-versions/windows/desktop/defender/msft-mpcomputerstatus

    But I'm not sure if AIDA64 (32Bit APP) could use Windows Defender WMI  (64 Bit DLL - C:\Program Files\Windows Defender\ProtectionManagement.dll )

  10. AIDA64 shows some strange DeviceIcons for common devices ?

     

    Example:

    any AMD CPU - AIDA64 displays ICON_Z_099 instead of ICON_Z_066.

     

    Solution:

    if Copy(DEVICEIDSTRINGORWHATEVER, 0 , 15)='AUTHENTICAMD_-_' then displayicon:=ICON_Z_066; // like "AuthenticAMD_-_AMD64_Family_23_Model_17_-_AMD_Athlon_200GE_with_Radeon_Vega_Graphics_____"

    for Intel it should be something like:

    if Copy(DEVICEIDSTRINGORWHATEVER, 0 , 15)='GENUINEINTEL_-_' then displayicon:=ICON_Z_066;

     

    More DeviceIDs and possible Icons:

    AMDI0030 & AMDIF030 (AMD GPIO) - ICON_Z_077

    ASD0001 - ICON_Z_009

    HPQ8001 - ICON_Z_045

    UEFI - ICON_Z_009

     

     

     

     

    AIDA_N_Icons.png

  11. here are the dumps

     

    ps my simple delphi tool detect all devices even on Windows 10 using winring0 driver

    simple

    for bus:=0 to 255 do

    for dev:=0 to 31 do

    for func:=0 to 7 do

    if ReadPCIConfigDword(Mix(bus,dev,func), 0) <>$ffff // checkin VendorID

    begin

    ...

    end;

     

    I will check the "fix" later - but why enum PCIdevices by registry if theres is a working (NT5.x) enum by devicedriver ?

    AIDA_PCI_BUG_NT52_DEVICEDUMP.txt

    AIDA_PCI_BUG_NT52_PCIDUMP.txt

    AIDA_PCI_BUG_NT52_REPORT.txt

  12. So back to business:

     

    I tested old (4.x) and current (5.0 final not current beta) AIDA64 versions on Windows NT 5.2 (PE 2005)  - AIDA64 found all !!!! PCI devices on both segments !

    Reboot to Windows NT 6.0 (PE 2007) - only devices on bus 0 & bus 1

    Reboot to Windows NT 6.1 (PE 2009) - only devices on bus 0 & bus 1

    Reboot to Windows NT 6.4 (PE 2015 - current internal beta) - only devices on bus 0 & 1

    againt test with older Windows, Windows NT 5.1 (PE 2004) - AIDA, both 4.7 and 5.0, found all devices

     

    Result:

    AIDA64 could find all devices as long as Windows is NT 5.x and not NT6.x

     

    So it looks like a OSrelated AIDA64 Bug

     

    (I will upload AIDA64 dumps from NT5x soon) 

  13. Thank you for the dumps. I suppose the issue may be the fact that your system has multiple PCI bus segments. We'll have to come up with a workaround for such situations. If possible, please export the following Registry path out to a .REG file:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI

    Rename the .REG file to .TXT, and attach it to a post.

     

    Maybe, but I'm not sure. It may worth a try. But please do the Registry export under Windows 7 or Windows Server 2008 R2.

    Thanks,

    Fiery

     

    Here are the Registry Exports from both systems

    reg_thor.txt

    reg_odin.txt

  14. all tested AIDA64 versions are unable to detect all PCI devices on my HP xw9400 based systems:

     

    AIDA found only device on PCI bus 0 and 1 - rest (on bus 24,43,44,64,69,70,71,72,107) are missing; because of that, AIDA64 wont display any infos about installed GPU etc.

     

    Systems:

    HP xw9400 Board (OEM Version of Tyan S2915e)

    Dual Opteron 2382 and Dual Opteron 2427

    Windows 7 sp1 x64 and Server 2008r2 x64 sp1
     

     

    PCI Device List AIDA64 vs SIV

    aidabug_pcidevs_comp_l0oyo.png

     

     

    PCI Device List AIDA64 vs Windows Device Manager

    aidabug_pcidevs_comp_vuun5.png

     

     

     

    I added:

    - ACPIDUMP

    - PCIDUMP

    - DEVDUMP

    and SIV-Dumps

     

     

    well if I boot Windows PE based on NT 5.1 or 5.2 AIDA64 will report all devices !?

    acpidump.txt

    devdump.txt

    pcidump.txt

    SIV_ODIN.txt

  15. Thank you for the list.  In order to verify the list, could you please provide the source you got it from? ;)  I'm just asking, because I'm not entirely sure about the accuracy of your list. For example, the APUs of Kaveri should rather be codenamed Spectre and Spooky.

     

     

    Regards,

    Fiery

     

     

    Casper & Slimer are taken from AMD OpenCL ICD so both could be the OpenCL-Names of the Kaveri-Devices instead of the CAL-Names - why the hell is AMD using different Names for a device in CAL and OpenCL ?

     

    Sources:

    1st discussion inside AMD Dev Forum

    2nd http://developer.amd.com/wordpress/media/2013/08/AMD_Accelerated_Parallel_Processing_OpenCL_Programming_Guide.pdf - page E-2 (theres the current offical CAL-target-List)

  16. Hi,

     

    there are some new AMD CAL TargetIDs missing in AIDA64

     

    Current CAL List:

    ....

    10 - Redwood

    11 - Cedar

    12 - Sumo (lower APUs in Llano / OpenCL=Winterpark)

    13 - SuperSumo (higher APUs in Llano / OpenCL=Beavercreek)

    14 - Loveland (OpenCL=Wrestler)

    15 - Cayman

    16 - Kauai

    17 - Barts

    18 - Turks

    19 - Caicos

    20 - Tahiti

    21 - Pitcairn

    22 - Capeverde

    23 - Devastator (higher APUs in Trinity/Richland)

    24 - Scrapper (lower APUs in Trinity/Richland)

    25 - Oland

    26 - Bonaire

    27 - Casper (APU inside Kaveri)

    28 -.Slimer (APU inside Kaveri)

    29 - Kalindi (APU inside Kabini)

    30 - Hainan

     

     

    Regards

    [P3D] Crashtest

  17. We've fixed an issue in the BIOS detection module of AIDA64. I hope it will fix the issues on your system.

     

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

     

    http://www.aida64.com/downloads/aida64extremebuild2327vtb1dhc3yjzip

     

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

     

    Let me know how it works ;)

     

    As for the ACPI VFCT table: it's a table where AMD stores the Radeon video BIOS when the system is booted up in UEFI mode.  We can add VFCT table details if you could post a VFCT table dump.  You can create such dump by right-clicking on the bottom status bar of AIDA64 main window --> ACPI Tool --> Save Table --> VFCT.

     

    Well I added the VFCT (added .txt because it wont upload if its a bin)

     

    AIDA still not display any BIOS infos at Motherboard\BIOS but it shows "all" infos at DMI and Motherboard\ACPI

    acpi_vfct.bin.txt

×
×
  • Create New...