Fiery
-
Posts
12604 -
Joined
-
Last visited
-
Days Won
565
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
Thank you, we'll fix that in the next AIDA64 beta release due next week.
Regards,Fiery
-
If you don't know what should appear in the AIDA64.INI file, then you should better go with the default settings
-
Please note that unlike 3DMark, Furmark or many other 3D benchmarks or 3D games, AIDA64 uses GPGPU compute tasks (via OpenCL) to put stress on the GPUs and APUs. It means, it has to call OpenCL to first copy a block of memory from system memory into the video memory, then start a program that performs the actual computation, and then when it's finished, it has to copy the memory back from the video memory to the system memory, in order to let it verify the results. And since all those tasks have to go through OpenCL driver, then the video driver (ForceWare in your case), the PCI Express link, and also the GPU itself, there's a lot of latency and bottlenecks involved in the process. It effectively means the GPU may not be driven 100% constantly, but sometimes a downward spike may appear when the OpenCL driver, the PCI Express link or the video driver lags a bit. That's normal, and can only be avoided by directly programming the GPU (which is impossible), or using a 3D scene instead of a GPGPU code.
However, the advantage of GPGPU stress test over 3D scenes is that using GPGPU code it's much easier to stress all available GPUs simultaneously.
Regards,
Fiery
-
As this actually is my area of expertise, that is exactly correct. While it can be supported and some iteration implemented, it is still in proposal and pre-draft stages.
I'm glad you chimed in
If it doesn't violate any protocols or NDAs, would you please share the pre-draft register locations and bit fields -- where the DevSleep capability and status can be detected -- with us? Or shall we wait for the first public ACS-4 drafts to become available for download?Thanks,
Fiery
-
As I've explained above, such issues may happen when under heavy load the CPU intermittently provides invalid core temperature readings to AIDA64. Such readings should be ignored. As for GPU, I'm not sure what may cause that, but since the GPU TDP% reading is measured via nVIDIA driver calls, it depends on the driver whether it provides reliable and stable readings.
-
What we need is those feature bits to appear in the ATA/ATAPI Command Set specifications. But as it seems, it's not been propagated for ACS-3 (latest revision), so I guess we would need to wait for ACS-4 to be drafted.
-
Make sure to read the two PDF documents available for download at:
http://www.aida64.com/downloads/aida64business300zip
Default AIDA64.INI file can be generated by going to main menu / File / Preferences, and pressing the OK button. The AIDA64.INI file can then be found in the AIDA64 folder.
-
1) 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.
2) Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic.
3) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic.
Thanks,
Fiery
-
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.
Using that data we may be able to calibrate the AIDA64 sensor module to better support your motherboard. But please note that the core temperatures are measured via the on-die temperature diode of your processor. And most FM1, FM2 and AM3+ socket based AMD processors feature a hardware issue in their temperature diodes that yields to very low temperature readouts at idle -- usually way below ambient (room) temperature. The measured core temperatures only make sense when the CPU is under load.
Thanks,Fiery
-
Thank you, but we haven't found the actual method to detect the Device Sleep capability and status in any of the documents we've got. It is possible via the IDENTIFY DEVICE command, but even the latest ACS doc doesn't mention Device Sleep, DEVSLP or DevSleep. So we don't know which register to use.
-
Asus P8Z68-V LX , BIOS was 4003, today I have upgraded it to the last (4102). Also I've tried to disable overclocking, but it doesn't help .Thanks.
Do you have Asus AI Suite installed?
-
It is one of the 3 temperatures your motherboard sensor chip measures. You may want to compare the measured values against ASRock F-Stream Tuning Utility, but I'm sure both Motherboard and CPU temperatures will match between AIDA64 and FSTU.
-
This may or may not be related here, but I get an access violation on each startup using beta 2505. I usually have to retart 4 or 5 times before it loads properly. Attached is a picture of the fault.
ASUS Z87-PRO EFI/BIOS 1007
i7-4770K
Try to reinstall AIDA64 using the latest ZIP package:
http://www.aida64.com/downloads/aida64extremebuild2505xh8pw4vstmzip
It looks like one or more of the main DLL files are either missing or got corrupted.
-
All readings look fine and accurate on your motherboard. If you believe "CPU" reading is too high, then just ignore it, and focus on CPU Package.
-
Whoops, I thought I had. That fixed it. Thanks.
It looks like this beta version has also stop the crashes.
Sounds great, thank you for the feedback!
-
Thank you for the bug report, we'll fix that in the next AIDA64 beta release due next week.
-
Thank you. Then the issue may be related to your motherboard. Please let us know what motherboard do you have, so we can try to reproduce it on a motherboard like that.
-
Thank you for the feedback
-
As for the icons, try to restart your computer, it should solve that.
-
AIDA64 Extreme Edition doesn't support command-line arguments.
Regards,Fiery
-
I've sent you your AIDA64 product key in email.
Regards,Fiery
-
Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild2505xh8pw4vstmzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know if it helps.
Thanks,
Fiery
-
We've made several modules of AIDA64 more solid by improving exception handling. We've also disabled CPU throttling measurement by default. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild2505xh8pw4vstmzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know if it helps.
Thanks,
Fiery
-
We've made several modules of AIDA64 more solid by improving exception handling. We've also disabled CPU throttling measurement by default. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild2505xh8pw4vstmzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know if it helps.
Thanks,
Fiery
AIDA64 CPUID is not starting (Asus P8Z68-V LX)
in Bug reports
Posted
Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic.
Thanks,
Fiery