Fiery

The mentioned new AIDA64 Extreme beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps

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

I'm sorry, I thought the temperature is 120+ Celsius on the DTS rails, which are listed as "CPU #1 / Core #n" temperature by AIDA64. It seems culprit is a temperature measured by the motherboard sensor chip. Have you tried checking the temperatures using MSI's own monitoring software?

Without the kernel driver you not only lose some sensors, but also GPU information, SPD memory modules list, chipset details, and a lot of other bits & pieces. So it's best to clear this up and make sure AIDA64 can use its kernel driver. BTW, do you get UAC prompt when you launch AIDA64?

The checklist for such issues is usually: 1) Check if an administrator user is running AIDA64, and that the elevation is successfully performed. In case UAC is enabled, AIDA64 should ask for elevation when you start it, and you should let it elevate user rights to gain administrator access. Do you get the UAC prompt when you start AIDA64? 2) Check if KERNELD.X64 file is there in the AIDA64 installation folder. After starting AIDA64 you can also verify if the AIDA64 kernel driver has been successfully loaded by going to the Operating System / System Drivers page, and finding "AIDA64Driver" there. It should have the filename "kerneld.x64", and the state "Running". 3) Under Win7 64-bit check if the SHA2 security patch (KB3033929) is applied. Go to the Security / Windows Update page, and find the hotfix there with the ID "KB3033929". If all of those are just fine, then my only guess would be that a security (anti-malware) software prevents AIDA64 (and perhaps other software as well) from performing low-level hardware access.

I'm not a CPU engineer, but to me it seems to be the fault of the CPU, where the DTS logic is located. But just because of that issue, I wouldn't go out and replace any of my hardware. There're several other temperature sensors in the computer that you can watch to detect an overheating situation. But, if you're considering replacing your CPU or motherboard, then I'd still wait a few months, since the successor to your CPU, Broadwell-E is right around the corner. With the new LGA2011v3 CPU generation I'm pretty sure motherboard vendors prepare a new fleet of X99 motherboards as well.

Your PSU is simply not among the USB devices. Scan those dumps for "1B1C", which is the vendor ID of Corsair, and you'll see that there're no occurences Try to perform a complete power-off of your system, by disconnecting the A/C cable from your PSU. If it doesn't help, then try to connect the PSU to a different USB header of the motherboard.

It seems to be an intermittent hardware failure of the Intel DTS (Digital Thermal Sensor) subsystem. We've seen such issues before, although it's very rare to happen.

What's happened? What did you do that made the readings disappear?

It's odd. We've just checked BitDefender 2016 Total Security under both Win7 64-bit and Win10 64-bit, and for us AIDA64 detected it just fine. Did you do a clean and standard (default) installation of BitDefender? Or did you perform an upgrade?

It is still the case I'm afraid.

Do you use Windows 10 64-bit, with latest patches applied? Thanks, Fiery

It seems the issue is the lack of administrative privileges. Make sure to check that the user who's running AIDA64 has got administrator rights, and that you've got KERNELD.X64 file present in the AIDA64 installation folder.

Both of you: please apply the Windows 7 AES security patch (if it's not installed yet) named KB3033929, then update to the latest AIDA64 beta available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let us know if it helps. Thanks, Fiery

Please note that 950 Pro is extremely slow when you use the built-in (default) Windows 10 NVMe driver called StorNvme. It provides over 1800 MB/sec sequential read but less than 100 MB/sec sequential write performance using that driver. However, after installing Samsung's own NVMe driver for 950 Pro, the same drive accelerates up to 800 MB/sec write speed. So it's really not a great idea to stick to the default NVMe driver of Windows

I understand your issue, but I'm not sure if there're any ready-to-use solutions that would fit your requirements LCDInfo sells a nice colour panel that may fit the bill (called USBD480), but it is just the panel, not a full device that could be slotted straight into a double 5.25" bay. As crazy as it may sound, your best bet might just be a cheap Android based phone/phablet that you could hack into the drive bay using a 3D printed (or otherwise sculpted) plastic frame. Then you could use AIDA64 RemoteSensor or Odospace: https://forums.aida64.com/topic/2776-display-pc-sensor-values-on-android-device-connected-via-usb-odospace-remote-panel/

It means the issue caused by a bug in the OpenCL compiler which is part of the OpenCL driver which is part of the video driver for your GPU. Try to update your video driver, it should help.

1) Yes, but it's still not the utilization of the GPU. GPU is a hardware component, and the listed items are software components. AFAIK it's not possible to measure GPU load on Intel GPUs. 2) Are you sure it's only one 2 GB chip soldered to the motherboard of your system? Anyway, it's best to simply run the AIDA64 Cache & Memory Benchmark, and see how the memory can perform. If it can push more than 10667 MB/sec (while running at DDR3-1333 speed grade), then it's definitely using a 2-channel configuration.

Previous AIDA64 versions didn't have the compatibility / supportedOS tags in the application manifest. We've had to add them to properly support Windows 10. However, by adding them to the manifest, it seems Windows drivers behave differently. Apparently Intel's legacy video drivers cannot handle such situations. We've checked, and it's not just AIDA64. The latest version of OpenGL Extension Viewer simply crashes when you start it under 64-bit Windows 10 with a Clarkdale IGP

1) What GPU-Z shows is not the GPU load, but the Direct3D load. 2) N2830 does support up to 2 memory channels. Do you mean your system utilizes only one memory channel out of the two?

Does it hang at the GPU test or CPU test? In other words: left column or right column on the GPGPU Benchmark Panel?

Thank you. As it turns out, this is a bug of Intel's Windows 10 video drivers. We've run into the same issue than this gentleman: http://stackoverflow.com/questions/34676697/embedding-manifest-into-the-application-binary-breaks-opengl-2

Thank you for the data. The issue will be fixed in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta is available for download.

Do you know approx. at what RPM your fans are spinning while your computer is not under heavy load (e.g. when you're using AIDA64 or browsing the web), and how many fans are spinning?

We've checked all those, but without a luck so far The registers you've mentioned are all zero