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: flags: none; facility: 0 (FACILITY_NULL); error: 190 (more)

Questions

3votes
1answer

grub doesn't seem to load my kernel correctly

I use grub to load my kernel. Although I specified .=0x100 0000 in the linker script, I can only find a valid MultiBoot2 header at 0x10 0000. After comparing them one by one, I found that it is not my kernel. And use gdb to debug Found that qemu's RIP [...] read more
assembly
gcc
osdev
grub
multiboot
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