gernericuserxyz Somehow I do not believe that this is some hardware defect since it was running for a couple days under heavy load without any flaws.
Unfortunately, given these symptoms, I suspect that a hardware problem is likely, and that the next steps to figure that out will need to be disruptive.
Maybe wait to see whether people agree with me or suggest a different path, but I would suggest:
- If you can manage it, enable developer mode and enable OEM unlocking,
- WIpe the user data partition (ouch!) by booting into recovery and doing a "factory reset",
- If that doesn't solve the crashing, flash the device back to Google's OS and use it for at least a week,
- If that doesn't solve the problem, try a repair shop (or warranty service, if available).
Since flashing an update didn't solve the problem, I doubt waiting and doing it again will do any better. The only other thing I can think of to try is to capture information about one or more of the kernel panics.
But overall I think the likelihood is fairly high that the device is failing.