Sending error reports in Windows Vista :: Watson on Vista

Awhile ago I blogged about Submitting Watson Crash information and now I wanted to update this for Windows Vista. Here is how a crash goes in Vista and where you can get the Watson Crash information so that we can diagnose your problem and you can submit a bug on OneNote's Connect site.

 

The crash!

This is what it looks like when you get a crash, to send information to Microsoft please click on "check online for a solution". I think my Vista build thought it was offline even though it was since I was connected via remote desktop!

 
 

Then you will see this dialog as Windows prepared the report to send:

 

 

Then please click "Send information" to send the report:

 

Now this information will be sent to Microsoft (and the OneNote team). Eventually you can actually get a solution back from Microsoft telling you how to fix the problem so you don't see it again. Since you are beta testing software there aren't any solutions yet : )

 
 

 

You will need to get the Watson bucket number from Windows. In my earlier post I talked about Event Viewer (eventvwr) and you can still do this in Vista but you will get a UAC prompt and instead you can use this new tool in Vista called Problem Reports and Solutions. To find it just click Start and then type "problem reports":

Note: this is also in the Control Panel

 
 

Then on the left you will want to select "View problem history":

 
 

You will end up in a window like this:

 
 

And you would open the option for any OneNote crashes:

 
 

Your bucket number is on the bottom there and this is what you would want to send us to submit a OneNote bug on the OneNote Connect site.

 
 

Of course you can still do this with Event Viewer:

 
 

Note that they no longer say source = Microsoft Office 12 instead you can find the two crashes right next to each other.

 
 

So that is how you can get us Watson info off of Vista machines. Please let me know if you have any questions!

Comments

  • Anonymous
    July 18, 2006
    PingBack from http://microsoft.wagalulu.com/2006/07/18/sending-error-reports-in-windows-vista-watson-on-vista/

  • Anonymous
    July 18, 2006
    The comment has been removed

  • Anonymous
    July 18, 2006
    That is amazing that you are already getting that inforamtion.  That is great!

  • Anonymous
    August 24, 2006
    The comment has been removed

  • Anonymous
    August 24, 2006
    The comment has been removed

  • Anonymous
    February 08, 2007
    Une des questions classiques sur Windows VISTA est la gestion des rapports d'erreur. Cette solution existe

  • Anonymous
    December 03, 2008
    je vous envoie le message d'erreur qui s'affiche, merci de bien vouloir m'éclairer, car internet cesse de fonctionner tout le temps.Signature du problème merci :  Nom d’événement de problème: APPCRASH  Nom de l’application: iexplore.exe  Version de l’application: 7.0.6001.18000  Horodatage de l'application: 47918f11  Nom du module par défaut: AcroPDF.dll  Version du module par défaut: 7.0.8.0  Horodateur du module par défaut: 446aa70a  Code de l’exception: c0000005  Décalage de l’exception: 0002fdb3  Version du système: 6.0.6001.2.1.0.768.3  Identificateur de paramètres régionaux: 1036  Information supplémentaire n° 1: fd00  Information supplémentaire n° 2: ea6f5fe8924aaa756324d57f87834160  Information supplémentaire n° 3: fd00  Information supplémentaire n° 4: ea6f5fe8924aaa756324d57f87834160 Lire notre déclaration de confidentialité :  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x040c merci,

  • Anonymous
    December 03, 2008
    je vous envoie le message d'erreur qui s'affiche, merci de bien vouloir m'éclairer, car internet cesse de fonctionner tout le temps.Signature du problème merci :  Nom d’événement de problème: APPCRASH  Nom de l’application: iexplore.exe  Version de l’application: 7.0.6001.18000  Horodatage de l'application: 47918f11  Nom du module par défaut: AcroPDF.dll  Version du module par défaut: 7.0.8.0  Horodateur du module par défaut: 446aa70a  Code de l’exception: c0000005  Décalage de l’exception: 0002fdb3  Version du système: 6.0.6001.2.1.0.768.3  Identificateur de paramètres régionaux: 1036  Information supplémentaire n° 1: fd00  Information supplémentaire n° 2: ea6f5fe8924aaa756324d57f87834160  Information supplémentaire n° 3: fd00  Information supplémentaire n° 4: ea6f5fe8924aaa756324d57f87834160 Lire notre déclaration de confidentialité :  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x040c merci,

  • Anonymous
    January 21, 2009
    PingBack from http://www.keyongtech.com/1853121-powerpoint-2007-tech-refresh-crash