DbgPrintViewer

Kernel DbgPrint and user-mode OutputDebugString, in one place.

Free download. No paid license key required.

DbgPrintViewer captures and displays debug output from Windows applications and the kernel in real time. It collects from two sources at once: OutputDebugString calls from user-mode processes, and DbgPrint statements from kernel-mode drivers and components. Both streams land in a single, searchable event list, so you can correlate what a driver and the application talking to it are printing without juggling two tools.

If you have used Sysinternals DebugView, the workflow will feel familiar. DbgPrintViewer covers the same core job and adds compound filters, regex search, stack dumps, and ETL trace files. See the DebugView comparison for the details.

Two Sources, One List

Each capture source can be toggled independently at any time:

• OutputDebugString captures debug strings from user-mode applications. This source can run without elevation.
• Kernel DbgPrint captures kernel debug print output from drivers and kernel components. This requires running elevated.
• Verbose Kernel raises the kernel output to high verbosity for deep diagnostics. It produces a large volume of messages and is meant for focused debugging sessions.

Every row carries the process or component name, PID, TID, a Source column showing whether it came from OutputDebugString or DbgPrint, and the message text. A configurable delta column shows the time since the previous event, which is handy for spotting stalls.

Filter, Highlight, and Search

Debug output is noisy, so DbgPrintViewer is built to cut it down quickly:

• Quick filter narrows the list by any field as you type.
• Compound filters combine field, operator, and value conditions with AND/OR logic.
• Find supports plain text, regex, case-sensitive, and whole-word search.
• Highlight rules color-code rows that match conditions you define.

Column layout, theme, delta unit, and your filter and highlight rules all persist between sessions.

Save and Reopen Traces

Save the current event buffer to send a focused log to another engineer, or open a saved ETL trace file to analyze debug output collected elsewhere. The same filtering and search apply to saved traces, so a captured session is just as easy to work through as a live one.

Requirements

• Windows 10 or later.
• Administrator privileges for kernel DbgPrint capture. OutputDebugString capture can run without elevation.

Get DbgPrintViewer

DbgPrintViewer is free. Download it, enable the sources you want, and watch debug output stream in.

Doing kernel work? See our Windows driver development services, the WppViewer Studio WPP and ETW trace viewer, and RpcViewer for live RPC activity.

DbgPrintViewer

• What our customers say about us?

  

  Read our customer testimonials to find out why our clients keep returning for their projects.

  View Testimonials