Getting a fatal error when using certain commands, closing or saving files, using hatch or when copying / pasting objects in AutoCAD. The following error message is displayed followed by AutoCAD closing.

AutoCAD Error Aborting

FATAL ERROR: Unhandled e0434352h Exception at fd099e5dh

Some customers have recently reported receiving a fatal error when launching their AutoCAD-based software. In addition to AutoCAD, the issue has affected customers using AutoCAD Architecture, AutoCAD Map 3D, and AutoCAD Civil 3D. When launching the software, the respective splash screen displays, and immediately after the Start Page appears, the following error displays:

[caption id="attachment_27958" align="alignnone" width="373"]

Fatal Error: Unhanded e0434352h Exception at 95a27788h[/caption]

Uninstalling and reinstalling the software will typically clear up issues like this, but it had no effect in this particular case. The issue proved to be a conflict with a recent Microsoft .NET update.

The final solution remedying this error was as follows:

1. Uninstall Microsoft .NET from your machine.
2. Uninstall AutoCAD (or AutoCAD-based vertical application affected).
3. Reboot Windows.
4. Reinstall AutoCAD (or AutoCAD-based vertical application affected).
5. Reboot Windows.
6. Launch AutoCAD (or AutoCAD-based vertical application affected).

In lieu of uninstalling AutoCAD, some customers have reported success choosing "Reinstall" in lieu of fully uninstalling the software. We've seen mixed success using this method, and recommend completing the full method outlined above if at all possible.

Sorry for the off-topic of SketchUp and Twilight, but I'm putting this here for safe-keeping in case it will help anyone out there on the interwebs searching for an answer to this problem.

Error message from ACAD every time it crashes is something like this: autocad LT error aborting fatal error unhandled e0434352h Exception at 5bb34b89h

Ok, so AUTOCAD crashing with fatal error unhandled e0434352h Exception appears to be solved!

The answer was unpredictable and weird.

In Windows 10 settings I disabled the text cursor indicator and returned the cursor thickness to normal default. ACAD stopped crashing! It hasn’t crashed today. Apparently Windows was fighting with ACAD to add these features to the cursor anytime I was typing in ACAD commands, but simultaneously I was drawing and it was getting confused what to do... causing a crash.

Read the full story only if interested:

I was trying to think of anything I changed lately that may effect autoCAD. I noticed that it crashed more the faster I tried to work. So the faster I typed my commands, then it would crash more often.

So then I remembered…

Lately my eyesight is not 20/20 like it used to be. So running double screens sometimes I find I lose where my mouse or cursor are.

I went into Windows system settings for the cursor and the mouse a couple of weeks ago and (foolishly) enabled “Turn on text cursor indicator” and increased the size of the cursor indicator as well as the cursor appearance which sort of acts as a “highlight cursor” feature.

This is what was apparently was causing ACAD to crash. Because after all the other major changes nothing changed and ACAD kept crashing (update ACAD, update graphics driver, update windows, yadda yadda).

But once I DISabled the text cursor indicator and returned the cursor thickness to normal default. ACAD stopped crashing! It hasn’t crashed today.

So annoying. How many hours of my life were lost to that weirdness?

Apparently ACAD and Windows could not figure out what to do with this cursor indicator when I was drawing and typing commands simultaneously.

Hello. Thank you for providing those CER

s. From what I can tell, both crashes point to a problem in an addon app called "PlayCAD".

I would suggest you check with the developer of that app to see if they are aware of any issues in their app when used on the newer versions of .NET that you have. Or, perhaps they have a newer version available.

Here is some .NET detail from those CERs that may be of use in your communication with the PlayCAD developer:

at PlayCADSupport.ColorCodeValidation.AllCodesFromRepStudioMatchPlayCAD()

at PlayCAD.Managers.CommandManager.DocumentManager_DocumentCreated(Object sender, DocumentCollectionEventArgs e)

at Autodesk.AutoCAD.ApplicationServices.DocumentCollectionEventHandler.Invoke(Object sender, DocumentCollectionEventArgs e)

at Autodesk.AutoCAD.ApplicationServices.DocumentCollection.FireDocumentCreated(DocumentCollectionEventArgs e)

-Last Unhandled Exception: -Last 3 'first chance' exceptions (may not be related to the crash if they were handled): -Last-0 'first chance' exception: System.Exception: There was an issue comparing the RepStudio color codes to the available PlayCAD color Codes. System.ArgumentException: The string was not recognized as a valid Uri. Parameter name: inputUri

at System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext)

at System.Xml.Linq.XElement.Load(String uri, LoadOptions options)

at PlayCADSupport.QueryTool..ctor(String fileName) at PlayCADSupport.PlayGroundData..ctor()

at PlayCADSupport.ColorCodeValidation.AllCodesFromRepStudioMatchPlayCAD()

at PlayCADSupport.ColorCodeValidation.AllCodesFromRepStudioMatchPlayCAD()

-----Last-1 'first chance' exception: System.ArgumentException: The string was not recognized as a valid Uri. Parameter name: inputUri

at System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext)

-----Last-2 'first chance' exception: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program Files\Autodesk\AutoCAD 2018\PlayCAD\ApplicationVariables.xml'.