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"
- Open the impacted system's Windows Event Logs
- Expand "Windows Logs" and select "Application"
- Navigate to the date/time of the incident's most recent occurrence
- Look for an entry with the following criteria:
Level: Error
Source: Application Error - Open it entry and confirm the Faulting Application references SBAMSvc.exe
Generating the Crash Dump file for SBAMSvc.exe:
- Click Here to download/install the Debugging Tools for Windows
- Create the following folder: C:\SBAMSvc-Crash\
- Open an Administrative Command Prompt
-
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)\ - Run the following command inside this directory:
ADPlus.exe -crash -NoDumpOnFirst -quiet -pn sbamsvc.exe -o C:\SBAMSVC-Crash\ - DO NOT CLOSE the additional Command Prompt that is opened
- Allow/Cause SBAMSvc.exe to crash (intermittent crashes may take some time)
Submitting the Crash Dump and Agent Logs to Support:
- After the crash occurs, navigate to: C:\SBAMSvc-Crash\
- Locate and Zip the "Crash_Mode_Date..." folder inside
- Rename the folder using the Support Ticket Number: ######-Crash.zip
- 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
- 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
For any questions or concerns, please Contact Support