Windows error 0x000000E4, 228

Detailed Error Information

WORKER_INVALID[1]

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

HRESULT analysis[2]

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[2][3]
DescriptionThe default facility code.[2][3]
Error Code228 (0x00e4)

Questions

1vote
0answers

C - Get File Bytes as Unsigned Int

I need the bytes of a BIN file converted to a unsigned int, in this format (JavaScript): p.write4(shellcode.add32(0x00000000), 0x00000be9); p.write4(shellcode.add32(0x00000004), 0x90909000); p.write4(shellcode.add32(0x00000008), 0x90909090); p.write4(shellcode.add32(0x0000000c), 0x90909090); p.write4(shellcode.add32(0x00000010), 0x0082b955); p.write4(shellcode.add32(0x00000014), 0x8948c000); p.write4(shellcode.add32(0x00000018), 0x415741e5); p.write4(shellcode.add32(0x0000001c), 0x41554156); p.write4(shellcode.add32(0x00000020), 0x83485354); p.write4(shellcode.add32(0x00000024), 0x320f18ec); p.write4(shellcode.add32(0x00000028), 0x89d58949); p.write4(shellcode.add32(0x0000002c), 0x64b948c0); p.write4(shellcode.add32(0x00000030), 0x77737069); p.write4(shellcode.add32(0x00000034), 0x49000000); p.write4(shellcode.add32(0x00000038), 0x4120e5c1); p.write4(shellcode.add32(0x0000003c), 0x000200bc); p.write4(shellcode.add32(0x00000040), [...] read more
c
0votes
2answers

How to turn on LED on stm32 board using assembly language that generated by llvm?

My English skill is poor because I'm not a native English speaker. Please understand. I compiled some test code that operating alright in IAR with LLVM infra but the generated code was not operated on my test board. Detail are as follows. TEST GOAL I want to see operating the [...] read more
makefile
llvm
cortex-m3
segger-jlink
stm32l152
0votes
0answers

Alamofire 5.2.2 TestFlight watchOS build crashes on Apple Watch Series 3 devices (32-bit) (Bitcode related?)

I have a WatchOS Application on TestFlight that is crashing on startup on Apple Watch Series 3 devices (32-bit). It works flawlessly on Simulators (Xcode 11.7) and Apple Watch Series 4. I am using Alamofire 5.2.2 with Swift Package Manager. Latest Xcode (version 11.7). The device is Apple Watch Series [...] read more
ios
swift
alamofire
watchos
bitcode
0votes
0answers

Why does address range 0xC0000000 ~ 0xFFFFFFFF always give 0x00 or 0xFF after switching to protected mode before enabling paging?

I'm making a custom boot loader, and currently in the stage of enabling paging after switching to protected mode. I tried to check all memory range is usable from 0x00000000 to 0xFFFFFFFF to make sure my kernel has full control over memories. Checking is done by copying value to the [...] read more
x86
nasm
memory-address
bootloader
osdev

Comments

Leave a comment

(plain text only)

Sources

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

User contributions licensed under CC BY-SA 3.0