5 Replies Latest reply on Jan 14, 2016 3:57 AM by SteveG(AudioMasters)

    Audition Crashed.  Now what?

    Charles VW Adobe Employee

      Supply General Information about the Crash

      1. What were you doing when it crashed?
      2. What have you done since you last launched the application?
      3. If it crashes with a plug-in or a file, supply information about the plug-in or file.
      4. Has anyone else experienced the crash?  Anyone else on the forums, or perhaps a friend that also owns Audition?
      5. Was there an error message?  Post a screenshot.



      Supply Information about your System

      Mac OS X
         Go to "About This Mac"Screen shot 2011-09-08 at 6.05.47 PM.jpg


      Press [ More Info... ] to launch the System Profiler

      Screen shot 2011-09-08 at 6.06.41 PM.jpg

      Go to the Start Menu > (All) Programs > Accessories > System Tools > System Information   Screen shot 2011-09-08 at 6.13.27 PM.jpg
      Save the profile to a file.   Screen shot 2011-09-08 at 6.07.06 PM.jpg

      Save the System Information to a file.

      Screen shot 2011-09-08 at 6.16.02 PM.jpg




      Supply Information about the Crash

      Mac OS X

      Copy the text from the OSX Crash Log, supply this information with any crash report.

      Screen shot 2011-09-08 at 6.22.12 PM.jpg

      When the application has crashed, before doing anything else, you'll want to create and supply a crash dump. (See next post)


      Screen shot 2011-09-08 at 6.27.24 PM.jpg

      Go ahead and still submit the crash report through the OSX crash reporter as well as the Adobe Crash Reporter Tool.  Be sure to supply comments that answer the questions mentioned above.

      Go ahead and still submit the crash report through the Windows Error Reporter.
        • 1. How to Create a Crash Dump on Windows
          Charles VW Adobe Employee

          When the application has crashed, immediately go to the task manager, select Adobe Audition, right-click and choose to Create Dump File


          Screen shot 2011-09-08 at 6.32.28 PM.jpg



          Repeatable Crashes

          If your crash is repeatable, you should download the ProcDump tool from Microsoft:


          Then open a command prompt (Start Menu > All Programs > Accessories > Command Prompt)


          Navigate to the folder that has the ProcDump.exe you extracted from the download.  I put the executable on my desktop, so in the Command Prompt window I would type:

          cd C:\Users\cvanwink\Desktop


          I can then do step 3 by typing this into the command prompt:

          procdump -e -x "C:\Program Files\Adobe\Adobe Audition CC 2015\Adobe Audition.exe" %USERPROFILE%\Desktop\AuditionCrash.dmp"


          You should see an output similar to this when the application launches:

          Screen shot 2011-09-08 at 6.41.56 PM.jpg


          You should see an output similar to this when the application crashes:

          Screen shot 2011-09-08 at 6.42.18 PM.jpg

          1 person found this helpful
          • 2. Re: How to Create a Crash Dump on Windows
            Charles VW Adobe Employee

            Finally, let us know if Audition's Crash Recovery system worked for you.

            • 3. Re: How to Create a Crash Dump on Windows
              SteveG(AudioMasters) Level 6

              Here is a link to the Feature Request/Bug Report Form


              Select Audition from the pull-down list, and the detailed form will appear.

              • 4. Re: How to Create a Crash Dump on Windows
                SteveG(AudioMasters) Level 6

                Further information from MusicConductor about another way to create Crash Dumps:


                Not all Windows users are comfortable working with command-line programs, so another option is the program Process Explorer.  This can be opened before running Audition, or even opened after the crash notification has occurred (just don’t clear it until completion of the following).  Also great is the fact that it runs in XP as well as Win 7, 32-bit or 64. 


                What is needed when a crash occurs is the detailed, full "dump file" that allows the developers to see what part of the program code caused the problem.  To create this is a very simple procedure:

                1 - Open Process Explorer.

                2 - When a crash occurs, DON’T click OK on the notification popup.

                3 - Find the Adobe Audition.exe process in Process Explorer’s process list (which is how it is listed for the current version at the time of this posting, Audition version 4, CS5.5).

                4 - right click for a popup menu, and select "Create Dump > Create Full Dump."

                5 - Name and save the file to an appropriate location.

                6 - Upload this file, along with information about your computer (OS, 32 or 64 bit, CPU, graphics adapter, sound interface, anything else requested) with a bug report at the above link.

                7 - Please note that the dump file could easily run a few hundred MB, so don’t be surprised by this.

                1 person found this helpful
                • 5. Re: Audition Crashed.  Now what?
                  SteveG(AudioMasters) Level 6

                  I should perhaps add that as far as submitting reports directly to the Audition team is concerned, they can be emailed to audbugs@adobe.com


                  Also, it's worth pointing out that every time Audition opens (or attempts to) it creates a log file. For Windows systems you can access these at

                  C:\Users\{username}\AppData\Roaming\Adobe\Audition\8.0\Logs (Mac info to follow).There will be one called Audition Loglast. There's a good chance that you will have to unhide everything in the path to see the folder though - by default it's hidden. When you've found it you can open it in Notepad.


                  Whilst it's possible to paste reports and logs directly to a thread on the forum, they tend to be rather long. Invariably it's better to post them directly to audbugs - they will be seen more quickly by the developers, and you will get a direct response. Also, it's not very likely that other users will be able to spot directly what's wrong, so it might be a rather frustrating exercise anyway. Whilst the developers will eventually see them on the forum, the delay is only going to add to your frustration!