@lopsigon Hmm, any recent hardware installs or anything like that? I had this happen forever ago and it was faulty RAM.