Fiery

If the fan spins at high RPM, but you still cannot feel the hot air coming out through the exhaust port(s), then it could well be a blocked exhaust port due to dust filling up on the inside of the laptop chassis. I don't think it could be a power supply issue, nor do I think you could upgrade the fan. In most cases there is simply no room for a bigger or better fan inside the laptop chassis, so even if you found a larger fan, you wouldn't be able to install it. I would take the laptop to a professional, and have it disassembled and completely cleaned. If that doesn't solve the issue, and you have to keep the machine, then maybe you could try downclocking the nVIDIA GPU and/or the CPU to prevent the chassis from getting too hot. BTW, a cooling pad will not help at all if a single component (like the GPU chip) is getting too hot on the inside of the laptop chassis. Even if you use a cooling pad, you have to make sure the airflow is properly vented out of the chassis.

All those issues are due to a very rare anomaly that causes AIDA64 to misidentify the motherboard. Then sensor adjustments will not be used properly, and that will cause temperature and fan labelling issues, etc. In the past few weeks we've been trying desperately to reproduce the anomaly on our own test systems, but without luck so far. Can you please let us know more about your software configuration? 1) What Windows version do you have running? Do you have all security packs and hotfix updates applied? 2) Do you have UAC enabled? 3) When you say "I reboot", do you mean you perform shutdown and then start the machine again, or you perform a Windows restart? 4) Does the issue come up after every reboot, or only like 1 out of 5 reboots, or 1 out of 10 reboots? 5) Do you have AIDA64 configured to start automatically at Windows bootup? 6) What version of AIDA64 do you have installed? Did you install it using the EXE package, or just extracted the ZIP package into a folder? If the latter, then what folder do you have AIDA64 files in? "CPU Package" is a value that is measured and reported by the CPU itself. It represents the overall CPU temperature, so it's not broken down to individual cores.

Yes, but yours is a special case

FYI, we've implemented the necessary sensor adjustments for Asus X99M-WS motherboard in the following new AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta

Not really, since that hidden feature is not supposed to be used at all. The JPEG size limiter is supposed to work automatically, without user intervention.

Great job, and thank you for posting your results. Have a great weekend Regards, Fiery

Try to move RemoteSensor to a different TCP/IP port, like 8080, it should help.

Thank you for letting us know about the resolution. However, when you disable both RAID SMART support and RAID member enumeration, AIDA64 is not supposed to be affected by potential issues about the RAID firmware. So it's still a weird issue, a real "head-scratcher" for us

Are you sure your video card is able to measure its own fan RPM? Can you see that reading in any software, e.g. HWMonitor or GPU-Z?

Thank you for the data. Looking at the registers, I'd say the issue is that the fan is stopped, not spinning. Please don't mix fan speed (RPM) and fan duty cycle (%). Duty cycle only means what speed is requested by the fan controller. Even a stopped or missing fan could be configured to any duty cycle. Please also do not link (couple) the motherboard sensor readings (like motherboard temperature, +12V voltage reading, etc) and the GPU fan or GPU temperature readings. They come from different sensor chips using different interface. X99-E WS, the motherboard itself is well supported, while X99-M WS is not fully supported yet. As for your GPUs, they both should be well supported, regardless of which motherboard do you install them in. As for serial keys, please note that a single AIDA64 Extreme license can be used on up to 3 computers: http://www.aida64.com/licensing

As for the GTX750Ti issue, please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic, or attach it as a TXT file to your post. You may need to enable status bar first in AIDA64 / main menu / View. Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach it as a TXT file to your post. Thanks, Fiery

Please be a bit more patient, it's only been 10 hours since you've opened this topic As for your issue, X99-E WS should be well supported already. After upgrading to a new beta, make sure to restart Windows to apply the changes. Also make sure your Windows user have administrator privileges. If you can still find an error about the sensor adjustments, please let me know exactly which readings are inaccurate. As for X99-M WS, that motherboard is indeed not supported yet. We'll implement support for it in the next AIDA64 stable update due next week. If you wish, I can send you a beta update tomorrow though, if you prefer to get the bug fix ASAP.

Thank you for your kind words. BTW, the whole AIDA64 RGB LED module idea came from one of Logitech's hardware engineers who is a big fan of AIDA64 and wanted to see what can we do about supporting their LED SDK and the great G910

No need to blame yourself, it's not an obvious or common issue about software registation in general. Happy Holidays

Your CPU seems to be running quite hot. Are you sure your notebook is not overheating under load? Try to check if the exhaust ports for the cooling solution are not blocked by dust from the inside. Also check if the fan is spinning inside the notebook when it's running hot.

You need to check if the system date is properly set on all your computers. AIDA64 will refuse to accept the license key if the system date is not set to today. Regards, Fiery

It's only available via editing the AIDA64.INI file. Look for the following line in it: HWMonSPLCDJPEGLimit=0

Make sure to install our Samsung SPF drivers that includes libusb DLL and libusb-compliant USB driver as well: http://download.aida64.com/resources/lcd/samsung_spf_lcd_driver.zip After installing this driver, you should be able to activate Samsung SPF LCD support in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Samsung. If you get a positive feedback there (saying LCD init is OK), you can start building your own LCD layout in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD Items.

CPU throttling is a technique used by modern Intel processors to prevent themselves from overheating. The CPU detects when it gets close to TJMax (maximum operating temperature basically), and then it starts stopping its execution pipelinesfor a moment. That pipeline stopping trick is what they call throttling. 38% means for 380 milliseconds out of 1 second the pipeline was stopped, so the CPU did an actual processing work only 62% of the time.

Those items measure the values for logical drives (like C: or Z:) Disk activity measures the values for physical drives. One physical drive may have 0, 1, 2 or more logical drives assigned to.

Only full per-key RGB keyboards are supported by the AIDA64 RGB LED module. And with an integrated big LCD screen, it wouldn't make much sense to hassle with the individual keys anyway.

We haven't yet found a reliable way to may phyiscal drives to drive letters. You can peek into the Task Manager though, to find that out. The only difference is that Task Manager calls the first disk Disk #0, while AIDA64 calls the same disk Disk #1.

The only way to achieve that right now is by making sure the GPU fan is spinning. You can only configure the GPU fan RPM item when the fan is spinning.

Yes, you're right. When the GPU provides a zero RPM reading, it's not easy to decide whether it's because you've got a passively cooled video card, or because the fan is not spinning at the moment. As soon as it spins up, the reading will be displayed. And when it stops, the latest zero RPM reading should be displayed from then on.

Looks great, thank you for the feedback!