Windows error 0x000000A4, 164

Detailed Error Information

MAX_THRDS_REACHED[1]

MessageNo more threads can be created in the system.
Declared inwinerror.h

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

CNSS_FILE_SYSTEM_FILTER[2]

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

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 Code164 (0x00a4)

Possible solutions

4

fputws to stderr crashes app

c
visual-studio-2012

I finally managed to google the issue, but it wasn't mentioned on SO before, so the link is following:

http://connect.microsoft.com/VisualStudio/feedback/details/772585/fputws-yields-access-violation

VS2012update1 fixes the problem. msvcr110d.dll version is 11.00.51106.1.

Another workaround is to use fputs("", stderr); before using the fwputs, to initialize the IO streams properly.

answered on Stack Overflow Sep 2, 2013 by nothrow • edited Sep 2, 2013 by nothrow
3

uiwebview webthread crashing

uiwebview
ios6

I fixed the bug, I was sending javascript logs to cocoa like this, I fixed those crashes by removing this.

Actually, that's not necessary anymore for iOS 6 cause now it's possible to debug javascript using MAC OX safari =)

answered on Stack Overflow Oct 5, 2012 by Filipe Roberto • edited May 23, 2017 by Community
0

How to load a stacktrace into Visual Studio 2013 for offline debugging?

windows
debugging
visual-c++
visual-studio-2013
visual-studio-debugging

You should see a crashdump somewhere, a .dmp file. You can export that through sysinternals PrcessExplorer, not sureif that's possible with the default task manager, but that's of course before the crash. I unfortunately don't know anymore how to force a process to generate a .dmp file on crash..

But once you have the .dmp file, you can open it in VS (I think since 2010, maybe 2012). There are two kinds of dumps, a minidump (basically just including the point of the execution at that point) which is usually < 1 MB, and a "full dump", which incorporates the whole working set of the process afair, which can easily be hundreds of megs. The minidump usually is enough to get started.

Sorry for the incomplete answer, but maybe it gets you on the right track (no time to investigate on my own right now).

answered on Stack Overflow Nov 16, 2014 by hko

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