UCCNC shuts down unexpectedly

[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...