Faulty instalation/ defective hardware?
Something is messed up with my computer. As you can see in the 24 second video It looks like the NVME is very slow or has some sort of issue because It was struggling to load the games in the preview.
Then I tried to launch a game and the system showed this error saying "the executable file cannot be found" (in spanish, sorry). Then the system froze and I had to reboot. If you check the third video youll see the PC refuses to boot. Then after a while if you unplug and plug again it boots but It does the same thing. It just breaks.
I tried formatting and it worked for a few days until It started doing the same. This is the third time the system just dies.
I had the xmp RAM profile turned on and I turned It off to rule out RAM problems and its doing the same. Should I assume it's the NVME which is faulty or did I do anything wrong during the instalation?
If I give it a few minites I Will be able to turn the machine again and run some tests.
For extra information I have:
I5 12400f
Xt 6600 xt
2x 8gb DDR 4 3200 (I used to have them with xmp but I turned It off just in case)
Asrock ITX motherboard
3 Replies
If theres any command that I can run to gather important logs please let me know. I am a complete Linux noob
system freezing and looping at boot indicates some sort of hardware issue, nine times out of ten. . The lockups and boot looping smells to me like bad/faulty ram sticks. . Before anything else, I would run memtest, for at least a full pass, ideally two or three passes : https://www.memtest.org. Next thing in order for diagnosis would be the PSU. If nothing shows up from the RAM, maybe try to test with another PSUs. Bad ones can throw the system in a fit, and cause this kind of issues. Finally, if you need the logs after a crash/freeze, you can run in terminal : 'ujust logs-last-boot > filename.txt'
Memtest86+
Memtest86+ | The Open-Source Memory Testing Tool
Memtest86+ is an advanced, free, open-source, stand-alone memory tester for 32- and 64-bit computers (UEFI & BIOS supported)
that will create a text file containing the last boot log, usually in your Home folder. The last minutes could show the errors your system encounters before crashing, but if those are freezes caused by hardware failure, there's a possibility the system doesn't have time to log them.