Windows 10 Pro - Shutdown Bug Check?

[coolspot]

Hello Everyone,

Upon shutting down my Windows 10 VM, sometimes it encounters a BugCheck - there are no obvious errors, the machine seems to shutdown gracefully.

However, upon re-Powering on the machine, in the Event Log, I see the following error:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000a0 (0x000000000000010a, 0x000000000000000a, 0xffffce8c7a2cf050, 0xffffffffc0000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

Interesting, there is no dump file in %SystemRoot%\Minidump, in my event log I see:

Unable to produce a minidump file from the full dump file.

It seems that Windows encounters some error during the shutdown process and it doesn't even dump the error log?

Any ideas why this could be happening?

I do have:

1. Nvidia GPU Passthrough Enabled
2. Disk Passthrough (2 x 4TB WD Reds)
3. RAID 1 enabled on the passed through disks for Blue Iris

Anyone seen this type of bug check upon a Proxmox Windows 10 guest shutdown and how to debug?

I'm running Virtual Environment 7.1-12.

Thanks.

 

[oguz]

hi,

there is no dump file in %SystemRoot%\Minidump

could you check also the path on the error message for the dump file?


in your error message:

A dump was saved in: C:\Windows\MEMORY.DMP

Upon shutting down my Windows 10 VM, sometimes it encounters a BugCheck

does it happen seemingly randomly or could it be reproducible in some way?

the error code on your bugcheck 0x000000a0 indicates this power error [0] so it might be related to your passthrough devices.

Any ideas why this could be happening?

I do have:

1. Nvidia GPU Passthrough Enabled
2. Disk Passthrough (2 x 4TB WD Reds)
3. RAID 1 enabled on the passed through disks for Blue Iris

could you also post your VM configuration? (qm config VMID (replace VMID for your VM)

[0]: https://docs.microsoft.com/en-us/wi...debugger/bug-check-0xa0--internal-power-error

 

[erioshi]

Are you running the recommended VirtIO-Win drivers for Windows systems from Red Hat?

I believe there is a balloon driver if you system is allowing for memory ballooning. Also there may be other drivers depending on your setup.

Link to the latest folder: https://fedorapeople.org/groups/vir...ownloads/archive-virtio/virtio-win-0.1.217-1/

 

[coolspot]

Are you running the recommended VirtIO-Win drivers for Windows systems from Red Hat?

I believe there is a balloon driver if you system is allowing for memory ballooning. Also there may be other drivers depending on your setup.

Link to the latest folder: https://fedorapeople.org/groups/vir...ownloads/archive-virtio/virtio-win-0.1.217-1/

The latest 0.1.217.1 drivers seem to be broken on Windows - the installer doesn't work. I see there was a GitHub issue opened for it but the developer said it'll be a few weeks before the next build. The installer seems to be broken for the past few version, I had to use one from December? The latest installer actually messed one of my VMs so badly that I had to rebuild!

I opened the memory.dump in Windbg Preview and got an inconclusive analysis.

Here is my VM config.

agent: 1
bios: ovmf
boot: order=ide0;scsi1;ide2
cores: 4
efidisk0: local-lvm:vm-100-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: 0000:05:00,pcie=1
ide0: none,media=cdrom
ide2: none,media=cdrom
machine: pc-q35-6.1
memory: 16384
meta: creation-qemu=6.1.0,ctime=1640885929
name: BlueIris
net0: virtio=BE:14:F9:39:5A:56,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win10
scsi1: local-lvm:vm-100-disk-0,discard=on,iothread=1,size=100G,ssd=1
scsi2: /dev/disk/by-id//ata-WDC_WD40EFZX-68AWUN0_WD-WXXXXXXXXXXX,backup=0,size=3907018584K
scsi3: /dev/disk/by-id//ata-WDC_WD40EFZX-68AWUN0_WD-WXYYYYYYYYYY,backup=0,size=3907018584K
scsihw: virtio-scsi-pci
smbios1: uuid=e1ae7890-5328-4a86-a03c-c5a2c735032b
sockets: 1
vmgenid: 3f64ad30-c70c-4961-9c35-1c6861673106

Error was occuring during every reboot; however when running, the system is stable. I haven't rebooted this week, but I will update with more details upon the next reboot.

 

[oguz]

Error was occuring during every reboot; however when running, the system is stable. I haven't rebooted this week, but I will update with more details upon the next reboot.

any news?

could you also try detaching the passthrough disks and PCI device to see if the bugcheck still occurs?

 

[coolspot]

any news?

could you also try detaching the passthrough disks and PCI device to see if the bugcheck still occurs?

Thanks for following up and getting me moving on debugging!

I noticed in my Event Log the bugcheck was still there, in fact, over the weekend I did reboot. My debug logs are below.

I did some additional debugging, it seems the bugcheck is related to my Nvidia Quadro T400 passthrough, I removed it from my VM and the bug check disappeared.

So it seems the bugcheck during shutdown is related to the GPU.

Any idea if these types of bug checks are related to IOMMU, hardware, driver, proxmox, or virtio?

I'm not sure how to further debug.

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000a0 (0x000000000000010a, 0x000000000000000a, 0xffffc08c9329bd70, 0xffffffffc0000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

I ran windbg on the memory dump, I don't have symbols loaded, but a copy is here: https://pastebin.com/vhHn9QZN

Looks like a similar issue occurs here: https://forum.proxmox.com/threads/windows-vm-rebooting-bugcheck.57683/

 

[marcosscriven]

I'm seeing the same "BugCheck" log upon restart, however I only noticed in passing. It doesn't actually seem to cause a problem.

Did you find out what's wrong?

 

[coolspot]

I'm seeing the same "BugCheck" log upon restart, however I only noticed in passing. It doesn't actually seem to cause a problem.

Did you find out what's wrong?

Yes, I think it was related to my Nvidia T400 GPU. I disabled hardware video acceleration in Blue Iris and also updated the Nvidia drivers to the latest release. I don't recall having a Bug Check in a while now.

 

[Inten]

I just recently noticed these "BugCheck" log entries on our Lab Windows 10 systems (21H2). They would appear after powering back on after a Shutdown (ie. not restart) After a bit of troubleshooting one setting change seems to have stopped these "BugCheck" entries after a shutdown.
Power & sleep > Additional power settings > Choose what the power button does > Change settings that are currently unavailable
Uncheck "Turn on fast startup"