Maya has stopped working. An error has stopped Maya from working properly.” when launching Maya 2023

What the "Maya Has Stopped Working" Error Means

When you launch Maya 2023 or later and see the error dialog "Maya has stopped working. An error has stopped Maya from working properly," the application either crashes immediately or becomes unresponsive before the main UI fully loads. This is frustrating because the error message itself provides almost no diagnostic detail — you're left guessing what went wrong.

The good news: this error has a finite set of causes, and we can narrow them down systematically. Over the years, we've worked with clients on distributed rendering farms encountering Maya launch failures, and the troubleshooting approach here applies whether you're rendering locally or submitting jobs to a render farm like our Maya cloud rendering service.

Step 1: Gather Diagnostic Information

Before attempting fixes, collect information about what's actually happening.

Check Windows Event Viewer for crash logs:

1. Press Windows + R, type eventvwr.msc, and press Enter
2. Navigate to Windows Logs → Application
3. Look for recent entries with "Maya" in the source or event description, typically showing error code or faulting module (like maya.exe)
4. Right-click the event, select Properties, and note:
   • Event ID (e.g., 1000 for application crash)
   • Faulting module (DLL or exe that crashed)
   • Exception code (hex code like c0000374)
5. Screenshot or copy the full event details — this tells us whether it's a graphics driver, plugin, or core Maya crash

Launch Maya in safe mode:

1. Open Command Prompt as Administrator
2. Run: "C:\Program Files\Autodesk\Maya2025\bin\maya.exe" -noPlugin -noDefaultMel
   • Adjust the path for your Maya version (2023, 2024, or 2025)
   • -noPlugin disables user-loaded plugins
   • -noDefaultMel skips MEL initialization
3. If Maya launches successfully, the crash is likely plugin-related or MEL script-related, not core Maya
4. If Maya still crashes, the issue is deeper — probably preferences, graphics driver, or installation corruption

Check Maya.env for problematic settings:

1. Locate your Maya.env file:
   • Windows: C:\Users\[YOUR_USER]\Documents\maya\[VERSION]\Maya.env
   • Replace [VERSION] with your Maya version (e.g., 2025)
2. Open it in a text editor
3. Look for:
   • Custom MAYA_RENDER_DESC_PATH or plugin paths pointing to offline/removed locations
   • Large or invalid MAYA_SCRIPT_PATH entries (missing folders cause slow initialization)
   • Graphics-related settings like MAYA_USE_GPU, MAYA_OPENCL_* if you've manually tweaked them

Document your system:

• GPU model (NVIDIA, AMD, Intel) and driver version
• Maya version (check Help → About Maya if it launches)
• Recent Windows or driver updates installed in the past week
• Any recently added plugins or custom scripts

Step 2: Identify the Root Cause

Once you have diagnostic data, match your situation to one of these causes.

Cause A: Corrupted Preferences and Cache

Why it happens: Maya stores UI layout, plugin settings, and rendering state in a preferences folder. If corrupted (by a crash, plugin failure, or disk error), Maya can hang or crash on initialization.

How to diagnose:

• Safe mode launch succeeded? Likely preferences-related
• Event Viewer shows repeated errors with the same module? Could be a stuck preference entry
• New Maya installation, but imported preferences from an older version? Incompatible preference format

How to fix:

1. Close Maya completely
2. Navigate to: C:\Users\[YOUR_USER]\AppData\Local\Autodesk\Maya\[VERSION]
3. Rename the folder to [VERSION]-backup (don't delete yet)
4. Launch Maya — it will recreate default preferences
5. Test rendering or import a simple scene
6. If it works, your old preferences are the problem; keep the new folder and you can delete the backup later
7. If it still crashes, restore the backup and try the next cause

Cause B: Corrupted Projects Folder or Asset Paths

Why it happens: Maya caches asset and project paths on launch. If a referenced file path is inaccessible (network share offline, external drive disconnected, path contains special characters), Maya can hang trying to resolve it.

How to diagnose:

• Safe mode succeeded? Preferences are OK
• Event Viewer shows delay or hang, not a crash? Could be asset path resolution
• Do you have linked references, external textures, or project-relative paths in your scene?

How to fix:

1. Rename your Projects folder: C:\Users\[YOUR_USER]\Documents\maya\[VERSION]\projects → projects-backup
2. Launch Maya
3. If Maya starts, the problem was your project folder or a scene in the default project
4. Move scenes one at a time from projects-backup\[PROJECT]\scenes back into projects\[PROJECT]\scenes and test each to isolate the culprit

Cause C: Graphics Driver Incompatibility

Why it happens: Maya's viewport renderer (OpenGL, NVIDIA RTX, or AMD HIP) depends on up-to-date, compatible GPU drivers. A stale, corrupt, or incompatible driver version crashes Maya during viewport initialization.

How to diagnose:

• Safe mode succeeded? Graphics drivers may still be involved because -noPlugin doesn't disable the viewport
• Event Viewer shows a faulting module like nvoglv32.dll, atioglxx.dll, or d3d12.dll? That's your graphics stack
• Recent Windows update installed? Sometimes Windows rolls back GPU drivers to generic versions

How to fix:

1. Download the latest GPU driver:
   • NVIDIA: https://www.nvidia.com/download/index.aspx
   • AMD: https://www.amd.com/en/technologies/radeon-drivers
   • Intel Iris: https://www.intel.com/content/www/us/en/support/products/80939/graphics.html
2. Uninstall the current driver via Control Panel → Programs and Features or the GPU vendor's uninstall tool
3. Restart
4. Install the downloaded driver
5. Restart again and launch Maya

Note: If you use distributed rendering, keep your local GPU drivers in sync with the render farm's driver versions to avoid viewport surprises during testing and submission.

Cause D: Corrupted Maya Installation

Why it happens: Installation files become corrupted during incomplete updates, forced shutdowns during patching, or filesystem errors.

How to diagnose:

• All previous steps completed with no improvement?
• Event Viewer shows random access violations or missing DLL errors?
• Run safe mode with an empty project; it still crashes?

How to fix:

1. Uninstall Maya via Control Panel → Programs and Features → Autodesk Maya [VERSION] → Uninstall
2. Delete any remaining files: C:\Program Files\Autodesk\Maya[VERSION] (may not exist, but check)
3. Restart
4. Download a fresh installer from Autodesk's download page
5. Install Maya with default options (don't try to restore your old preferences immediately)
6. Launch Maya once and confirm it works
7. Then restore your preferences incrementally if needed (copy plugins one at a time to test compatibility)

Maya Launch Troubleshooting Checklist

Here's a quick reference to run through systematically:

1. Event Viewer — Check for crash details and faulting modules
2. Safe mode — Does Maya launch with -noPlugin -noDefaultMel?
3. Preferences — Rename preferences folder and retry
4. Projects — Rename projects folder and retry
5. GPU driver — Update to latest version and restart
6. Clean reinstall — Uninstall, restart, download fresh, install

Work through each step in order. If one succeeds, you've found your cause.

FAQ

Q: Is this error Windows-only, or does it affect Maya on macOS and Linux?

A: We focus on Windows for distributed rendering (Windows Server is our primary platform), so this guide targets Windows diagnostics. macOS and Linux have equivalent issues (preference corruption, driver problems) but different paths and commands. Check the official Autodesk Maya documentation for platform-specific troubleshooting.

Q: If I uninstall Maya, will I lose my custom scripts and plugins?

A: Custom scripts are stored in C:\Users\[YOUR_USER]\Documents\maya\[VERSION]\scripts — this folder is separate from the Maya installation folder and won't be deleted by the uninstall. Plugins in that same location are also preserved. If you've installed plugins via an installer, they may install to Program Files, so check your plugin vendor's documentation.

Q: Can I fix this without a clean reinstall?

A: In most cases, yes. Start with preferences and projects (Causes A and B) — these are quick and preserve your setup. Only resort to a clean reinstall if graphics drivers don't help (Cause C) and you've confirmed safe mode still crashes.

Q: What if Event Viewer shows an error from a specific DLL, like a plugin I use for rendering?

A: That DLL is likely incompatible with your Maya version, corrupted, or conflicting with another plugin. Try disabling it: move the plugin file from C:\Users\[YOUR_USER]\Documents\maya\[VERSION]\plug-ins to a backup folder, then launch Maya. If it works, contact the plugin vendor for an updated version compatible with your Maya version.

Q: We submit Maya jobs to a render farm. Could a farm's driver version mismatch cause local crashes?

A: Not directly — your local Maya installation is independent. However, if you test a scene locally and it renders fine, but fails on the farm, mismatched drivers (or missing assets) are common culprits. Ensure your local GPU drivers match the farm's render node drivers, and always use project-relative or network-accessible asset paths when submitting jobs.

Q: How do I prevent this error from happening again?

A: Keep Windows and your GPU drivers updated; avoid disabling plugins or MEL scripts manually unless you know what they do; and if Maya crashes, use Event Viewer to note what failed so you can report it to your plugin vendor. Regular backups of your Documents\maya folder also save time if you need to recover custom scripts.

Last Updated: 2026-03-17