BSOD 371 (COREMSGCALL_INTERNAL_ERROR): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: COREMSGCALL_INTERNAL_ERROR

Could be also:
Constant	Type	OS
ERROR_FILE_SYSTEM_VIRTUALIZATION_BUSY	Win32 error	Windows

Previous	Next
CRYPTO_LIBRARY_INTERNAL_ERROR	COREMSG_INTERNAL_ERROR

COREMSGCALL_INTERNAL_ERROR

COREMSGCALL_INTERNAL_ERROR is bug check 0x173. Microsoft states that CoreMessageCall detected an unrecoverable error. Parameter 1 contains the failure type; parameters 2, 3, and 4 are reserved. No public enumeration of failure-type values is supplied on the bug-check page, so parameter 1 should be preserved numerically rather than assigned an invented label.

Distinguish 0x173 from CoreMessaging 0x174

The neighboring COREMSG_INTERNAL_ERROR code names CoreMessaging, while 0x173 names CoreMessageCall. They have a similar published argument shape, but they remain different stop codes and different named detection layers. Do not merge dumps solely because both descriptions mention an unrecoverable messaging error.

What to inspect

Record parameter 1 and the exact Windows build; reserved arguments should not be given portable meanings.
Use !analyze -v and inspect the failing thread and stack for the component interacting with the CoreMessageCall path.
Compare repeated 0x173 dumps by parameter 1 and call stack before grouping them as one incident.

References

Looking for a different code? Search another status or error code.