Squall Leonhart

[code] ------[ Versions ]------ Program Version : AIDA64 Extreme v6.70.6000 BenchDLL Version: 4.5.868.8-x64 Windows Version : Microsoft Windows 11 Pro 10.0.22621.1 (64-bit) GetProductInfo : 0x00000030 ------[ Motherboard Info ]------ Motherboard ID : <DMI> Motherboard Model : Asus ROG Strix Z690-E Gaming WiFi Motherboard Chipset : Intel Alder Point-S Z690, Intel Alder Lake-S DMI MB Manufacturer : ASUSTeK COMPUTER INC. DMI MB Product : ROG STRIX Z690-E GAMING WIFI DMI MB Version : Rev 1.xx DMI MB Serial : 211296426600972 DMI SYS Manufacturer: ASUS DMI SYS Product : System Product Name DMI SYS Version : System Version DMI SYS Serial : System Serial Number DMI BIOS Version : 1403 ITE SuperIO Port = 00h ITE SuperIO HWMonitor Port = 0000h ( 0000h / 0000h) ITE SuperIO HWMonitor MMIO = 00000000h (00000000h / 00000000h) ITE SuperIO Device ID = 0000h ( 0000h / 0000h) ITE SuperIO Version = 00h ( 00h / 00h) Winbond SuperIO Port = 2Eh Winbond SuperIO HWMonitor Port/60 = 0290h (0290h / 0000h) Winbond SuperIO HWMonitor Port/64 = 0A00h (0A00h / 0000h) Winbond SuperIO Device ID = D42Bh (D42Bh / 0000h) Winbond Sensor ID A3/5C/reg$58 = FF / FF / FF Fintek SuperIO Port = 00h Fintek SuperIO HWMonitor Port = 0000h (0000h / 0000h) Fintek SuperIO Device ID = 0000h (0000h / 0000h) SMSC SuperIO Port = 00h SMSC SuperIO HWMonitor Port = 0000h (0000h / 0000h) SMSC SuperIO Device ID = 0000h (0000h / 0000h) ASpeed SuperIO Port = 00h ------[ NCT6791 ISA Sensor Device at 0A00 ]------ 0000 95 7D D6 D0 80 02 00 D6 CB 42 4A 42 85 4D 70 69 0010 22 29 7F 10 2C 20 7F 2C 71 2A 2A 2A 2A 2A 2A 7F 0020 22 02 B7 B7 B7 B7 B7 B7 00 00 00 00 00 00 FF 1F 0030 FF 1F FF 1F FF 1F FF 1F FF 1F 00 00 00 00 00 00 0040 00 00 00 00 00 00 00 00 CC FF 1F CC B7 B7 B7 B7 0050 B7 B7 28 C0 00 00 00 39 00 00 00 00 00 00 00 00 0060 00 00 00 2A 00 FF FF 00 FF FF FF FF FF FF FF 00 0070 00 2A 00 01 00 22 29 00 FF FF FF FF FF FF FF FF 0080 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0090 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00A0 00 FF 00 00 FF FF FF FF FF FF FF FF FF FF FF FF 00B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 10 11 12 13 1B 20 52 71 73 75 T: 34 41 127 16 42 34 40 42 1 34 T: 34 41 127 16 42 34 44 42 1 34 T: 34 41 127 16 42 34 41 42 1 34 T: 34 41 127 16 42 34 39 42 1 34 T: 34 41 127 16 39 34 38 39 0 34 T: 34 41 128 16 39 34 37 39 0 34 T: 34 41 127 16 38 34 38 38 1 34 T: 34 41 127 16 38 34 37 38 1 34 T: 34 41 127 16 39 34 37 39 2 34 T: 34 41 127 16 40 34 37 40 3 34 0000 0001 0002 0003 0004 0005 0006 0007 0008 0009 000A 000B 000C 000D 000E 000F V: 93 7D D6 D0 80 03 00 D6 CB 42 4A 29 85 4E 70 69 [ VID = 1.30542 V ] V: 86 7D D6 D0 80 04 00 D6 CB 42 4A 29 85 4E 70 69 [ VID = 1.32019 V ] V: 86 7D D6 D0 80 04 00 D6 CB 42 4A 29 85 4E 70 69 [ VID = 1.32361 V ] V: 86 7D D6 D0 80 04 00 D6 CB 42 4A 11 85 4D 70 69 [ VID = 1.09485 V ] V: 86 7D D6 D0 80 04 00 D6 CB 42 4A 11 85 4D 70 69 [ VID = 0.88049 V ] V: 84 7D D6 D0 80 04 00 D6 CB 42 4A 11 85 4D 70 69 [ VID = 0.96521 V ] V: 84 7D D6 D0 80 02 00 D6 CB 42 4A 11 85 4D 70 69 [ VID = 1.27588 V ] V: 84 7D D6 D0 80 03 00 D6 CB 42 4A 3F 85 4E 70 6A [ VID = 1.01379 V ] V: 84 7D D6 D0 80 04 00 D6 CB 42 4A 1B 84 4E 70 6A [ VID = 1.31238 V ] V: 84 7D D6 D0 80 04 00 D6 CB 42 4A 1B 84 4D 70 6A [ VID = 1.17712 V ] ------[ ACPI Temperatures & Fans ]------ _TZ_.THM0._TMP : _TZ_.THM1._TMP : _TZ_.THR0._TMP : _TZ_.THR1._TMP : _TZ_.TZ00._TMP : <TYPE>0</TYPE><LEN>4</LEN><DATA>3010</DATA> _TZ_.TZ01._TMP : _TZ_.RTMP : _TZ_.RFAN : _TZ_.RFAN(0) : _TZ_.RFAN(1) : _SB_.ATKD._HID : <TYPE>1</TYPE><LEN>8</LEN><DATA>PNP0C14</DATA> _SB_.ATKD.TMPR : _SB_.PCI0.LPC0.EC0_.CCTV : _SB_.PCI0.LPC0.EC0_.LRPM : _SB_.PCI0.LPC0.EC0_.HRPM : _SB_.PCI0.SBRG.EC0_.ECPU : _SB_.PCI0.SBRG.EC0_.TACH(0): _SB_.PCI0.SBRG.EC0_.TACH(1): _SB_.PCI0.SBRG.EC0_.TAH0 : _SB_.PCI0.SBRG.EC0_.TAH1 : _SB_.PCI0.SBRG.EC0_.ST00 : _SB_.PCI0.SBRG.EC0_.SC01 : _SB_.PCI0.SBRG.EC0_.SC02 : _SB_.PCI0.SBRG.EC0_.SC03 : _SB_.PCI0.SBRG.EC0_.SC04 : _SB_.PCI0.SBRG.EC0_.SC05 : _SB_.PCI0.SBRG.EC0_.SC06 : _SB_.PCI0.SBRG.EC0_.TH0R : _SB_.PCI0.SBRG.EC0_.TH1R : _SB_.PCI0.SBRG.EC0_.F0TS : _SB_.PCI0.SBRG.EC0_.F1TS : _SB_.PCI0.PIB_.EC0_.TCRT : _SB_.PCI0.SBRG.EC0_.CTPM : _SB_.PCI0.SBRG.EC__.CPUT : _SB_.PCI0.SBRG.EC__.SYST : _SB_.PCI0.LPC_.EC0_.CTMP : _SB_.PCI0.LPCB.EC0_.CTMP : _SB_.PCI0.LPC_.EC0_.TMP1 : _SB_.PCI0.LPC_.EC0_.TMP2 : _SB_.PCI0.LPC_.EC0_.TMPI : _SB_.PCI0.LPC_.EC0_.TMPV : _SB_.PCI0.LPCB.EC0_.A1TP : _SB_.PCI0.LPCB.EC0_.A2TP : _SB_.PCI0.LPCB.EC0_.FAN0 : _SB_.PCI0.LPCB.EC__.TS1R : _SB_.PCI0.LPCB.EC__.TS2R : _SB_.PCI0.LPCB.EC__.TS3R : _SB_.PCI0.LPCB.EC__.F1FL : _SB_.PCI0.LPCB.EC__.F1FH : _SB_.PCI0.LPCB.EC__.F2FL : _SB_.PCI0.LPCB.EC__.F2FH : _SB_.PCI0.LPC_.H8EC.RTMP : _SB_.PCI0.LPC_.H8EC.LTMP : _SB_.PCI0.LPC_.H8EC.MTMP : _SB_.PCI0.LPC_.H8EC.GTMP : _SB_.PCI0.LPCB.H8EC.CTMP : _SB_.PCI0.LPCB.H8EC.DTMP : _SB_.PCI0.LPCB.H8EC.GTMP : _SB_.PCI0.LPCB.H8EC.ITMP : _SB_.PCI0.LPCB.H8EC.MTMP : _SB_.PCI0.LPCB.H8EC.STMP : _SB_.PCI0.LPCB.H8EC.PFAN : _SB_.PCI0.LPCB.EC0_.OTPC : _SB_.PCI0.LPCB.EC0_.VGAT : _SB_.PCI0.LPCB.EC0_.CHPT : _SB_.PCI0.LPCB.EC0_.CPUT : _SB_.PCI0.LPCB.EC0_.SYST : _SB_.PCI0.LPCB.EC0_.DTS1 : _SB_.PCI0.LPCB.EC0_.DTS2 : _SB_.PCI0.LPCB.EC0_.DIMM : _SB_.PCI0.LPCB.EC0_.FANH : _SB_.PCI0.LPCB.EC0_.FANL : _SB_.PCI0.LPCB.EC0_.CUTP : _SB_.PCI0.LPCB.EC0_.PHTP : _SB_.PCI0.LPCB.EC0_.DIMT : _SB_.PCI0.LPCB.EC0_.INLE : _SB_.PCI0.LPCB.EC0_.PANT : _SB_.PCI0.LPCB.EC0_.F0RM : _SB_.PCI0.LPCB.EC0_.F0DT : _SB_.PCI0.LPCB.EC0_.F1RM : _SB_.PCI0.LPCB.EC0_.F1DT : _SB_.PCI0.SBRG.EC0_.CUTP : _SB_.PCI0.SBRG.EC0_.PHTP : _SB_.PCI0.SBRG.EC0_.DIMT : _SB_.PCI0.SBRG.EC0_.INLE : _SB_.PCI0.SBRG.EC0_.PANT : _SB_.PCI0.SBRG.EC0_.F0RM : _SB_.PCI0.SBRG.EC0_.F0DT : _SB_.PCI0.SBRG.EC0_.F1RM : _SB_.PCI0.SBRG.EC0_.F1DT : _SB_.SAMB.TMPC : _SB_.SAMB.TMPH : _SB_.STR0._TMP : _SB_.STR1._TMP : _SB_.STR2._TMP : _SB_.STR3._TMP : _SB_.STR4._TMP : _SB_.STR5._TMP : _SB_.STR6._TMP : _SB_.STR7._TMP : CPUT : GPUT : SYST : FANT : BATT : [/code]

12700k, z690 strix e, 3080ti Windows 11 22h2 Condition 1: Aida64 set to run at startup, MSI Afterburner is not. Window does not pop up during gameplay in this condition. Condition 2 Aida64 already running, cpu voltage and vid reading shared to external apps. Start MSI Afterburner, Afterburner has CPU Voltage and Vid item accessed via the aida64 plugin After some time the aida64 window will open by itself stealing focus while gaming. The aida64 config file and afterburner configuration were copied from a 1680v2/R4E/1060/Windows10 configuration that does not present this issue. My suspicion is that it has to do with the fact the VID setting sporadically disappears in the sensors list. Edit: With further testing, it started to occur on the desktop as well. It looks like its actually a Windows 11 22621 issue with the plugin trying to respawn aida64 while its still running, this causes it to pop back up because its already open, you get the same behavior clicking on the aida64 shortcut while its already running. Its not reproduciable on 21h2 aida64.ini MSIAfterburner.cfg

Don't disable the page file.

not a bug, you have the windows setting that restores open applications enabled.

I've seen it mentioned on a number of occasions that SpeedFan is safe to use with Aida64, however on Asus boards this isn't exactly the case. When I have both running there is a high degree of chance that all the devices indicated to be accessed via ATK vanish. Is aida64 and Speedfan accessing these via the ATK0 driver (ASACPI.sys)? Systems in question are Rampage 3 and Rampage 4 extreme boards.

There is no such security concern, the application run at user level permissions cannot perforrm any kernel level escalation, all it can do is read (and not write to) the aida64 driver.

I've put this towards a vanguard user to try and get a repro and then forward onto AMD, theres clearly an issue with a driver mutex or kernel memory corruption when the two software are paired that needs to be investigated from there end.

Your BSOD is caused by a defective CPU or cosmic waves, contact Intel for a replacement.

Sensor and GPU Sensor info latency is massive, report the issue to nvidia, I'll notify ManuelG of this thread and to be on the watch for the feedback. https://forms.gle/kJ9Bqcaicvjb82SdA You might also go further and perform the following Use nsight to analyze your system for causes of hitching and stutters https://developer.nvidia.com/blog/using-nsight-systems-for-fixing-stutters-in-games/ Then follow on with these if it doesn't display a trigger or theres evidence the issue is in the nvidia driver. Performance reports require the user to submit a gpuview or gpu-z log. How to generating an event trace log for GPUView to troubleshoot performance issues/low FPS/game stutter https://nvidia.custhelp.com/app/answers/detail/a_id/3507/~/how-to-generating-an-event-trace-log-for-gpuview-to-troubleshoot-performance Collecting GPU logs using GPU-Z https://nvidia.custhelp.com/app/answers/detail/a_id/4749/ extended logs can be put on a filestorage host like google drive and their share link mailed to driverfeedback@nvidia.com For the LM78 sensor, disable EC (Embedded Controller) monitoring and iirc for this mainboard you turn Asus WMI on? Your issue is basically caused by multiple utilities on the system hitting the same sensors at the same time which is neither a safe or performant thing to do. Ie, don't run aida64 at the samet time as Hwinfo64, speedfan, corsair link etc.

These are listed as not supported on Processors that support either or both in some cases, meanwhile HWInfo64 is logging the time the processor is in the C6 state just fine.

By allowing the administrator account to set a persistent Start = 0x2 from within the Aida64 options, and change the task schedule to include the user account in the name of the Run at Startup task so multiple admins or users can choose to start it or not.

I see, well that would have to be a placeholder name, because the product is the Turing version of the Tesla T10 as shown running here

Why In the change notes do you have the T10-8 identified as a Geforce RTX, when this nomenclature is a Tesla part.? TU102 T10 Generation 8 Tesla board.

No, that didn't seem to work. I found why though, devices on the ASUSTOR driver are treated as a Raid device, so RAID Smart needs to be enabled.

Easy, here you go. The drive is currently on the ASUS UASP driver, but Smart was also missing on the mass storage driver, regardless both could pass through smart to Crystaldisk, and I can also see the data in HD Tune, SSD-Z, etc. diskctrldump.txt raiddump.txt smartdump.txt I also have a cable based on the ASM1351 on order so i can get trim working on this ssd, so i'll likely be back with dumps for that too after it arrives lol.

Hey Feiry, i grabbed a UASP sata 3 adapter cable produced by startech it uses the ASMedia - ASM1153E https://www.startech.com/au/HDD/Adapters/USB-3-SATA-adapter-cable-with-UASP~USB3S2SAT3CB Aida64 is unable to pull smart data from the drive attached, but CrystalDiskInfo has no such problem. Need a dump to add support? if so which ones.

Fiery, the feature this user wanted is possible. The drive itself can report what SATA mode it is in, but not all do so and seems more likely when the Drive is Sata Rev3 / 6Gb with some exceptions being ODD's The utility SSD-Z implements it. Attached to Intel ICH10 sata Attached to Marvel SATA 6G Attached to JMI E-Sata

Interestingly enough, the fields are now visible, seems that this information is not presented by hotplugged drives?

This is resolved by 417.71+

Something strange with AIDA64's support of this. It seems aida64 lacks the active udma field on some drives declaring them to be running in MWDMA 0 or 2, meanwhile HDD Scan and HD Tune both agree that the current active mode is UDMA6 for those drives, and buffered read tests come back as expected.

yeah, there was an issue from 397.65 to 411.63.

what driver have you got installed?

this might be fixed in 411.63

Aida64 is just a victim to nvidia's unstable NVAPI code at the present time.