sand_

Members
  • Posts

    9
  • Joined

  • Last visited

sand_'s Achievements

Noob

Noob (1/14)

0

Reputation

  1. Solved? Didn't crash and was able to complete a parity rebuilt after changing C-States in bios from Auto to Disabled.
  2. I managed to capture the moment when it reboots and it spits out this. mce: [Hardware Error]: CPU 2: Machine Check Exception 5 Bank 1: bf80000000000124 mce: [Hardware Error]: RIP !INEXACT! 10:<ffffffff81334b4e> {percpu_counter_add_batch+0x4e/0x52} mce: [Hardware Error]: TSC 3963ac8a7429 ADDR 40b9a9340 MISC 86 mce: [Hardware Error]: PROCESSOR 0:306c3 TIME 1596582445 SOCKET 0 APIC 4 microcode 27 mce: [Hardware Error]: Run the above through 'mcelog --ascii' mce: [Hardware Error]: Machine check: Processor context corrupt Kernel panic - not syncing: Fatal machine check Kernel Offset: disabled Rebooting in 30 seconds.. I don't currently have a power supply on hand, I would use my main pc's psu when I manage to find a good sale to replace however. It would suck if it is the psu as this one is only 4ish months old.
  3. Tried safe mode, this time the reboot happened around 10 hours in. Will try other stuff soon
  4. While I do have pets, none were in my room during the time while it rebooted and there are no children in my house. This is a recycled computer, it was my old gaming computer from about 5 years ago. It has an i5 4690k, 2x8gb of ram and a corsair CX450 psu. Before I started using unraid, it was functioning as a windows/ubuntu computer for a couple of weeks, which had no problems. I'm going to try and snap a picture of when it crashes because the most recent reboot showed that text does appear on screen when it does crash.
  5. It took about 6 hours for it to reboot this time, I was able to catch it and I think it might've said there was a kernal panic. syslog
  6. Zero errors during the memtest. 10 passes
  7. 8 hours in with 4 passes, still no errors. Good, I'm guessing?
  8. Not sure what's occurring, trying out unraid right now and running a parity check seems to cause the system to reboot (? not sure since I'm never able to observe it when it does) after like 4 or something hours. Fix Common Errors found that I had Machine Check Events. tower-diagnostics-20200801-0200.zip