Quick answer
Make sure the machine has enough RAM (32 GB is a sensible floor for large models) and that Revit and your graphics driver are up to date. Then clean the file itself: Purge Unused, open with Audit ticked, and if it's a workshared model, compact the central file and recreate locals. Run the model from a fast local drive, not over the network.
WHY IT HAPPENS
Revit is memory-hungry — and files get heavy over time.
Revit loads the entire model into memory and can use roughly twenty times the file size in RAM, so a large multidiscipline project quickly outpaces a machine that's short on memory or running an ageing graphics card. On top of that, projects bloat: unused families and materials pile up, imported CAD and heavy links drag on every redraw, thousands of unresolved warnings slow down every edit, and running the file over a slow network share adds lag to every save. Persistent crashes on one specific file usually point to corruption. The steps below tackle each of those in turn.
THE FIX
Work through these in order.
- Check the hardware firstRAM is the biggest single factor. 16 GB struggles with serious models; 32 GB is a practical floor and 64 GB is comfortable for large federated jobs. A supported, current professional GPU handles 3D views and shaded styles far better than integrated graphics. If Task Manager shows memory maxing out while you work, more RAM will help more than anything else here.
- Update Revit and your graphics driverInstall the latest Revit update from Autodesk Access, and update your graphics driver from the card maker (NVIDIA or AMD), not just Windows Update. Outdated drivers are a common cause of crashes and visual glitches in 3D views. After updating, check that hardware acceleration is enabled under Options → Graphics — though on a machine with a flaky driver, temporarily turning it off can restore stability.
- Purge unused contentOn the Manage tab, run Purge Unused and clear out families, materials, groups and object styles that are loaded but never placed. On a neglected project this alone can shrink the file noticeably and cut how much Revit has to load and regenerate. Review warnings too (Manage → Warnings) and resolve the worst offenders.
- Open with Audit tickedIn the Open dialog, tick Audit before opening the model. Audit scans the file, detects corrupt elements and fixes what it can as the file opens. It takes longer to open, so do it periodically (say weekly on a busy project) rather than every time — but it's the first thing to try when a file starts misbehaving.
- Compact a workshared central fileIf the model is workshared, ask everyone to Synchronize with Central, relinquish all elements and close Revit. Then open the central file, run a Synchronize with Central with Compact Central Model ticked. This rebuilds the file and reclaims space that accumulates with normal use. Afterwards, have the whole team create fresh locals.
- Recreate your local fileA corrupt or stale local copy causes crashes and sync errors even when the central file is fine. Close Revit, then reopen the central file with Create New Local ticked so Revit builds you a clean local from the current central. Don't just keep reopening an old local that's been playing up.
- Tame links and CAD importsHeavy imported DWGs and unmanaged links are a classic performance killer. Import CAD rather than leaving it linked when you don't need live updates, clean up imported layers, and unload links you're not actively working against. Where possible, link CAD into a workset you can switch off. eTransmit for Revit can also repath and tidy links when you package a model.
- Run the model from a fast local driveNever work directly on a file sitting on a network share or a syncing cloud folder — that adds latency to every save and can corrupt the file. Keep your working local copy on a fast internal drive (ideally NVMe SSD), and pause OneDrive or Dropbox syncing on Revit project folders.
If it keeps crashing after all this — especially the same file across different machines — you may be looking at genuine file corruption or a central model that needs recovering from its backup folder. At that point, stop working in the file so you don't make it worse, and get help before you lose hours of modelling.
