Skip to main content

.NET crash reporting

Your .NET app crashed on a customer's PC. You get a minidump with the C# and C++ frames named.

One NuGet package for .NET Framework 4.7.2+ and .NET 10+. Unhandled exceptions on any thread, native crashes called from C#, hangs, and the fail-fasts only Windows Error Reporting sees, all reported as minidumps and symbolicated from the PDBs you upload.

Why BugSplat for .NET

One NuGet package turns managed exceptions, native crashes, hangs, and WER fail-fasts from .NET Framework 4.7.2+ and .NET 10+ apps into symbolicated minidumps.

01 · It lands

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

Install the BugSplat NuGet package and create one BugSplat instance at startup. That installs the exception handler and hang detection, so unhandled exceptions on any thread, including the WPF dispatcher, and access violations in native code your app calls all become minidumps with no handlers of your own. Register the WER helper from your installer and the crashes that end a process before any handler runs are reported too: heap corruption, __fastfail, /GS failures, .NET 10 runtime fail-fasts, and every WinUI 3 crash.

  • One NuGet package for .NET Framework 4.7.2+ and .NET 10+, on x64, x86, and ARM64
  • Windows Error Reporting helper catches the fail-fasts no exception handler ever sees
  • Handled exceptions reported from the catch block while the app keeps running, plus user feedback
A crash report in BugSplat with application, group, exception, platform, and the user's feedback - how .NET crashes arrive

02 · It groups and resolves

A report count is not a bug count.

BugSplat groups .NET 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. Every report is a minidump symbolicated from the PDBs you upload, so a crash in native code called from C# shows one stack with both the managed and the native frames named, and your app never ships a .pdb.

  • Thousands of reports collapse into a short list of distinct bugs
  • C# and C++ frames in one stack, named from your managed and native PDBs
  • 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.

Alerting for .NET crashes hits 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. A .NET crash is one.

BugSplat for .NET is built on the same native SDK as BugSplat for Windows, so minidumps, Windows Error Reporting, and symbol resolution work the way they have for C++ since 2005.

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 .NET question and you'll hear back from an engineer who builds BugSplat, usually the same day.

.NET setup

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

Add the SDK and upload PDBs 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 .