The first thing to know about FATAL ERROR: Unhandled e0434352h Exception at fd1ba06dh is that the second hex value is worthless. Autodesk says so explicitly: “the last sequence of letters and numbers will be different for every machine.” Searching for your specific address is how people lose an evening. It identifies nothing.
The first code is not worthless. e0434352h is the Windows exception code for a .NET Framework exception — which is exactly why a corrupt .NET installation sits on Autodesk’s list of causes. The other common variant, Unhandled Access Violation Reading 0x0000, means AutoCAD dereferenced a null pointer. Both usually resolve to the same short list of culprits.
Split the problem before you fix anything
Autodesk maintains separate articles for the two situations because the causes barely overlap.
| When it happens | Most likely area |
|---|---|
| While working — intermittently, during normal drawing | Graphics card, driver, permissions, file location |
| At launch or on opening a drawing — reproducible | File path length, user profile, .NET, add-ons, updates |
If you also see “Error Handler Re-Entered. Exiting now.”, or AutoCAD comes up missing its ribbon and tool palettes before dying, you are firmly in the second group — that combination points at a damaged user profile or installation.
Crashing while you work: start with graphics
For intermittent fatal errors during normal use, Autodesk’s cause list is short and graphics-heavy: high load on an older graphics card, an outdated or corrupted display driver, missing permissions on Autodesk folders and registry keys, and the file’s location.
1. Update the display driver — the certified one
Not the newest driver: the certified one. Autodesk publishes a graphics-hardware certification list per product and release, and the certified driver is frequently older than what the vendor’s auto-updater installs. If you have recently let NVIDIA or AMD update itself and the crashes started, that is your first suspect.
2. Turn off the expensive display features
Type GRAPHICSCONFIG at the AutoCAD command line and switch off High Quality Geometry and Smooth Line Display. If it still crashes, go back and turn hardware acceleration off entirely.
Hardware acceleration off is a slower AutoCAD, and it is not where you want to end up permanently — but it is a decisive test. If the crashes stop dead, the fault is the GPU or its driver, and you now know what to fix rather than guessing.
3. Force the discrete GPU
On laptops with switchable graphics, AutoCAD is often running on the integrated chip without anyone noticing. Set the high-performance profile for AutoCAD in the graphics driver control panel so it uses the discrete card. Autodesk documents this separately for exactly this failure.
4. Older or low-end cards: change the system variables
Autodesk publishes a set of system-variable changes for improving AutoCAD performance on older or low-end graphics hardware, and separately notes that setting the system environment to run with a previous version of DirectX can help, depending on the card and the AutoCAD release. Both are legitimate steps for an ageing workstation.
5. Test with an administrator account
If AutoCAD is stable as an administrator but crashes for a standard user, the cause is permissions on Autodesk folders and registry keys. Fix the permissions to Autodesk’s published requirements rather than leaving people running elevated.
6. Save the file locally
Working directly on a network share, a synced cloud folder, or through Desktop Connector is a documented cause. Copy the drawing to the local disk and work there. If the crashes stop, the network path was the problem and the answer is a proper workflow — check out, work local, check in — not a faster network.
Crashing at launch or on opening a drawing
1. Check the file path length
This is first on Autodesk’s list and it is the one nobody expects. An excessively long path to the drawing will crash AutoCAD on open. Move the file to a shorter path — or map a network drive to part of the path so what AutoCAD sees is shorter. Deeply nested project folders on a server are the usual offender.
2. Reset the AutoCAD user profile
Corruption in the AutoCAD profile is a named cause, and resetting AutoCAD to defaults is quick. Note what you lose: custom workspaces, palette layouts, support file search paths. Export or note them first if they matter, then reset and test.
3. Install the product updates
From Autodesk Account or Autodesk Access. As with Revit, an update frequently clears a crash its release notes never mention.
4. Repair the .NET Framework
Given what e0434352h means, this is more relevant here than it looks. Check Microsoft’s download page for the current recommended version and repair the installation. Autodesk’s guidance is blunt about the endgame: if .NET cannot be repaired, the operating system needs reinstalling.
Reinstalling the Visual C++ redistributables belongs in the same pass — and on a 64-bit system you need both the x86 and x64 packages.
5. Read Windows Event Viewer for the faulting DLL
Event Viewer names the module that failed. That single line converts a generic fatal error into a specific one — a graphics DLL points at drivers, a plug-in DLL points at the add-on that owns it.
One entry has its own documented meaning: Microsoft-Windows-PerfProc Event ID 2002. Autodesk lists it as caused by a corrupt performance-counter list, the Remote Registry service not running on a remote system, File and Printer Sharing not being enabled through the firewall on a remote system, or the application running as a user with insufficient privileges. The first move there is sfc /scannow from an elevated command prompt to repair system corruption, then relaunch AutoCAD.
6. Remove third-party plug-ins — and one specific module
A corrupt or incompatible plug-in is a standard cause; disable them all and retest. Two are named explicitly in Autodesk’s documentation: a File Locking plugin, which should be updated or uninstalled from Control Panel, and the AutoCAD SPDS module — the add-on supporting the Russian construction documentation standards — whose corruption produces this exact error.
7. Proxy, VPN and LAN settings
Invalid proxy or VPN settings are listed as a cause of the launch crash. To check the LAN configuration: Control Panel → search Internet Options → Connections tab → LAN Settings. An automatic-configuration script pointing at something unreachable will hang and then fail AutoCAD’s start-up network calls.
8. Clean uninstall, then reinstall
Last, not first. Follow Autodesk’s clean-uninstall procedure for Windows so residual files and registry entries actually go, then reinstall. A plain uninstall and reinstall usually reproduces the fault, because the corruption lives in what a plain uninstall leaves behind.
The five-minute triage
If you have five minutes and want the highest chance of a result:
- Copy the drawing to
C:\Tempand open it from there. Tests path length and network location at once. GRAPHICSCONFIG→ hardware acceleration off. Tests the entire graphics stack.- Launch with add-ins disabled.
- Open Event Viewer and read the faulting module name.
Those four steps will tell you which of the two lists above you should be working, and often solve it outright.
What not to do
Do not search for your hex address. It is machine-specific. Forum threads titled with a specific address are not about your problem.
Do not reinstall as step one. It does not remove the plug-ins, the corrupt profile, the driver or the permissions — the four things most likely to be causing it.
Do not replace your installation with a copy from elsewhere. A fatal error is a condition on your machine. An unverified installer changes nothing about the cause and adds a package nobody has checked.
Common questions
Is my drawing corrupt?
Possibly, but test it properly: open a different drawing. If everything crashes, the file is not the cause. If only one does, AutoCAD has documented repair procedures for damaged DWG files — use those rather than reopening it repeatedly.
Does this affect Civil 3D too?
Yes. Civil 3D is built on AutoCAD and produces the same e0434352 unhandled exception, with its own Autodesk article covering it. The causes and the approach are the same.
It only happens when I save to our cloud folder.
That is a separately documented case: fatal errors when opening or saving to Autodesk Construction Cloud via Desktop Connector. Work locally and sync deliberately while you resolve it.
How do I know if my machine is simply below spec?
Check the real figures rather than assuming. AutoCAD 2026 asks for 8 GB of RAM as a minimum and 32 GB as the recommendation, with a 2 GB DirectX 11 GPU as the floor and 8 GB DirectX 12 recommended — and DirectX 12 Feature Level 12_0 is required for the “Fast” visual styles. The full table for every Autodesk product is in our 2026 system requirements comparison.
Related
If AutoCAD will not install at all, see Autodesk install error 1603. If it installs but refuses to license, see Autodesk licensing errors. For Revit specifically, see Revit crashes on startup.
And if the crashes have you reconsidering which licence you are paying for, we cover what AutoCAD costs in 2026, AutoCAD against AutoCAD LT, and what the specialised toolsets actually include.
Sources
Based on Autodesk’s own support documentation, checked on 29 August 2026: “FATAL ERROR: Unhandled e0434352h Exception at…” when starting AutoCAD products, “Fatal Error: Unhandled e0434352h Exception at…” while working in AutoCAD, and “FATAL ERROR: Unhandled Access Violation Reading…” when launching AutoCAD products.
