UCCNC shuts down unexpectedly

[JAZZCNC]

I don't know if the above would help you, but I suspect the issue is not UCCNC, but your installation, or Windows trying to access the server to get updates. Another question is your Windows version. UCCNC is not very demanding on the computer performance, so your PC is not too weak. After all, it can happily run on a 20+ years old PC with W95 or XP also, so if changing to your brand new Dell would help, it is probably because the differences in the installation, not because of the better PC.

Completely agree with A_Camera on this, it will 99% be a windows issue and not UCCNC or the controller. I have installed over 30 AXBB-E controllers since Xmas and most are running on Refurbished Dell PC's which are low spec compared to your i7 laptop and running on Win7, 8, and 10 without any issues if using V1.12111.
I have had a couple of issues with the development versions but these mostly revolved around low memory, it seems the new Development versions are more memory intense so if memory is on the low side, which the Refurbs tend to be then occasionally it would crash.

I'm not a Windows OS guru so follow the guy's suggestions and I'm sure you'll find the cause.

[Kitwn]

Completely agree with A_Camera on this, it will 99% be a windows issue and not UCCNC or the controller. I have installed over 30 AXBB-E controllers since Xmas and most are running on Refurbished Dell PC's which are low spec compared to your i7 laptop and running on Win7, 8, and 10 without any issues if using V1.12111.
I have had a couple of issues with the development versions but these mostly revolved around low memory, it seems the new Development versions are more memory intense so if memory is on the low side, which the Refurbs tend to be then occasionally it would crash.

I'm not a Windows OS guru so follow the guy's suggestions and I'm sure you'll find the cause.

I am using V1.12111 but as you will have sen above, Andy's pointing me to Event Viewer in W10 has thrown up some evidence. As a simple first option I'm gong to try re-loading UCCNC itself (after ensuring the configuration is saved!) in case there's been a corruption of the .dll file mentioned in the error report. If the problem shows up again at least I know where to find the error log which I can send to Balazs if necessary.


EDIT:
Having done some research on the ntdll.dll file blamed for the problem, this turns out to be a Windows issue as suggested. This little file has been part of every version of Windows since NT (hence the name) and it's corruption is a know cause of crashes of all sorts.

Thanks to everybody for the help.

Kit

[AndyUK]

Having done some research on the ntdll.dll file blamed for the problem, this turns out to be a Windows issue as suggested. This little file has been part of every version of Windows since NT (hence the name) and it's corruption is a know cause of crashes of all sorts.

Thanks to everybody for the help.

Kit

Hi Kit,

Unfortunately the ntdll.dll error is quite a common one, but common because it can have a wide array of causes. It's basically the Windows kernel is freaking out and killing UCCNC. The status code it's given (0xc000374) is telling us that the reason is memory heap corruption - i.e. UCCNC is trying to use a bit of memory that it thinks should belong to it but Windows thinks otherwise. If you can copy paste / screenshot more of the details that screen shows it might be helpful, also slightly worryingly you have a lot of other warnings there which could give some clues.

This can be caused by a new update introducing a bug, a new bit of software that is being evil and corrupting the memory, a bad device driver (or a device misbehaving), or the PCs RAM is starting to fail.

I would try the following in this order:
Swap out the RAM for fresh / alternative sticks if you have them handy. If not, but slightly less conclusive, run a memory test tool like memtest86
See if disabling that plugin helps, could be the Xbox controller device / driver is faulting.
Swap to another ethernet card if possible to rule out the ethernet driver or NIC dying.
Try the windows SFC repair tool - long shot but if it works then easier than reinstalling everything.
Fresh reinstall of Windows, preferably on a new SSD (they're a lot cheaper than they were!)

Hope we get to the bottom of it soon...