Hello Thank you for your question and reaching out. I can understand you are having query\issues related to Backup and Blue screen. As you are using VMware and Veeam , which are non Microsoft products or services , I would suggest you to post or get in touch with their respective VMware and Veeam forums or support. --If the reply is helpful, please Upvote and Accept as answer--
Diagnosing PNP_DETECTED_FATAL_ERROR bluescreen/bugcheck
Hi, We have 3 VMs running on ESXi 7, that we backup with Veeam. When the initial backup was configured and run, it was ok and completed successfully. The job has guest file system quiescing enabled. Since the initial backup, we have removed some leftover folders from an application that was uninstalled. This was the only change on the VMs we made before the next backup job. Now, every time we run the backup (or more specifically, take a snapshot of the VM with guest file system quiescing enabled), the VM blue screens with a "PNP__DETECTED__ FATAL_ERROR" message. Looking at bluescreenview, the culprit drivers are hal.sys and partmgr.sys Hal.sys I just take to mean that some driver has put the HAL into a weird state, not hal.sys itself causing an issue, and partmgr.sys is related to partition management or file systems? I do see some NTFS events around the time of the snapshots, with detail such as:
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{e48532b2-0000-0000-0000-602200000000}, DeviceName: \Device\HarddiskVolume7.
(The specified request is not a valid operation for the target device.)
And
The default transaction resource manager on volume \\?\Volume{e48532b2-0000-0000-0000-602200000000} encountered a non-retryable error and could not start. The data contains the error code.
I'm not really sure where my next port of call is to determine what driver is actually having an issue and causing the bluescreen? Can anyone point me in the right direction please? Many thanks James