VHD_BOOT_INITIALIZATION_FAILED

Code: 0x12f (303)

As HRESULT:As NTSTATUS:

Parameters

ParameterDescription
1

Action that failed

1 : Couldn't extract VHD information from boot device. 2 : Timeout waiting for VHD parent device to surface. 3 : VHD path string memory allocation error. 4 : VHD path construction failed. 5 : VHD boot device mount failed. 6 : Disable sleep states failed. 7 : VHD information memory allocation error. 8 : VHD information construction failed.
2NT status code
3Reserved
4Reserved

Description

The VHD_BOOT_INITIALIZATION_FAILED bug check has a value of 0x0000012F. This indicates that an initialization failure occurred while attempting to boot from a VHD.

Important

This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

ModuleCodeFound inDescription
ESENT.dll0x12f8.11011%1 (%2) %3Database engine error %4 occurred.
EventCreate.exe0x12f78.11011%1
KernelBase.dll0x12f78.1The file cannot be opened because it is in the process of being deleted.
appmgmts.dll0x12f78.11011The removal of the assignment of application %1 from policy %2 succeeded.
dxgkrnl.sys0x12f11Generic Monitor (%1)
kernel32.dll0x12f78.11011The file cannot be opened because it is in the process of being deleted.
microsoft-windows-system-events.dll0x12f1011Microsoft-Windows-AeSwitchBack
ntdll.dll0x12f1011At least a portion of IO range intersects with a ghosted file range.
rekeywiz.exe0x12f78.11011Your old EFS keys are protected using a different smart card. This will likely be one of the smart cards you previously used to protect your EFS files. Insert this smart card now.
webservices.dll0x12f78.11011The unsigned 32 bit integers %1 and %2 could not be added because it would be out of the range of an unsigned 32 bit integer.
10 entries