Description:

This document will help you use Microsoft DebugDiag, which is a tool that is used gather information for hangs, slow
performance, fragmentation, and memory leaks. This tool can be used to gather scripts on Internet Information Services
(IIS), COM+, specific processes and related Microsoft technologies.

ESTIMATED TIME OF COMPLETION: TBD

Steps:

1. Set a user environment variable named MS_TRAP

Control Panel->System->Advanced->Environment Variables->User variables->New...

2. Search on the internet, Download and install (with default options) latest 32-bit or 64-bit DebugDiag (depending of
your Operating System)

3. Start DebugDiag: Start->All Programs->Debug Diagnostics Tool ->DebugDiag

4. Select Rule Type->Crash->Next

Copyright © Bentley Technical Support Group

09/16/2009
5. Select Target Type->A specific process->Next

6. Select Target"->Selected Process->ustation.exe->Next

[note that ustation.exe will not appear in the task list if it is not already running, as for startup crashes, but the
“ustation.exe” can and should be typed into the “Selected Process” field.]

Copyright © Bentley Technical Support Group

09/16/2009
7. Advanced Configuration (Optional)->Action type for unconfigured first chance exceptions->Log Stack Trace->Action
limit->200

8. Advanced Configuration (Optional)->Advanced Settings->Breakpoints...

Copyright © Bentley Technical Support Group

09/16/2009
8. Configure Breakpoints->Add Breakpoint...

9. Configure Breakpoint->Breakpoint->Ntdll!ZwTerminateProcess->Action->Action Type->Full Userdump->Action Limit-

>5->OK (Note: If you have much available disk space, you can set the Action Limit to 10)

10. Configure Breakpoints->Save & Close

11. Advanced Configuration (Optional)->Advanced Settings->PageHeap Flags...

12. Configure PageHeap Flags->Enable Full PageHeap->OK

Copyright © Bentley Technical Support Group

09/16/2009
13. Debug Diagnostic Tool->Yes

14. In the Advanced Configuration (Optional)->Next

15. Select Dump Location And Rule Name (Optional – and note location where dump files will be written, and optionally
change it) ->Next

Copyright © Bentley Technical Support Group

09/16/2009
18. Rule Completed->Activate the rule now->Finish

19. Debug Diagnostic Tools->Yes

20. Debug Diagnostic Tool - Connected to DbgSvc

21. (should observe that the "Crash Rule" status is "Active")

22. File->Exit

Debug Diagnostic Tool will now report MicroStation issue(s), and up to 25 or so memory dumps will be collected.

Navigate in Windows Explorer to location defaulted or specified in steps 15/16 above after issue has been reproduced,
and right-click send to compressed folder the "Crash rule for all instances of ustation.exe" folder and upload to Bentley
via ftp or sharedfiles.

Also add all .log files from "C:\Program Files\DebugDiag\Logs" to the above .zip archive before uploading; in fact, it may
be easier (if the location for dump files has not been customized) to just recursively send the whole "C:\Program
Files\DebugDiag\Logs" folder tree to a compressed folder.

Copyright © Bentley Technical Support Group

09/16/2009
Note! When all finished collecting dumps (may be minutes or days later), be sure to remove the Crash Rule using these
steps:

1. Start DebugDiag: Start->All Programs->Debug Diagnostics Tool 1.2->DebugDiag 1.2

2. Select "Crash rule for all instances of ustation.exe"

3. "Remove Rule"

4. File->Exit

5. Unset the user environment variable named MS_TRAP

It is important to remove the rule, or otherwise Debug Diag will keep on logging MicroStation and log files can fill up
your memory space.

Upload:

Post all files generated for analysis.

Collect and zip the output files produced from the steps above and place these files on the FTP server:
ftp://ftp.bentley.com/pub/incoming

If prompted to log in: Check ‘log on anonymously’ PASSWORD: Your email address (john.doe@company.com)

Copyright © Bentley Technical Support Group

09/16/2009