This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

Debugging a Crash in Measurement & Automation Explorer (MAX) with Windows

Updated Jan 9, 2019

Reported In


  • Measurement and Automation Explorer (MAX)

Issue Details

Measurement & Automation Explorer (MAX) keeps crashing on me, and I want to figure out what is wrong.  How can get an in-depth crash report from Windows?


The NI Error Reporting feature was added to NI MAX with the release of NI System Configuration 5.5. NI Error Reporting should create a .dmp file if MAX crashes. The .dmp file will be saved in C:\User\username\Documents\LabVIEW Data\LVInternalReports\NIMAX\ and a pop-up dialog should also provide you the option to send the .dmp file to National Instruments for evaluation.

Alternately, if you are using a version of MAX prior to 5.5, you can create a .dmp file using WinDbg. WinDbg is a tool provided by Microsoft for debugging Windows applications. It can be downloaded from Windows Hardware Developer Central website, as part of the Debugging Tools for Windows SDK.

Follow the steps below to use the WinDbg tool:
  1. Install the debugging tool on the computer where you are experiencing the crash.
  2. Once it has finished installing, go to the Start>>All Programs>>Debugging Tools for Windows (x86)>>WinDbg to run it. On 64-bit Windows, this will be under Windows (x64).
  3. Once you are ready to duplicate the crash, you should attach WinDbg to Measurement & Automation Explorer by selecting File>>Open Executable....
  4. In the window that appears, browse to <National Instruments>\MAX\NIMAX.exe then click Open. This will open a new command window. Don't be alarmed if this window shows statements that begin with *** ERROR, this is normal.
  5. In the WinDbg window (not the command window), select Debug>>Go. This will launch NI MAX. 
  6. Now that MAX is running with WinDbg monitoring it, replicate the crash. If, during replication, you encounter a status such as *BUSY*, Debuggee is running... and this status does not change for an extended period of time, click Debug>>Break.
  7. In the WinDbg command window, type .dump <filename>.dmp. Your dump file will be saved in <Program Files>\Debugging Tools for Windows (x86). On 64-bit computers, the default dump file location is C:\WinDDK\debugger version\Debuggers\.


Not Helpful