Windows 10: skype crashes, event viewer flags ntdll.dll

so...the last few days I've been dealing with skype crashing every few days, and when I check the event viewer logs, it flags on ntdll.dll.

below is attached an image of the last instance of this occurring.






I ran check disk, I ran the system error checking, I just ran the scannow, and every single built in windows utility says she's go flight.

I doubled that up by reinstalling the program.

:)

 

Legacy application not working on windows 10 RS2/Windows 10

Hi All,

I have an application that is working fine on other Windows platforms (Windows 7 and Windows 8), but the same is not working on Windows 10. I checked the event logs on Windows 10 RS2 and noticed that one of our application processes is being terminated and
indicates that the process is terminated when accessing ntdll.dll.

Error Details from event viewer:



Event logs

Faulting application name:<application.exe>, version: 0.0.0.0, time stamp: 0x59159deb

Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xb79b6ddb

Exception code: 0xc0000005

Fault offset: 0x0000000000011636

Faulting process id: 0x13fc

Faulting application start time: 0x01d2cd6a272ae2c0

Faulting application path: <application_path>

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: fc609e89-603a-4bc3-a37f-9e680b842356

Faulting package full name:

Faulting package-relative application ID:

I didn't find the crash dumps of the application's process but I took the dump forcibly. From the crash dumps, it looks like our application is waiting for response from ntdll.dll.



Questions:

1) In what scenarios does ntdll.dll not respond ?

2) Is there any way to get more information from event viewer logs to find the root cause for termination of our application?

 

Windows Explorer crash When Moving or opening Files

I have been fighting the same problem for months with Windows 10. Explorer crashes when opening or moving files, multiple File Explorer windows open for certain folders, etc.. Even after doing a clean install the problem reappeared. Event Viewer shows the
faulting module as either ntdll.dll or windows.storage.dll.

Any suggestions would be appreciated!

Tim