Windows 10: Computer Crash related to ntdll.sys

Hey everyone - once in a while on startup my system BSODs, and today I decided I wanted to figure out why. Thank you for any help that you're able to provide!

Here is the link to the mini-dump file zipped: https://www.dropbox.com/s/iw4if5e495iuyov/111520-8250-01.zip?dl=0


System Information local



Computer name: DESKTOP-QTION60
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\WINDOWS
Hardware: MS-7C02, Micro-Star International Co., Ltd, B450 TOMAHAWK MAX MS-7C02
CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor AMD586, level: 23
12 logical processors, active mask: 4095
RAM: 17126649856 bytes total





Crash Dump Analysis



Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 11/15/2020 12:17:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111520-8250-01.dmp
This was probably caused by the following module: ntkrnlmp.exe nt!KeBugCheckEx+0x0
Bugcheck code: 0x1A 0x41201, 0xFFFFDF00C8B07328, 0x8000002277642867, 0xFFFFB587278F30A0
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 11/15/2020 12:17:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntdll.sys ntdll!NtQueryVirtualMemory+0x14
Bugcheck code: 0x1A 0x41201, 0xFFFFDF00C8B07328, 0x8000002277642867, 0xFFFFB587278F30A0
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .
Google query: ntdll.sys MEMORY_MANAGEMENT

:)

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

Explorer.exe crashes whenever I try to open a network computer

I have a Windows 10 computer that is experiencing some unusual problems accessing networked computers and devices.

If I go to "This PC" (My Computer) and expand the "Network" section in the left-hand navigation bar, I can see all of the computers on our network. However, if I double click on the icon for one of those networked computers, explorer.exe will crash, I temporarily lose the start bar and then moments later explorer.exe restarts.

I captured a dump of the crash and this is the stack:

It would appear that Windows_UI_Xaml is causing the crash somehow, but unfortunately that DLL seems to be a pretty central part of Windows 10. Googling for issues with the DLL and crashes related to networked computers has turned up nothing.

For what it's worth, this computer also cannot find any of the shared networked printers on my network and I've been unable to get it to join the "Homegroup" to share devices. I do not have these problems for other computers on the network.

Any ideas on the root cause of the crashing? Any suggestions for additional troubleshooting steps?

 

NTDLL error persistent

Hi Antoniyap,

Thank you for posting here in the Community forum. We would like to inquire if the NTDLL error issue that you posted here has already been resolved. If not, kindly post here the troubleshooting steps that you have taken in order to avoid repetition.

We look forward to your next post.

Regards.