Crash with ntdll.dll as faulting module

[Anonymous]

F360 crashed on me this morning...just opened it up and was about to open a new file and down it went. When I checked windows event viewer, I noticed something that has me a bit concerned...the faulting module was ntdll.dll. This is primarily a concern to me because here at our shop, we have been using Alphacam Essential (2-D) for about 5 years, and it crashes almost every day, and the cause is always ntdll.dll. The fact that this has been an ongoing problem with multiple users, and even though we pay BIG bucks for the program AND THE SUPPORT PACKAGE, their programmers can't seem to figure out what's wrong. That led me to searching for a replacement program...enter F360.

So, now F360 crashes and has the same faulting module. The easy assumption here is that the one thing in common with these 2 situations is my computer, and that must be the cause. Very well may be...or, more concisely, Windows' ntdll.dll file. That being said, I've made sure my computer is fully up-to-date, ran DISM just to make sure Windows wasn't corrupted at all, etc... 

I did find a post in your forum from 2016(ish) where someone else had a crash caused by the same ntdll.dll, but it wasn't concluded with a resolution, and so far, I can't find anything helpful online with helping decipher what is going on with ntdll.dll in general.

Anyway, I've attached both the F360 diagnostic folder and my event viewer log folder. Hopefully something in there will be of use in finding the cause of these crashes. I would LOVE to fully switch from ACam to F360, but if I'm going to have the same issues, it's kind of a moot point. Any input would be greatly appreciated. Thank you!

[karina.harper]

Hi @Anonymous 

A disclaimer here - I am not an IT expert and am not super versed in general computer hardware issues, but I did find this step-by-step list to go through to diagnose the issues. Since this has happened with mutliple programs on the same computer, I would say starting here would be a good idea. Particularly step 13 which is the most drastic, performing a full reinstall of Windows.

Hope this helps,

Karina