Windows error 0x00000234, 564

Detailed Error Information

INVALID_LDT_DESCRIPTOR[1]

MessageIndicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors.
Declared inwinerror.h

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

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][1]
DescriptionThe default facility code.[2][1]
Error Code564 (0x0234)

Questions

3votes
5answers

Efficient way of determining minimum field size required to store variances in user input

Sorry about the clumsy title; I couldn't find a bit way of expressing what I'm trying to do. I am getting an input from the user of multiple 32-bit integers. For example, the user may enter the following values (showing in hex for ease of explanation): 0x00001234 0x00005678 0x0000abcd In [...] read more
c++
bit-manipulation
0votes
0answers

critical section blocking (deadlock?)

In the critical section of a multithreaded thread, it is not locked, but it is blocking. It occurs frequently in 2 ~ 3 times in 10 and it is only occurred in debug build so far. I have tested about 40,000 times in release build, but it is not reported [...] read more
multithreading
visual-c++
deadlock

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0