This page provides assistance for creating minidump files.

Steps to Report a Problem

If you encounter an issue that is not included in the Troubleshooting page, create a minidump file that will be useful for the Chaos Group Support team when tackling the issue.

In the sections below, you will find information on how to create a minidump file.


Collecting the Minidump File when Autodesk Error Report Window is Available

What is the minidump file?

A minidump file contains information that allows Chaos Group support team to understand an issue (such as what exactly happened during the crash or freeze), and helps Chaos Group developers provide a fix, or at least an explanation, as soon as possible.

How to get the minidump file?

When Maya crashes, it usually displays the Maya Error Report window. To find the location of your minidump file:


1. Do not close the error report window during this whole process.

2. Click on the View Report Details option.

3. Hover your mouse over each file to see its location.

4. Go to that location and find the .dump file. You need the file, which contains all the necessary dump files.



If you are rendering your Maya scene with V-Ray Standalone and the app crashes, the VRay.dmp dump file contains information about the crash process of V-Ray Standalone. It is located by default in the %temp% folder.

If rendering with V-Ray plugin in Maya, the crash dump file contains information about both the V-Ray plugin processes and the host application processes.


Collecting the Minidump File if Autodesk Error Report Windows is not Available

If your V-Ray application crashes, a crash dump file, is automatically created.

In case the crash dump file is missing from the its designated folder, you can create it manually. Depending on the OS you are using, you can do so:




  1. Open the standard Windows Task Manager from the Start Menu.
  2. Right-click on the Maya application in the Processes tab to select the Create dump file option, while the Maya app displays the notification that unexpected error has occurred.



3. The crash dump file is created in the temporary folder.





The crash dump files are stored either in the /Library/Logs/DiagnosticReports (system-wide) or ~/Library/Logs/DiagnosticsReports (user-wide) directories, depending on the type of the process that has led to the crash.

Another crash dump file named core.<pid> (where <pid> stands for the PID of the crashed process) must be created in the /cores directory. In order to create this second crash dump file, activate the full core dumps via the ulimit -c unlimited command which makes the core dump files size unlimited. Also make sure to have write permissions for the /cores directory.

In case the /cores directory is hidden in Finder, you can show the hidden files via the defaults write AppleShowAllFiles TRUE command.




You should make the size of the core dump files unlimited via the ulimit -c unlimited command. If the core dump files are not disabled in any other way, this should be sufficient to create a core.<pid> dump file in the current working directory or in the /var/lib/systemd/coredump directory, if using systemd. Here, <pid> stands for the PID of the crashed process.

In case no core dump file has been created, the following configuration files must be checked based on the Linux distribution used:

  • (non-systemd GNU Linux distributions - CentOS 6.x and others): Make sure that there is either no /etc/sysctl.d/50-coredump.conf file or it has a valid configuration value for the kernel.core_pattern. If you are uncertain, just remove the line from the file. This action may require root access.

  • (systemd based GNU Linux distributions - CentOS 7, Fedora and others): Make sure that there is no limit for the storage in /etc/systemd/coredump.conf.d/custom.conf by confirming that the [Coredump] Storage=none configuration lines are not present.