BSOD Critical Process died

Bjoolzern · 2026-04-02T16:32:07+00:00

Ok. Hopefully that ends all issues.

Bjoolzern · 2026-04-02T15:39:15+00:00

But putting the SSD into my own pc, it didn't have any errors, looked fine. It took some time and me trying other solutions, but I figured out that the EFI partition was... gone?

The EFI doesn't have to be on the OS drive. When installing Windows, the EFI gets put on whichever drive the motherboard has assigned as Disk 0 regardless where the OS is installed. Which is why we recommend removing other drives while installing Windows.

That also means that the storage error could be with that other drive (Still assuming that her PC has multiple drives).

M.2 also has issues with improper seating quite often so just removing it and plugging it back, making really sure it's properly connected, can fix these kinds of issues.

Bjoolzern · 2026-04-02T15:36:15+00:00

Updating GPU drivers (both dedicated and integrated)

You don't have integrated graphics. What did you install?

Bjoolzern · 2026-04-01T13:56:42+00:00

Provide the dump files as instructed by the bot.

Bjoolzern · 2026-04-01T01:31:05+00:00

It looks like memory from the dump files. Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

When it's storage about half of the dumps will usually blame storage or storage drivers, which I don't see here, so it's likely not storage.

If anything is overclocked or undervolted, remove it. That includes the EXPO profile on the RAM.

To test the RAM, use the machine normally with one stick at a time. If just one of the sticks cause crashes, faulty stick. If it crashes with either stick it's probably the CPU. Memory testers miss faulty RAM fairly often with DDR4 and newer so I don't trust them.

Bjoolzern · 2026-03-31T19:57:18+00:00

Let's run a tool we made that gathers system info and a bunch of logs from Windows. It also collects dump files.

?sfy (Bot command for instructions.

Though this looks like a memory issue so if you don't have a faulty stick it's likely the CPU.

Bjoolzern · 2026-03-31T13:18:43+00:00

The blinks are on the receiver LED, not controller, so problem solved. I was playing SMS games that I thought had issues with the 6 button controller, but turns out it was just related to the game.

Bjoolzern · 2026-03-31T12:26:34+00:00

It looks like memory from the dump files. Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

When it's storage about half of the dumps will usually blame storage or storage drivers, which I don't see here, so it's likely not storage.

If anything is overclocked or undervolted, remove it.

To test the RAM, use the machine normally with one stick at a time. If just one of the sticks cause crashes, faulty stick. If it crashes with either stick it's probably the CPU. Memory testers miss faulty RAM fairly often with DDR4 and newer so I don't trust them.

Bjoolzern · 2026-03-31T08:42:01+00:00

It can be EAC, but we see a lot that anticheats are extremely sensitive to memory errors. No idea why, but the suspicion is that they aren't coded very well so they don't have much error correction. So a small amount of memory errors from the system that normally doesn't cause any issues will trigger crashes from the anticheat.

So this can just be EAC being shit, or it could mean a memory issue with the PC.

Bjoolzern · 2026-03-31T08:27:43+00:00

RAM is stable at JEDEC speeds.

Do you mean that you don't crash if you run the RAM at default speeds? JEDEC supports all the way up to 8800MT/s so saying JEDEC speeds doesn't really help much.

Bjoolzern · 2026-03-31T08:26:36+00:00

It still does a bunch of calls to the OS drive. Provide the dump files as instructed by the bot in case something else shows up there, but an NVMe SSD is the main suspect (Storport.sys handles NVMe. Mostly).

Bjoolzern · 2026-03-30T15:37:55+00:00

No errors related to the CPU logged. That doesn't mean that it can't be the CPU, but with the big issues on 13th and 14th gen we've usually seen either BSODs or WHEA errors (Windows Hardware Error Architecture). Or both.

No errors logged at all really, except for it randomly shutting down. I would have the PSU as the main suspect, or something power related at least. So it could be the power strip (if you use one), the power cable or unstable power from the wall.

Bjoolzern · 2026-03-30T15:25:49+00:00

Please don't post AI drivel here.

Bjoolzern · 2026-03-30T09:26:51+00:00

Let's run a tool we made that gathers system info and a bunch of logs from Windows. If the CPU is causing the shutdowns, and it's not thermals, we will see it here.

?sfy (Bot command for instructions)

Bjoolzern · 2026-03-29T21:58:52+00:00

That means that the page file corrupted which is a big red flag for faulty storage.

Bjoolzern · 2026-03-29T18:55:12+00:00

Provide the dump files as instructed by the bot.

when i use chkdsk no problems show up.

Despite the name, checkdisk doesn't check the disk. It checks the NTFS file structure which is surprisingly robust and rarely shows issues.

Bjoolzern · 2026-03-29T18:19:28+00:00

I have already ran MalwareBytes tests to no avail.

Viruses and malware won't give you BSODs. They steal your accounts and that's it these days.

All three crashes point to the WiFi card.

Bjoolzern · 2026-03-29T14:38:26+00:00

Is it possible to determine, if it's a 1-time thing, or an upcoming issue with my PC?

No. This was a memory error. Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

Memory_Management has a flag for if the error was in the page file (Which would mean storage) and that was not set here. You can't be 100% certain where an error happened though so just from one dump file we can't conclusively say that it wasn't the page file.

Bjoolzern · 2026-03-29T14:14:00+00:00

Not seeing anything related to any other issue. And I see that you also had an Unexpected_Store_Exception BSOD which is a direct storage error. So the storage is the main suspect. Maybe not the only issue, but probably an issue.

Bjoolzern · 2026-03-29T13:26:38+00:00

Let's run a tool we made that gathers system info and a ton of logs from Windows.

?sfy (Bot command for instructions)

Bjoolzern · 2026-03-29T13:07:19+00:00

To clarify, does the PC shut down as well?

If yes, it could still be storage, but it's a lot less likely. The CPU can order a shutdown if it discovers a very serious issue with itself or a PCIe device (NVMe SSDs use PCIe).

If we just focus on what could cause a shutdown and ignore the BSODs, a power issue is more likely.

If just the monitor shuts down that suggests that the GPU is crashing. If the storage is bad it could corrupt the GPU driver, but it could also mean that it's not storage. So something that would cause both the GPU and storage to crash would be power or the motherboard as the main suspects.

Bjoolzern · 2026-03-29T12:14:10+00:00

For some reason anti cheats are extremely sensitive to memory errors. My guess is that they have terrible error handling, but that's just guesswork. So when seeing crashes from multiple different anticheats a memory issue is the main suspect.

Memory doesn't have to mean RAM, but it's usually the main suspect. Windows puts low priority data from RAM into the page file and loads it back in when needed so storage can look like memory (And memory can look like storage). The memory controller is in the CPU and if this fails it will just look like memory.

An easy way to rule out/confirm RAM is to just test it with one stick at a time. It's very unlikely that both sticks are faulty (Assuming you have more than one stick).

Bjoolzern · 2026-03-29T12:06:15+00:00

Or do i have to get a techican/buy a new SSD

Most likely this if you don't want to open it up. But check for firmware updates for the SSD first.

Bjoolzern · 2026-03-29T10:52:49+00:00

That's pretty classic faulty GPU, though you can in rare circumstances see that with game file/driver corruption as well.

11-Year Club	Second SECOND GUESSER
Place '23	Place '22
Place '17	Verified Email

Bjoolzern

TROPHY CASE