sedebar crash

  • Thread starter Thread starter piaqt
  • Start date Start date
P

piaqt

post 04/08 updates:
Product
Windows Sidebar

Problem
Stopped working

Date
4/8/2008 2:02 PM

Status
Report Sent

Problem signature
Problem Event Name: APPCRASH
Application Name: sidebar.exe
Application Version: 6.0.6001.18000
Application Timestamp: 4791952a
Fault Module Name: StackHash_0275
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a7a6
Exception Code: c0000374
Exception Offset: 000b015d
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0275
Additional Information 2: cdff3720a18c6cc1c6eee32a403e501d
Additional Information 3: df43
Additional Information 4: 7d998c8655fe88d5285c49e255adc764

Extra information about the problem
Bucket ID: 661576341
In English?
 
What gadgets do you have installed? Did you change your installed gadgets
before this started happening... ?
 
Rebooting fixed it. Thanks for thr response. btw: how can I find out what all
that gibberish (to humans) means?
 
Generally you can open up the .DMP file that a crash produces in the Windows
Debugging Toolkit and get some data. That's generally way way more than any
normal user should ever need to do, though.
 
Thanks, but what I meant was, what's a bucket id, a stack, an offset, etc? In
other words, where can I get a glossary of the terminology?
 
You would want to start with the SDK or MSDN, most likely. There's tons of
information here available: I wouldn't even know where to begin - this could
be a five minute conversation or several quarters of classes. Search away or
check the Windows Debugging Toolkit site - there's tons of great information
already out there. =)
 
I imagine that the Toolkit should have a help file. I haven't kept track of
where one might find introductory lessons in this venue so wouldn't
personally know of where to get you started here. I would suggest that
MSDN.microsoft.com would generally be a great starting point for anyone
interested. I imagine most questions within this field would quickly lead
to more questions, which is why a tool such as MSDN (or a search engine)
that lets you follow those further references is probably most ideal for
your references.

The short short short version is that those data points define the crash in
question. =)
 
Back
Top