Windows error 0x00000154, 340

Detailed Error Information

INVALID_KERNEL_INFO_VERSION[1]

MessageThe supplied kernel information version is invalid.
Declared inwinerror.h

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

UNEXPECTED_STORE_EXCEPTION[2]

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

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 Code340 (0x0154)

Possible solutions

5

unknown arm linux kernel image format

linux
kernel
arm

ARM Linux kernels are usually self-loading plain binaries, generated from the original ELF by extracting the code+rdata sections from it and appending the "piggy" loader. They're loaded by the bootloader at some place in the memory and just run from there. The piggy loader unpacks/copies the main payload to the final address and jumps to it.

Restoring ELF from the binary might be possible (the final runtime address is usually fixed to 0xC0008000, and you can find out .data/.bss ranges by analyzing boot code), but the symbol table is trickier. Recent kernels don't use ELF symbol table as-is but employ compression to save space. If you can boot the kernel, the easiest way is to read /proc/ksyms or /proc/kallsyms as it will have the symbols in uncompressed format. Otherwise you'd have to find the compressed table in the binary and decompress it manually.

answered on Stack Overflow Feb 11, 2013 by Igor Skochinsky
2

g++ symbol versioning. Set it to GCC_3.0 using version 4 of g++

g++
jni

No. They are mean to be incompatible. You have to use a older version of g++.

Also, the different is at libstdc++.so.5 and libstdc++.so.6.

answered on Stack Overflow Jun 29, 2009 by J-16 SDiZ
0

apps doesn't work after update opencv manager

android
eclipse
opencv
  • I have the same problem, I've just updated OpenCV manager and my application stoped working (Freezes) when tyring to initialize the opencv library.

the temproray solution is to fall back to older version, I got OpenCV manager 2.0 from the following website

http://android.brothersoft.com/opencv_manager-212868-download.html

try to download it and hope that solves your problem.

answered on Stack Overflow Jul 4, 2013 by moh.sukhni
0

Opendaylight Can't Connect to HP Aruba SDN Switch

sdn
opendaylight

someone else recently made a post about HP switches not connecting to ODL, but I cannot find that post to reference?

I would check the switch logs. the packet capture seems to indicate there is some communication between the switch and controller:6633.

you can also look for clues in OpenDaylight's karaf.log file

at the end of the day, since your other switches are connecting fine you probably will have to find HP switch support, more-so that OpenDaylight support.

answered on Stack Overflow Apr 12, 2018 by jamo

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