How do I generate a Kernel Mode dump file for ProxyClient?



If a Blue Screen Of Death (BSOD) or kernel panic occurs on a workstation where ProxyClient is installed, you must generate a full kernel dump to diagnose the problem.

In the event of a system crash, the Microsoft Windows crash dump settings determine whether a dump file will be created, and if it is created, what size the dump file will be. This document describes how to configure the crash dump settings.

Note: If the ProxyClient service or application hangs or crashes, you must generate User Mode (Dr. Watson) dump files. For information on generating User Mode dump files, see KB4887


This procedure applies to Windows XP, Vista, 2003, and 2008. Core dump generation is not supported on Mac OS.

To configure crash dump settings: 

  1. Verify that you are logged into Windows with Administrator rights.
  2. Go to Control Panel and click the System icon.
  3. Select the Advanced panel. 
  4. (Windows XP and later) Click the Settings button in the Startup and Recovery section.
  5. Under Write Debugging Information, select the size of dump files you want to have as the default:
    • Complete memory dump - Largest size, containing the most information
    • Kernel memory dump - Contains the kernel memory, smaller than the complete dump
    • Small memory dump - The default size and the smallest, containing only 64 KB 
      The advantage to the larger files is that, since they contain more information, they are more likely to help you find the cause of the crash. The advantage of the smaller files is that they are written more quickly. Speed is often valuable; if you are running a server, you may want the server to reboot as quickly as possible after a crash, and the reboot will not take place until the dump file has been written.
      Important:  Blue Coat requires a kernel memory dump  at a minimum, and might require a complete memory dump in some cases.
  6. Accept or change the default dump file path and file name.
  7. Select or deselect any of the options: Write an event to the system log, Send an administrative alert, and Automatically reboot.
  8. Click OK. If you made any changes, the system might prompt you to reboot.


Additional Information
Bug Number
InQuira Doc IdKB4882

Article Feedback

Did this Article solve your issue?
Additional Comments:
Previous MonthNext Month