Before you change a single setting, answer one question: does Revit crash at launch, with no model open, or does it crash when you open a particular model? Autodesk’s own troubleshooting splits at exactly that point, and the two paths share almost nothing. Getting this wrong is why people spend a day reinstalling Revit to fix a corrupt link inside one project.
If Revit reaches the splash screen and dies before you have touched anything, you are on Path A. If it starts fine and only falls over when a specific file opens, you are on Path B. Work the one that matches.
Read the journal first
Revit writes a journal file every time it runs, and it keeps writing right up to the moment it dies. This is the difference between troubleshooting and guessing.
Open several journals from crashed sessions in a text editor, jump to the end of each, and compare the last lines. If they look the same, you have one fault and a fixable pattern. If they look different, you have several unrelated crash conditions, and Autodesk’s own guidance is to gather a larger sample before changing anything — otherwise you will “fix” one cause, see the crashes continue, and conclude the fix did not work.
One line is worth recognising on sight:
ExceptionCode=0xc0000005, ExceptionFlags=0x00000000, ExceptionAddress=...0xc0000005 is an access violation — Revit tried to read memory it was not allowed to touch. On its own it does not name the culprit, but combined with Windows Event Viewer it usually does: Event Viewer names the faulting module, and that DLL is your answer.
Path A — Revit crashes at launch
Install the latest Revit update. Then open Autodesk Access and confirm the shared components are current too — the Licensing Service, Identity Manager and Single Sign-On component. People update Revit and stop there; the shared components are a separate update stream and are a documented cause of launch crashes. Finish with Windows Update, including the optional items.
Even when the release notes say nothing about your symptom, applying the current update frequently clears unexplained behaviour. It is the cheapest thing on this list.
2. Disable every add-in and clear TEMP
Third-party add-ins are the leading cause of Revit instability, and the test is binary: disable all of them, launch Revit. If it starts, re-enable them one at a time until it breaks again. Yes, that is tedious. It is also the only way to identify which one, and it takes less time than any other approach.
While you are there, clear the Windows temporary files. Press Start, type %TEMP%, press Enter, select everything and delete it.
3. Run as administrator, with antivirus off
A diagnostic, not a fix. If Revit launches as administrator with the antivirus disabled, you have learned that the problem is permissions or security software rather than Revit — and you then solve it properly with folder exclusions or corrected permissions instead of running elevated forever.
4. Test with a brand-new Windows profile
Create a fresh local user account, give it administrator rights, sign in and launch Revit. This single test separates “Revit is broken” from “this Windows profile is corrupt”, and a corrupt profile is a documented cause. If Revit works in the new account, repair or migrate the old profile rather than reinstalling anything.
5. The AMD driver case: atiadlxx.dll
This is the payoff for reading Event Viewer. If the faulting module is named as atiadlxx.dll:
- Go to
C:\Windows\system32. - Find
atiadlxx.dll. - Rename it to
atiadlxx.dll.bak. - Restart the machine and launch Revit.
Do this only when Event Viewer actually names that file. Renaming system DLLs on a hunch is not a troubleshooting strategy.
6. ProjectWise Explorer
Bentley’s ProjectWise Explorer integration is documented by Autodesk as a cause of Revit crashing on launch. Remove it and test. If Revit then starts, the fix is a compatible ProjectWise version, which is a question for Bentley support rather than Autodesk.
7. Revit 2019 and older only
Older releases use the FlexNet licensing files, and stale ones can stop Revit launching. With all Autodesk software closed:
- In
C:\ProgramData\FLEXnet, rename or deleteadskflex_<number>_tsf.data,adskflex_<number>_event.logandadskflex_<number>_tsf.data_backup.00. Turn on hidden files first or you will not see them. - Rename
C:\Users\<username>\AppData\Roaming\Autodesk\ADUTto something else, e.g.ADUT2. - Empty the contents of
C:\ProgramData\Autodesk\CLM\LGS.
Do not run these on 2020 or newer. Those releases use the Desktop Licensing Service instead, and the fixes for it are in our Autodesk licensing errors guide.
Path B — Revit crashes when opening a model
Different fault, different list. Start by establishing whether it is every model or one model, because that answer redirects everything.
If it is a cloud model
Models on BIM 360 or Autodesk Docs have their own documented failure mode — a crash, with or without a Customer Error Report, on opening any cloud model. That is a separate Autodesk article and a separate fix path; do not treat it as a local Revit fault.
If it is one specific model: bisect the links
This is the most useful technique on the page and almost nobody does it.
- Try opening the file with Audit enabled.
- If that fails, open the model with the worksets containing linked models closed.
- If it opens that way, the fault is in a link. Reload each linked model one at a time until it crashes.
- The last link you loaded is the problem. Now you have something specific to repair or replace, instead of a general suspicion that “the file is corrupt”.
If Revit reports that data in the file is corrupt and needs to be manually recovered, that message has its own recovery procedure — follow it rather than repeatedly reopening the file, which can make matters worse.
If it is every model
Perform a clean uninstall of Revit, reinstall it, disable add-ins, then apply the current updates — in that order. Adding the updates before you have confirmed a clean baseline only muddies the result.
Known specific scenarios worth ruling out
Autodesk documents several crashes that look generic but have named causes. If any of these match your environment, check them before working the general list:
- Windows 11 24H2. There is a documented crash condition tied specifically to that Windows feature update.
- Steel connections on Windows 11. A
SQLDUMPER.EXEwindow flashing open and closed when launching or working in Revit or Advance Steel is a known, separately documented issue. - Revit 2024 with mixed updates. Conflicting or corrupted schemas arise when different machines in a team run different Revit 2024 update levels. The fix is standardising the update level across the team, not repairing individual machines.
- Crash in the File Open / Save / Save As dialogs specifically. That is its own documented condition — often a shell extension rather than Revit at all.
Freezing is not crashing
If Revit does not die but goes unresponsive — particularly in a workshared model — the causes are different again. The journal typically shows long file-existence checks and gaps such as !!!BIG_GAP acquirePermissionsLocks, which is Revit waiting on the network rather than failing.
Autodesk’s recommendations for that case are: apply missing updates, disable third-party plug-ins and retest, install natively rather than running through virtualisation software, and set Worksharing Update Frequency to manual in Revit options. That last one is the setting most likely to give you an immediate improvement on a busy central file — Revit stops polling the central model continuously and only checks when you tell it to.
How to narrow it when nothing obvious matches
Four questions, from Autodesk’s own methodology. Each answer removes a large part of the search space:
- Is the crash specific to one project? → the model or its links.
- Is it specific to one user account? → profile or permissions. Test with a new local administrator account.
- Is it specific to one workstation? → drivers, hardware, installed software.
- Is it specific to one workflow? → the hardest to spot. If a user hits the crash on a second machine that was previously fine, it is something they are doing, not the machine.
Also worth testing: does the crash survive a simplified startup environment, with non-essential services and start-up items disabled? If not, something else on the machine is involved.
Common questions
Could my hardware just be too weak?
It is worth checking, because Revit’s floor is higher than people expect. The 2026 release lists 16 GB of RAM as the minimum, not the recommendation, along with 30 GB of disk space and a further 100 GB of temporary space for point-cloud and rendering work. Our 2026 system requirements comparison has the full figures. Insufficient resources also show up in the journal as an InsufficientResourcesException, which is unambiguous when you see it.
Should I send the Customer Error Report?
Yes. It costs you nothing, and a CER attached to a repeatable crash is what Autodesk Support will ask for anyway. Keep your journal files as well — they are the evidence.
Will reinstalling Revit fix it?
Sometimes, and it is near the bottom of the list for a reason. A reinstall does not remove add-ins, does not repair a corrupt Windows profile, does not update graphics drivers, and does not touch the licensing components. Most launch crashes have one of those four causes.
Is an “unrecoverable error” the same thing?
No — Revit’s unrecoverable/fatal error has its own dedicated Autodesk guide and its own causes. If that is the exact wording you see, follow that path rather than this one.
Related
If Revit will not install in the first place, see Autodesk install error 1603. If it installs but will not license, see Autodesk licensing errors. If you are weighing Revit against AutoCAD for the work you actually do, we compare them in Revit vs AutoCAD, and how much Revit costs in 2026 covers the licence side.
Sources
Based on Autodesk’s own support documentation, checked on 29 August 2026: Troubleshooting Revit crashes, Revit Stability: Fix Crashes on Startup or During File Opening, and Freezing or not responding when working in Revit.
