this post was submitted on 21 May 2026
26 points (100.0% liked)

PC Master Race

21190 readers
905 users here now

A community for PC Master Race.

Rules:

  1. No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
  2. Be respectful. Everyone should feel welcome here.
  3. No NSFW content.
  4. No Ads / Spamming.
  5. Be thoughtful and helpful: especially when new beginners have questions.

founded 2 years ago
MODERATORS
_MoveSwiftly@lemmy.world
The_Vampire@lemmy.world
Fudgeknuckles98@lemmy.world
Brunbrun6766@lemmy.world
IowaMan@lemmy.world
BobaFett26@lemmy.world
CatZoomies@lemmy.world
Xeon@lemmy.ml
geosoco@kbin.social
26
PC randomly restarts out of nowhere (sh.itjust.works)
submitted 16 hours ago* (last edited 11 hours ago) by HerbalGamer@sh.itjust.works to c/pcmasterrace@lemmy.world
41 comments fedilink hide all child comments
 

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(R) Core(TM) 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.

you are viewing a single comment's thread
view the rest of the comments
[–] EpeeGnome@feddit.online 1 points 15 hours ago* (last edited 15 hours ago) (2 children)

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.

[–] vk6flab@lemmy.radio 2 points 15 hours ago (2 children)

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.

[–] HerbalGamer@sh.itjust.works 1 points 11 hours ago

Well it ran fine for 2/4 passes in under 4 hours before I got fed up with waiting and canceled the rest to do it tomorrow while I'm gone so that seems promising!

[–] EpeeGnome@feddit.online 1 points 15 hours ago

Good point.

[–] Triumph@fedia.io 1 points 14 hours ago (1 children)

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

[–] EpeeGnome@feddit.online 1 points 14 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.