ntdll.pdb not loaded error

[Carlygao]

Hi,

I have some memory issues before, so I enabled heap and check stack. Now I think I deactivated these features. However, I always have the error "ntdll.pdb not loaded" error. A snapshot is included in this message. I tried to check the two boxes, but didn't solve the problem. It seems I messed my VS2019 setting.

If I switched to run the code in release mode, it has no error.

Thanks.

Carly

[jimdempseyatthecove]

This indicates that the Microsoft file (libroutine) ntdll.dll through an exception and you were debugging your program. The debugger would then search for the .pdb file for ntdll.dll ... which is not distributed by Microsoft.

If you perform a google search for "ntdll.dll" you will find several links regarding failures within ntdll.dll together with possible solutions.

Jim Dempsey

[Steve_Lionel]

This is not an "error" - as Jim explains, it is telling you that it doesn't have debugging information for ntdll.dll. You can ignore that.

[Carlygao]

Hi Steve,

How to ignore it? The running was stuck there and no more process.

I also googled "ntdll.dll". But I did not find any solution for VS2019. This website (https://www.lifewire.com/how-to-fix-ntdll-dll-errors-2624474) did not provide any reasonable suggestion except reinstall everything. 

Thanks.

Carly

[AlHill]

@Carlygao Your link is broken.

Doc (not an Intel employee or contractor)
[Maybe Windows 12 will be better]

[jimdempseyatthecove · Accepted solution]

The "Standard Operating Procedure (SOP)" in this situation is to use the Call Stack window, and scroll down (look at higher stack levels) to locate the line in your closest source to the .dll and then check if something odd/wrong is with the call.

I suggest you modify your search to narrow the results to microsoft.com

    ntdll.dll crash site:microsoft.com

The Lifewire site does not necessarily contain all the potential solutions.

Did you try: https://answers.microsoft.com/en-us/windows/forum/all/app-crash-with-ntdlldll/9aa59f80-99a1-4f3c-b2f0-7eb72df05b2a

Also check stackoverflow.com: https://stackoverflow.com/questions/53727265/unexplained-crashes-related-to-ntdll-dll

Your screenshot did not show the exception code (possibly the console window did, or there is a hidden dialog box). The stackoverflow page indicates an error: 0xc0000374 STATUS_HEAP_CORRUPTION could be the source for error. Your cause may be different.

Jim Dempsey

[Carlygao]

If I go to the output window, it also complains the following heap issue after a bunch of exception throws.

HEAP[bsam20_2022_09_30_9b502dd.exe]: Invalid address specified to RtlValidateHeap( 0000017AF6940000, 000011A6F6F22A80 )  

All the messages in the output window:

'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'D:\Zhenjia\BSAM20_fix\bsam20\build\Debug\bsam20_2022_09_30_9b502dd.exe'. Symbols loaded.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\oneAPI\compiler\2022.1.0\windows\redist\intel64_win\compiler\libiomp5md.dll'. Symbols loaded.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\oneAPI\mkl\2022.1.0\redist\intel64\mkl_intel_thread.2.dll'. Module was built without symbols.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\oneAPI\mkl\2022.1.0\redist\intel64\mkl_core.2.dll'. Module was built without symbols.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbase.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\oneAPI\compiler\2022.1.0\windows\redist\intel64_win\compiler\libifcoremdd.dll'. Module was built without symbols.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\oneAPI\compiler\2022.1.0\windows\redist\intel64_win\compiler\libifportmd.dll'. Module was built without symbols.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\oneAPI\mpi\2021.6.0\bin\release\impi.dll'. Symbols loaded.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\imagehlp.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64\clang_rt.asan_dbg_dynamic-x86_64.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\win32u.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\gdi32.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\ws2_32.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\gdi32full.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\oneAPI\compiler\2022.1.0\windows\redist\intel64_win\compiler\libmmdd.dll'. Symbols loaded.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\msvcp_win.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\IPHLPAPI.DLL'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\msvcp140d.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\vcruntime140.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\vcruntime140d.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Program Files (x86)\Intel\oneAPI\compiler\2022.1.0\windows\redist\intel64_win\compiler\libmmd.dll'. Symbols loaded.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\vcruntime140_1d.dll'.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbased.dll'.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000117A265FA762.
Exception thrown at 0x00007FF9121947B0 (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x000001AA55C284D3.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000017B06EFC006.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x000001AA55BFEC27.
Exception thrown at 0x00007FF9121947B0 (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x000001AA55C29473.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000117A19219A79.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000117A197463C7.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000117A260A9239.
Exception thrown at 0x00007FF9121947B0 (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000117A262B8A90.
Exception thrown at 0x00007FF9121947B0 (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000117A26605000.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x000001AA55BFA0EE.
Exception thrown at 0x00007FF9121800DE (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x000011798A76A238.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000117A265F9850.
'bsam20_2022_09_30_9b502dd.exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'.
Exception thrown at 0x00007FF91217F5A7 (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x000001AA55C2E504.
Exception thrown at 0x00007FF91217F5A7 (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x000001AA55C2F71A.
Exception thrown at 0x00007FF91217F5A7 (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x000001AA55C2ADF6.
Exception thrown at 0x00007FF9121947B0 (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000117A262BD13C.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x000001AA55BFF602.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000117A261AFF83.
Exception thrown at 0x00007FF91218006F (clang_rt.asan_dbg_dynamic-x86_64.dll) in bsam20_2022_09_30_9b502dd.exe: 0xE0736171: Access violation reading location 0x0000117A194A02C5.
HEAP[bsam20_2022_09_30_9b502dd.exe]: Invalid address specified to RtlValidateHeap( 0000017AF6940000, 000011A6F6F22A80 )
bsam20_2022_09_30_9b502dd.exe has triggered a breakpoint.

[jimdempseyatthecove]

This suggests you check your code for something that could corrupt the heap.

You should be able to use the debug heap (https://learn.microsoft.com/en-us/visualstudio/debugger/crt-debug-heap-details?view=vs-2022) and place calls to _CrtCheckMemory (use C interoperability feature) in selected places of your code (start with entry points of your code in the call stack producing the error. Then pop up one level, look for something wrong, if unsuccessful, insert additional calls to _CrtCheckMemory to try to locate the source of the problem.

Jim Dempsey