Fiery
-
Posts
11334 -
Joined
-
Last visited
-
Days Won
476
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
I understand that the issue doesn't affect the older betas, but it would still be important to know whether you changed or updated any hardware in your system recently. In the past few beta updates we've been working hard on adding support for all the new Z270, H270, Q270 and B250 motherboards out there, as well as the upcoming AM4 motherboards. Maybe you've got a new Z270 motherboard recently which works fine with the older betas but not with the newer ones? Also, we've revamped the way AIDA64 handles DDR4 SPD on Haswell-E and Broadwell-E processors. So if your memory modules have DIMM TS (thermal sensing) capabilities, it may be worth trying to disable DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability, and see if it helps. You need to restart AIDA64 after altering that option.
-
Task Scheduler causes SST interface to lag when started.
Fiery replied to 00110100's topic in Bug reports
I guess either the AIDA64.EXE process or the SST/benchmark process (AIDA_BENCH64.DLL or AIDA_BENCH32.DLL) may get started with a sub-optimal priority setting through the Task Scheduler. The main process that also updates the SST interface (AIDA64.EXE) has to have a higher priority setting than the SST process. By default the main process uses the Normal priority level, and the SST process uses the Below Normal priority level. However, if for some reason they use the same priority level or the SST process uses a higher priority level than the main process, then the SST interface update will not get enough CPU cycles from the Windows kernel scheduler, which will make the SST interface jerky/lagging. Regards, Fiery -
Even if you have a 500 millisec or 100 millisec update rate, the clock will not go crazy. It will however not skip a second, so it will look smoother than with a 1 sec update rate. CL: Great to hear, thank you!
-
You can get the informational blue box back on your tablet if you have the RemoteSensor feature enabled, but you hide all items in your layout. You don't have to remove those items, just select them all and press the Hide button to hide them. As soon as you get the blue box, you can unhide all items again, and continue tweaking your layout.
-
Linear Write + Verify shouldn't take days to complete, as long as the drive performs at least as good as an average USB 2.0 pendrive. Even if the drive can do only 25 MB/s, filling the drive and verifying it would take "only" 23 hours. In case the drive performs considerably worse than that, that fact alone would make one suspicious about authenticity of the pendrive... BTW, a true USB 3.0 pendrive would do at least 100 MB/s, and so it would complete the Linear Write + Verify test in 6 hours (considering it's a 1TB capacity drive).
-
AIDA64 installed on SSD or HDD ? (G19 LCD API disk leak)
Fiery replied to killik's topic in Hardware monitoring
If you use the automatic update feature, then that alone would explain the 783 MB write in a year. Since it first downloads the update package, then extracts the files. So at every update it writes cca. 120 MB on the disk right now. It was less than that before we've implemented DPI scaling though. Also, if you use the Logging facility or the disk write benchmark, those could write gigabytes on the disk very quickly Regards, Fiery -
Are you sure Corsair Link software has no background service that would keep monitoring your RAM modules and control their LEDs, even when the main application is closed? We've seen such issues with several other software, the prime example is of course Asus AI Suite
-
Such 2-second steps are absolutely normal. The way it works is that for example when you have a 1 second update frequency set, the sensor values are updated in a 1 second step. But, that 1 second delay starts when the previous sensor polling is done. So when the polling itself takes more than zero seconds, the actual update rate will be longer than 1 second. When the polling of all sensor values take e.g. 600 milliseconds, the effective update rate will be 1600 milliseconds or 1.6 sec. The solution to that pecularity is to lower the update frequency to e.g. 500 miliseconds.
-
Did you configure the resolution that was indicated by RemoteSensor in a blue box on your Android tablet? It may or may not be 800x1280 pixels, but smaller. On our 8-inch 800x1280 resolution Android tablet (Asus MeMO Pad 8) the right resolution to have configured is 980x1292. We've also checked the font size issue, and 72 seemed quite large already. However, in order for you to have more flexibility, we'll unlock setting the font size to even larger values in the next AIDA64 beta update due next week
-
There could be 2 reasons behind that. Either your RAM modules fail to provide a stable and accurate reading sometimes; or there's a SMBus access collision between another software and AIDA64. Do you have any other software installed that may also poll the SMBus?
-
Maybe it's the sensor thread that freezes. Did you change anything in your computer recently? I mean like a hardware replacement, hardware upgrade? Can you please check what happens if you leave the Computer / Sensor page open for a few minutes? Or if you leave the System Stability Test window open for a few minutes, without starting any stress tests?
-
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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
-
I've sent you a private message about this, responding to your private message
-
IMHO having a single status is fine. If any of the disks fail, the status will show "FAIL", and then you can dig deeper by navigating to the mentioned Storage / SMART page. Yes, the SMART status should be available fro M.2 SSDs and NVMe SSDs as well. However, please note that not all SSD controllers are supported, so your particular SSD may need further adjustments/tweaking.
-
We've already added a disk health sub-window to the Storage / SMART page
-
When you have that done, please drop me a private message. We're not skilled with Labview, so any direct source code that is Delphi, C, Visual Basic (etc) -- tested to be working under Windows -- would be extremely helpful to have.
-
Yes, we're working on it. It may be a bit difficult to implement support for that hardware without having a sample hardware at hand, but we'll do our best.
-
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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
-
One day we'll get to joining the other hardware monitoring modules with the Sensor page, and use just a single module. That will simplify everything, and also will make it possible for you to rename or rearrange the readings on the Sensor page.
-
No, renaming is not simple at all. The main issue is that the Sensor page is not linked directly with the other hardware monitoring modules (e.g. OSD Panel, SensorPanel, External LCD, etc). Hence what you can do with all the other hardware monitoring modules, you cannot do to the Sensor page. But, you can switch to using the SensorPanel or OSD Panel anytime And with those you can rename and shuffle the readings any way you want.
-
Well... It was a very stupid mistake. I was lazy to properly assemble a PC, and left the SSD on top of a HDD. I thought after installing the OS and drivers, I'll remove the HDD and install the SSD in its drive bay. The two device heating themselves up ended up in a disaster, even though it was only for a few hours...
-
Thank you for your feedback
-
ASRock H270M Pro4 all mobo sensors are missing.
Fiery replied to JohnSS's topic in Hardware monitoring
Thank you, we'll add VCCST (VCC Sustain) voltage to the next AIDA64 beta -
Once I've had a SSD heating up over 100 Celsius, and that killed it. Not immmediately, but shortly it just died. I'd definitely get Corsair's take on the subject. If they fail to respond in a few days, then I'd get a refund and look elsewhere.
-
ASRock H270M Pro4 all mobo sensors are missing.
Fiery replied to JohnSS's topic in Hardware monitoring
Can you see the missing set of voltages in the UEFI Setup or in ASRock's own monitoring software? As for the PCH temperature, we will add it in the next AIDA64 beta update due next week. We will also check how to detect the chassis intrusion state.
