Windows error 0x000000BE, 190

Detailed Error Information

INVALID_MODULETYPE[1]

MessageThe operating system cannot run %1.
Declared inwinerror.h

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY[2]

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

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 Code190 (0x00be)

Questions

0votes
1answer

stack parameters read from wrong memory address in the stack

I am trying to debug a process core dump on ARM architecture. It is a telecom stack software written in C. The process is single-threaded. Some debugging through gdb indicated that the stack parameters (local variables or function arguments) are being read from a memory location that is at a [...] read more
c
gdb
stack
arm
corruption
0votes
1answer

Send socket result 0x000000be

What means a result of 0x000000be in send command: iResult = send( ConnectSocket, dataToSend, (int) strlen(dataToSend), 0 ); I didn't found this return code here: http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx Any ideas? Thx read more
c++
winapi
sockets
send

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