Windows error 0x000000AD, 173

Detailed Error Information

CANCEL_VIOLATION[1]

MessageA lock request was not outstanding for the supplied cancel region.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x800700AD.

VIDEO_DRIVER_DEBUG_REPORT_REQUEST[2]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0xAD: VIDEO_DRIVER_DEBUG_REPORT_REQUEST.

HRESULT analysis[3]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[3][1]
DescriptionThe default facility code.[3][1]
Error Code173 (0x00ad)

Questions

4votes
2answers

Investigating Memory Leak

We have a slow memory leak in our application and I've already gone through the following steps in trying to analyize the cause for the leak: 1. Enabling user mode stack trace database in GFlags 2. In Windbg, typing the following command: !heap -stat -h 1250000 (where 1250000 is the [...] read more
windows
debugging
memory-management
memory-leaks
windbg

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  3. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0