Quote from: AbsentSixth on January 16, 2018, 08:03:37 PM

Now though when I run bitcoin-qt everything is as it should be for approx 40-50 min's until it crashes. I could probably even send the little bitcoin I have in that wallet out to somewhere else if the mining fee wasn't as high as it is. But then again I wonder what might happen if that transaction didn't confirm within the 40-50 min window before my node crashed again. But other than that it syncs up and then connects to approx 8 inbounds and 8 outbound peers at the beginning, shows my balance and runs properly for about 45mins then gives the fatal internal error. The wallet dat file is encrypted but is in the bitcoin folder and I have checked that my user has read and write access.

So the wallet is from your local computer and not the 21 raspi? If so, the raspi is completely irrelevant to this discussion.

Quote from: AbsentSixth on January 16, 2018, 08:03:37 PM

I read back thru the debug file to the 7th of this month which I believe is when I tried to connect the 21 pi and found a line in there that said "possible stale tip detected" I'm not sure what that means

It means nothing. That error is benign.

Quote from: AbsentSixth on January 16, 2018, 08:03:37 PM

but it occurs to me that I only put a days worth of the debug log file in the Pastebin would it be more helpful if I loaded more of the debug file?

Yes.