title: Does "Faulting Application" in Windows Event Viewer correlate to segmentation fault in software?
body: <p>A C++ application that we don't have the source code for is crashing.<br>
  The crash is being reported in the Windows Event Viewer:  </p>
  
  <p><a href="https://i.stack.imgur.com/19ldT.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/19ldT.png" alt="enter image description here"></a>  </p>
  
  <p>More specifically, the report shows the following:  </p>
  
  <pre><code>Faulting application name: SEP.exe, version: 0.0.0.0, time stamp: 0x586d8900
  Faulting module name: SEP.exe, version: 0.0.0.0, time stamp: 0x586d8900
  Exception code: 0xc0000005
  Fault offset: 0x0000000000031ab0
  Faulting process id: 0x13bc
  Faulting application start time: 0x01d26abbb48ffc6b
  Faulting application path: C:\Program\Program.exe
  Faulting module path: C:\Program\Program.exe
  </code></pre>
  
  <p>Based on this information, I'd like to make a conclusion about the software bug.   The software experienced a segmentation fault.   </p>
  
  <p>I would just like to confirm whether this information specifically alludes to a segmentation fault, and not something like uncaught exceptions, or exits with failure codes, or any other C++ signals (such as divide by zero (SIGFPE)).  </p>
  
  <p>To rephrase the question again:<br>
  Based on this log information, can I conclude with confidence that the program is crashing due to a segmentation fault and not any other reason?  </p>