Application Crash when any version after 4.00 2760 beta is installed

[pbcopter]

With every version of AIDA64 extreme after 4.00 2760 beta, including the latest 4.20 2800, I have had the application stop working after being idle for some period of time,

This usually happens when I leave my system running overnight.

 

This did not happen prior to 4.00 2766.

 

I have included the Event log entrees.

 

Any ideas?

 

Thank you.

 

 

 

Aida64event log.txt

[Fiery]

1) What motherboard, CPU and video card do you have?

 

2) Are you running Windows 7 SP1 64-bit?

 

3) Have you tried to restart Windows after the last upgrade of AIDA64?

 

Thanks,

Fiery

[pbcopter]

Hi Fiery,

 

I am using a Gigabyte GA-X79-UD5, Intel I7 3820 processor, and EVGA GTX 460 SC.

 

Windows 7 x64 SP1 Ultimate

 

Yes, I have restarted many times.

 

Thank you for the response

 

Paul

[pbcopter]

I installed 4.20 2800 in another system

 

GA-EP45-UD3P, GTX 280, Windows 7 x64 and have not been able to reproduce the problem yet.

 

I will restore a previous Windows 7 x64 installation (from a fresh install) into my GA-X79-UD5 to see if it occurs there.

[pbcopter]

Another piece of data.

 

I have a USB 3.0 card reader/hub from Hootoo plugged into one of the rear USB 3.0 ports on the X79 mother board.

 

Today the card reader began disappearing and reappearing constantly accompanied by the  normal hardware sounds.  I decided to restart the computer since nothing I did, seemed to stop it.  I could not restart as AIDA64 was preventing it.  I tried to exit from AIDA64 and was not able to.  I ended the AIDA64 process in the task manager.

 

I was just about to restart when I noticed that the card reader became stable again.

 

I restarted AIDA64 and all appears normal for the time being.

 

I don't know if this is related to my original problem or not.

 

Also the GA-EP45-UD3P has no USB 3.0

[Fiery]

The card reader issue may be caused by a firmware glitch in your card reader.  You can try disabling the two RAID-related options in AIDA64 / main menu / File / Preferences / Stability, that should fix that issue.  Make sure to restart Windows after altering that option.

[pbcopter]

Thanks Fiery, I tried that and I got the same results. I also tried 4.20 2805 beta.

 

I can only say that 4.00 2760 beta works great with no issues.

 

I shall continue  with my  trouble shooting.

 

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: aida64.exe
  Application Version: 4.20.2805.0
  Application Timestamp: 2a425e19
  Fault Module Name: ntdll.dll
  Fault Module Version: 6.1.7601.22436
  Fault Module Timestamp: 521eaa80
  Exception Code: c0000025
  Exception Offset: 000907ec
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033
  Additional Information 1: abcc
  Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9
  Additional Information 3: abcc
  Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9

[Fiery]

Please upgrade to the latest beta version of AIDA64 Extreme available at:

 

http://www.aida64.com/downloads/aida64extremebuild2808b9s8mvtkpqzip

 

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

 

Let me know if it makes a difference.

[pbcopter]

I have updated to the latest beta version 4.20 2815 and the problem continues.

 

I have totally removed all USB 3.0 hubs and still occasionally get an application crash.

 

This problem only occurs after I let my system run overnight and as such requires significant time to get troubleshooting results.

 

I have also reported another issue in this thread.

 

http://forums.aida64.com/topic/2171-application-error/

[pbcopter]

After uninstalling BitDefender, I have had no further issues with AIDA64.

[Fiery]

Thank you for the info.  Meanwhile, we've done a lot of test runs while having BitDefender 2014 installed, and were able to reproduce the issue.  It seems when AIDA64 creates a new thread, BitDefender makes it produce a memory leak.  We've tried a lot of tricks to avoid it, but found no solution.  No other software or driver causes AIDA64 to produce such memory leak when creating a thread, so we've concluded that this is a BitDefender-related issue that I'm afraid we cannot fix from our end.