Unhandled exception at 0x00000000772CA267 (ntdll.dll) in *****.exe : 0xC0000005: Access violation writing location 0xFFFFFCA800000000

-1

I am getting this exception

Unhandled exception at 0x00000000772CA267 (ntdll.dll) in ******.exe: 0xC0000005: Access violation writing location 0xFFFFFCA800000000.

When I look into callstack I don't see my code in the stack but the below:

ntdll.dll!RtlFreeHeap() Unknown
kernel32.dll!HeapFree() Unknown
winhttp.dll!CAuthData::Clear(void)  Unknown
winhttp.dll!HTTP_USER_REQUEST::_AdjustCredentialStates(unsigned short,int *)    Unknown
winhttp.dll!HTTP_USER_REQUEST::_ResponseProcessingLoop(class PENDING_API_CALL *)    Unknown
winhttp.dll!HTTP_USER_REQUEST::OnRecvResponse(unsigned long)    Unknown
winhttp.dll!WEBIO_REQUEST::OnIoComplete(unsigned long,unsigned __int64,class HTTP_ASYNC_OVERLAPPED *)   Unknown
winhttp.dll!HTTP_THREAD_POOL::_WorkItemCallback(void)   Unknown
ntdll.dll!TppWorkpExecuteCallback() Unknown
ntdll.dll!TppWorkerThread() Unknown
kernel32.dll!BaseThreadInitThunk()  Unknown
ntdll.dll!RtlUserThreadStart()  Unknown

We use SOAP req/res. But we have updated couple of req/res to REST not we use json req/res. After this change we get the above problem. Sometimes everything works fine You could say failure is 50% times.

c++
windows
winapi
visual-studio-debugging
winhttp
asked on Stack Overflow Oct 11, 2018 by Vivek Yadav • edited Oct 11, 2018 by Micha Wiedenmann

1 Answer

0

Found the solution for this problem. Actually before this call there was bufferoverflow which was corrupting my heap. Fixing the bufferoverflow solved my problem.

answered on Stack Overflow Oct 23, 2018 by Vivek Yadav

User contributions licensed under CC BY-SA 3.0