Event ID 1015: Error reporting was unable to create a temporary file to hold the crash dump

Windows Event ID Lookup: What Windows event IDs mean: 4625, 4624, 4740, 6008, 41, 7045, 1102 and 3,000 more, with Windows' own message text, the fields and what to check.

Look up a Windows event ID from Event Viewer, a SIEM alert or a log export: what it means, the fields it records, and what to check. Many IDs are used by more than one source (event 41 is both a Kernel-Power crash and a boot error), so every definition is shown, the one people usually mean first. The message text is Windows' own, read from the event providers of Windows 10.0.26200.0, 2026-10-28; the notes are ours, based on Microsoft's security auditing reference.

Try: 4625, 4624, 4740, 6008, 41, 1074, 7045, 1102, 4104, 1149

Error reporting was unable to create a temporary file to hold the crash dump.

Event 1015

WER-SystemErrorReporting

System log

Error

Message and fields (as Event Viewer shows them)

Error reporting was unable to create a temporary file to hold the crash dump.

Name resolution for the name … timed out after the DNS server … did not respond.

Event 1015

DNS-Client

System log

Information

Message and fields (as Event Viewer shows them)

Name resolution for the name … timed out after the DNS server … did not respond. Client PID ….

… has detected a suspicious behavior.

Event 1015

Windows Defender

Windows Defender/Operational log

Warning

Message and fields (as Event Viewer shows them)

… has detected a suspicious behavior.
 	Name: …
 	ID: …
 	Severity: …
 	Category: …
 	Path Found: …
 	Detection Origin: …
 	Detection Type: …
 	Detection Source: …
 	Status: …
 	User: …\…
 	Process Name: …
 	Security intelligence ID: …
 	Security intelligence Version: …
 	Engine Version: …
 	Fidelity Label:  …
 	Target File Name:  …

Decrypt call failed.

Event 1015

SMBServer

SMBServer/Operational log

Error

Message and fields (as Event Viewer shows them)

Decrypt call failed.

Client Name: …
Client Address: …
Session ID: …
Status: … (…)

Guidance:

This event commonly occurs because a previous SMB session no longer exists. It may also be caused by packets that are altered on the network between the computers due to either errors or a "man-in-the-middle" attack.