APC index Mismatch on Virtual Windows Server 2016

Question

Hello,

I would like to ask for your help because I am experiencing a boot problem on a Windows Server 2016 virtual machine.

Following a power cut, the Proxmox hypervisor restarted, as did the virtual machines.

All have restarted except the virtual machine in question.

After acknowledging the "APC Index Mismatch" message, a second screen appears with a log collection percentage (which I imagine is intended for Microsoft).

I am unable to access desktop, only stop the computer or access to advanced option for troubleshooting.

I've tried several things:

• boot in safe mode with and without network support
• starting up in safe mode from the command prompt (unsuccessful, the message "Preparing Windows, do not shut down the computer" runs in a loop)
• advanced troubleshooting option and opening a cmd, chkdsk, sfc /scannow or dism commands don't work

What other steps could be taken to solve this boot-up problem?

Thank you in advance for any help you can give me.

Regards,

Ben

Answer 1

Hello,

Thank you for posting in Microsoft Community forum.

Based on the description, I understand your question is related to boot issue.

The APC_INDEX_MISMATCH bug check has a value of 0x00000001. The bug check indicates a mismatch in the asynchronous procedure calls (APC) state index.

• In Event Viewer, check System Log for more error messages that might help you identify the device or driver that's causing this bug check.
• If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
• Confirm that any new hardware that's installed is compatible with the installed version of Windows. For example, you can get information about required hardware at Windows 10 specifications.

Bug Check 0x1 APC_INDEX_MISMATCH - Windows drivers | Microsoft Learn

Have a nice day. 

Best Regards,

Molly

Answer 2

Hello Molly,

Thank you for your reply, I had indeed read what you said in the Microsoft forums.

The only possible actions from the vm are the diagnostic and troubleshooting tools, but after several hours spent trying to troubleshoot, nothing has worked:

• Sfc for system file analysis
• Chkdsk for disk error analysis
• Bcedit / bootrec for boot reconfiguration and repair
• wusa for uninstalling potentially corrupt kb...
• iso live windows server
• iso live hiren boot cd)

All these commands are not fully functional and do not repair the error in question, as disks are virtualized and not necessarily detected when booting via live cd.

RESTORATION ACTIONS

Without the possibility of repairing from the VM SRVMAIL, we attempt to restore the VM101-DISK-0 disk via the Veeam ISO and backups located on the NAS.

After incremental or full restores, VM startup presents exactly the same problem, APC INDEX MISMATCH, no login prompt.

INSTALLATION OF A NEW MAIL SERVER (SRVMAIL2024)

I installed a new SRVMAIL2024 VM, still composed of two disks: C: for the system and the second is the old SRVMAIL disk, which I attached to retrieve the database.

I've also mounted the VM101-DISK0 disk in G: which is the system disk in error.

ACTIONS ON THE VM 101 SRVMAIL C:\ DISK

On the new virtual machine 109 SRVAIL2024:

• Mounting of VM-101-DISK-0 disk (C:\ disk of our VM in question, which has therefore taken the letter G:)
• Analysis of event logs (application, system), trusted installer service error (service related to Windows updates)
• Execution of chkdsk on G:\ disk (no errors, following chkdsk, boot test on old vm, non-functional)
• Execution of sfc /scannow /offbootdir=G:\ /offwindir=G:\windows (unsuccessful, error indicating that a repair is pending)

In cmd,

• wusa /uninstall /kb:4046065 /quiet /norestart (to remove the KB that could be responsible for the boot problem), not functional
• Download and install 2024-08 Cumulative Update for Windows Server 2016 for x64-based Systems (KB5041773)
• Non-functional because the update application affects the system and not the mounted disk, which will not be reflected in SRVMAIL.
• Execution of DISM /Image:G:\ /Cleanup-Image /RestoreHealth, which fails to succeed, either online or via a Windows Server 2016 iso dvd source.

I also deleted the pending file in G:\Windows\winsxs\pending.xml after making a backup copy.

This allowed me to perform an sfc /SCANNOW /OFFBOOTDIR=G:\ /OFFWINDIR=G:\Windows which went through but didn't reveal any errors.

Last action: I attached my functional disk of the newly created VM to the VM in error, with the two system disks (one functional, the other showing a BSOD).

I have a double boot (choice of two installations of windows server 2016), in this case I don't have a BSOD when choosing the OS that causes the problem, but a boot error that indicates an error in the file \Windows\system32\winload32

Status: 0xc000000e

Thank you for your time and help

Regards,

Ben

Answer 3

Hello,

Thanks for sharing the current status of the trouble-shooting, maybe you can also try do an inplace upgrade use the same version ISO.

Preparation:

Download the ISO file for Windows Server 2016 from VLSC at: https://www.microsoft.com/Licensing/servicecenter/default.aspx

Note: For the sake of double security, it is recommended that you back up your important data first to prevent unknown issue during the upgrade.

Steps:

Perform an in-place upgrade of Windows Server | Microsoft Learn

Best Regards,

Molly