Hello, and welcome to Sysnative!
Thank you very much for uploading those logs in your first post, saves a lot of time :)
Unfortunately, there's an issue. One of my jobs on any Windows Update thread is to consider the root cause. And unfortunately, I don't think yours was just bad luck. In actual fact, I think it is caused by hardware failure, specifically bad RAM. I know that this is probably the last thing you want to hear right now, but it unfortunately looks that way. Please follow these instructions to test this assertion of mine:
Test RAM With Memtest86+
With hardware failure, it's always better to know for sure than to not know. RAM is very cheap these days, and is usually financially viable to replace, and I'll talk you through all of your options if it comes to it. But to start off with, we need to know whether it's actually the RAM or not, or whether it's not hardware at all. I will temporarily put the fix on hold until we get to the bottom of any hardware problems. Otherwise new problems will start popping up faster than I can fix them. Once it's all over, I'll make a totally new assessment.
However, if in the last couple of months you have already found and removed a failed RAM stick, then of course the above doesn't apply :)
Richard
