Windows error 0x0000023A, 570

Detailed Error Information

NET_OPEN_FAILED[1]

MessageThe NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows Lan Manager Redirector to use in its internal error mapping routines.
Declared inwinerror.h

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

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 Code570 (0x023a)

Questions

2votes
0answers

mspgcc-size ROM/RAM usage in percentage

With mspgcc-size I can get an output like this: text data bss dec hex 13072 236 65296 78604 1330c We know that: Flash = data + text RAM = data + bss How can I extract the size of ROM/RAM from the selected -mmcu=msp430g2553 with the toolchain? e.g. ROM: 8192 [...] read more
microcontroller
avr-gcc
toolchain
2votes
1answer

How to diagnose a corrupted suffix pattern in a mixed managed/unmanaged x32 .NET application

I've got a .NET application that pinvokes several libraries, all 32 bit (the application is 32 bit as well). I recently started getting crash bugs that occurred when the GC started freeing memory, and when I attached I saw that it was an access violation. After some web searches, I [...] read more
c#
pinvoke
windbg
unmanaged
2votes
1answer

Page Heap doesn't record useful stack infomation?

I'm trying to test a crash scenario (in an isolated test-app) with normal page heap (not full). I have set up the flags with gflags /p /enable Test.exe and I'm overwriting an integer buffer by one element ... const size_t s = 100; vector<int> v1(s, 0); int* v1_base = &v1[0]; [...] read more
debugging
visual-c++
windbg
gflags
pageheap
1vote
2answers

Memory leak due to marshalling managed delegate?

I seem to be experiencing a memory leak in some code that's been in production for a while now (I see the Process\Private Bytes counter rising over time in PerfMon for my process). Note the code works without issue other than the leaking. The code that seems to be responsible [...] read more
c#
c++
0votes
1answer

The !address windbg command says that heap address is 'REGionUsageIsVAD' even though it was allocated using HeapAlloc

My heap buffer of interest was allocated as follows: 0:047> !heap -p -a 1d7cd1f0 address 1d7cd1f0 found in _DPH_HEAP_ROOT @ 5251000 in busy allocation ( DPH_HEAP_BLOCK: UserAddr UserSize - VirtAddr VirtSize) 1cf8f5b0: 1d7cc008 3ff8 - 1d7cb000 6000 68448e89 verifier!AVrfDebugPageHeapAllocate+0x00000229 76e465ee ntdll!RtlDebugAllocateHeap+0x00000030 76e0a793 ntdll!RtlpAllocateHeap+0x000000c4 76dd5dd0 ntdll!RtlAllocateHeap+0x0000023a 000ca342 TEST+0x0002a342 000be639 TEST+0x0001e639 As [...] read more
debugging
windbg

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