Fiery
-
Posts
12444 -
Joined
-
Last visited
-
Days Won
554
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
Thank you. We've been able to make our box work on a USB 3.0 port with a NEC uPD720200 controller. However, through the course of a 3-day test run we haven't been able to reproduce the disconnection issue
We've tried it with driver version 2.1.39.0 and also with an old version 2.0.20.0.However, when we've tried to connect the box manually to the USB 3.0 port, the box worked roughly once out of 5 tries, so 4 times the board didn't even sense a connection, and so Windows didn't find any devices connected and failed to mount the HDD in the box. On the rare occasion of a successful manual connection, the box worked just fine until we unmounted it via the System Tray icon. We prefer not to point fingers on hardware, but on this particular issue we strongly believe the VIA VL700 controller is the one to blame, since with an Etron USB 3.0 controller chip it fails to connect everytime, and with our NEC USB 3.0 controller chip it fails to connect a lot of times. While on USB 2.0 ports it works just fine everytime. BTW, we have a few USB 3.0 boxes, converters and flash drives around with various controller chips, but we've only found issues with the VIA VL700 controller based box of ours.
-
Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild2406twdq1v8hcszip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know if it helps. It would also be a huge help for us if you could create an ISA Sensor Dump using this beta release, and copy-paste the results into this topic. You can create such dump by right-clicking on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump.
-
For MySQL you need to select the MySQL ODBC driver in the Driver drop-down list, enter your Database name, enter your Server address (hostname or IP address), and enter your credentials (User + Password). If you fill in all those fields, you can leave the Data source field empty.
Regards,Fiery
-
Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild2406twdq1v8hcszip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know if it helps.
-
Thank you. It's definitely not C1 stepping, but C2, so AIDA64 is correct. C1 in the BIOS Setup may refer to the X79 PCH stepping.
-
It may use a correction value (offset) on the raw temperature readout to make it look more real. You can apply such offset on the temperature values with AIDA64 as well, if you go to main menu / File / Preferences / Hardware Monitoring / Correction.
-
Modern AMD processors (including FX Series, Trinity, Richland) implement such a temperature diode that only provides meaningful values when the system is under heavy load. This is a hardware limitation, and not the fault of AIDA64.
Regards,Fiery
-
Please let us know what the 3rd line on the Motherboard / CPUID page of AIDA64 says about the CPUID revision of your processor.
Thanks,Fiery
-
I'm sorry for the misunderstanding. What you're looking for is AFAIK cannot be detected under Windows.
-
1
-
-
The current SATA revision used by your HDD/SSD drives is displayed on the Storage / ATA page of AIDA64.
Regards,Fiery
-
With both benchmarks it is very crucial that you have proper memory bandwidth. With single-channel memory your scores will be much lower than the reference systems. Single-channel memory is a huge bottleneck in your system, so make sure to install at least 2 identical memory modules to activate dual-channel operation.
Regards,Fiery
-
Alternating values for the same reading is not really the best idea, since that would make it tough to configure an item on the OSD Panel, Logitech LCD or SensorPanel.
-
Yes, that's grammatically true. However, AIDA64 uses a fixed label, so based on the current battery status (discharging / charging / neutral) it's not possible to change the sensor reading label. Instead, AIDA64 uses a negative value to indicate discharging, a positive value to indicate charging, and zero value to indicate the neutral state. It's not a perfect solution, but it works
Regards,Fiery
-
AIDA64 detects Windows Firewall status via a standard Microsoft API call:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365287(v=vs.85).aspxIn case the API reports the firewall is disabled when it isn't, then it seems to be a bug of Windows rather than an AIDA64 bug... Although, quite frankly we've never heard of this API failing on any systems.
Regards,Fiery
-
Thank you, the bug will be fixed in the next AIDA64 beta release. I'll post a message into this topic once the new beta is available for download.
Regards,Fiery
-
That could happen when AIDA64 cannot load its resources from AIDA_CPUID.DLL because the file is missing or corrupted. You need to reinstall AIDA64 from the authentic download package:
http://www.aida64.com/downloads/aida64extreme270exe
Regards,Fiery
-
Thank you for the feedback
-
Thank you. I've just sent you a private message about this issue.
-
What version of AIDA64 do you use?
Thanks,Fiery
-
The latest AIDA64 update implements full support for the upcoming AMD Radeon HD 8000 Series graphics accelerators, adds AVX-optimized 64-bit benchmarks for AMD A-Series “Richland†APU, and supports the latest GeForce and Tesla GPUs by nVIDIA.
New features & improvements- Optimized 64-bit benchmarks for AMD A-Series “Richland†APU
- Improved support for AMD “Kabiniâ€, “Temash†and “Kaveri†APUs
- Improved support for Intel “Haswell†and “Valleyview†processors
- Preliminary support for AMD “Beema†APU
- Preliminary support for Intel “Avoton†SoC, “Crystal Well†CPU, “Haswell-E†CPU, “Haswell-ULT†SoC, “Ivy Bridge-E†CPU, “Lynx Point-LP†PCH, “Wellsburg†PCH
- Preliminary support for DDR4 memory modules and GDDR5 system memory
- GPU details for AMD Radeon HD 8000 Series and nVIDIA GeForce GTX Titan
What’s new since AIDA64 v2.00
- Microsoft Windows 8 RTM and Windows Server 2012 RTM support
- OpenCL GPGPU Stress Test
- Enhanced UPS support
- SensorPanel graphs and gauges
- Revamped Desktop Gadget
- Optimized 64-bit benchmarks for AMD A-Series “Trinity†APU and FX-Series “Vishera†CPU
- Optimized benchmarks for Intel Atom Z2760 “Cloverview†SoC
- Revamped PhotoWorxx digital photo processing benchmark with AVX, SSE4.1 and XOP optimizations
- Rewritten AES data encryption benchmark with AESNI, SSE4.1 and VIA PadLock optimizations
- Support for Intel Atom “Cedarview†processors
- Support for Intel Core “Ivy Bridge†CPU and Intel 7-Series chipsets
- Preliminary support for AMD “Kabini†APU
- Preliminary support for Intel “Haswell†CPU and Intel “Lynx Point†PCH
- Preliminary support for Intel “Penwell†SoC
- VIA VX11 platform, Nano X2 and QuadCore CPU support
- Socket FM2 motherboards support
- Speech API information
- Support for VirtualBox v4.2 and VMware Workstation v9
- ACPI 5.0, APP SDK 2.8, CUDA 5.0, OpenCL 1.2 Update, OpenGL 4.3, OpenGL ES 3.0 support
- Intel 330, Intel 520, Intel 710, OCZ Vector, OCZ Vertex 4, Samsung 830, Samsung 840, Samsung 840 Pro SSD support
- GPU details for AMD Radeon HD 7000, nVIDIA GeForce 600 Series, Quadro K-Series, Tesla K-Series
-
Thank you for your help. Just to be on the safe side, we'll disable CPU throttling monitoring in the upcoming new stable release of AIDA64. We'll put it back in the first beta release after that, and continue testing it to find out whether the issue you're experiencing is an isolated case, or it is due to a generic implementation issue that may affect a wider public.
-
The DeLock 61854 box has arrived, and we've already put it under heavy test runs
Problem is: it doesn't seem to work properly when connected to USB 3.0 ports (of an Etron EJ168 xHCI controller of a Gigabyte GA-Z68XP-UD3-iSSD motherboard), even though we use everything "by the book", with the bundled blue USB 3.0 cable, under Windows 7 64-bit SP1 + all patches installed. Windows can see the VIA VL700 USB 3.0 bridge chip itself, but cannot see the drive that is inserted in the box.When connected to a USB 2.0 port, the box works just fine, and we haven't found any disconnection or dismounting/remounting issues. We've tested it with both a 2.5-inch SSD and a 3.5-inch 7200rpm HDD.
We'll continue testing with different USB 3.0 controllers and different motherboards. Meanwhile, can you please let us know what sort of USB 3.0 controller do you have the MediaSonic box connected to?
-
Thank you for the info. We've tried it with several card readers that were lying around in our labs, and also with quite a few notebooks and HTPCs, but none of them produced an error message with AIDA64. Can you please send us a bit more info on your card reader? The most interesting one would be the USB hardware ID that you can find either in the Device Manager, or on the Devices / USB Devices page in AIDA64.
Also, if possible, please post a screen shot of the error message. Quite frankly, the last time we saw such an issue about polling removable media drives was under Windows NT 4.0 and was about Zip drives -- quite a long time ago.BTW, the disk size and free disk space detection code in AIDA64 are (or let's just say: designed to be) exception proof, and so the calls shouldn't produce any Windows error messages or popups, even when there's no disk or media inserted in the removable media slots. It's not the code in AIDA64 that is designed improperly, but there must be something else that causes the issues on your system. We will do everything we can to make sure the issue is fixed, so you can be assured to purchase a flawless product.
-
Hi
I'm new member . I have a problem with "cooling fans". Why Cooling fans displaying in the sensor ?
I used Hp4530s i5-2450 and setup Aida64 2.30.1900.
Sorry my bad english.
Thank you.
Most notebooks (including your HP 4530s) aren't capable of reading out cooling fan speed RPM values.
Gigabyte A75-D3H + AMD A6-3670 Wrong Readings
in Hardware monitoring
Posted
I'm afraid that may be due to the improperly implemented temperature diode logic of Llano, Trinity, Richland, Zambezi, Vishera processors
Such issue can only be fixed by applying an offset on the temperature readings in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.