Windows error 0x000000AD, 173

Detailed Error Information

CANCEL_VIOLATION^[1]

Message	A lock request was not outstanding for the supplied cancel region.
Declared in	winerror.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.

Flags	Severity	Success 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
	Origin	Microsoft
	NTSTATUS	false
	Reserved (X)	false
Facility	Code	0 (0x000)
	Name	FACILITY_NULL^[3]^[1]
	Description	The default facility code.^[3]^[1]
Error Code		173 (0x00ad)

Questions

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

how to correctly store the address of a procedure in a register x86_64 nasm?

I want to store the address of a procedure in a register as follows : extern _printf section .text global _foo _foo : mov rax, [rel _printf] call rax ret but i get this error when compiling with a main written in C : ld: warning: PIE disabled. Absolute addressing [...] read more

nasm

linker-errors

Comments

Sources

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

User contributions licensed under CC BY-SA 3.0