Home/ Questions/Q 8052657
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T07:36:06+00:00

Our application crashes with the following error. =========================================================== VERIFIER STOP 00000003: pid 0x2E54: multithreaded

  • 0

Our application crashes with the following error. 

===========================================================
VERIFIER STOP 00000003: pid 0x2E54: multithreaded access in HEAP_NO_SERIALIZE heap
       00161000 : Heap handle
       00001444 : Thread owning heap lock
       00003188 : Current thread trying to acquire the heap lock
       00000000 :
===========================================================

We have enabled a full page heap for the application. The application crashes at a random location. Often the crash location is the inner portions of STL. In all cases, the callstack seems to be corrupted.

The application uses a list of libraries and DLL files. All DLL files and libraries are built with the multithreaded DLL library (command line option /MD) .

One of the libraries is using the HeapAlloc method for allocating memory in heap.

what techniques should I use to identify the crash?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You appear to have already done it, by running your program under WinDbg.

    A quick Google search on the interesting bits of the error message found the MSDN article Multithreaded Access In A HEAP_NO_SERIALIZE Heap, which suggests to me that some module you are loading is linked against the single-threadded CRT.

    I would examine each part of your project, and all the project settings, very carefully to verify that everything is really using the MD libraries. Something may be statically linked.

    • 0