We are seeing the following on Server 2016:
Log Name: System
Source: volmgr
Date: 17/09/2019 07:14:22
Event ID: 46
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: pc.domain.local
Description:
Crash dump initialization failed!
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="volmgr" />
<EventID Qualifiers="49156">46</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-09-17T06:14:22.231603000Z" />
<EventRecordID>496259</EventRecordID>
<Channel>System</Channel>
<Computer>pc.domain.local</Computer>
<Security />
</System>
<EventData>
<Data>\Device\HarddiskVolume3</Data>
<Binary>0000000001000000000000002E0004C004100000080000C000000000000000000000000000000000</Binary>
</EventData>
</Event>
Log Name: System
Source: volmgr
Date: 17/09/2019 07:14:22
Event ID: 46
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: pc.domain.local
Description:
Crash dump initialization failed!
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="volmgr" />
<EventID Qualifiers="49156">46</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-09-17T06:14:22.231603000Z" />
<EventRecordID>496259</EventRecordID>
<Channel>System</Channel>
<Computer>pc.domain.local</Computer>
<Security />
</System>
<EventData>
<Data>\Device\HarddiskVolume3</Data>
<Binary>0000000001000000000000002E0004C004100000080000C000000000000000000000000000000000</Binary>
</EventData>
</Event>
0