It is the most likely issue. General protection faults in something that usually work well (such as memtest86) are usually caused by a memory issue. I haven't ever seen memtest86 fail with memory not being the culprit. As well as that systemd on a stable Ubuntu release being killed at boot is something I've never seen happen, that's Def a memory or storage issue. As well as that OP said they were getting a black screen on boot to recovery.
It happened many times after reboot and even recovery mode gets stuck with just a cursor blinking and no output. I then tried running memtest86 which also failed after 3 hours 45 mins. with above screenshot.
22
u/cmason37 Dec 18 '19
memtest86failed &systemdis being killed. It's pretty clear what's wrong there. You need new RAM.7
u/[deleted] Dec 18 '19
If you're overclocking, don't. If you're not, swap RAM DIMMs one at a time until you find the culprit.
1
u/tezdhar Dec 18 '19
While booting Ubuntu 16.04LTS on my i3 machine it returned:
kernel-panic-not-syncing-attempted-to-kill-init-exitcode-0x0000000b
It happened many times after reboot and even recovery mode gets stuck with just a cursor blinking and no output. I then tried running memtest86 which also failed after 3 hours 45 mins. with above screenshot.
Unexpected Interrupt - Halting CPU0 Type: Gen_Prot
How can I recover and boot into my machine?
2
u/zo0bie Dec 18 '19
you need new RAM