wpf - WinDbg Help Pls -

i'm pretty new using windbg, application started having issues, on windows 7 machines (it runs fine first time pc started crashes or disappears silently each time after).

i got mdmp file, find myself lacking on how best extract data need it. got following analysis (might doing wrong)...

can shed light on issue or if i'm running analysis incorrectly:

0:000> !analyze -v ******************************************************************************* *                                                                             * *                        exception analysis                                   * *                                                                             * *******************************************************************************  getpageurldata failed, server returned http status 404 url requested: http://watson.microsoft.com/stageone/star_exe/1_0_0_0/4dbad268/kernelbase_dll/6_1_7600_16385/4a5bdaae/e0434352/00009617.htm?retriage=1  faulting_ip:  kernelbase!raiseexception+58 752d9617 c9              leave  exception_record:  ffffffff -- (.exr 0xffffffffffffffff) exceptionaddress: 752d9617 (kernelbase!raiseexception+0x00000058)    exceptioncode: e0434352 (clr exception)   exceptionflags: 00000001 numberparameters: 5    parameter[0]: 80070002    parameter[1]: 00000000    parameter[2]: 00000000    parameter[3]: 00000000    parameter[4]: 57af0000  process_name:  star.exe  error_code: (ntstatus) 0xe0434352 - <unable error code text>  exception_code: (ntstatus) 0xe0434352 - <unable error code text>  exception_parameter1:  80070002  exception_parameter2:  00000000  exception_parameter3:  00000000  exception_parameter4: 0  mod_list: <analysis/>  ntglobalflag:  0  application_verifier_flags:  0  managed_stack: !dumpstack -ee no export dumpstack found  managed_bitness_mismatch:  managed code needs matching platform of sos.dll proper analysis. use 'x86' debugger.  additional_debug_text:  followup set based on attribute [is_chosencrashfollowupthread] frame:[0] on thread:[pseudo_thread]  last_control_transfer:  57c03970 752d9617  faulting_thread:  ffffffff  default_bucket_id:  stackimmune  primary_problem_class:  stackimmune  bugcheck_str:  application_fault_stackimmune_nosos_clr_exception_wrong_symbols  stack_text:   00000000 00000000 star.exe+0x0   symbol_name:  star.exe  followup_name:  machineowner  module_name: star  image_name:  star.exe  debug_flr_image_timestamp:  4dbad268  stack_command:  ** pseudo context ** ; kb  failure_bucket_id:  stackimmune_e0434352_star.exe!unknown  bucket_id:  application_fault_stackimmune_nosos_clr_exception_wrong_symbols_star.exe  followup_ip: *** warning: unable verify timestamp star.exe  star!.ctor+0 [c:\users\aj\documents\visual studio 2010\projects\star\star\viewmodels\viewmodelbase.cs @ 22] 00360000 ??              ???  watson_stageone_url:  http://watson.microsoft.com/stageone/star_exe/1_0_0_0/4dbad268/kernelbase_dll/6_1_7600_16385/4a5bdaae/e0434352/00009617.htm?retriage=1  followup: machineowner --------- 

you may want use article starting point: sos: it's not abba song anymore

it looks application .net application, make sure you've got right .net framework installed. when load sos.dll file windbg, may have provide full path. also, can set access public microsoft symbol servers of stack tracing. article may help: debugging tools , symbols: getting started. make sure you've got latest version of debugging tools.

!analyze give information fault, not else. should @ first article see else going on.

posting information application people see if having similar issue.

it looks fault happening in viewmodelbase.cs file. may want add logging (using log4net or similar tool) catch exception , print out stack trace. can hook appdomain.currentdomain.unhandledexception event (or application.dispatcherunhandledexception event wpf applications) catch that's getting thrown , printing out log file. in case, won't need resort windbg figure out what's going on.