Windows error 0x0000014F, 335

Detailed Error Information

COMPRESSED_FILE_NOT_SUPPORTED[1]

MessageAn operation is not supported on a compressed file.
Declared inwinerror.h

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

PDC_WATCHDOG_TIMEOUT[2]

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

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 Code335 (0x014f)

Possible solutions

1

.NET application handle leak, how to locate the source?

windows
performance
memory-leaks
windbg

WinDbg isn't the ideal tool for memory leaks, especially not without preparation in advance.

There's a GFlags option (+ust) which can be enabled for a process to record the stack trace for handle allocations. If you don't have this flag enabled, you'll probably not get more info out of your dump. If you have it, use !htrace to see the stack.

You can also try UMDH (user mode dump heap), which is a free tool. Or get something like memory validator which has certainly a better usability, so it might pay off in the long run.

answered on Stack Overflow Dec 21, 2016 by Thomas Weller

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