BSOD or Blue Screen of Death errors are one of the toughest issues you can encounter in Windows 10 as well as the hardest ones to resolve as they simply shut the system down or restart it abruptly and claims that it isn’t possible to boot Windows again. One of the difficult BSOD errors is the Machine Check Exception BSOD error. The reason why it is hard to fix is that in most cases, it occurs soon after Windows loads which gives users little to no time in resolving it. To make things worse, the system also freezes right before it displays the blue screen error and shuts the system down.
Usually, the Machine Check Exception Stop error occurs due to the failure or overstressing of the hardware components. And in the case of almost all Blue Screen of Death errors, the issue usually has something to do with the drivers. So if you frequently see this BSOD error from time to time, now’s the time to act on it by following the solutions given in this post.
The Blue Screen troubleshooter is a built-in tool in Windows 10 that can be found on the Settings Troubleshooters page. To use it, refer to these steps:
System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be causing the Machine Check Exception BSOD error. To run the SFC command, follow the steps given below.
The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:
In the Blue Screen where the Machine Check Exception error is displayed, tap the F8 key to go to the Startup Settings where you can find Startup Repair and then run it. Note that this is a must-try option especially if you are unable to start your computer and if you can use your computer for a few moments.
There are cases when the Machine Check Exception error is caused by the Windows System Image so you need to repair it using the DISM or Deployment Imaging and Servicing Management tool. The DISM tool is another command-line tool in the Windows operating system that could help users fix various corrupted system files. To use it, follow these steps:
If you have made some modifications in the BIOS that might have caused this error, you have to revert those changes to resolve the issue. On the other hand, if you have made a couple of changes and you do not remember which is which, you might have to reset the BIOS.
To fix this BSOD error, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, this reset option resets all the system settings and files.
“This policy setting allows you to hide the Switch User interface in the Logon UI, the Start menu, and the Task Manager. If you enable this policy setting, the Switch User interface is hidden from the user who is attempting to log on or is logged on to the computer that has this policy applied. The locations that the Switch User interface appears in the Logon UI, the Start menu, and the Task Manager. If you disable or do not configure this policy setting, the Switch User interface is accessible to the user in the three locations.”
“Something went wrong, Sorry, installation cannot continue because no compatible office products are detected.”When you have to work on two different languages, that’s where the language packs come in handy. You might have to work on one language but when it comes to proofreading or help, you need another language. Note that some language accessory packs offer partial localization which is why some parts of the Office might show the default language. If you are using Office 365 or Office 2019, 2016, 2013, or 2010, you need to go to the language accessory pack page from office.com and select your language. Once you see the download link, click on it to start downloading the pack. It includes the display in the chosen language, proofing tools for the selected language, as well as the Help in the selected language. Once the installation is complete, follow each one of the given options below to configure the language accessory pack properly.
"Error 2738. Could not access VBScript run time for custom action."
Error 80070490 (Element not found)
‘The file I386Ntkrnlmp.exe could not be loaded. The error code is 7.’ or ‘The file I386L_intl.nlf could not be loaded. The error code is 7.’
“It looks like you don’t have permission to save changes to this file. Try saving a copy instead.”There are several options you can explore to resolve this error. You can try updating the Microsoft Photos app or verify the ownership of the destination folder. You can also re-register and reinstall the app. For more detailed instructions, make use of the options provided below.
Set-ExecutionPolicy Unrestricted
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}Note: In the command given, do not forget to replace the “PackageFullName” with the actual package name for the Photos app. After executing the command, it will uninstall the Photos app from your computer so you need to install it again from the Windows Store by simply looking for it. Once you found it, just click on install to start the installation process.