Fiery
-
Posts
12273 -
Joined
-
Last visited
-
Days Won
541
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
Suggestion: Hard Drive access activity/ process Monitor
Fiery replied to StackOverflow13's topic in Brainstorming
What version of Aquasuite are you using? And what AquaComputer hardware do you have? -
Nice video Let us know if the issue comes back. Maybe it's related to another Windows software that you sometimes are running, but many times not.
-
1) Memory Copy means writing a memory block and then reading it back. If there are no separate (dedicated) paths for writing and reading, then the copy scores will be close to the read and write scores. 2) AIDA64 uses multiple threads to perform memory bandwidth benchmarks. Modern applications are multi-threaded, so a single-threaded memory bandwidth benchmark (that we used in AIDA64 1.xx and 2.xx) is considered obsolete in 2017. Regards, Fiery
-
Does SST change behavior when screen goes to sleep? (Quadro K5100M)
Fiery replied to delerious's topic in General Discussion
No, AIDA64 doesn't behave differently in different power management states. It executes the same stress testing code no matter the screen is powered or sleeping. Radeon video cards however work differently in those states, so it must be due to a video driver (Catalyst) pecularity. Regards, Fiery -
We will fix the issue in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new AIDA64 beta build is available for download. Regards, Fiery
-
Throttling detection only works on Intel processors. Regards, Fiery
-
No sensors require an internet connection. Regards, Fiery
-
We've tried but wasn't able to reproduce the issue on our own Windows 10 test systems. Are you running Windows 10 Anniversary Update? (Build 14393)
-
Using our benchmarks under virtual machines is not supported. Regards, Fiery
-
One possible explanation is that AIDA64 displays a message box that is not displayed anywhere, since you have AIDA64 running as the SYSTEM account. Can you please try to replace /CUSTOM \\server\aida\aida64.rpf with /SUM ? Maybe one of the pages that you have in your report profile causes the issue. In which case (when /SUM works fine) you need to remove some of the pages from your report profile.
-
Memory DIMM info. display error? (Asus X99-E WS/USB 3.1)
Fiery replied to gbohn's topic in Hardware monitoring
We've already seen such issues on Haswell-E and Broadwell-E systems, but couldn't reproduce it on our own test systems using the same processors It must be due to SMBus timing pecularities, but when we've tried to adjust the timing to a more relaxed value, surprisingly things (ie. SPD detection) got even worse. As for Aquasuite, you can try to close that software, but I'm pretty sure it's not the culprit. -
Thank you. We'll implement advanced support for MX300 SSDs in the next AIDA64 beta update due next week
-
Yes, using a microcontroller would probably be the ultimate solution -- although not the easiest or most cost effective one We will keep things on hold until you have the final hardware assembled and tested to be working.
-
Thank you. I think I misunderstood you then All looks fine in the dump, so no issues
-
Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART 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
-
You seem to know your stuff, so let me ask you a few further deep technical questions, to make sure we initialize your device in a way it's expected. 1) What baud rate shall we use when calling FT_SetBaudRate? 2) What argument values shall we use when calling FT_SetDataCharacteristics, FT_SetFlowControl and FT_SetTimeouts? 3) Can you please provide the exact command bytes we need to issue at the OLED init, and the command bytes we need to use at each frame update?
-
As for the GTX1080 fan 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 the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Make sure to have the video card fan spinning at a non-zero RPM when you're issuing the dump. Thanks, Fiery
-
It works the way it's supposed to be. It's due to the fact that it's not possible to tell the difference between a stopped fan and an unconnected fan AIDA64 shows the 0 RPM reading only in the SensorPanel and LCD modules. But first you need a spinning fan to place the items on your panel, and then when it stops, 0 RPM will be shown. On the Sensor page the stopped fans will not be displayed.
-
NVMe doesn't support thresholds/value/worst fields as ATA/SATA drives do.
-
You've got the OnePlus 3T device. The small glitches about detection will be corrected in the next AIDA64 app update. Regards, Fiery
-
Thank you. It seems the USB communication protocol used by your Kraken X52 device is completely different to the one used by previous Kraken coolers that are supported by AIDA64. So it's normal that AIDA64 doesn't support Kraken X52 We will need to do more research -- and possibly get a Kraken X52 -- to find out how to handle the new Kraken protocol. I'll let you know in this topic once we have an update to this issue.
-
Then please close CAM Software, start AIDA64, and right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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'm confused... Do you have X51 or X52? In your opening post you've mentioned X51, but in your latest post you mention X52/X62
-
Thank you. Do you have an idea on the amount of data that needs to be transferred in each cycle to update the OLED screen content? The pixel data alone seems to be 30 KiloBytes, plus the overhead of the command issuing, etc. What is the speed of the SPI connection that your device would utilize? I'm a bit concerned about the whole thing being too slow. We consider a display too slow when the update rate cannot be kept at an acceptable level, like twice a second.
-
While I personally find it an intriguing idea, I'm afraid we have no plans to implement such a feature in AIDA64. Regards, Fiery
