How to collect in-memory CDF trace along with a system crash dump upon a Citrix VDI BSOD incident

book

Article ID: CTX695119

calendar_today

Updated On:

Description

Prerequisites
1. Download the latest CDFControl tool from CTX111961.
2. Run CDFControl in the affected Citrix VDI with administrative privilege.
3. In [Tools] - [Options], apply the following settings,

  • Trace file settings: tick "Circular Log"
  • Max Log Size: 1024 MB
  • Trace details settings:
    • Enter Flags: FFFFFFFF
    • Enter Level: 16
  • Event Buffer Management:
    • Untick "User Default Settings"
    • Buffer Size (KB): 1024
    • Minimum Buffers: 127
    • Maximum Buffers: 127
  • Trace file path (for capturing trace): set a desired file path

Main Steps
1. Under "Trace Categories" drop-down list, select the target modules. If the target modules is unknown yet, please select [All Modules].
2. Click "Start Tracing" button to start the tracing.
3. Reproduce the Windows OS BSOD incident.
4. Once the BSOD incident occurs and the machine is rebooted, please gather the system crash dump generated by Windows OS.

  • Note: The CDF trace remaining in system memory prior to the BSOD will be included in the system crash dump.

5. Share the system crash dump with Citrix Support though Citrix Insight Services (CIS). Citrix Support will be able to extract the CDF trace from the dump.

 

Issue/Introduction

In troubleshooting a Window OS BSOD incident occurring in a Citrix VDI, a system crash dump is the primary data to be referenced by Citrix Support. However, in some cases, especially BSOD incidents directly pointing to a Citrix driver, the "last minute" CDF trace remaining in system memory prior to the BSOD may be equivalently critical to the root cause analysis. You might be asked by Citrix Support to collect in-memory CDF trace along with a system crash dump once a BSOD incident is reproduced. The article describes the main steps of the log collection.