If you frequently see an error message The exception unknown software exception (0xe0434352) occurred in the application at location 0x77312c1a when shutting down your Windows computer, here are some possible solutions that might be helpful for you. Although the location can be different at different moments or the error codes could be 0xe0434352, 0xc06d007e, 0x40000015, 0xc00000d, 0xc0000409, etc. – but the solution is more or less the same.
The exception unknown software exception occurred in the application
This particular error message can appear due to various reasons. For example, you can get it because of a corrupted .NET Framework installation as well as a corrupted device driver.
1] Use .NET Framework Repair Tool
If you are using Windows 7 or an older version, use .NET Framework Repair Tool made by Microsoft to repair corruptions in the Framework. This tool supports .NET Framework 4.6.1, 4.6, 4.5.2, 4.5.1, 4.5, 4.0 and 3.5 SP1.
2] Run Check Disk
Open an elevated command prompt and execute the following command-
chkdsk /f
Check if this helps.
3] Troubleshoot in Clean Boot State
A Clean Boot helps users fix various Windows device driver related problems. Hence, if you have recently updated your PC to a newer version and you have some very old device drivers, perform a Clen Boot and try to troubleshoot the issue manually.
4] Run System File Checker
System File Checker is a command line tool that can be used to get back corrupted system protected files. It is possible to restore protected files from cached version if it finds any corrupted files, folders or registry keys. To run this tool you need to open Command Prompt with administrator privileges and execute this command-
sfc /scannow
You may have to restart your computer after the scan is over.
5] Use System Restore
If you have suddenly started getting this error without updating your system or installing any driver, you can make use of System Restore Point to go back to a good point.
Hope you will find something here useful to solve your issue.

- Tags: Troubleshoot