Skip to content

Event ID 1017: Error reporting was unable to copy a crash dump from the paging file

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 copy a crash dump from the paging file.

Event 1017
WER-SystemErrorReporting
System log
Error
Message and fields (as Event Viewer shows them) 
Error reporting was unable to copy a crash dump from the paging file.

The DNS server's response to a query for name … indicates that no records of the type queried are available, but could indicate that other records for the same name are present.

Event 1017
DNS-Client
System log
Information
Message and fields (as Event Viewer shows them) 
The DNS server's response to a query for name … indicates that no records of the type queried are available, but could indicate that other records for the same name are present. Client PID …. Send Blob …. Context …

Handle scavenged.

Event 1017
SMBServer
SMBServer/Operational log
Information
Message and fields (as Event Viewer shows them) 
Handle scavenged.

Share Name: …
File Name: …
Resume Key: …
Persistent File ID: …
Volatile File ID: …
Durable: …
Resilient or Persistent: …

Guidance:

The server closed a handle that was previously reserved for a client after 60 seconds. You should expect this event on a computer that is continuously available where a client did not gracefully close its session. For instance, this may occur when the client unexpectedly restarted.