Fiery

Please find the latest AIDA64 beta release at: http://www.aida64.com/downloads/aida64extremebuild1913tqrs2v6chnzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Please post a screen shot that shows HWMonitor readings and AIDA64 Computer / Sensor page side-by-side, so we can compare the readings against each other. Thanks, Fiery

What I can tell you is that apart from this topic, we never got any bug reports about ThinkPad and AIDA64 incompatibility or stability issues. When we tested ThinkPads in the past, we haven't found any issues. Truth be told, we didn't try to run ThinkPad Power Manager and AIDA64 together to try and see if there's a collision between them. Our current test hardware collection doesn't include any ThinkPads, but in case multiple users can confirm here (in this topic) that there's a definitive issue about one or more ThinkPad models while running AIDA64, then we can arrange to get an affected notebook part, and try reproducing the bug and then fixing it.

Rendition seem to be a bit "lazy", since they only rebrand the Crucial (Micron) memory modules, without altering the SPD block to put their manufacturer ID replacing Crucial's there. The reason behind that may be that Rendition doesn't have a JEDEC manufacturer's identification code allocated (yet). BTW, Micron makes great memory modules, so there's nothing wrong with your memory module, no matter what the SPD manufacturer code says Regards, Fiery

1) Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Copy-paste the full results into this topic. Thanks, Fiery

What version of Comodo Internet Security do you have installed?

1) We'll add the "Save Report" line to the language modules soon. 2) Those 3 lines are not meant to be translated. 3) We'll fix this issue in the next AIDA64 beta release. Thanks, Fiery

I don't think the motherboard temperature reading is stuck. In this dump you have 30 Celsius, while in your other topic the motherboard temperature is 32 Celsius. Hence it does change. Make sure to compare AIDA64 sensor readings against ASRock F-Stream readings. If you see a discrepancy there, please post a screen shot that shows AIDA64 Sensor page and F-Stream readings next to each other (side-by-side), so we can compare the values.

Thank you. Can you see a North Bridge temperature or South Bridge temperature measured in the BIOS Setup or in ASRock's own monitoring application called F-Stream?

Is the motherboard temperature stuck in ASRock's own monitoring application (F-Stream) as well? If you try that application, then please let us know what version of it do you have installed. Thanks, Fiery

Thank you for the feedback The RSoD occured when AIDA64 tried to read the video BIOS flash image. On pre-Kepler GeForce GPUs there was a GPU register that AIDA64 had to alter to read the image from the flash chip. On GeForce 600 Series (Kepler, GK1xx) that register doesn't exist anymore, but still, altering it sometimes triggered the driver to throw a RSoD. It didn't actually lock the machine or AIDA64, but it was annoying for sure The RSoD doesn't occur in other software because most diagnostic software doesn't read video BIOS flash image from video adapters. And even in AIDA64 it was very rare to occur.

Core i7-965 with Triple Channel DDR3-1333 and X58 chipset has a theoretical memory bandwidth of 32000 MB/sec. AIDA64 measures 13899 MB/sec memory read bandwidth (cca. 43% of theoretical bandwidth). Core i7-3960X with Quad Channel DDR3-1600 and X79 chipset has a theoretical memory bandwidth of 51200 MB/sec. AIDA64 measures 16788 MB/sec memory read bandwidth (cca. 33% of theoretical bandwidth). So as you can see, with only a single thread it's not possible to get close to even half the theoretical memory bandwidth of such platforms. That explains why in single-threaded applications (like most 3D games) it doesn't matter if you use more than 2 channels for your memory While in heavily multi-threaded applications multi-channel memory configurations look much better. We don't yet have a beta of the multi-threaded memory benchmarks. We expect to roll the new memory benchmarks out in the 2nd half of 2012. It will be a major change, since all memory scores will change in the switch, so the new benchmarks will debut with a major AIDA64 version update -- probably v3.00. BTW, in the first half of 2012 we'll update other benchmarks like CPU PhotoWorxx to implement SSE and AVX optimizations. Thank you for your feedbacks on the Intel RSTe driver issue.

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. 3) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. Thanks, Fiery

Thank you. So VTT is actually measured by the sensor chip of your motherboard. Quite odd that neither the BIOS Setup or ET6 shows the measured voltage value. Anyway, it will be implemented in the next AIDA64 beta release due next week

Then please configure 2 different VTT levels in the BIOS Setup, and copy-paste the relevant AIDA64 ISA Sensor Dumps, indicating what VTT level is configured. Thanks, Fiery

Thank you for the feedback! AFAIK VTT voltage cannot be measured on your motherboard. That's why it's missing from the BIOS Setup HW Monitor page and ET6 sensor page as well.

We've fixed the RSoD issue in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1911np6gm0bjczzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1911np6gm0bjczzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Meanwhile we've performed a few test runs with various RAID settings and configuration on our own X79 test system. With RST Enterprise 3.0.0.3020 WHQL driver AIDA64 startup is indeed noticably slow, although the delays we've experienced were no longer than 5 seconds. With RST Enterprise 3.0.1.7016 WHQL driver AIDA64 startup was much quicker, with no noticable delays due to RAID scanning. So if it's possible, please use the latest RSTe WHQL driver of 3.0.1.7016. Hopefully it fixes the issues on your system. If not, then you can still disable the RAID member enumeration in the AIDA64 Preferences

Please try to enable the option RAID SMART support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps. If not, then please let us know more about your system configuration, e.g. motherboard model, IDE or AHCI or RAID mode selected for your SATA controller, any RAID arrays defined, AIDA64 version? Thanks, Fiery

Thank you for the tests. If you don't plan to use RAID arrays in your system, then you can simply disable RAID member enumeration in AIDA64 / main menu / File / Preferences / Stability. In case you cannot get AIDA64 to load due to this issue, then go to AIDA64 installation folder, and create a new AIDA64.INI file by writing only these 3 lines into it: [Generic] LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 BTW, since at Intel RAID scanning we're doing everything "by the book", and full SMART details are unavailable even when it loads up fine, all we can hope for is that Intel will soon release a proper, fixed RST Enterprise driver. BTW #2, have you tried to use the latest Intel RST Enterprise driver 3.0.1.7016 WHQL? Maybe it would help about the slowdown. --- As for the quad-channel memory bandwidth results, they are actually accurate. The single-threaded memory bandwidth performance -- that AIDA64 currently measures -- doesn't scale when going from 2-channel to 4-channel configuration on X79 systems. We're already working on multi-threaded memory bandwidth benchmarks: they will be able to properly measure the performance improvement due to 3+ memory channels. Regards, Fiery

IMHO "Aux" is the actual system temperature, "CPU" is labelled right. I'm not sure where PCH temperature comes from. If it's possible, please check if "Motherboard" in AIDA64 may be the actual PCH temperature with an offset. Thanks, Fiery

Thank you. We'll fix that in the next AIDA64 beta release.

Rampage IV Extreme uses a peculiar bank switching mechanism on its EC (Embedded Controller) chip. Due to the collision between AI Suite 2 and 3rd party applications, potentially it would be dangerous to switch EC banks from AIDA64. Hence AIDA64 only reads the sensor values available in the default EC bank (which is bank #0).

We're working on it. Later this year we'll introduce multi-threaded memory bandwidth benchmarks, a new memory latency benchmark, a revamped CPU PhotoWorxx benchmark, etc. So stay tuned