Jump to content

nfsking2

Members
 View Profile  See their activity

  • Posts

    12

  • Joined

  • Last visited

 Content Type 

Posts posted by nfsking2

    Huge performance drop in AIDA64 Memory&Cache Benchmark after Hyper-V was enabled in Windows 11

    in Benchmarking, system performance

    Posted

    1 hour ago, Fiery said:

    On certain Intel processors, before the Ice Lake and Rocket Lake era, suffer from this issue under Windows 11.  You need to disable Memory Integrity to get proper BCLK and CPU core clock measurement, as well as accurate benchmark results.  Even Intel's own tool (XTU) suffers from major issues under Windows 11, so it's definitely not a bug in AIDA64 but a serious limitation that Microsoft introduced in Windows 11.  One that causes headaches to both Intel and us.

    AMD processors do not suffer such limitations under Windows 11, but there used to be other problems about them under Windows 11 that Microsoft resolved by now.

    Thanks for your reply Fiery!

    I have checked Memory Integrity setting in Windows Defender and it was disabled, but the problem still existed.

    And the problems you mentioned on AMD processors, I think you meant high L3 latency which had been fixed by Microsoft recently?

    Huge performance drop in AIDA64 Memory&Cache Benchmark after Hyper-V was enabled in Windows 11

    in Benchmarking, system performance

    Posted

    I got an Intel NUC8i7HVK (or known as Hades Canyon).

    It came with an Intel i7 8809G CPU running at 4.5GHz (overclocked), 16GB*2 DDR4-3200 CL19 (overclocked).

    I recently updated my system to Windows 11 and enabled the Hyper-V function which was required by Windows Subsystem for Android (WSA).

    Then I found that the CPU and RAM speed was wrongly recognized by AIDA64. It reported that the CPU was running at around 1100MHz and RAM clock was about 600MHz (but Windows task manager still reported correct clock speed).

    When running the Memory&Cache Benchmark, I could only managed to get about 6xxxMB/s read speed, 8xxxMB/s write speed and 7xxxMB/s copy speed, and the memory latency was high up to more than 380ns. The CPU cache speed was also much slower than it should be.

    I tried to restore BIOS settings to default but with no help. As soon as I have disabled Hyper-V function in Windows Control Panel, AIDA64 could detect correct clock speed, and benchmark results were also back to normal.

    I have another PC laptop which is based on AMD platform (5900HS, 40GB DDR4-3200). When Hyper-V was enabled and WSA installed on this PC, no any familiar issue occurred at all.

    So I was confused, who is to be blamed for this issue? Microsoft, or Intel? Or it was just a bug from AIDA64?

    fixed: AIDA64 v2.50.2042 BSoD with Intel RSTe v3.2.0.1135 WHQL RAID driver

    in Bug reports

    Posted

    When both RAID options are disabled, AIDA64 will use standard Windows API calls to detect ATA devices and to acquire SMART attributes list incl. disk temperature (if available). It means, if that causes a BSoD, it is caused by the storage controller driver, so it should be the fault of Intel RSTe drivers rather than AIDA64's.

    Thanks for reply.

    But without AIDA64 running in the background, the BSOD won't happen.

    fixed: AIDA64 v2.50.2042 BSoD with Intel RSTe v3.2.0.1135 WHQL RAID driver

    in Bug reports

    Posted

    I too have been experiencing blue screens and it seems to be due to aida64. Have used a64 for a long time but just updated my computer and since then I get usually 1 blue screen crash per day and the log points to iastora.sys. I have tried removing the Intel RST drivers and still got the same blue screen errors. I am now running the RST 3.5.0.1092 drivers (cause the intel ssd toolbox doesn't work properly without them) Since I saw a thread about a64 I decided to turn it off and have since had no blue screens. I am currently running a64 again and have turned off low level smart operations in the stability options to see if that makes any difference. Attached are the windows minidumps and the aida system report. I will report back when I have more data.

    Thanks

    Same RST version, same issue.

    Every times after the system running for a long time (about 5hrs), I've got BSOD with the error code:D1.

    My SSD is Plextor M5 Pro, not Intel, so there is no any kind SSD toolbox or something like it running background.

    BTW, the both RAID options in Preferences / Stability are disabled.

    fixed: AIDA64 makes ThinkPad crash

    in Bug reports

    Posted

    Thanks for the info. It's quite odd that noone else (out of those users you mentioned) reported this issue to us. And stating that all of them face this issue is even more odd...

    Just to clarify: if you start AIDA64 on such notebooks with its default settings (so OSD Panel not activated, Sidebar support not activated), and you just leave it sitting on the main screen, does it still lock up after a while?

    Yes, no matter leaving it on the main screen or minimizing it to the background, the laptop will be locked up after a few minutes.

    The odd thing is, the laptop won't be locked up as soon as AIDA64 start up, but after a couple minutes. Maybe it's because the AIDA64 will update some kind of sensor information after a period?

    fixed: AIDA64 makes ThinkPad crash

    in Bug reports

    Posted

    Does it lock up while it is measuring some sensor values? In other words, do you have such features like the OSD Panel, Logitech LCD, Vista Sidebar, Logging, Alerting, SensorPanel, or External Applications activated?

    No, no any external applications.

    I'm using Logitech LCD and sidebar on my desktop computer, there is no such issue.

    And I'm not the only person encounter this problem. As I mentioned above, ALL the ThinkPad X201i, X201, T410 users encountered this issue.

    fixed: AIDA64 makes ThinkPad crash

    in Bug reports

    Posted

    AIDA64 (ver. 2.20.1839 beta) will make the system freeze after running for about 10 minutes (no stability test, no performance test). No BSOD, just freeze, the only thing I can do is to press and hold the power button to do a forced shutdown.

    This problem happen on EVERY Lenovo ThinkPad X201, X201i, X201T and T410 (probably even more models) under Windows 7 64bit, no mater what kind of hardwares are inside.

    BTW, the old version Everest has the same issue.

    AIDA64 v2.00.1754 cannot report the SMART infos of hard disks on Intel X79 chipset

    in Bug reports

    Posted

    Please have this option enabled, and right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic.

    BTW, what version of Intel RST drivers do you have installed?

    Thanks,

    Fiery

    ------[ AIDA64 v2.00.1754 Beta ]------

    ------[ Microsoft Windows 7 Ultimate 6.1.7601 Service Pack 1 (64-bit) ]------

    ------[ Motherboard Info ]------

    Motherboard ID : 63-0100-000001-00101111-102010-Chipset$1APEQ006_BIOS DATE: 11/23/11 13:37:22 VER: 08.03

    Motherboard Model : Asus Rampage IV Extreme

    Motherboard Chipset : Intel Patsburg X79, Intel Sandy Bridge-E

    DMI MB Manufacturer : ASUSTeK COMPUTER INC.

    DMI MB Product : RAMPAGE IV EXTREME

    DMI MB Version : Rev 1.xx

    DMI MB Serial : 112610180001013

    DMI SYS Manufacturer: System manufacturer

    DMI SYS Product : System Product Name

    DMI SYS Version : System Version

    DMI SYS Serial : System Serial Number

    DMI BIOS Version : 0803

    ------[ SMART List ]------

    <ORD>A0001</ORD><MODEL>ATA PLEXTOR PX-128M</MODEL><SERIAL>002141100397</SERIAL><REV>1.06</REV><DEVTYPE>SATA</DEVTYPE><SPTIPATH>\\?\scsi#disk&ven_ata&prod_plextor__px-128m#4&19bf6b6&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}</SPTIPATH><SPTITEMP>1</SPTITEMP><PRIORITY>5</PRIORITY><MODSER>ATA PLEXTOR PX-128M</MODSER><LASTTEMP>255</LASTTEMP>

    <ORD>A0002</ORD><MODEL>ATA ST31000528AS</MODEL><SERIAL>9VP2ZY91</SERIAL><REV>CC38</REV><DEVTYPE>SATA</DEVTYPE><SPTIPATH>\\?\scsi#disk&ven_ata&prod_st31000528as#4&19bf6b6&0&020000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}</SPTIPATH><SPTITEMP>1</SPTITEMP><PRIORITY>5</PRIORITY><MODSER>ATA ST31000528AS</MODSER><LASTTEMP>255</LASTTEMP>

    <ORD>A0003</ORD><MODEL>ATA WDC WD20EARS-00M</MODEL><SERIAL>WD-WCAZA4719879</SERIAL><REV>AB51</REV><DEVTYPE>SATA</DEVTYPE><SPTIPATH>\\?\scsi#disk&ven_ata&prod_wdc_wd20ears-00m#4&19bf6b6&0&040000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}</SPTIPATH><SPTITEMP>1</SPTITEMP><PRIORITY>5</PRIORITY><MODSER>ATA WDC WD20EARS-00M (WD-WCAZA4719879)</MODSER><LASTTEMP>255</LASTTEMP>

    <ORD>A0004</ORD><MODEL>ATA WDC WD20EARS-00M</MODEL><SERIAL>WD-WCAZA3494835</SERIAL><REV>AB51</REV><DEVTYPE>SATA</DEVTYPE><SPTIPATH>\\?\scsi#disk&ven_ata&prod_wdc_wd20ears-00m#4&19bf6b6&0&050000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}</SPTIPATH><SPTITEMP>1</SPTITEMP><PRIORITY>5</PRIORITY><MODSER>ATA WDC WD20EARS-00M (WD-WCAZA3494835)</MODSER><LASTTEMP>255</LASTTEMP>

    <ORD>A0005</ORD><MODEL>ATA WDC WD20EURS-63S</MODEL><SERIAL>WD-WCAZA4802603</SERIAL><REV>AB51</REV><DEVTYPE>SATA</DEVTYPE><SPTIPATH>\\?\scsi#disk&ven_ata&prod_wdc_wd20eurs-63s#4&19bf6b6&0&030000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}</SPTIPATH><SPTITEMP>1</SPTITEMP><PRIORITY>5</PRIORITY><MODSER>ATA WDC WD20EURS-63S</MODSER><LASTTEMP>255</LASTTEMP>

    <ORD>A0006</ORD><MODEL>ATA WDC WD740ADFD-00</MODEL><SERIAL>WD-WMANS1564702</SERIAL><REV>7QR4</REV><DEVTYPE>SATA</DEVTYPE><SPTIPATH>\\?\scsi#disk&ven_ata&prod_wdc_wd740adfd-00#4&19bf6b6&0&010000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}</SPTIPATH><SPTITEMP>1</SPTITEMP><PRIORITY>5</PRIORITY><MODSER>ATA WDC WD740ADFD-00</MODSER><LASTTEMP>255</LASTTEMP>

    <ORD>R0008</ORD><MODEL>PLEXTOR PX-128M2P</MODEL><SERIAL>002141100397</SERIAL><REV>1.06</REV><IDBUFSIZE>512</IDBUFSIZE><RAIDMEMBER>1</RAIDMEMBER><SMARTINFO>1</SMARTINFO><INTSASSMARTCTRL>4</INTSASSMARTCTRL><INTSASSMARTDEV>7</INTSASSMARTDEV><PRIORITY>9</PRIORITY><MODSER>PLEXTOR PX-128M2P</MODSER>

    The RST driver version is " Intel® Rapid Storage Technology Enterprise Driver 3.0.0.1112"

×
×
  • Create New...