Welcome to StackHash
StackHash /stæk hæʃ/ (noun):
- A Windows error occurring in no identifiable module (learn more).
- A tool and community for making the most of Windows Error Reporting and WinQual.
We're building a new way to learn about why your application or web site fails, discover the root cause and get the fix to your customers quickly. StackHash builds on Microsoft's WinQual service to provide:
- A local store of crash events and related minidumps. There's no need to waste time wrestling with the WinQual portal. Double-click a crash to start debugging.
- Bug tracking / defect management integration. Track crashes using your current tool, assign crashes to the right developer and ensure that real-world problems aren't trapped in a silo.
- Automatic crash debugging. Let StackHash do the heavy lifting and send you a crash analysis including the call stack.
- Reporting, trend analysis and filtering tools. Understand product quality over time, geographical distribution of crashes and problem third party modules.
- Much more...
We need your help!
StackHash is launching later in 2010. If you use WinQual, Windows Error Reporting and WinDbg we'd like to invite you to participate in our beta program. If you've considered using WinQual in the past but been put off by the complexity then we'd also like to hear from you.
Sign up for the StackHash beta.
You'll receive access to beta releases and our private feedback forum.
What is WinQual?
Windows Quality Online Services or WinQual for short provides developers with access to crash reports submitted via Windows Error Reporting (WER).
When an application or web site running on Windows fails the user has the opportunity to send a report to Microsoft. By signing up for WinQual the developer can access these reports and diagnose the cause of the problem. The developer can also close the loop and publish a response so that the next time the crash occurs the user is automatically directed to the solution. Windows Vista and 7 also keep a list of errors (Problem Reports and Solutions) so the user can be notified as soon as a fix is available.
Why develop StackHash?
WinQual is a fantastic resource for anyone shipping software for Windows, but it can be difficult and inefficient to use. The web portal is slow and hard to navigate. A considerable amount of expertise is required to make the most effective use of the information contained in the crash reports.
Many developers choose to roll out their own error reporting instead. This is useful, but insufficient for two critical reasons:
- Windows Error Reporting is part of the OS and picks up crashes that your own handler can't - for instance hard to track down configuration and deployment bugs.
- Windows Error Reporting can provide the fix to the user at the time that the crash occurs. This is especially important the first time a customer tries your product. Instead of giving up and uninstalling, the user is immediately told that the problem has been fixed and provides a URL to get back on track.
We have realized incredible value from WinQual while shipping both consumer and business applications. Integrating StackHash and WinQual with your development lifecycle will help you drive product quality up and support cost down.
Need more information?
If you're intrigued but not ready to sign up for the beta please contact us, or leave a comment on StackHash beta for better WinQual.
