Crashtest
-
Posts
35 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Crashtest
-
-
AIDA64 cant identify Windows Server 2025 Datacenter Azure Edition - just displays "Microsoft Windows 10 Server"
CPUZ identify it as "Microsoft Windows Server (10.0) (0x197) (x64), Version 24H2, Build 26100.2605"
Maybe AIDA64 needs some "new" ProductIDs. Based on ntdef.h (from Windows SDK 26100) you should add:
#define PRODUCT_AZURESTACKHCI_SERVER_CORE 0x00000196 = Windows Server (2022/2025) Azure Stack HCI
#define PRODUCT_DATACENTER_SERVER_AZURE_EDITION 0x00000197 = Windows Server (2022/2025) Datacenter Azure Edition
#define PRODUCT_DATACENTER_SERVER_CORE_AZURE_EDITION 0x00000198 = Windows Server (2022/2025) Datacenter Azure Edition (Core install)You may add:
#define PRODUCT_IOTENTERPRISESK 0x000000CD = Windows (10/11) IoT Enterprise Subscription LTSC
-
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
-
Pushing this ...
-
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)
-
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"
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_079Regards,
[P3D] Crashtest
-
Problems 1,2 & 4 solved, Thanx
Bug3 is also on AMD Cezanne
-
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...
-
Hi,
AIDA64 6.33.5749 has several problems with ASRockRack X570D4U Mainboard:
1st it cant identify the Mainboard
2nd it cant access the IPMI (ASpeed AST2500)
3rd it cant read the Memory SPD (maybe because of the IPMI mutex)
4th some basic PCI-Devices (1022:790b & 1022:790e) cant be identified
I tested it with Windows 7 PE (x32), Windows 10 (19044.1200) and Windows 11 (22000.160)
-
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)
-
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
-
After installing my Radeon RX 6900XT there are some new PCI devices but AIDA64 cant identify them...
1002-73A4 - AMD UCM-UCSI Device [1002-73A4] [NoDB]
1002-73A6 - ATI/AMD USB 3.10 eXtensible-Hostcontroller – 1.10 (Microsoft) [1002-73A6] [NoDB]
-
Problem 1 - solved
Problem 2-4 open
Btw there is the Windows shipped IPMI device driver installed ...
ipmiaccessdump.txt ipmidump.txt isasensordump.txt smbusdump_full.txt
-
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)
-
On my AMD Picasso based system:
AIDA64 6.20.5331 detects 1022:15E5 as an AMD SATA Controller even if its PCI Class 0C0330 (but shows correct ICON for USB).
AIDA should identify it as "AMD K17.1 - USB xHCI Controller"
-
It is working !
-
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 !?!?!
-
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 )
-
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, 6.00.5122, is unable to identify serveral new Windows SKUs, incl. Windows 10 IoT Enterprise (0xBC).
AIDA reports Windows 10 Professional instead of Windows 10 IoT Enterprise …..
I added the ntdef.h from Windows 18362 SDK with the current definitions; some pictures and reports
AIDA_BUG_Win10_iot_ent - boinc_stdoutdae.txt
AIDA_BUG_Win10_iot_ent - ntdef.h
-
Only 1 Question left:
Why is it working on NT 5.x but not on NT 6.x ?
AIDA64 4.7 on NT 6.1 and my small not finished delphi tool:
and the current Beta :
so its working now ....
-
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 ?
-
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)
-
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
-
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
PCI Device List AIDA64 vs Windows Device Manager
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 !?
AIDA64 cant identify Windows Server 2025 DC Azure...
in Bug reports
Posted
Problem solved with new update.
You may add:
#define PRODUCT_WNC 0x000000D2 = Windows Cloud PC