AutoCAD 2016 mc3.dll / mc3d.dllARX Command Error

[Anonymous]

Upon opening a drawing in AutoCAD Architecture 2016 I get the error Exception in mc3.dll / mc3d.dll ARX Command. Unhandled Exception C0000005 (Access Violation Reading 0x0000) at Address C9C860F4h I am running windows 7 and Autocad is completely up to date. This randomly started happening after windows forced close the application to restart

[Anonymous]

I tried to repair installation with no success.

[Anonymous]

After hitting OK the AutoCAD Error Aborting message says: FATAL ERROR: Unhandled Access Violation Reading 0x0000 Exception at cb1060f4h

[Anonymous]

Then a screen pops up saying AutoCAD Error-abort: Error handler re-entered. Exiting now.

[Anonymous]

I'm having this same exact issue as well.  My entire company to be exact.  Mix of Win10, 8, & 7 all 64bit.  AutoCAD MEP 2016 Service Pack 1.

This is bringing our entire production to a screeching halt.

[Anonymous]

I know it's a reply to myself, but it seems that anyone that has updated to Service Pack 1 has the issue.

[Anonymous]

I am having the same issue! I completely unistalled all 2016 software and restarted the machine many times and completely reinstalled.  Now OOB it is still giving me the error!  I did install the Service Pack 1 and it gave me the error before and after the install.

Now what do we do?!

[pgraf]

Chiming in here - I'm having the exact same issue right now. It started between 10 and 11 this morning.

[sgallant-P_2137]

same problem here: all the computer in my company equiped with mep 2016, sp1 or not, have the MC3D.dll error ! the problem arrive here in Quebec, Canada this morning exactly on november 5.

[Anonymous]

I should have mentioned this too - I am using ACA 2016.  It started for me about 7-7:30 CST.

Of course, there is a deadline tomorrow! 

[Anonymous]

After a little more research it does affect any installation of AutoCAD 2016, regardless of service pack install.  A current possible fix for us so far has been to replace the mc3.dll on local machines with mc3.dll found within the installation/deployment folder.

I'll update more with more testing.

[Anonymous]

we are having the same issue.   could it be a microsoft .net 4.5.1 or a .net 4.5 issue?

[Anonymous]

Seems the temporary fix is easier than expected.  We simply renamed the mc3.dll file to something different (mc3.dll.bak in our case) and AutoCAD repopulates this file on its own.  I only say temporary fix because this is a blatant Autodesk issue and they should have a real fix coming soon.

[Anonymous]

I installed SP1 and the issue seems to have stopped.  

[Anonymous]

Just wait, it will come back.  We have done it all: Update to SP1, failed eventually.  Uninstall-reinstall, failed immediately.  Uninstall-reinstall-update to SP1, failed eventually.

[Anonymous]

This problem has occupied my entire morning looking for a solution and I am glad to have found this thread. PLEASE post if you have been informed of any real fix from Autodesk.

Just to add to the burning pile of frustration: I have restarted the computer after every attempt of normalizing the software, repaired and reinstalled AutoCAD Arch 2016, fully uninstalled and reinstalled the program. Nothing has worked, it shuts down due to the fatal error every time.

Edit: I have also installed the service pack, which allowed the program to work for a longer duration than other attempted remedies, but ultimately resulted in the same fatal error.

[dbroad]

Just so you know you're not alone, it is happening here as well. Started this morning.  Our only workaround has been to back up to AutoCAD 2015.

[chughes]

Same error, Autocad Architecture 2016 SP1 Windows 10

[Anonymous]

Good evening I am an Italian student and I had the same problem: Error C0000005.
I installed Autocad Architecture 2016 English version with Italian package 1 week ago and only now this problem presents to me.
What I have to do now?
Maybe I have to uninstall ACA 16 and install it again? Or do you think I have to wait that Autodesk resolve the problem?
Thank you everyone
Edoardo

[Anonymous]

So Jesse, how's that rename workaround doing? Is it holding so far?