I think there are many cases in which a program or application crashes with error . Sometimes the program closes and a message appears: " An error has occurred in .. the application will be closed " and then " Reporting the problem to Microsoft ". Obviously reporting the problem to Microsoft by sending the details of the error is a completely useless operation which in 99.9% of cases does not lead to anything. At other times, in more serious cases, the computer completely freezes and a blue screen appears with an incomprehensible message that leads to restarting the PC.
READ ALSO: Force the closure of a program on Windows
We have already seen how to be able to interpret blue screen crashes, how to understand the cause, analyze them and how to prevent or correct them. In a nutshell, the fault lies with a piece of hardware connected to the computer and its driver. In fortunate cases, the blue screen does not appear by disconnecting the device (printer, external hard disk, USB stick and so on) and updating the driver. In other cases it depends on the hardware acceleration which must be disabled from the Control Panel -> screen -> Advanced -> Troubleshooting or from the video card settings.
In the case of errors of programs that close on their own, the tool for understanding what happened and making a diagnosis is, in Windows 7 and Windows 10, the reliability monitoring function, explained in another post.
Another way is to go to the Event Log (it's in Administrative Tools) and study the error codes for the applications. In support there is also a software called MyEvent Viewer, which allows you to facilitate the detection and understanding of errors.
On Windows 7, 8 and Windows 10 the details of crashing program errors are stored by the Windows Error Reporting (WER) component .
Whenever an application crashes then there is a report written in .Wer file.
To recover this information and read the details of all the error messages on Windows there are two small alternative programs of Nirsoft, free and that do not require installation.
1) Wincrash Report allows you to see the description of all Windows errors, including those of individual programs when they close themselves by mistake by showing that unpleasant window with the red X.
2) AppCrashView displays the list of all system shutdowns and the contents of the .wer file relating to the error selected in the upper pane.
When an application crashes or does not work due to incompatibility or any other problem and closes without any useful information (that of sending to Microsoft is not) then you can try to make an error check using AppCrashView to understand the problem .
3) WhatIsHang allows you to understand why a program crashed giving details of the type of error that caused the crash. Even if it is a very technical program, it can also give an indication to the less experienced on the solution to search on Google.
It is clear that these are useful tools particularly for systems engineers and more experienced people, while remaining obscure and difficult to understand for others. In general, however, once the references of an error are obtained, you can always do a search for the solution on Google.
It is understood that, almost always, the problems on programs and applications depend on the version in use and on who developed the software.
READ ALSO: If a program crashes and does not respond, resolve errors and crash problems (Windows) .
