Fiery

PhotoWorxx is a very cache and memory dependent benchmark test. I suppose while you overclock your system, you hit a memory bandwidth bottleneck. It looks like it is based on DDR2-800 memory (issue #1), and also it has the IGP part of the chipset activated (issue #2). If you cannot overcome the memory bottleneck, then no matter how you raise the CPU core clock, the PhotoWorxx results will not increase considerably.

We've tested it with that RSTe release, and also with the v3.5.0.1101 WHQL available at .. http://www.station-d...ntel%20raid.htm ... and found no issues whatsoever. Are you sure you're running AIDA64 Business Edition v2.60 now?

Please make sure to use the latest WHQL release of Intel Rapid Storage Technology Enterprise driver. Alpha and beta stage drivers may have major issues...

Thank you for the feedback.

Please upgrade to AIDA64 v2.60. It will fix that issue. Regards, Fiery

Please post an ATA Dump, SMART Dump and RAID Dump. Do you know what chipset is the HDD dock based on?

Thank you for the feedback

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2127ds1yzptwckzip 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 implemented the requested feature in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2127ds1yzptwckzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that you cannot hide the columns permanently, since only those columns will be restored next time that are at least 10 pixels wide. So if you accidently or deliberately hide a column by sizing it to 0 pixels wide, it will be restored next time you start AIDA64.

We've tried it that way, and worked fine for us, no main window appeared at startup. Do you happen to have a Logitech keyboard with LCD? Their LCD Manager software may also try to launch AIDA64 at its startup, interfering with AIDA64's own "Load at Windows startup" facility.

Corsair responded to our request. They currently have no interest in opening up their Corsair Link API to let 3rd party developers access Corsair Link hardware Let's hope they change their mind in the future...

The graphics for gauges are currently embedded in the resources section of one of the DLL files of AIDA64, so it is not currently open for editing. In the future we may implement a facility to let you use any image files to define the gauge states. It would however require you to make one image for each state that the gauge displays, so a total of 16 images per gauge style. Regards, Fiery

Do you have the option Hide icon and bubble in Notification Area enabled or disabled in AIDA64 / main menu / File / Preferences / Layout?

Any of the following things would happen: - AIDA64 reports a hardware error (System Stability Test window turns red) - AIDA64 crashes (application error) - BSoD - computer locks up - computer restarts - computer powers off Regards, Fiery

Yes, the lack of SDK prevents 3rd party developers like us from implementing support for such LCD devices As soon as its manufacturer publishes a SDK, we will happily add support for the device in AIDA64. Regards, Fiery

You can activate the Logging feature in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging. If that doesn't reveal any useful information about your issue, then you can try running the AIDA64 System Stability Test in AIDA64 / main menu / Tools / System Stability Test. BTW, what I would try to do about your system to diagnose the issue: 1) Restore all settings to default (no overclock, no tuning about the RAM or chipset) 2) Update system BIOS to the latest stable one 3) Run AIDA64 System Stability Test with only the "FPU" subtest enabled to see if it is overheating under heavy stress 4) Replace the PSU (Power Supply Unit). Check if you could borrow a stable PSU from a friend. In many cases the PSU is behind the stability issues, especially if the PSU is in use for several years already Regards, Fiery

If it's possible, please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA Dump. Copy-paste the full results into this topic. Also right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic. Please do those 2 dumps both before and after hibernation, to let us see what difference does the hibernation make. Thanks, Fiery

Thank you. Please expand the Devices group in the left menu in AIDA64, and right-click on USB Devices --> Quick Report --> Plain Text. Copy-paste the full results into this topic. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic. Let me know if the device disconnects while performing the dump.

1) What kind of USB 3.0 enclosures do you use? Is it one particular model, or multiple models? Which one(s) exactly? 2) Do you know what USB-ATA bridge chipset do your USB 3.0 enclosures use? 3) Do you experience similar issues with HD Sentinel or CrystalDiskInfo? Thanks, Fiery

Thank you for the feedback

Yes, it's a BIOS (firmware) limitation that cannot be overridden on your system. On other Dell and Asus systems it is possible to do that, but on several other system the re-activation fails to work for some reason Fortunately on newer systems Intel dropped the MCHBAR locking trick.

Thanks. It seems our efforts to activate MCHBAR in your chipset doesn't work. The BIOS locks the MCHBAR, prevents AIDA64 from re-activating it, and so AIDA64 is still unable to read chipset details from MCHBAR. I'm afraid there's nothing more we can do about that

Thank you for the feedback. Please do the following: 1) Go to the Motherboard / Chipset page in AIDA64 2) Then right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Copy-paste the full results into this topic. Thanks, Fiery

I'm afraid we couldn't find a way to get around that limitation yet

Thank you for the feedback