How to Fix the COREMSGCALL_INTERNAL_ERROR BSoD

Uninstall any software you installed prior to this error started occurring

Reading time icon 4 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

How to fix COREMSGCALL_INTERNAL_ERROR BSoD
XINSTALL BY CLICKING THE DOWNLOAD FILE
A message from our partner

Fix all BSoD events and keep computer safe and clean:

Fortect will find the cause of BSoD and fix it. Here is how to do it with 3 easy steps:

  • Download Fortect and install it on your PC
  • Launch the tool and Start scanning to find broken files that are causing BSoD
  • Right-click on Start Repair to fix issues affecting your computerโ€™s security and performance
Download Now Fortect has been downloaded by 0 readers this month, rated 4.6 on TrustPilot

The COREMSGCALL_INTERNAL_ERROR BSoD comes with the value of 0x00000173. The bug check points out that the CoreMessageCall detected an unrecoverable error. Now, this CoreMessageCall is a Windows OS component that facilitates communication between different applications and processes.

So, this error is most likely caused by software conflicts and driver issues, although, as with any other BSoD, we can’t exclude hardware malfunctioning.

How do I fix the COREMSGCALL_INTERNAL_ERROR BSoD?

1. Uninstall any recently installed software

  1. Press Win + I to start Settings.
  2. Go to Apps > Installed apps and identify any recently installed apps.
  3. Now, click the three dots button to the right of the app and select Uninstall.
  4. Reboot your PC to see if the COREMSGCALL_INTERNAL_ERROR shows up again.

You may also try booting Windows in Safe mode to troubleshoot this issue. The PC will start with a minimum set of drivers and processes and that will help you determine which app is causing this problem.

2. Update or reinstall the problematic driver

  1. Right-click the Start button and select Device Manager.
  2. Click on the component categories one by one to expand them, and look for a driver with a yellow exclamation mark next to it.
  3. Once located, right-click the driver and choose Update driver from the context menu.
  4. Click Search automatically for drivers.
  5. Follow the on-screen prompts to complete the process.

Of course, you should start by looking for a driver you installed recently, because that might be causing this issue. Also, if Windows cannot find a driver for your device, the best way would be to download it manually from the manufacturerโ€™s website.

As this whole process might take a lot of time and effort, we recommend using a reliable driver updater tool. They automatically scan your system for problematic drivers and automatically update or replace them with just a few clicks.

3. Perform SFC and DISM scans

  1. Click the Start button, type cmd in the search box, and click Run as administrator to launch Command Prompt with full permissions.
  2. Type the following command to scan and repair the corrupted system files and press Enter: sfc /scannow
  3. Wait for the process to finish, then copy & paste the following command to repair the Windows OS files, and hit Enter: DISM /Online /Cleanup-Image /RestoreHealthRestore health
  4. Once the scan is complete, restart your computer to confirm the changes.

As with any BSoD error out there, it’s recommended to perform SFC and DISM scans because most of the times, they will help you fix any related system and Windows image errors.

4. Restore your system to a previous point

  1. Press the Windows key, type control panel in the search box, and click Open.    
  2. Select Large icons for View by, then click the Recovery option.Recovery Control PaneL
  3. Click the Open System Restore option.Open system restore
  4. Now, select Choose a different restore point and click Next.Next Choose a different restore point
  5. Choose the restore point created before the error started to occur, then click Next.
  6. Click on Finish to initiate the process.

Windows will reboot and restore your system settings to the chosen point. Of course, that will only work if you actually created a restore point along the way. If you see the System Restore didnโ€™t complete the successfully, we suggest you check out this detailed guide for solutions.

So, by performing the solutions above, you hopefully fixed the COREMSGCALL_INTERNAL_ERROR BSoD. We remind you that BSoD errors are also triggered by faulty or malfunctioning hardware components. So, if nothing worked, you should probably ask for professional help from a technician or a repair shop.

Speaking of BSOD errors, we recently covered Elam_Driver_Detected_Fatal_Error, so don’t miss it for more information.

If you have any questions or know about other tested solutions that worked for you, let us know in the comments below.

More about the topics: BSOD, BSoD error codes, BSoD errors

User forum

0 messages