Jump to content
AIDA64 Discussion Forum


  • Content Count

  • Joined

  • Last visited

Everything posted by Crashtest

  1. 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
  2. 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) epyc.txt
  3. 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" AIDA_Bug_K17M1_Rep.txt
  4. 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 !?!?!
  5. 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 )
  6. 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
  7. 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_Report_PCI.txt AIDA_BUG_Win10_iot_ent - boinc_stdoutdae.txt AIDA_BUG_Win10_iot_ent - ntdef.h
  8. 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 ....
  9. 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
  10. 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)
  11. Here are the Registry Exports from both systems reg_thor.txt reg_odin.txt
  12. 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 !? acpidump.txt devdump.txt pcidump.txt SIV_ODIN.txt
  13. 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)
  14. 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
  15. 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
  16. As part of the bugreport I posted an ACPI-Dumb, inside is an unknow ACPI-Table (VFCT) <SIG>VFCT</SIG><DESC>Unknown</DESC><ADDR>2917717368</ADDR><LENGTH>20612</LENGTH><OEMID>ALASKA</OEMID><OEMTABLEID></OEMTABLEID><OEMREV>1</OEMREV><CREATORID>AMD</CREATORID><CREATORREV>827346759</CREATORREV> Whats that ?
  17. No replay ? AIDA cant read any BIOS Infos on my MSI FM2-A75MA-E35
  18. Well I have to report 2 "Bugs" 1st - AIDA wont detect any BIOS-Infos from my Trinity-System with MSI FM2-A75MA-E35 it cant detect BIOS Typ, AGESA Version, BIOS Date etc Sys: - A8-5500 - 8GB RAM - MSI FM2-A75MA-E35 - W8x64 - UEFI-BIOS 2nd AIDA wont display most AGESA-Infos on my Bulldozersystem (ASRock 985GM-GS3 FX) it wont display the AGESA Version but it reports AGESA infos on my Pharaosystem (ASUS M4A785TD-V Evo) and reports it on my Ontariosystem (ASUS E350M1-) Well the AGESA Infos are important for CPU-Upgrades - examples: - on the Orochi-Family, OR-C0 CPUs wont work untill "OrochiPIV1.2...." or newer - on the K10-Family, HY-Dx CPUs wont work until AGESA 3.5.x or newer; while PH-E0 CPUs mostly want the 3.7.... or newer (OrochiPI) One could open BIOS-file with notepad and search for the AGESA-String but it would be easier if AIDA reports them - on all branches! OK AMD has many AGESA-Branches but the "most important ones" are: - "TrinyPI " - "OrochiPI" - "OntaroPI" - "LlanoPI " - "DanNiPI " - "TigrisPI" - "DragonPI" - "MarG34PI" I added a small report of my Trinity-System with acpidump because theres a BIOS-Part AIDA wont recognize Regards [P3D] Crashtest AIDA_REPORT_TRINITY.txt AIDA_TRINITY_acpidump.txt
  19. AIDA wont display O&O SafeErase x64 because AIDA is looking inside 32Bit Registry (HKLM\Software\Wow6432Node\ ... so please change this using Reg:=TRegistry.Create(KEY_ALL_ACCESS OR KEY_WOW64_64KEY); This works even on Delphi 6 after using a patched registry.pas ... and be expanded by adding more .... so here are some Registrypaths: O&O CleverCache HKLM\Software\O&O\O&O CleverCache\6.0\ HKLM\Software\O&O\O&O CleverCache\7.0\ "SerialNo" (REG_SZ) O&O Defrag HKLM\Software\O&O\O&O Defrag\10.0\Pro\licenses\ HKLM\Software\O&O\O&O Defrag\10.0\Server\licenses\ HKLM\Software\O&O\O&O Defrag\11.0\Pro\licenses\ HKLM\Software\O&O\O&O Defrag\11.0\Server\licenses\ HKLM\Software\O&O\O&O Defrag\12.0\Pro\licenses\ HKLM\Software\O&O\O&O Defrag\12.0\Server\licenses\ HKLM\Software\O&O\O&O Defrag\14.0\Pro\licenses\ HKLM\Software\O&O\O&O Defrag\14.0\Server\licenses\ HKLM\Software\O&O\O&O Defrag\15.0\Pro\licenses\ HKLM\Software\O&O\O&O Defrag\15.0\Server\licenses\ "SerialNo" (REG_SZ) O&O DiskRecovery HKLM\Software\O&O\O&O DiskRecovery\4.0\ HKLM\Software\O&O\O&O DiskRecovery\6.0\ "SerialNo" (REG_SZ) O&O DriveLED HKLM\Software\O&O\O&O DriveLED\2.0\ "SerialNo" (REG_SZ) O&O FormatRecovery HKLM\Software\O&O\O&O FormatRecovery\4.0\ "SerialNo" (REG_SZ) O&O MediaRecovery HKLM\Software\O&O\O&O MediaRecovery\4.0\ HKLM\Software\O&O\O&O MediaRecovery\6.0\ "SerialNo" (REG_SZ) O&O PartitionManager HKLM\Software\O&O\O&O PartitionManager\2.0\license\ "SerialNo" (REG_SZ) O&O UnErase HKLM\Software\O&O\O&O UnErase\4.0\ HKLM\Software\O&O\O&O UnErase\6.0\ "SerialNo" (REG_SZ) Regards Crashtest DELPHI ROCKZ !!!
  20. Hi, AIDA reports wrong or none CPU Revisions for following AMD CPUs CPUIDs: 0x00200F30 = not inside AIDA64.exe; should be reported as LG-B0 // is ES 0x00500F00 = not inside AIDA64.exe; should be reported as ON-A0 // is ES 0x00500F01 = not inside AIDA64.exe; should be reported as ON-A1 // is ES 0x00500F10 = reported as B0 but should be reported as ON-B0 0x00500F20 = reported as C0 but should be reported as ON-C0 Please could you fix this ? Regards Crashtest
  21. Reading 64Bit Keys is a BASIC-Bug of AIDA64; wont detect any O&O Software Product Key if its the 64Bit Version ... only 32Bit.
  22. Everest & AIDA64 share the same bug - they detect a Mobile AMD Athlon 64 Odassa based CPU as a Newcastle with wrong Wattage, Codename, Voltage ! CPUID : 00000FC0 BrandID : 8 (Mobile Athlon64) -> 35W BrandID : 9 (Mobile Athlon64) -> 25W CPUID "FC0" & BrandID=8 --> Odessa (35W) and not Newcastle (its only Newcastle based) see http://de.wikipedia.org/wiki/Liste_der_AMD-Mobile-Athlon-64-Prozessoren too! AIDA infos: --------[ AIDA64 Extreme Edition ]-------------------------------------------------------------------------------------- Version AIDA64 v1.50.1200/de Benchmark Modul 2.7.333-x32 Homepage http://www.aida64.com/ Berichtsart Berichts-Assistent Computer SCHLEBTOB Ersteller Boss Betriebssystem Microsoft Windows XP Media Center Edition 5.1.2600 (WinXP RTM) Datum 2011-03-03 Zeit 12:09 --------[ CPU ]--------------------------------------------------------------------------------------------------------- CPU-Eigenschaften: CPU Typ Mobile AMD Athlon 64, 1800 MHz (9 x 200) 2800+ CPU Bezeichnung Newcastle S754 CPU stepping DH-CG Befehlssatz x86, x86-64, MMX, 3DNow!, SSE, SSE2 Vorgesehene Taktung 1800 MHz Min / Max CPU Multiplikator 4x / 9x L1 Code Cache 64 KB (Parity) L1 Datencache 64 KB (ECC) L2 Cache 512 KB (On-Die, ECC, Full-Speed) CPU Technische Informationen: Gehäusetyp 754 Pin uOPGA Gehäusegröße 4.00 cm x 4.00 cm Transistoren 68.5 Mio. Fertigungstechnologie 9Mi, 0.13 um, CMOS, Cu, SOI Gehäusefläche 144 mm2 Kern Spannung 0.900 - 1.250 V I/O Spannung 1.2 V + 2.5 V Maximale Leistung 89.0 W CPU Hersteller: Firmenname Advanced Micro Devices, Inc. Produktinformation http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118,00.html Treiberupdate http://www.aida64.com/driver-updates CPU Auslastung: CPU #1 100 % --------[ CPUID ]------------------------------------------------------------------------------------------------------- CPUID Eigenschaften: CPUID Hersteller AuthenticAMD CPUID CPU Name Mobile AMD Athlon 64 Processor 2800+ CPUID Revision 00000FC0h Erweiterte CPUID Revision 00000FC0h AMD Markenzeichen ID 0206h (Mobile Athlon 64 2800+) Plattform ID D2h (Socket 754) HTT / CMP Einheiten 0 / 1 Befehlssatz: 64-bit x86-Erweiterung (AMD64, Intel64) Unterstützt AMD 3DNow! Unterstützt AMD 3DNow! Professional Unterstützt AMD 3DNowPrefetch Nicht unterstützt AMD Enhanced 3DNow! Unterstützt AMD Extended MMX Unterstützt AMD FMA4 Nicht unterstützt AMD MisAligned SSE Nicht unterstützt AMD SSE4A Nicht unterstützt AMD XOP Nicht unterstützt Cyrix Extended MMX Nicht unterstützt Float-16 Conversion Instructions Nicht unterstützt IA-64 Nicht unterstützt IA MMX Unterstützt IA SSE Unterstützt IA SSE 2 Unterstützt IA SSE 3 Nicht unterstützt IA Supplemental SSE 3 Nicht unterstützt IA SSE 4.1 Nicht unterstützt IA SSE 4.2 Nicht unterstützt IA AVX Nicht unterstützt IA FMA Nicht unterstützt IA AES Extensions Nicht unterstützt VIA Alternate Instruction Set Nicht unterstützt CLFLUSH Befehl Unterstützt CMPXCHG8B Befehl Unterstützt CMPXCHG16B Befehl Nicht unterstützt Conditional Move Befehl Unterstützt LZCNT Befehl Nicht unterstützt MONITOR / MWAIT Befehl Nicht unterstützt MOVBE Befehl Nicht unterstützt PCLMULQDQ Befehl Nicht unterstützt POPCNT Befehl Nicht unterstützt RDRAND Befehl Nicht unterstützt RDTSCP Befehl Nicht unterstützt SYSCALL / SYSRET Befehl Unterstützt SYSENTER / SYSEXIT Befehl Unterstützt VIA FEMMS Befehl Nicht unterstützt Sicherheits Besonderheiten: Advanced Cryptography Engine (ACE) Nicht unterstützt Advanced Cryptography Engine 2 (ACE2) Nicht unterstützt Dateiausführungsverhinderung (DEP, NX, EDB) Unterstützt Hardware Zufallsnummern Generator (RNG) Nicht unterstützt PadLock Hash Engine (PHE) Nicht unterstützt PadLock Montgomery Multiplier (PMM) Nicht unterstützt Prozessor Seriennummer (PSN) Nicht unterstützt Energieverwaltungs Fähigkeiten: Automatic Clock Control Nicht unterstützt Digital Thermometer Nicht unterstützt Dynamic FSB Frequency Switching Nicht unterstützt Enhanced Halt State (C1E) Nicht unterstützt Enhanced SpeedStep Technology (EIST, ESS) Nicht unterstützt Frequency ID Control Unterstützt Hardware P-State Control Nicht unterstützt LongRun Nicht unterstützt LongRun Table Interface Nicht unterstützt PowerSaver 1.0 Nicht unterstützt PowerSaver 2.0 Nicht unterstützt PowerSaver 3.0 Nicht unterstützt Processor Duty Cycle Control Nicht unterstützt Software Thermal Control Nicht unterstützt Temperatur Sensing Diode Unterstützt Thermal Monitor 1 Nicht unterstützt Thermal Monitor 2 Nicht unterstützt Thermal Monitoring Nicht unterstützt Thermal Trip Unterstützt Voltage ID Control Unterstützt CPUID Besonderheiten: 1 GB Page Size Nicht unterstützt 36-bit Page Size Extension Unterstützt Address Region Registers (ARR) Nicht unterstützt Core Power Boost Nicht unterstützt CPL Qualified Debug Store Nicht unterstützt Debug Trace Store Nicht unterstützt Debugging Extension Unterstützt Direct Cache Access Nicht unterstützt Dynamic Acceleration Technology (IDA) Nicht unterstützt Fast Save & Restore Unterstützt Hyper-Threading Technology (HTT) Nicht unterstützt Invariant Time Stamp Counter Nicht unterstützt L1 Context ID Nicht unterstützt Local APIC On Chip Unterstützt Machine Check Architecture (MCA) Unterstützt Machine Check Exception (MCE) Unterstützt Memory Configuration Registers (MCR) Nicht unterstützt Memory Type Range Registers (MTRR) Unterstützt Model Specific Registers (MSR) Unterstützt Nested Paging Nicht unterstützt Page Attribute Table (PAT) Unterstützt Page Global Extension Unterstützt Page Size Extension (PSE) Unterstützt Pending Break Event Nicht unterstützt Physical Address Extension (PAE) Unterstützt Safer Mode Extensions (SMX) Nicht unterstützt Secure Virtual Machine Extensions (Pacifica) Nicht unterstützt Self-Snoop Nicht unterstützt Time Stamp Counter (TSC) Unterstützt Turbo Boost Nicht unterstützt Virtual Machine Extensions (Vanderpool) Nicht unterstützt Virtual Mode Extension Unterstützt x2APIC Nicht unterstützt XGETBV / XSETBV OS Enabled Nicht unterstützt XSAVE / XRSTOR / XSETBV / XGETBV Extended States Nicht unterstützt CPUID Registers (CPU #1): CPUID 00000000 00000001-68747541-444D4163-69746E65 CPUID 00000001 00000FC0-00000800-00000000-078BFBFF CPUID 80000000 80000018-68747541-444D4163-69746E65 CPUID 80000001 00000FC0-00000206-00000000-E1D3FBFF CPUID 80000002 69626F4D-4120656C-4120444D-6F6C6874 CPUID 80000003 6D74286E-34362029-6F725020-73736563 CPUID 80000004 3220726F-2B303038-00000000-00000000 CPUID 80000005 FF08FF08-FF20FF20-40020140-40020140 CPUID 80000006 00000000-42004200-02008140-00000000 CPUID 80000007 00000000-00000000-00000000-0000000F CPUID 80000008 00003028-00000000-00000000-00000000 CPUID 80000009 00000000-00000000-00000000-00000000 CPUID 8000000A 00000000-00000000-00000000-00000000 CPUID 8000000B 00000000-00000000-00000000-00000000 CPUID 8000000C 00000000-00000000-00000000-00000000 CPUID 8000000D 00000000-00000000-00000000-00000000 CPUID 8000000E 00000000-00000000-00000000-00000000 CPUID 8000000F 00000000-00000000-00000000-00000000 CPUID 80000010 00000000-00000000-00000000-00000000 CPUID 80000011 00000000-00000000-00000000-00000000 CPUID 80000012 00000000-00000000-00000000-00000000 CPUID 80000013 00000000-00000000-00000000-00000000 CPUID 80000014 00000000-00000000-00000000-00000000 CPUID 80000015 00000000-00000000-00000000-00000000 CPUID 80000016 00000000-00000000-00000000-00000000 CPUID 80000017 00000000-00000000-00000000-00000000 CPUID 80000018 00000000-00000000-00000000-00000000 MSR Registers: MSR 0000001B 0000-0000-FEE0-0900 MSR C0010015 0000-0000-0000-0000 MSR C0010042 000C-1A12-0C0A-000A
  • Create New...