Windows error 0x000000CC, 204

Detailed Error Information


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

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.

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
Reserved (X)false
FacilityCode0 (0x000)
DescriptionThe default facility code.[2][3]
Error Code204 (0x00cc)

Possible solutions


Can I use libcurls CURLOPT_WRITEFUNCTION with a C++11 lambda expression?


You actually can do that by casting the lambda function to function pointer. You can first make a typedef to make cast easier.

typedef size_t(*CURL_WRITEFUNCTION_PTR)(void*, size_t, size_t, void*);

Then you use static_cast.

curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, static_cast<CURL_WRITEFUNCTION_PTR>(curl_callback));

Note: In order to convert to C function pointer, you can only use empty captures [].


unknown arm linux kernel image format


ARM Linux kernels are usually self-loading plain binaries, generated from the original ELF by extracting the code+rdata sections from it and appending the "piggy" loader. They're loaded by the bootloader at some place in the memory and just run from there. The piggy loader unpacks/copies the main payload to the final address and jumps to it.

Restoring ELF from the binary might be possible (the final runtime address is usually fixed to 0xC0008000, and you can find out .data/.bss ranges by analyzing boot code), but the symbol table is trickier. Recent kernels don't use ELF symbol table as-is but employ compression to save space. If you can boot the kernel, the easiest way is to read /proc/ksyms or /proc/kallsyms as it will have the symbols in uncompressed format. Otherwise you'd have to find the compressed table in the binary and decompress it manually.

answered on Stack Overflow Feb 11, 2013 by Igor Skochinsky

RStudio crashes when reading mzML file, R terminal doesn't


When running this with a version of R compiled with sanitizers, I see:

> source("msdata.R", echo = TRUE)

> library(mzR)
Loading required package: Rcpp

> library(msdata)

> mzxml <- system.file("threonine/threonine_i2_e35_pH_tree.mzXML",
+                      package = "msdata")

> aa <- openMSfile(mzxml) # this works
ramp.cpp:1197:34: runtime error: index -1 out of bounds for type 'char [513]'
SUMMARY: AddressSanitizer: undefined-behavior ramp.cpp:1197:34 in

> mzml <- system.file("microtofq/MM8.mzML", package = "msdata")

> bb <- openMSfile(mzml) # this crashes R, but only in RStudio

In particular, this bit:

> aa <- openMSfile(mzxml) # this works
ramp.cpp:1197:34: runtime error: index -1 out of bounds for type 'char [513]'
SUMMARY: AddressSanitizer: undefined-behavior ramp.cpp:1197:34 in

implies there may be something going wrong with the openMSfile() function -- it appears to be attempting to read data at an invalid offset. I would file this issue with the mzR maintainers.

> sessionInfo()
R Under development (unstable) (2017-01-17 r72002)
Platform: x86_64-apple-darwin16.3.0 (64-bit)
Running under: macOS Sierra 10.12.2

[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
[1] msdata_0.15.0        mzR_2.9.3            Rcpp_0.12.9
[4] testthat_1.0.2       rmarkdown_1.3        knitr_1.15.1
[7] roxygen2_5.0.1       devtools_1.12.0.9000

loaded via a namespace (and not attached):
 [1] magrittr_1.5        BiocGenerics_0.21.3 pkgload_0.0.0.9000
 [4] R6_2.2.0            stringr_1.1.0       tools_3.4.0
 [7] pkgbuild_0.0.0.9000 parallel_3.4.0      Biobase_2.35.0
[10] withr_1.0.2         htmltools_0.3.5     ProtGenerics_1.7.0
[13] rprojroot_1.2       digest_0.6.11       crayon_1.3.2
[16] codetools_0.2-15    memoise_1.0.0       evaluate_0.10
[19] stringi_1.1.2       compiler_3.4.0      backports_1.0.5

EDIT: Here's the configure call used to build R; the same compiler + flags are used for all built packages as well. (Extracted from R.home("etc/Makeconf"))

# R was configured using the following call
# (not including env. vars and site configuration)
# configure  '--with-blas=-L/usr/local/opt/openblas/lib -lopenblas' '--with-lapack=-L/usr/local/opt/lapack/lib -llapack' '--with-cairo' '--disable-R-framework' '--enable-R-shlib' '--with-readline' '--enable-R-profiling' '--enable-memory-profiling' '--with-valgrind-instrumentation=2' '--without-internal-tzcode' '--prefix=/Users/kevin/r/r-devel-sanitizers' 'PKG_CONFIG_PATH=/opt/X11/lib/pkgconfig'

CC = clang-3.9 -std=gnu99 -fsanitize=address,undefined -fno-omit-frame-pointer -fno-sanitize=float-divide-by-zero
CXX = clang++-3.9 -fsanitize=address,undefined -fno-omit-frame-pointer -fno-sanitize=float-divide-by-zero 

EDIT V2: Given the lldb stack trace, it looks like the culprit may indeed be a clash between Boost versions (the bundled version used by RStudio vs. the version used by mzR). Note that mzR is now inadvertently calling the Boost routines in the rsession executable, when it likely intends to call its own bundled version.

answered on Stack Overflow Jan 19, 2017 by Kevin Ushey • edited Jan 21, 2017 by Kevin Ushey

Can I use libcurls CURLOPT_WRITEFUNCTION with a C++11 lambda expression?


libcurl is plain C library, you need to set a callback that can be called from a such. This means funny C++ things need to be "C'ified" first to work. Like into an old-style function pointer.

This is also addressed in the libcurl FAQ entry "Using C++ non-static functions for callbacks?"

See also: C-style Callbacks in C++11

answered on Stack Overflow Sep 2, 2011 by Daniel Stenberg • edited May 23, 2017 by Community

Application crash due to dereference garbage pointer


Have a look at thread 10:

one of these functions might some issue:

19  TestApplication                          0x00155e90 -[TestApplicationRequestInfoController showScanAlertForErrorType:Barcode:] + 2380
20  TestApplication                          0x00151c48 -[TestApplicationRequestInfoController showAlertForErrorType:Barcode:] + 72
21  TestApplication                          0x001fe090 -[TestApplicationBOPISOrdersScanningController processFirstNonSerialNumberScan:] + 3788
22  TestApplication                          0x0020dd38 -[TestApplicationScanController processScanInfo] + 3512
23  TestApplication                          0x0020cf38 __39-[TestApplicationScanController startScanThread]_block_invoke + 44

Double check them. Or put breakpoints at them and rerun the program to see what happens when the program goes through these functions..

Hope this helps... Just a starter..

Remember there is no random crashing.. These crashes are due to mistakes in the code.

answered on Stack Overflow Apr 4, 2013 by lakesh

Java application crash when uses icepdf library


From the snippet you pasted,its a segmentation fault (ExceptionCode=0xc0000005, writing address 0xe1ecbd40) because function tried to write some contents to the memory address 0xe1ecbd40,which is either protected,or lies in kernel memory region, or inaccessible. This is why it crashed. This segfault is happening in sun AWT library awt.dll. Because eventLoop() should be calling some native function which in turn causing this segfault.So its not a problem with your application,its a crash within class library of JDK. Further analysis of this issue requires debugging of the postmortem logs.You are already on the latest JDK level,so it looks to be new issue within class library library. I think if you can open a ticket with SUN,then they might be able to look into it and can help you.Meanwhile you can try with some older version of JDK,it might be possible that some new code changes in the recent version might be causing this issue,but its just a guess.

answered on Stack Overflow Aug 30, 2010 by Anil Vishnoi

Java application crash when uses icepdf library


There isn't much to go on from the dump but you could try the following system property encase it's Direct3D issue.


answered on Stack Overflow Sep 7, 2010 by pcorless


Leave a comment

(plain text only)


  3. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0