AOS Crashed with Exception : an access violation (0xC0000005) when trying to read from memory location 0x00000000 on thread 39

(0) Share

Report

Posted on by Community Member

Hi,

We are facing this issue on our production environment.

AOS randomly crashes with the error.

In Ax32Serv__PID__17992__Date__01_05_2019__Time_03_07_26PM__295__Second_Chance_Exception_C0000005.dmp the assembly instruction at Ax32Serv!DBDAlloc+din C:\Program Files\Microsoft Dynamics AX\60\Server\MFEL_PROD_AX2012R3\bin\Ax32Serv.exe from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 39

Has anyone faced this issue. I tried uploading the error dump file on LCS Crash\Hang Analysis tool but its been more than a day and still no report has been generated.

would be thankful of anyone could help.

Rajat.

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Community Member on at

Like (0)

Report

Hi Rajat Garg,

If LCS Analysis Tool doesn't work,you can also use the Debug Diagnostic Tool to analysis the dump file.

Here is the Debug Diagnostic Tool download link :www.microsoft.com/.../details.aspx.

And this is step by step tutorial for using Debug Diagnostics to analyze a memory dump :docs.microsoft.com/.../how-to-use-debug-diagnostics-to-analyze-a-memory-dump.

Best regards

Tom Cai

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Tom Cai,

Thanks for Replying

I followed the suggested steps and got following output.

Can you please suggest what should be the next course of action.

Thanks,

Rajat Garg

Was this reply helpful? Yes No
guk1964 10,888 on at

Like (0)

Report

Check that you have not enabled hot swapping of assemblies.

Try the information suggestion in your screen shot to also analyse hangs.

Check your kernel version is up to date and is the same on all aos and clients.

Check through all of the user logs for the 30 minutes or so before the crash and see what is logged/what they were doing. tedious but should give some clue.

Check for any hotfixes released since your current version.

The other suggestion given in your screen shot is to contact Microsoft which would seem a good idea when you have an obscure message like this..

Was this reply helpful? Yes No