Fiery

Thank you. Please upgrade to AIDA64 v5.50.3600 (stable update), and send us an updated set of debug dumps of: ISA Sensor Dump SMBus Dump (Full) Embedded Controller Dump (the last one is necessary because you've got a high-end Asus ROG motherboard that uses special EC sensor besides the regular ISA sensor chip) Thanks, Fiery

Thank you in advance. It would be imperative to see exactly which software (or Windows itself) pops up the error message, and what the message says exactly. Because AIDA64 is not supposed to show a warning about low memory, unless of course you enabled the Alerting feature in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Alerting

No, there's nothing wrong with your CPU. Haswell and Devil's Canyon processors tend to work at extremely high temperatures and it's normal that they start throttling under very demanding stress. The FPU subtest of AIDA64 System Stability Test (SST) is designed to put the processor under the heaviest load, and so drive its working temperature to the maximum. You should however let it run for several hours. 5 minutes is great to see if there's an immediate issue, e.g. you get a BSoD or such. As for the other subtests of the AIDA64 SST, you should simply enable them all, and let it run for several hours. Drawing a conclusion of the stress tests is easy: if any error message pops up, your computer restarts, locks up, powers off suddenly, or a BSoD is shown, then your computer is not stable. If the test keeps working without any negative feedback for several hours, then it's a pass. Just make sure to run it in both modes: first with only the FPU subtest enabled, that is the thermal stress test. And the second time with all subtests enabled, that is the general stress test using a more diverse workload. Regards, Fiery

Samsung SM951-NVMe hasn't got a proper firmware at this time, and so it cannot report SMART attributes at all. Not even Samsung's own SSD companion software (Magician) supports it. Hopefully Samsung will soon roll out a new firmware to fix those issues. As soon as the drive gets the proper features in its firmware about SMART interrogation, it will start working with AIDA64 as well. If not, or if you will see any issues, please let us know, and we'll fix it up right away. BTW, the explained firmware deficiency of SM951-NVMe is why we promote the new AIDA64 feature as: "Autodetect information and SMART monitoring for Intel NVMe SSDs" As opposed to describing it as: "Autodetect information and SMART monitoring for NVMe SSDs"

AIDA64 already provides a lot more SMART information on Intel NVMe SSDs than for classic SSDs What kind of information do you miss? Regards, Fiery

What kind of warning is displayed by AIDA64? Can you please post a screen shot? Based on your posts I assumed Windows gives you the warning messages, and not AIDA64 itself.

The latest AIDA64 update introduces monitoring of sensor values on RGB LED keyboards, implements enhanced support for Intel NVMe SSDs and LGA-1151 motherboards, and supports the latest graphics and GPGPU computing technologies by both AMD and nVIDIA. New features & improvements - Support for Corsair K65, Corsair K70, Corsair K95, Logitech G910 and Razer Chroma RGB LED keyboards - Support for LGA-1151 motherboards - Autodetect information and SMART monitoring for Intel NVMe SSDs - Preliminary support for AMD Bristol Ridge APUs - Preliminary support for Intel Broadwell-E/EN/EP/EX processors - Sensor support for NZXT Kraken water cooling systems - Support for USB 3.1 peripherals - Extended ACPI table decoding - OpenGL ES 3.2 support - Advanced support for Adaptec and Marvell RAID controllers - Support for Kingston HyperX Predator, Plextor M6V, SanDisk Z400s and SK Hynix SC300 SSDs - GPU details for AMD Radeon R9 Nano and nVIDIA GeForce GTX 950 What's new since AIDA64 v5.00 - Microsoft Windows 10 RTM and Windows Server 2016 support - RemoteSensor smartphone and tablet LCD integration - Logitech Arx Control smartphone and tablet LCD integration - AVX2 and FMA accelerated 64-bit benchmarks for Intel Skylake and Broadwell-H CPUs - AVX and SSE accelerated 64-bit benchmarks for AMD Nolan APUs - Optimized 64-bit benchmarks for AMD Carrizo APUs - Optimized 64-bit benchmarks for Intel Braswell and Cherry Trail processors - AVX2 and FMA accelerated 64-bit benchmarks for Intel Broadwell CPUs - Preliminary support for AMD Stoney APUs - Preliminary support for Intel Cannonlake, Goldmont and Skylake-E/EN/EP/EX processors - AlphaCool Heatmaster II, Aquaduct, Aquaero, AquaStream XT, MPS, PowerAdjust 2, PowerAdjust 3 sensor devices support - Thermaltake DPS-G power supply unit sensor support - Support for Gravitech, LCD Smartie Hardware, Leo Bodnar, Modding-FAQ, Noteu, Odospace, Saitek Pro Flight Instrument Panel, Saitek X52 Pro, UCSD LCD devices - Portrait mode support for AlphaCool and Samsung SPF LCDs - SensorPanel and LCD: right-to-left bars, static label control strings - 0.01 Celsius temperature measurement resolution for select sensor items - System certificates information - CUDA 7.0, OpenCL 2.1, SMBIOS 3.0, VirtualBox 5.0 support - Corsair Neutron XT, Crucial BX100, Crucial MX200, Kingston HyperX Savage, OCZ Trion 100, OCZ Vector 180, SanDisk Ultra II SSD support - GPU details for AMD Radeon Rx 300 and R9 Fury Series - GPU details for nVIDIA GeForce GTX 960, GeForce GTX 980 Ti, GeForce GTX Titan X, Tesla M60 [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v5.50 ] [ Download ]

Thank you. Somehow the kernel driver cannot be loaded, probably due to a special security policy setting on your system. I've just sent you a private message about this issue.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. You may need to enable the statusbar from mainmenu / View first. BTW, does your Windows user have administrator privileges?

Under Win7 64-bit you may have to install the following security patch to make AIDA64 work properly: KB3033929. That became necessary because we had to transition from the old kernel driver to the latest and much more secure EV (Extended Validation) kernel driver with SHA2 digital signature. Regards, Fiery

The mentioned new AIDA64 beta update is already available for download at: http://www.aida64.com/downloads/latesta64xebeta

I'd just keep using the drive with HDSentinel monitoring it in the background. I use HDSentinel on my main machine, even though I have no HDDs or SSDs with such pending sectors (yet)

I don't think such an issue makes your driver eligible for a replacement or repair. It's not a re-allocated sector (a.k.a. bad sector), but only a pending sector. You could call it a "suspicious sector" that may or may not become a bad sector. What I would do is install HDSentinel and keep it running, and configure its alerting system to warn you about any further issues that may come up. That pending sector may mean nothing, or may be a "teaser" of worse things to come. It's hard to tell which one, at this time.

AIDA64 warns you about the fact that there's a single pending sector on your HDD. You may want to check it out with another software like HDSentinel as well: http://hdsentinel.com Regards, Fiery

The main problem is that since Windows 8 shutdown doesn't mean an actual shutdown, but more like a low-power sleep state. With the AIDA64 build you have installed you can only have the right UpTime statistics if you disable Fast Startup in Control Panel / Power Options / System Settings. But, we've just implemented a fix to get around that issue, so please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works Thanks, Fiery

Changes may or may not be small. You cannot possibly expect to have the same OpenCL driver for a particular GPU architecture intact for 3 or 12 months. And results obtained with a specific OpenCL driver should only be compared with results obtained with the same driver. So when the OpenCL driver gets updated for a GPU, we would have to re-run the benchmarks and update the reference results database.

Several hours is best. You should test all cores at once.

As I've stated above, AIDA64 does not explicitly load that DLL, so we cannot make it not load it.

We currently don't know of a generic Windows API call to read or detect such property for a network adapter. Do you know of a Windows software that can show you that information? Regards, Fiery

It usually means the CPU is overheating. Throttling percentage is read directly from Intel processors, and they reflect the amount of overheating the CPU is suffering from. As long as it's under 10%, it's not a big deal, and could be normal for certain Haswell and Broadwell processors.

Thank you, we'll fix that issue in the next AIDA64 beta update due in a few days from now. Regards, Fiery

Yes, you should close other programs, since they may interfere with AIDA64 Stability Test, or eat up too much CPU cycles that would be better spent on running stress test threads. But, after having a few hours spent with AIDA64 Stability Test running, and getting no errors, you may want to start opening other applications as well, to see if it makes a difference. Sometimes the computer locks up or throws a BSoD quicker with a more diverse workload than with a single very demanding workload. Regards, Fiery

No, I'm afraid AIDA64 doesn't support plugins. If you can build a DLL and send us the interface (API) documentation, we can pull the data from your DLL. We do the same already with Fraps for example. As for transparency, no, it's not possible to make a fully transparent or opaque graph. But you can disable the graph background, frame and grid, so only the graph itself will be drawn. It would effectively mean a transparent background for the graph area.

GPGPU benchmark results could change by simply updating the video driver, since companies like AMD, Intel and nVIDIA keep fine-tuning and optimizing their OpenCL driver all the time. So it wouldn't make much sense to add reference results, since we would have to update them everytime a new video driver is rolled out -- which is basically twice a week

64KB is very low, I don't think your device (or any other Samsung SPF device for that matter) would expect that small of an image. 256KB sounds more realistic.