pbcopter Posted November 17, 2011 Share Posted November 17, 2011 I am using the latest beta version of AIDA64 Extreme build 1720 (although I have tested it with previous versions as well). When I safely remove a portable drive, AIDA64 crashes with the following error. Exception EStringListError in module aida64.exe at 000257C2. List index out of bounds (8). I am using the sensor panel. I am running Windows 7 x64 Ultimate. Quote Link to comment Share on other sites More sharing options...
Fiery Posted November 17, 2011 Share Posted November 17, 2011 1) Do you simply disconnect the drive without ejecting it from the System Tray icon? 2) Is it a USB, FireWire or eSATA drive? Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
pbcopter Posted November 17, 2011 Author Share Posted November 17, 2011 I eject it from the System Tray. It happens with both USB and eSATA hard drives. It does not happen with USB thumb drives. Quote Link to comment Share on other sites More sharing options...
pbcopter Posted November 18, 2011 Author Share Posted November 18, 2011 I have found that this will occur when any internal drive is removed as well. For example, if the drive is disable in the Device manager. If I uncheck Low-level SMART operations, the crash does not occur. Quote Link to comment Share on other sites More sharing options...
pbcopter Posted December 2, 2011 Author Share Posted December 2, 2011 Any updates on this issue? Quote Link to comment Share on other sites More sharing options...
Fiery Posted December 5, 2011 Share Posted December 5, 2011 I'm sorry for the delays. It took quite a while to reproduce the issue and fix it up. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...40jw8gb7pkfzzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
pbcopter Posted December 5, 2011 Author Share Posted December 5, 2011 Hi Fiery, It appears that the latest update 2.00.1740 beta has fixed this problem. Thank you for your efforts. Paul Quote Link to comment Share on other sites More sharing options...
Fiery Posted December 5, 2011 Share Posted December 5, 2011 Thank you for the feedback Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.