System Error: E105 00000000 8007045D (Xbox One - Scorpio Edition)

I received an Xbox One Scorpio Edition recently, up appeared this message.

I was going through the service replacement system online and the system was out of warranty... Fine, i'll pay to have it fixed. Looking at the back of the system and the black tag over the screw wasn't there, looked in the box and found it loose in the
box. Well.... since it's not on the back of the box Microsoft won't fix the system...

So... i did what everyone wants to do but is afraid to do so to avoid voiding their warranty... but since mine is out of warranty there is no choice but to open it up.

I cloned the original HDD onto another brand new Seagate, same model number as the original... booted the system up and seemed fine for a few minutes and then bam, there we go error. Ok, so does the error follow the HDD contents? i reformatted the disk with
a low level format, set it back up the same as the original, and put my profile back on, and played the game off my USB HDD. A while later and..... BAM... Error.... ok, the game wasn't even on the HDD, so is it a game save issue on the internal HDD? i tried
another game... and BAM same error. I moved the game from the external HDD to the internal HDD, it took a while, but started playing it, and it took a while longer, but once again BAM... error.

I opened it back up again, i bought an SSD and installed that. Set it up the same as before, this time it lasted a lot longer before i saw the issue but it still occurred E105... So 2 brand new Hard Drives, one that is the same make/model as the original
and another top shelf SSD.

Since the SSD lasted longer the thought was is it a thermal issue since it takes some time for it to occur? I took it apart again and removed the heatsink and fan, and found that there was barely any thermal paste on the CPU. When i say barely any... i mean
there was plenty around the processor edges, however not much on the processor itself... that may explain the fans erattic spinup/down that i hear while playing some intensive games. i laid down new thermal paste and replaced all the thermal pads on the DDR
with the same green thermal pads making sure that they cover all the chips perfectly. Cleaned out any dust from the heatsink. The game lasts a little longer, the next time testing it, this time it lasted a good few hours... but then BAM - Error 105. (Playing
less intensive games doesn't seem to create this issue.)

So... attempting to "Restart this Xbox" causes it to immediately come back up with the same screen, turning it off and back on, same screen. Turning it off and leaving it 5 minutes and then turning it back on and it's working again.

The issue seems related to the thermal temperature of the unit rather than the HDD. ( i have discounted the HDD and Processor and RAM at this point.)

So where is the issue?

I'd love it if Microsoft would give a clear answer on this, as i'm not the first with this issue, and if there's a hardware fault inherent in the design of the Xbox i'd sure like to hear about it. I'm not expecting a replacement unit, (Although that would
be wonderful). I'll be continuing to go over the hardware in an attempt to work out what's going on.

It says "To play, you'll need to delete and sync them again. To do this blah blah blah.... Clear local saved games. and can be re-downloaded from the cloud"... after a reset... If you don't do that, turn the system off and leave it a few minutes and then
reboot the system, then after it loads up the game saves still appear to be fine. Most likely because when the issue occurs it stops writing the game saves to the HDD and therefore protects the content... but then why does it say they're corrupt?

I'll be checking the RAM again this weekend and placing some probes within the unit and will see if i can track down what's going on, but the "corruption of the game save" doesn't appear to be corruption of the game save at all, and seems more likely that
it's memory corruption within the Samsung DDR exacerbated by thermal temperatures that should be within acceptable parameters that is causing the issue.

Can someone from Xbox can please comment

I've been a Microsoft insider for many years now. Please don't treat me like an idiot.

I'm posting this as a question, if the response isn't satisfactory, this will be re-posted as a discussion and open to others to build upon with their experience until we dig down to the crux of the problem.

:)