SMBClient Errors: 30611 followed by multiple 30906

Hello,

I have researched online but could not find anything relevant. A hyper-v managed windows server 2016 instance is crashing and throws multiple events of:

"The IO operation at logical block address 0x###### for Disk 0 "

 On the hyper-v host, after the VM has crashed there has been a pattern of a SMBClient 30611 error of:

"

Failed to reconnect a persistent handle.

Error: The account is not authorized to login from this station.

FileId: 0x200000E0265CBEE:0x20E000000A9
CreateGUID: {b3d6066e-563c-11e8-a949-0002c937dda1}
Path: \networked\path\to\instance.vhdx

Reason: 201

Previous reconnect error: STATUS_SUCCESS
Previous reconnect reason: The reason is not specified

Guidance:
A persistent handle allows transparent failover on Windows File Server clusters. This event has many causes and does not always indicate an issue with SMB. Review online documentation for troubleshooting information.

"

Followed by several 30906 errors:

"

A request on persistent/resilient handle failed because the handle was invalid or it exceeded the timeout.

Status: The transport connection is now disconnected.

Type: Write (and Read)
Path: \networked\path\to\instance.vhdx
Restart count: 0

Guidance:
After retrying a request on a Continuously Available (Persistent) handle or a Resilient handle, the client was unable to reconnect the handle. This event is the result of a handle recovery failure. Review other events for more details.

"

Then the server crashed. If someone has any ideas or could point me in a direction to recover other more logs that would be super.

Thanks!