Overview
The Virtual Display Driver includes logging capabilities to help diagnose issues. This guide covers how to enable logging, interpret log files, and collect diagnostic information for troubleshooting.Logging is disabled by default to minimize performance impact and prevent large log files. Only enable logging when actively troubleshooting issues.
Logging Configuration
Logging is controlled through thevdd_settings.xml configuration file.
Configuration File Location
The default location for the settings file is:Logging Settings
The driver supports two levels of logging:- Standard Logging
- Debug Logging
- Logging Disabled
Standard logging captures important events and errors without excessive detail.Configuration:When to use:
- Investigating general issues
- Monitoring driver behavior
- Troubleshooting installation problems
Applying Configuration Changes
After editingvdd_settings.xml, you must restart the driver:
Restart the driver
Option 1: Using Device Manager
- Open Device Manager (
Win + R, then typedevmgmt.msc) - Expand Display adapters
- Right-click Virtual Display Driver
- Click Disable device
- Right-click again and click Enable device
Log File Locations
Windows Event Tracing (ETW)
The driver uses Windows Event Tracing for Performance (WPP) for logging. Logs can be viewed using:-
Event Viewer:
- Press
Win + R, typeeventvwr.msc, press Enter - Navigate to Windows Logs > System
- Look for entries from “Virtual Display Driver” or “IddSampleDriver”
- Press
-
Tracelog utility (part of Windows SDK):
Driver Log Files
WhenSendLogsThroughPipe is enabled, the driver may create log files in:
The exact log file location may vary depending on driver version and configuration.
Reading and Interpreting Logs
Common Log Messages
Initialization Messages
Initialization Messages
Look for messages indicating driver startup:
Driver loaded successfullyReading configuration from vdd_settings.xmlMonitor count: XGPU selected: [GPU Name]
- Verify the correct GPU is selected
- Confirm the expected number of monitors
- Check that configuration file was read successfully
Resolution and Mode Changes
Resolution and Mode Changes
Messages related to display mode changes:
Resolution added: [width]x[height]@[refresh]HzMode set: [width]x[height]@[refresh]HzPreferred mode: [resolution]
- Verify that your configured resolutions are being loaded
- Check that refresh rates match your configuration
- Look for errors in mode setting
Error Messages
Error Messages
Common error patterns to look for:
Failed to initializeConfiguration errorGPU not foundEDID parse errorMemory allocation failed
- Note the exact error message
- Check the context (what was happening when the error occurred)
- Verify your configuration file syntax
- See Common Issues for solutions
Performance Messages
Performance Messages
When debug logging is enabled, you may see performance-related messages:
Frame rendered: [time]msBuffer allocated: [size]MBCursor update: [time]us
- High frame render times may indicate performance issues
- Large buffer allocations may explain memory usage
- Frequent cursor updates may impact performance
Log Analysis Tips
- Timestamps: Pay attention to when errors occur relative to other events
- Patterns: Look for repeating errors that might indicate a persistent issue
- Context: Read messages before and after errors for additional context
- Severity levels: Focus on ERROR and WARNING messages first
Using PowerShell for Diagnostics
The Community Scripts folder includes PowerShell scripts that can help with diagnostics.Getting Display Information
Checking Driver Status
Querying Display Configuration
View full diagnostic script example
View full diagnostic script example
Collecting Diagnostic Information for Bug Reports
When reporting issues, include the following information:Enable logging and reproduce the issue
- Enable debug logging in
vdd_settings.xml - Restart the driver
- Reproduce the issue
- Collect the log files
Export Event Viewer logs
- Open Event Viewer
- Navigate to Windows Logs > System
- Right-click System and select Save All Events As…
- Save as
vdd-system-logs.evtx
Advanced Diagnostic Tools
IddCx Version Query
The driver includes a utility to query the IddCx framework version:- Installed IddCx version
- Framework capabilities
- Supported features
WPP Tracing
For advanced users, Windows Performance Toolkit can capture detailed traces:Using Windows Performance Recorder
Using Windows Performance Recorder
- Install Windows Performance Toolkit (part of Windows SDK)
- Create a custom recording profile for display drivers
- Start recording:
- Reproduce the issue
- Stop recording:
- Analyze with Windows Performance Analyzer (WPA)
This is an advanced technique primarily useful for driver developers and detailed performance analysis.
Disabling Logging After Troubleshooting
Once you’ve finished troubleshooting, remember to disable logging:- Edit
C:\VirtualDisplayDriver\vdd_settings.xml - Set logging to false:
- Restart the driver (disable/enable in Device Manager)
- Delete old log files to free up disk space
Common Diagnostic Scenarios
Driver not loading at startup
Driver not loading at startup
Diagnostic steps:
- Enable standard logging
- Restart computer
- Check Event Viewer for driver initialization messages
- Look for errors in System log during boot
- Configuration file syntax error
- Missing dependencies (vcruntime140.dll)
- GPU driver conflicts
- Corrupted driver files
Virtual display disconnecting randomly
Virtual display disconnecting randomly
Diagnostic steps:
- Enable debug logging
- Monitor logs when disconnection occurs
- Check for power management settings
- Review GPU driver logs
Monitor disconnectedmessages- GPU driver errors
- Power state changes
- Memory allocation failures
Performance issues or lag
Performance issues or lag
Diagnostic steps:
- Enable debug logging
- Monitor frame render times in logs
- Check GPU usage in Task Manager
- Review cursor rendering performance
- High refresh rates with insufficient GPU power
- Debug logging enabled during normal use
- Multiple high-resolution virtual displays
- Software cursor fallback instead of hardware cursor
Next Steps
After collecting diagnostic information:Common Issues
Check if your issue matches a known problem with a documented solution
GitHub Issues
Search existing issues or report a new bug with your diagnostic data
Configuration Reference
Review detailed configuration options that may help resolve your issue
Safe Mode Recovery
If your issue prevents normal Windows access, use Safe Mode recovery