Skip to main content

Windows C++ crash reporting

Your Windows app crashed on a customer's machine. Here is the line that did it.

BugSplat captures the minidump, resolves it against your PDBs, and shows you the faulting function and line. Integration is a few lines of code.

Why BugSplat for Windows

A few lines of code turn every unhandled exception in your Windows app into a minidump, resolved against your PDBs to the function and line that faulted.

01 · It lands

Something breaks in your Windows build. You find out first.

Add the BugSplat SDK with a few lines of code and every unhandled exception produces a minidump, with thread state, loaded modules, and OS and hardware details. It works with MFC, Qt, Win32, or your own framework.

  • Minidumps captured on every unhandled exception, automatically
  • Symbols resolved against the exact PDBs from the build that shipped
  • Works with MFC, Qt, Win32, and custom native frameworks
A crash report in BugSplat with application, group, exception, platform, and the user's feedback - how Windows crashes arrive

02 · It groups and resolves

A report count is not a bug count.

BugSplat groups Windows crashes your way: your rules decide which call stacks count as the same bug, and the list is ranked by how many people each one hit. Stacks resolve against your PDBs, so you get function names and line numbers in your own code, with the arguments and locals on each frame.

  • Thousands of reports collapse into a short list of distinct bugs
  • Function names and line numbers, not memory addresses
  • OS, hardware, and build on every report
A symbolicated active thread in BugSplat with the faulting frame expanded to its file, line, arguments, and locals

03 · It tells you

Stay ahead of the next one.

Alerts for Windows crashes reach Slack, Discord, or Teams the moment something spikes. Version-over-version analytics show whether each release is more stable than the last.

  • Regressions flagged when a fixed crash comes back
  • Daily and weekly digests with the highlights
A BugSplat new group alert in Discord with the crash group and stack trace

What makes BugSplat different

Crash reporting built for native code.

The part of Windows C++ crash reporting that's hard is the part we've always done.

Native from the start

BugSplat has been turning minidumps into readable stacks since 2005. Symbols, PDBs, and native crashes are the core of the product.

A bill that holds still

Flat monthly plans with fixed limits. A spike in crash volume after a release doesn't change your bill.

Answered by the people who build it

Email support with a Windows question and you'll hear back from an engineer who builds BugSplat, usually the same day.

Windows C++ setup

Wire up Windows and read a real stack the same day.

Add the SDK and upload symbols with each build. If you get stuck, contact support and you'll reach the engineers who build BugSplat.

By clicking "Accept", you agree to the storing of cookies on your device. View our Privacy Policy .