You will need to oen a case with the response center. In addition to normal debugs, I would suggest that you get a crash dump from the Windows Media Agent. You didn't specify the OS-version, so:
Windows 2003
enable the 'drwts32' debugger, and gather the crash dumps when you see this error in the Application Event log
To configure Dr. Watson, follow these steps:
- Click Start, and then click Run.
- Type drwtsn32, and then click OK.
By default, the log file created by Dr. Watson is named Drwtsn32.log and is saved in the following location:
Since there is no Drwtsn32.exe on Vista/Server 2008/Windows 7/Server 2008 R2, we get to use the W.E.R. (Windows Event Reporting)
If the application is not UAC elevated (LUA), it will be at
C:\Users\UserProfileName\AppData\Local\Microsoft\Windows\WER\ReportArchive
Note: Where UserProfileName is the actual user profile name.
or
C:\Users\UserProfileName\AppData\Local\Microsoft\Windows\WER\ReportQueue
The easiest method to look for the user mode memory dumps is to go down to CMD (run as admin) or Powershell
Cd\ProgramData\Microsoft\Windows\WER\
dir *.*dmp /s
and
C:\Users\
dir *.*dmp /s
Note: In Windows 7/Server 2008 R2, there has been an improvement on how dumps are collected. If the same application is crashing repeated, Windows 7/Server 2008 R2 optimizes so that it does not collect the dumps for the same type of crash more than once.
I'm not sure if the current residents of the REsponse center are aware that this needs to be gathered, so you can be pro-active about it