Jump to content

Randomn AutoIt3_x64 Crashes with dmp file created


Recommended Posts

Hello,

we are getting randomnly AutoIt3_x64 crashes, and cannot find the reason.

Windows 7 64bit tells, that AutoIt3_x64 must be closed and creates dmp file.

We would be very thankful for a solution to find out the reason.

Cheers mike

Edited by mike1950r
Link to post
Share on other sites

Hi,

I cannot say from which script this bug came, since it's aserie of scripts beeing run.

The only information comes from the dmp file:

Symbol search path is: SRV*c:\programme\winddk\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Version 7601 (Service Pack 1) MP (12 procs) Free x64
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Sun Sep 18 22:11:07.000 2022 (UTC + 2:00)
System Uptime: not available
Process Uptime: 0 days 0:01:55.000
.........................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(b24.b4c): Access violation - code c0000005 (first/second chance not available)
ntdll!NtWaitForMultipleObjects+0xa:
00000000`77359d5a c3              ret
0:000> ecxr
*** ERROR: Module load completed but symbols could not be loaded for AutoIt3_x64.exe
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for iertutil.dll - 
Couldn't resolve error at 'cxr'

May be I can get more light into this.

Thanks mike

 

Link to post
Share on other sites

thanks,

btw
all my scripts are syntax checked.
Autoit does not prompt any error and the crashes are rare and randomly.

if I use a newer version of the program,
will this be downward compatible with older scripts?

cheers mike

Edited by mike1950r
Link to post
Share on other sites

..an incompatibility is unlikely. Syntax tends to remain with newer versions BUT if the original script is too old then there may be script braking changes but those would show in the syntax checker, unless SciTE wasn't updated accordingly.
There may be challenges in regards to iExplorer due to it, been replaced by chromium browsers in newer OSs. So you may have to re-engineer that aspect of your code to stay current with these new technologies.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...