Access Violation errors in Random modules (or no module mentioned at all)

[Squall Leonhart]

This appears to have been introduced in build recently,

 

though i can atleast trigger it manually in 2327 by opening the summary page

 

newer versions do it at random, with 2341 having the highest frequency.

 

I expect it may have something to do with the Logitech LCD driver, as others have mentioned before.

 

 

I don't get them with build 2300 and build 2313

[Fiery]

Can you please check if you experience the access violation issue with Build 2320?

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

 

We've implemented CPU Throttling monitoring in Build 2317, so if 2313 works fine but 2320 fails, then there's a chance CPU Throttling monitoring causes the issues.

 

 

Thanks,

Fiery

[Squall Leonhart]

yeah, errors start with 2320 (Access Violation at address FFFFFF)

[Fiery]

I've just sent you a private message about this issue.

[Squall Leonhart]

Replied

[Fiery]

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.

[Squall Leonhart]

Yup, i can't use any version of Aida64 that has throttle monitoring, i do remember suggesting that it could be an option under stability settings.

User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: SRV*c:\symbols\win7_64*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Wed May  8 15:59:14.000 2013 (UTC + 10:00)
System Uptime: not available
Process Uptime: 0 days 0:16:54.000
................................................................
......
Loading unloaded module list
...................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(2570.2d60): Unknown exception - code c0000096 (first/second chance not available)
eax=00000000 ebx=00000000 ecx=00003933 edx=00003932 esi=0043b728 edi=00000000
eip=007cf478 esp=ab8717aa ebp=007cf42a iopl=0         ov up ei pl zr na pe cy
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010a47
*** ERROR: Module load completed but symbols could not be loaded for aida64.exe
aida64+0x3cf478:
007cf478 656c            ins     byte ptr es:[edi],dx       es:002b:00000000=??
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for LgLcdApi.dll -
GetPageUrlData failed, server returned HTTP status 404
URL requested: http://watson.microsoft.com/StageOne/aida64_exe/2_85_2440_0/2a425e19/aida64_exe/2_85_2440_0/2a425e19/c0000096/003cf478.htm?Retriage=1

FAULTING_IP:
aida64+3cf478
007cf478 656c            ins     byte ptr es:[edi],dx

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 007cf478 (aida64+0x003cf478)
   ExceptionCode: c0000096
  ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME:  aida64.exe

ERROR_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

DEFAULT_BUCKET_ID:  STATUS_PRIVILEGED_INSTRUCTION

MOD_LIST: <ANALYSIS/>

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

FAULTING_THREAD:  00002d60

PRIMARY_PROBLEM_CLASS:  STATUS_PRIVILEGED_INSTRUCTION

BUGCHECK_STR:  APPLICATION_FAULT_STATUS_PRIVILEGED_INSTRUCTION

UNALIGNED_STACK_POINTER:  ab8717aa

LAST_CONTROL_TRANSFER:  from 00000000 to 007cf478

STACK_TEXT:  
007cf42a 00000000 55007cf4 c38b49e8 89f88bff aida64+0x3cf478


FOLLOWUP_IP:
aida64+3cf478
007cf478 656c            ins     byte ptr es:[edi],dx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  aida64+3cf478

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aida64

IMAGE_NAME:  aida64.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  2a425e19

STACK_COMMAND:  dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s; .ecxr ; kb

FAILURE_BUCKET_ID:  STATUS_PRIVILEGED_INSTRUCTION_c0000096_aida64.exe!Unknown

BUCKET_ID:  APPLICATION_FAULT_STATUS_PRIVILEGED_INSTRUCTION_aida64+3cf478

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/aida64_exe/2_85_2440_0/2a425e19/aida64_exe/2_85_2440_0/2a425e19/c0000096/003cf478.htm?Retriage=1

Followup: MachineOwner
---------
 

[Fiery]

Have you tried it with the latest beta version of AIDA64 Extreme Edition?

 

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

[Squall Leonhart]

Yep, thats where i got that crash.

 

dmp file link in pm

[Fiery]

Thank you.  Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:

 

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

 

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

 

Let me know if it helps.

[Squall Leonhart]

Seems to be ok so far,  I guess the dump file helped?

 

Edit

 

spoke too soon,  same crashes still happening, and i can rule out the Asus AsIO and AsUpIO as well

[Pill]

Confirmed, happens if sensor page is left open when AID64 is minimized to taskcbar.

 

It only started to occur after installing the latest 13.6 AMD drivers, It may help you to know the latest 13.6 set require an updated VC runtime (included with package).

[Squall Leonhart]

It happens at any time in my case, possibly because i have Logitech LCD support enabled.

[Fiery]

Confirmed, happens if sensor page is left open when AID64 is minimized to taskcbar.

 

It only started to occur after installing the latest 13.6 AMD drivers, It may help you to know the latest 13.6 set require an updated VC runtime (included with package).

 

Since the exception seems to be related to NTDLL.DLL, we've added stronger exception handling for every calls in AIDA64 that uses NTDLL.DLL.  It will be implemented in the next AIDA64 stable release due tomorrow

[Squall Leonhart]

Excellent, this improves the debug information generated as well

 

 

 

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for LgLcdApi.dll -
*** ERROR: Module load completed but symbols could not be loaded for aida64.exe
GetPageUrlData failed, server returned HTTP status 404
URL requested: http://watson.microsoft.com/StageOne/aida64_exe/3_0_2500_0/2a425e19/unknown/0_0_0_0/bbbbbbb4/c0000005/00000019.htm?Retriage=1

FAULTING_IP:
+b6f0210
00000019 ??              ???

EXCEPTION_RECORD:  0265fa34 -- (.exr 0x265fa34)
ExceptionAddress: 00000000
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000000
Attempt to read from address 00000000

PROCESS_NAME:  aida64.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000008

EXCEPTION_PARAMETER2:  00000019

WRITE_ADDRESS:  00000019

FOLLOWUP_IP:
user32!InternalCallWinProc+0
74a562d7 55              push    ebp

FAILED_INSTRUCTION_ADDRESS:
+0
00000019 ??              ???

MOD_LIST: <ANALYSIS/>

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  0265fa84 -- (.cxr 0x265fa84)
eax=75d90009 ebx=0265fd88 ecx=7725128f edx=75d70000 esi=00b6b0cf edi=00000000
eip=00000000 esp=0265fd6c ebp=0265fd88 iopl=0         nv up ei pl nz ac pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010216
00000000 ??              ???
Resetting default scope

ADDITIONAL_DEBUG_TEXT:  Followup set based on attribute [is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

LAST_CONTROL_TRANSFER:  from 0043b728 to 00000000

FAULTING_THREAD:  ffffffff

BUGCHECK_STR:  APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID_EXH

PRIMARY_PROBLEM_CLASS:  SOFTWARE_NX_FAULT_INVALID_EXH

DEFAULT_BUCKET_ID:  SOFTWARE_NX_FAULT_INVALID_EXH

STACK_TEXT:  
0265fd6c 00000000 unknown!unknown+0x0
0265fd70 0043b728 aida64+0x3b728
0265fd90 0043b73a aida64+0x3b73a
0265fdbc 004269fe aida64+0x269fe
0265fdd4 74a562fa user32!InternalCallWinProc+0x23
0265fe00 74a56d3a user32!UserCallWinProcCheckWow+0x109
0265fe78 74a577c4 user32!DispatchMessageWorker+0x3bc
0265fed8 74a57bca user32!DispatchMessageA+0xf
0265fee8 0049b818 aida64+0x9b818
0265ff54 00ba31e0 aida64+0x7a31e0
0265ff90 75d833aa kernel32!BaseThreadInitThunk+0xe
0265ff9c 77249ef2 ntdll!__RtlUserThreadStart+0x70
0265ffdc 77249ec5 ntdll!_RtlUserThreadStart+0x1b


STACK_COMMAND:  .cxr 000000000265FA84 ; kb ; dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; dds 265fd6c ; kb

SYMBOL_NAME:  user32!InternalCallWinProc+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: user32

IMAGE_NAME:  user32.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7ba59

FAILURE_BUCKET_ID:  SOFTWARE_NX_FAULT_INVALID_EXH_c0000005_user32.dll!InternalCallWinProc

BUCKET_ID:  APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID_EXH_BAD_IP_user32!InternalCallWinProc+0

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/aida64_exe/3_0_2500_0/2a425e19/unknown/0_0_0_0/bbbbbbb4/c0000005/00000019.htm?Retriage=1

Followup: MachineOwner
---------

 

i'll upload the dmp file in a little while

[Tomorrow]

Hmm i too have crashes with 3.00.2500

Although in my case it crashes without an error message or trace. Just quits and leaves no sign in Event Log.

So i took and backed up my main ini file. Then started with a clean one (let AIDA64 generate one). No crashes. Perfectly stable.

 

So i started to enable settings i have one by one in the hope of finding the culprit.

Everything was stable until i got to File > Prefereces > External Applications. Namely enabling Shared Memory produces an instant crash (again no error message). Also trying to enable any values to be written to Rivatuner OSD serves seems to greatly increase crash frequency.

 

So i figured i had solved the problem and went deleted the new ini file. Replaced with my old ini file and disabled both shared memory and wrinting to OSD (infact disabled all settings under External Applicatons). But no luck. For some reason i even got more frequent crashes than with the new ini.

 

On a hunch i disabled desktop gadget and voila - Stable. No crashes. I went into windows gadgets and noticed there were 2 of them there by AIDA64 - 2.70 and 3.0. Uninstalled 2.70 but no difference.

 

However for complete stability i must have everything unchecked under Extrenal Applications and Desktop Gadget Support must be disabled. For those of you who have problems you may try and disable those and see if it solves your problems. Its ofcourse entirely possible that my problem is completely unrelated to this but you never know.

 

Core i5 2500K

Windows 7 x64 SP1 fully updated

Latest Visual C++ runtimes and latest .NET 4.5

Logitech LCD support NOT enabled tho i do have Logitech G11 (SetPoint and Gaming Software v8 running in background).

[Psychor]

Our issues may be related. Here's a direct link to my thread: http://forums.aida64.com/topic/1333-crash-city-application-error-w-v3002500/

[Fiery]

We've made several modules of AIDA64 more solid by improving exception handling.  We've also disabled CPU throttling measurement by default.  Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:

 

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

 

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

 

Let me know if it helps.

 

 

Thanks,

Fiery

 

[Psychor]

We've made several modules of AIDA64 more solid by improving exception handling.  We've also disabled CPU throttling measurement by default.  Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:

 

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

 

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

 

Let me know if it helps.

 

 

Thanks,

Fiery

 

 

Thanks. Updating through AIDA64 now. I'll let you know.

[Tomorrow]

We've made several modules of AIDA64 more solid by improving exception handling.  We've also disabled CPU throttling measurement by default.  Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:

 

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

 

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

 

Let me know if it helps.

 

 

Thanks,

Fiery

 

This fixed it for me.

[Fiery]

Thank you for the feedback

[ssdpro]

This may or may not be related here, but I get an access violation on each startup using beta 2505.  I usually have to retart 4 or 5 times before it loads properly.  Attached is a picture of the fault.

 

ASUS Z87-PRO EFI/BIOS 1007

i7-4770K

 

 

[Fiery]

This may or may not be related here, but I get an access violation on each startup using beta 2505.  I usually have to retart 4 or 5 times before it loads properly.  Attached is a picture of the fault.

 

ASUS Z87-PRO EFI/BIOS 1007

i7-4770K

 

Try to reinstall AIDA64 using the latest ZIP package:

 

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

It looks like one or more of the main DLL files are either missing or got corrupted.

[ssdpro]

Thank you for that suggestion Fiery.  I did uninstall then run from the zip package and didn't have a single error today.  Consequently I did download the stable and had it auto-update to the beta and got the same issue - I am not sure if my system is borked that or it is just a glitch but either way... the zip itself works great for me.  Thanks