How to fix C:\WINDOWS\SYSTEM32\ntdll.dll errors

John Robak 0 Reputation points
2024-04-09T19:04:11.49+00:00

WINDOWS\SYSTEM32\ntdll.dll errors

We have Windows 10 on all 30 workstations which are accessed through a VPN and Remote Desktop Connection From our outside locations When in Sage Business Works application and have a high volume of activity at 1 location the workstations freeze up Looking at the event log, we are getting Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll I have done SFC /scannow and removed the last windows update to this file and am still getting errors. I believe it is not the application because it is not happening on other machines and only happens when there is a lot of activity in the application out of only 1 location I think it is a firewall issue but vendor says everything is configured correctly We have a static IP at the location Can anyone enlighten me on the problem and possible fix - Thanks

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,649 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,248 questions
Windows Server Printing
Windows Server Printing
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Printing: Printer centralized deployment and management, scan and fax resources management, and document services
641 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Michael Taylor 48,486 Reputation points
    2024-04-09T19:36:43.89+00:00

    It is unlikely ntdll.dll. However that module is often in the callstack of errors because it is heavily used. Get the entire callstack for the crash. This will tell you what was going on at the time. Also, we have no visibility into what you're seeing so what is the actual error message involved? The more information you provide the better.

    If it were a single machine then I'd lean toward a bad disk or memory. But if it is several then either network or something with the app. Without any error information it is hard to say.

    If you can get a crash dump then that would be ideal. If the app crashes then Windows will generate one temporarily for you. If the app is hanging then you could use Process Explorer to generate a crash dump of the running process while it is hung.

    0 comments