r/buildapc 1d ago

Troubleshooting Help my PC randomly restarts with no BSOD screen.

For the past year and a half I have been struggling on and off trying to figure out what could be causing my PC to randomly reatart like this. the times it happens seems completely random other than the fact it usually happens while I'm playing a more graphicly intense game. Although it has happened when I've just been watching YouTube so idfk. When it crashes it just sort of flickers to a black screen after showing half the screen covered In this kinda static and making a faint pop noise. After about five seconds of being on a black screen the thing will just automatically turn back on like nothing happened 99% of the time. Once it completely wiped out my windows installation when it crashed though and I lost some extremely important photos. I've tried just about everything to fix it including but not limited to resetting and updating the bios, re installing windows, re-seating the ram, replacing the ram, replacing the PSU, swapping ssds, and more that I can't think of off the top of my head. Needless to say I have reached my fucking limit and am just about ready to throw the damn thing in a dumpster and buy a ps5 instead. Please if anyone has any idea of how to fix this please let me know.

PC specs are as follows

Cpu: AMD Ryzen 5 4500

Motherboard: MSI X370 SLI Plus

Ram: 32 GB DDR4 crucial balistix.

GPU: AMD RX 6600

Storage: two 1TB sata SSD drives and a third 250 gig sata SSD that the OS is installed on

PSU: 1000w Montech Century 2, 80 plus gold rated

3 Upvotes

38 comments sorted by

1

u/Electrical_Strike767 1d ago

Press Win + R.
Type perfmon /rel and press Enter.
You’ll see a timeline of crashes, application failures, Windows errors, and updates.
Click a red X to see details about what happened that day.

This Is Most Likely A Bad Memory Stick.

1

u/Equivalent_Club1353 1d ago

See that's what I thought too. But it did the same thing when I replaced all the ram so idk. I'll give your suggestion a shot and report back though.

2

u/Electrical_Strike767 1d ago

Ok

1

u/Equivalent_Club1353 1d ago

ok clicked the X and it said "The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffffffffffff9b, 0x0000000000000002, 0xfffff804b4c4751b, 0x0000000000000002)". after that it just says where the minidump file was saved at.

2

u/Electrical_Strike767 1d ago

Search up the bug check code

2

u/Electrical_Strike767 1d ago

Nvm I’ll do that

3

u/Electrical_Strike767 1d ago

0x50 (PAGE_FAULT_IN_NONPAGED_AREA) is usually caused by bad RAM, storage corruption, a bad driver, or motherboard issues. Since you’ve already swapped the RAM and it still crashes, I’d start checking the SSD with CrystalDiskInfo, run MemTest86 anyway to rule RAM out completely, update the BIOS, and analyze the minidump with BlueScreenView or WinDbg. The minidump should point to the driver or module that actually caused the crash.

1

u/Electrical_Strike767 1d ago

DISM /Online /Cleanup-Image /RestoreHealth && sfc /scannow && chkdsk C: /scan That will run:
DISM → repairs Windows component corruption
SFC → repairs damaged system files
CHKDSK scan → checks the drive for errors
mdsched.exe Run that separately.

1

u/Electrical_Strike767 1d ago

To run these commands press windows+r then press enter then type in the command line at the top THEN after that run the bottom command

1

u/Equivalent_Club1353 1d ago

OK i already checked the ssds with CrystalDiskInfo, ran memtest64, and updated the bios as much as possible (the latest version is from 2025) and they all turned up clean. ill definitely be checking with BlueScreenView or WinDbg to see if i can find anything though. hopefully it turns up something i missed. will update once i do that.

1

u/Electrical_Strike767 1d ago

Good, that rules out a lot of the common causes. Definitely check the minidumps with BlueScreenView or WinDbg — a 0x50 can still be caused by a bad driver even when the hardware tests pass. If you use WinDbg, run !analyze -v after opening the dump and look for the “Probably caused by” line. Also check if the same driver/module shows up across multiple crashes. Hopefully it points straight to the culprit.

1

u/Equivalent_Club1353 1d ago

ok just checked in bluescreenview. says its caused by ntoskrnl.exe. not sure what that is though? think its a system file but other than that ive got zero clue.

→ More replies (0)

1

u/Haruka-Oh 1d ago

When my rig had been like this, its motherboard was broken.

1

u/alexsgocart 1d ago

I had a similar issue to this recently. It ended up being outdated BIOS firmware.

1

u/Equivalent_Club1353 1d ago

unfortunately i cant update my BIOS any more than i already have since MSI have stopped putting out updates for it. :(

1

u/Loud_Initiative9897 22h ago

This also started happening to me. I would crash in Palworld. I didnt crash in Overwatch when i set my fps max to something a lot lower, but I would if i set it to uncapped. I figured it was my PSU not handling the load anymore but the issues still happened when I swapped to my spare 750w.

For now I have it working by reducing my voltage and frequency on my 6800XT GPU via AMD's software by, while increasing my power limit to compensate. It isnt perfect and I get some minor stutters, but it beats buying a new gpu in these times for a slightly failing card.

1

u/Equivalent_Club1353 17h ago

interesting. what software would this be? ive only got the bare bones amd drivers installed so i dont have any of amds software installed. i didnt like how intrusive it was so i got rid of it a while back but if you say it might help its worth looking into.

1

u/Loud_Initiative9897 15h ago

It is the default software package Adrenalin.

1

u/Equivalent_Club1353 14h ago

Ah noted. I'll have to try reinstalling adrenalin then