Fiery Posted February 28, 2014 Share Posted February 28, 2014 Maybe the Access violation message comes up on your systems when your computers go to sleep? Can you please try to initiate a manual sleep, and see if the error comes up?Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
Darien Posted February 28, 2014 Author Share Posted February 28, 2014 Mine is a desktop, and sleep and hibernate are both disabled. I just did a shutdown and cold boot, and the issue popped up again, followed by AIDA64 crashing entirely ("AIDA64 has encountered a problem..."). I'm running the latest Beta (updated today - 4.20.2815). Quote Link to comment Share on other sites More sharing options...
Darien Posted March 5, 2014 Author Share Posted March 5, 2014 Update: from cold boot today, this happened again: Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 6, 2014 Share Posted March 6, 2014 We've done quite a few changes to threading features of AIDA64, so please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2820nk4ztxrp6fzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Quote Link to comment Share on other sites More sharing options...
Darien Posted March 7, 2014 Author Share Posted March 7, 2014 Thanks Fiery, I'll give it a try. Quote Link to comment Share on other sites More sharing options...
Darien Posted March 9, 2014 Author Share Posted March 9, 2014 No luck. Cold boot this morning: I think I'll just give up and live with it. Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 10, 2014 Share Posted March 10, 2014 No luck. Cold boot this morning: I think I'll just give up and live with it. Thank you The strange thing is that the issue seems to be coming up when doing plain & simple string operations while scanning for Windows Devices. We suspect the issue could be caused by a driver of an installed device in your system that returns a scrambled text that causes the string operations to go south. If you have a bit more patience about this issue, I can send you a special beta build of AIDA64 that would output a lot more debug information, so we could dig down deeper and hopefully find out which device causes the issues, and which device information string has the improper content that makes the string operations go wrong. BTW, the actual device that is behind these issues must be a rare one, since we haven't got similar bug reports from other users. Do you happen to have a very unique, very rare device in your system? Either a PCI/PCIe card, a USB or eSATA device? Quote Link to comment Share on other sites More sharing options...
Darien Posted March 10, 2014 Author Share Posted March 10, 2014 Not that I know of... The only PCIe cards I have are my two GTX460's, and I don't have any esoteric USB/eSATA devices. I'm happy to keep working on fixing it if you guys are, but I realise it must be a time sink for one user. Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 10, 2014 Share Posted March 10, 2014 No problem about the time. We definitely want to find this issue and implement a fix or a workaround to get around it. I've just sent you a private message about this. 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.