Windows error 0x0000016E, 366

Detailed Error Information

CLOUD_FILE_PROPERTY_BLOB_CHECKSUM_MISMATCH[1]

MessageThe Cloud File property blob is possibly corrupt. The on-disk checksum does not match the computed checksum.
Declared inwinerror.h

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

ERESOURCE_INVALID_RELEASE[2]

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

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 Code366 (0x016e)

Possible solutions

0

ASM help - assembly language binary bomb phase_6

assembly

Note that there are many versions of the bomb, so the fact that some people told you the answer was 3 5 9 7 6 4 1 8 2 0 doesn't have much to do with the facts. As you can see, phase6 invokes a single strtol on line +29, so only a single number is expected as input. That number is then stored into node0 and fun6 is invoked with the node's address, which will eventually return with a node pointer that is checked for some condition. Try to work out what fun6 is doing and what the condition is.

answered on Stack Overflow Mar 5, 2014 by Jester

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