Fiery

1) What version+build of AIDA64 are you running? 2)What version of Windows do you have installed? (32-bit or 64-bit) 3) Do you have any external drives connected, either via eSATA, USB or FireWire? Thanks, Fiery

It's best not to use the computer, but in rare cases using the computer could help to get to the system crash quicker

Thanks for the info. So the issue only comes up when RTSS is active?

Older AIDA64 versions did not use all available physical memory, while the latest versions (v4.20 and v4.30) use it all up. What you see is normal. As for how long you should have the test running. We generally recommend a few hours, since not many users have the patience to have it running for the ideal 24 hours. In your case, if at 1.524V you got a BSoD in a few minutes, but at 1.65V it runs for an hour, that should be enough to assure the 1.65V setting is superior

It's odd, we haven't found such issues with ForceWare 337.50. Please let me know what Windows version (and 32-bit or 64-bit) and what video card were you using for the test. GTX680 with 64-bit Win7 SP1 maybe?

Are you sure that voltage is enough for your memory modules? Also, do you use default memory timings? If you're using CR (Command Rate) of 1T, try to up it to 2T -- it helps in many cases to stabilize the system. And I'm pretty sure the issue is not AIDA64. If it was the culprit, then the BSoD would come up by just clicking through the pages of AIDA64, like Motherboard / Chipset, Computer / Summary, Computer / Sensor. Please note that the AIDA64 System Stability Test is designed for exactly to reveal such issues that your system is having. It puts such an enermous stress on the system that it can reveal instability easier -- and in many cases quicker -- than by using other tools.

It simply means your system is not stable. You have to use more conservative overclocking settings (if your system is overclocked), or check out the components, because one of them may be failing. Regards, Fiery

It's quite possible that the panels are shown, but outside the visible Windows desktop area. You can move them to the desired location by altering the SensorPanelPosX, SensorPanelPosY, OSDPosX and OSDPosY values in the Registry, under HKEY_CURRENT_USER\Software\FinalWire\AIDA64. It's not the most user-friendly method, but it should help in your case to make your panels visible again. Regards, Fiery

It is not possible to convert from HTML to any other formats. Regards, Fiery

I can understand your idea, but I'm afraid it's currently not possible because of the way the hardware monitoring module of AIDA64 is designed. We may make that possible in the future when the hardware monitoring module gets revamped (rewritten). Regards, Fiery

Thank you

It will last until the next beta is out Or, if you mean how long will it take for this to go stable, then we're planning to release the next AIDA64 stable update late May.

Thank you. There's no other temperature reading, so Defraggler must be using a minus 8 Celsius compensation value on the temperature reading.

Please post a screen shot of the Storage / SMART page of AIDA64 as well. There's a chance Defraggler reads temperature from another SMART attribute.

Please check the Storage / Optical Drives page of AIDA64 Regards, Fiery

On ASRock ConRoe1333-D667 motherboard we have no information on what Aux temperature represents. It looks like it's a valid reading though.

Core 2 Duo T7400 has no IMC (Integrated Memory Controller) in the CPU package, so I'd need to know the notebook model to find that out.

It's a bug that will be fixed in the next beta update. The 4 GB is only valid for the desktop version of your CPU (codenamed Pineview-D, where "D" stands for desktop).

Atom N450 supports a maximum of 2 GB system memory, according to Intel's site: http://ark.intel.com/products/42503/Intel-Atom-Processor-N450-512K-Cache-1_66-GHz

You may have that information listed on the Motherboard / Chipset page in AIDA64. If not, then please let me know the notebook model and CPU type. Regards, Fiery

You can try Battery Eater for example

I think that's a bug of the smart logic of the battery itself. The Current Capacity is reported by the battery via a standard Windows API call. Regards, Fiery

Here's the mentioned new AIDA64 Extreme beta release that improves on the Logitech LCD support at Windows bootup: http://www.aida64.com/downloads/aida64extremebuild2914kf2mbs7dcqzip Please let me know how it works on your system.

Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2914kf2mbs7dcqzip Let me know if it helps.

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. If possible, please list the fans you have connected when you made the dump, with their corresponding RPM value as well. That way we can have a reference list of readings and we can compare them with the sensor registers output.