Crash Dump debug logs are very helpful in troubleshooting crashes involving SBAMSvc.exe.

However, it's important to confirm SBAMSvc.exe is in-fact experiencing an "Application Error"

1. Open the impacted system's Windows Event Logs 
2. Expand "Windows Logs" and select "Application"
3. Navigate to the date/time of the incident's most recent occurrence
4. Look for an entry with the following criteria:
   
   Level: Error
   Source: Application Error
5. Open it entry and confirm the Faulting Application references SBAMSvc.exe

1. Click Here to download/install the Debugging Tools for Windows
2. Create the following folder: C:\SBAMSvc-Crash\
3. Open an Administrative Command Prompt
4. Change Directory to the Debugging Tool's Install Folder:
   
   x86: C:\Program Files\Debugging Tools for Windows\
   x64: C:\Program Files (x86)\Debugging Tools for Windows (x86)\
5. Run the following command inside this directory:
   
   ADPlus.exe -crash -NoDumpOnFirst -quiet -pn sbamsvc.exe -o C:\SBAMSVC-Crash\
6. DO NOT CLOSE the additional Command Prompt that is opened
7. Allow/Cause SBAMSvc.exe to crash (intermittent crashes may take some time)

1. After the crash occurs, navigate to: C:\SBAMSvc-Crash\
2. Locate and Zip the "Crash_Mode_Date..." folder inside
3. Rename the folder using the Support Ticket Number: ######-Crash.zip
4. Upload the Zipped Crash Dump and a set of Agent Logs to Support:
   • Click Here for Crash Dump Upload Instructions
   • Click Here for Agent Log Submission Instructions
5. Once both of the uploads finish, please Inform Support

Important Considerations:

• The Debugger may cause performance trouble from high CPU utilization
• To alleviate; Active Protection can be disabled (unless it's the cause of the crash)
• Once started, the User must be logged in until the crash occurs
• However, the System can be locked without issue