QUOTA_UNDERFLOW

Code: 0x21 (33)

As HRESULT:As NTSTATUS:

Parameters

ParameterDescription
1The process that was initially charged, if available.
2The quota type. For the list of all possible quota type values, see the header file Ps.h in the Windows Driver Kit (WDK).
3The initial charged amount of quota to return.
4The remaining amount of quota that was not returned.

Description

The QUOTA_UNDERFLOW bug check has a value of 0x00000021. This indicates that quota charges have been mishandled by returning more quota to a particular block than was previously charged.

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
EhStorAuthn.exe0x217Invalid device response
EventCreate.exe0x2178.11011%1
KernelBase.dll0x2178.1The process cannot access the file because another process has locked a portion of the file.
NetTCPIP.dll0x211011DefaultGateway %1 is not on the same network segment (subnet) that is defined by the IP address %2 and PrefixLength %3!lu!.
VSSVC.exe0x211011Volume Shadow Copy Service error: The VSS management class is not registered. This may be caused due to a setup failure or as a result of an application's installer or uninstaller. %1
WinSAT.exe0x211011The assessment was requested to be run on on battery power. Please try again when the system is running DC power.
cipher.exe0x2178.11011%1: Encryption updated.
compact.exe0x211011The system is in the Compact state. It will remain in this state unless an administrator changes it.
dsreg.dll0x2110Failed to discover the Azure AD DRS service. Exit code: %1.
dsreg.dll0x2111Failed to discover the Microsoft Entra DRS service. Exit code: %1.
dssec.dll0x2178.11011Allocate RIDs
ehepgres.dll0x217%1
kernel32.dll0x2178.11011The process cannot access the file because another process has locked a portion of the file.
microsoft-windows-kernel-processor-power-events.dll0x211011Platform based performance and throttle power management features on processor %2 in group %1 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.
msprivs.dll0x2178.11011Increase a process working set
nslookup.exe0x2178.11011%1Received %2!d! record%3.
powershell.exe0x2178.11011Windows PowerShell version in the Windows PowerShell console file "%1!ls!" cannot be empty.
reagentc.exe0x218.11011%1: The Windows RE image was not found.
sstpsvc.dll0x211011CoId=%1: “Secure Socket Tunnelling Protocol (SSTP)” service could not configure the VPN server specific cookies. The detailed information on the error is given below. %2
tpm.sys0x2111The Trusted Platform Module (TPM) has been cleared as requested by %3. Keys previously created in the storage and endorsement hierarchies will no longer work.
w32time.dll0x211011The time service has jumped the local system clock by %1 seconds. This occurs when the time source and local system time are far enough apart that clock rate adjustments cannot be made to reach the time specified by the time source.
webservices.dll0x2178.11011The message contained a header '%1' that did not have a namespace.
wecutil.exe0x2178.11011EventSourceAddress is not specified.
wevtutil.exe0x211011Failed to read XML node %1!s!.
wevtutil.exe0x2178.1Failed to read xml node %1!s!.
wfascim.dll0x211011The IPsec NAT traversal setting is invalid.
win32k.sys0x2178.1Background
win32kbase.sys0x211011Background
wuaueng.dll0x211011Windows Update was unable to connect to proxy server %1 because valid credentials (user name and password) were required, but were either not available or were incorrect. Please check your proxy credentials, and then try searching again for updates.
wuauengcore.dll0x2111Windows Update was unable to connect to proxy server %1 because valid credentials (user name and password) were required, but were either not available or were incorrect. Please check your proxy credentials, and then try searching again for updates.
30 entries