Fiery

Please send me your full name, email address and the approx. purchase date in private message, and I'll send you your product key. Regards, Fiery

We've implemented a workaround for the tCAS issue after resuming from sleep. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2536f5mtnpwq1lzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Please note that now AIDA64 implements 3 different methods to read tCAS on Intel Lynnfield, Bloomfield, Gulftown and Westmere processors, but none of them is perfect Somehow Intel forgot to implement a proper tCAS detection register in the mentioned CPUs. It should work fine on your particular motherboard from now on though

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

We've implemented support for the onboard CHL8328 VRM chip of your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2536f5mtnpwq1lzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. With this beta you'll see new items on the Sensor page. The most important one would be the CPU VRM voltage, which hopefully would indicate the right Vcore voltage you're looking for. Let me know how it works.

It's two memory channels per processor node. A 12-core Magny-Cours processor has 2 nodes, so a single processor package supports 4 memory channels. It effectively works as two 6-core processors (each supporting 2 memory channels) put into a single CPU package.

Yes, those values are already available as a SensorPanel item. It's also available on the OSD Panel, Desktop Gadget and Logitech LCD item. But please note that not all motherboards are capable of monitoring such values. Regards, Fiery

1) Do you have 2 or 4 processor sockets populated? 2) Do all processors have DDR3-1333 memory installed? So every processors use the same memory configuration? In case you have 4 processor sockets populated, and every processors use the same DDR3-1333 memory configuration, that would mean you've got 16 memory channels total, each running at DDR3-1333 speed, which would mean a total memory bandwidth of 166.6 GBytes/sec. Hence the results could well be accurate The confusion may come from the fact that AIDA64 (the main application itself) only supports up to 32 processor threads, so it cannot show you all processors on the Cache & Memory Benchmark Panel. However, the multi-threaded memory benchmarks support up to 64 processor threads, so it can utilize all 48 processing threads you've got in your system (if you have all 4 processor sockets populated, each with a 12-core Magny-Cours CPU). Regards, Fiery

Thank you. If it's possible, please try removing the Master Volume item from your SensorPanel (backup your AIDA64.INI file before doing this), and let me know if it makes the thread creation error go away. If it doesn't help, then please try removing the NIC rate items as well. Let me know if it makes a difference. Thanks, Fiery

The label System Cooler indicates any sort of coolers that aren't for CPU cooling. We use the term cooler to make sure it could be used for both cooling fans and water cooling solutions as well. What we can do is add 2 more System Cooler fields, and also a bunch of Misc Devices fields to make sure you can enter more devices in there. We'll do that in the next AIDA64 beta release due in a few days Regards, Fiery

Thank you. Do you use IXTU to adjust your memory timings, or do you only do overclocking and fine-tuning using the BIOS Setup?

Thank you for the data. There shouldn't be any collision with CPU-Z and CoreTemp, but maybe one of them (or another software) reconfigures IMC (Integrated Memory Controller) registers. Please create a new PCI Dump in case you find the timings bad again. As for the beta release, it's up to you. Your motherboard is well supported by AIDA64 v3.00 stable release as well.

We've checked it on our Intel DP55SB motherboard with Core i7-860 CPU, and couldn't reproduce the issue So it may be related to motherboard model or BIOS release. Please help us by sending us some data of your configuration: 1) When the CAS Latency is correct (before sleep), please right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Copy-paste the full results into this topic. 2) Then repeat that when the CAS Latency is wrong (after sleep). MC0 and MC1 are the two memory controllers of your processor. MC = Memory Controller. Thanks, Fiery

We've tested it on our Asus Z87-Pro motherboard, and it seems this issue is due to a BIOS bug of Asus Z87 Series boards. We've notified Asus about this issue, hopefully they will fix their BIOSes. I'm not quite sure however why only Windows 8.1 throws a BSoD when reading from the invalid memory address provided by the ACPI BIOS. It works similarly on our test systems: under Win7 and Win8 no BSoD is generated, the memory reading simply fails. Until Asus could fix the BIOS, we'll implement a workaround in AIDA64 to avoid the BSoD. It will be rolled out as a new AIDA64 beta release in a few days. Thanks, Fiery

What motherboard and processor do you have? Thanks, Fiery

Industry standard memory module temperature monitoring is called DIMM-TS (TS = Thermal Sensor). You can activate that feature in AIDA64 / main menu / File / Preferences / Stability. You don't need anything else, it can be any motherboard or CPU, as long as your memory module does have a DIMMTS compliant thermal sensing diode. In case DIMM temperature(s) do not appear on the AIDA64 Sensor page after enabling that feature (and after restarting AIDA64), then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full), and copy-paste the full results into this topic.

Great news! One of you please try it with AIDA64, and report us the results Thanks, Fiery

CPU utilization measurement shouldn't collide with each other, even without synchronization. What would cause a collision is the low-level hardware interrogation features, like sensor readings (temperature, voltage, fan speed measurement). But most of the software out there are synchronized together, so only those software could cause a headache that don't use synchronization. Some of the software that do use synchronization: AIDA64 (of course ) CoreTemp CPU-Z EVGA E-LEET GPU-Z HWiNFO32/64 HWMonitor Motherboard Monitor MSI Afterburner Rivatuner SIV SpeedFan One of the software that doesn't use synchronization, even though their authors were asked numerous times to do so: Asus AI Suite.

Done, thank you

I'm glad you've made progress about this issue. And yes, you can use AIDA64 v3.00 or even the latest v3.00.2529 Beta release as well.

Thank you, we'll fix that in the next AIDA64 beta release due next week

PrefetchW should be the line "AMD 3DNowPrefetch", but regular AMD 3DNow! supporting processors also support PrefetchW. It is not supported by current Intel processors, but Windows 8.1 will still work on them. I admit it's quite odd We've asked Intel, and they said PrefetchW can be executed on current Intel processors, although it is executed as NOP (no operation / no instruction). AFAIK next-generation Intel Core processors codenamed Broadwell will officially support PrefetchW. Regards, Fiery

That's very creative, thank you for posting it

Please avoid posting your issues into multiple topics. I've replied in your other topic. This topic closed.

It depends on your video driver

It looks absolutely normal. That list shows the installed video adapters, as they're managed by Windows. Windows installs one video adapter for every display outputs, so if you have a dual-output (e.g. DVI + HDMI) video card, then you will have 2 adapters listed there. Regards, Fiery