Update -
Turns out it was a faulty stick of memory. I was inspired to troubleshoot all the memory from a similar thread with a similar issue. If you are getting the same error and have not checked the memory using Windows Diagnostic Tool, I would strongly suggest looking there first. Would have saved me a ton of time.