As title suggests.
Coming home the other day I find my PC started to restart out of nowhere, with no warning before or errors afterwards. I haven’t changed anything and haven’t had this problem before.

Any suggestions on what to do?

Device specs:
Processor Intel® Core™ i9-9900K CPU @ 3.60GHz 3.60 GHz
Installed RAM 64.0 GB
Storage 233 GB HDD ST9250315AS, 112 GB SSD OCZ-VERTEX2, 466 GB SSD Samsung SSD 970 EVO Plus 500GB
Graphics Card NVIDIA GeForce RTX 3060 (12 GB)
System Type 64-bit operating system, x64-based processor
OS Windows 10

UPDATE: Memtest got through 2 out of 4 passes in under 4 hours before I got fed up with waiting, which in itself seems a good sign since it didn’t restart there.
Event viewer showed one odd Event: The process C:\WINDOWS\Explorer.EXE (ANDROID-17) has initiated the restart of computer ANDROID-17 on behalf of user ANDROID-17\smuld for the following reason: Anderer Grund (geplant) Reason Code: 0x80000000 Shut-down Type: restart Comment:

No idea why because automatic restart is disabled.

  • Onno (VK6FLAB)@lemmy.radio
    link
    fedilink
    English
    arrow-up
    4
    ·
    11 hours ago

    Make a bootable USB or CD with memtest86 and boot from it. Then let it test your memory. Based on what you’re describing, it’s a good candidate for a fault.

    • EpeeGnome@feddit.online
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      10 hours ago

      Usually a memory fault results in random blue screens on most crashes, not in a consistent pattern of going dark and booting again. Still, it could be memory, and it doesn’t hurt to try it.

      • Onno (VK6FLAB)@lemmy.radio
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 hours ago

        That’s a fair comment, but there’s a secondary reason I suggested it, eliminating the OS as a potential cause. If it still crashes while booted into memtest86, it’s much more likely to be a hardware fault, on the other hand, if it stays running overnight, it’s more likely to be software.

      • Triumph@fedia.io
        link
        fedilink
        arrow-up
        1
        ·
        9 hours ago

        I believe the default behavior is to crash dump and restart on BSOD. Holding on BSOD display must be configured.

        • EpeeGnome@feddit.online
          link
          fedilink
          English
          arrow-up
          1
          ·
          9 hours ago

          Usually shows on the screen for at least a moment, but yeah, if it writes the crash dump fast enough you might not see it.