BSOD 85 (DATA_COHERENCY_EXCEPTION): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: DATA_COHERENCY_EXCEPTION

Could be also:
Constant	Type	OS
ERROR_ALREADY_ASSIGNED	Win32 error	Windows
ERESTART	errno	Linux
EBADEXEC	errno	Mac
ELIBSCN	errno	Solaris

Previous	Next
LM_SERVER_INTERNAL_ERROR	INSTRUCTION_COHERENCY_EXCEPTION

DATA_COHERENCY_EXCEPTION

DATA_COHERENCY_EXCEPTION is bug check 0x55. Microsoft's individual reference describes it only as very infrequent and does not assign public meanings to the four stop arguments. Because the contract is sparse, the phrase “data coherency” should not be expanded into a universal cache, RAM, or storage diagnosis.

Architecture and build context matter

For a coherency-named stop, processor architecture and the exact Windows build are especially important context, but the code itself does not publish a portable syndrome format. Keep the original dump and symbols. A stack, trap context, or platform-specific debugger output can provide evidence that the generic code name cannot.

What not to skip

Record all four raw parameters even when the documentation gives them no stable labels.
Query !analyze -show 0x55 and then analyze the captured dump with !analyze -v.
Do not treat memory replacement, firmware changes, or driver rollback as code-defined remedies; correlate any such action with recurring dump evidence.

References

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