Time for some MemTest burn-in.
mnem
not mnemTest... that's something else altogether. ![Evil >:D](https://www.eevblog.com/forum/Smileys/default/xevil.gif.pagespeed.ic.tdrs7Uj5gu.png)
Actually it seems it wasn't what I expected although the hint you gave about rolling back W10 updates got me tinking............
After much shagging around in which it got close to Bob Pease flying lessons a couple of times I stopped the boot in Bios and let everything cook for a while yet after some time it went into reboots again
![Blah :blah:](https://www.eevblog.com/forum/Smileys/default/blah.gif.pagespeed.ce.iJS9qlFEPg.gif)
so ripped the Data drive out and took it to our family PC to ensure the last days work was saved and safe
![Phew :phew:](https://www.eevblog.com/forum/Smileys/default/phew.gif.pagespeed.ce.n2uLOVFYMP.gif)
and then threw it all back together after eraser and IPA work on the RAM pads and let it cook while stopped in Bios where it now ran for an hour without issue.
![Confused :-//](https://www.eevblog.com/forum/Smileys/default/confused0024.gif.pagespeed.ce.5xOqKkq0Co.gif)
Then let it full boot into W10 and another hours cooking where it seem just fine.
![Phew :phew:](https://www.eevblog.com/forum/Smileys/default/phew.gif.pagespeed.ce.n2uLOVFYMP.gif)
So now it's back in its normal spot allowing me to type this reply.
![Smiley :)](https://www.eevblog.com/forum/Smileys/default/xsmiley.gif.pagespeed.ic.R8GFI-pF6f.png)
The only thing I can put this down to is last evening when putting it into Sleep mode noticed the HD light was showing some activity which has never worried me or it for that matter before but it may have been working on one of them silent W10 updates and sending it to sleep in the middle of it may have forked something.
![Confused :-//](https://www.eevblog.com/forum/Smileys/default/confused0024.gif.pagespeed.ce.5xOqKkq0Co.gif)
Anyways my head hurts now from all these carry on's not to mention all the oogling at new $ PC's and $ PC bits and $ bobs while waiting for GB backups to finish.