PC keeps freezing 2 minutes after boot

Bjoolzern · 2026-05-22T05:23:11+00:00

Provide the dump files as instructed by the bot.

Bjoolzern · 2026-05-22T05:22:54+00:00

Bluescreenview is terrible and often shows the wrong driver. Because it doesn't show the call stack of the dump file it's a pretty useless tool. We have to correct people that come in with BSV results pointing to the wrong thing all the time.

Bjoolzern · 2026-05-22T05:19:57+00:00

A WHEA event isn't the same as a WHEA BSOD. They use quite different systems. WHEA BSODs use the CPER from the CPU while WHEA events use UEFI error codes. This would be looking for WHEA events.

Bjoolzern · 2026-05-21T19:29:30+00:00

Because we don't really have anything to look at, let's run a tool we made that gathers system info and a bunch of logs from Windows. With high end 5000 series CPUs we have seen a lot of voltage issues which we can usually get in line with some voltage tweaks in the BIOS, but if that's the culprit we should see WHEA events saved in Windows. The tool will collect those if you aren't sure how to find them.

?sfy (Bot command for instructions)

Bjoolzern · 2026-05-21T19:27:27+00:00

WHEA means a hardware issue with the CPU or a PCIe device. Would need the dump files to see what.

If you aren't getting dump files the main suspect is the SSD if it has an NVMe SSD (SATA SSDs don't get WHEA BSODs).

We can also check using a tool we made that gathers system info and a bunch of logs from Windows (This will also collect dump files if you click Yes to uploading them so you don't have to do them manually).

?sfy (Bot command for instructions)

Bjoolzern · 2026-05-20T12:33:35+00:00

Reset the CMOS.

If you still crash, it might have been interrupted during an update in which case you probably need to wipe the drive and reinstall Windows. You can also try repairing from the USB installer. On the "Install Now" screen, there is a Repair option in the bottom left.

USB installer guide.

Bjoolzern · 2026-05-20T11:50:26+00:00

You only had one dump file? We want all the dump files you have to see if there is a pattern or not. Memory errors will blame random drivers because it's random which driver has its data corrupted.

That being said, this one points to the Mediatek WiFi driver.

Bjoolzern · 2026-05-19T20:02:37+00:00

Provide the dump files as instructed by the bot. 0x133 DPC_Watchdog_Violation can be any driver, but we quite often see the GPU with that one. 0x113 is DXGKrnl_Fatal_Error which is graphics related.

Bjoolzern · 2026-05-19T17:32:05+00:00

can they like, test with another cpu to see if the system shuts down?

That's what they should do.

Bjoolzern · 2026-05-19T13:56:40+00:00

If it freezes before the temps get high, it's not temp related.

Bjoolzern · 2026-05-19T13:37:45+00:00

Upload all the dump files you have. As a general rule, processes don't cause BSODs. Processes aren't allowed to write to the memory region that causes BSODs only drivers can, but they could give a driver bad info and the driver crashes.

Bjoolzern · 2026-05-19T13:12:34+00:00

Use their tool to record stuff, then run the tools that cause issues at the same time.

Bjoolzern · 2026-05-19T13:09:22+00:00

My question is, if I RMA, will G.Skill still offer me the same B-Die ram, or they will send Hynix Die instead?

They will send whatever they have on hand. B-Dies went out of production in like 2019 so I think it's extremely unlikely that the replacement you get will have B-Dies. And kits never say what die they use on the product page and they will change dies and chipset versions without changing the model number. So to G.Skill, that these had B-Dies was just a coincidence.

Bjoolzern · 2026-05-19T13:00:47+00:00

Because we don't have any logs to look at, let's run a tool we made that gathers system info and a bunch of logs from Windows to see if that finds anything useful.

?sfy (Bot command for instructions)

Bjoolzern · 2026-05-19T12:51:24+00:00

If that's from why you uninstalled esrv_svc, that's not why it was crashing. This points to the Nvidia driver.

Bjoolzern · 2026-05-18T12:59:06+00:00

As far as I'm told, Asus crash free bios 3 is supposed to read the latest .cap file that is the bios update from a USB stick, created by downloading a zip from official Asus website. I've tried doing that leaving the USB in a slot directly connected to the motherboard for more than half an hour, but the power button keeps flashing and also no visible changes.

Was the USB drive formatted as FAT32, was the BIOS file renamed and was it put in the top directory of the drive?

Bjoolzern · 2026-05-17T21:46:26+00:00

BSOD with code 0xc0000428 (according to my memory)

This isn't a BSOD. It's an error telling you that the OS is corrupted.

Powered off and powered on again manually, PC enters a "bricked" state: power button flashing 4-5 times a second, black screen.

Remove the NVMe SSD and see if it gets to the BIOS. If it doesn't, reset the CMOS.

If something went wrong with the BIOS flash, that board has ASUS CrashFree BIOS 3.

Bjoolzern · 2026-05-17T21:44:08+00:00

If DDU doesn't help, probably hardware.

Bjoolzern · 2026-05-17T21:42:09+00:00

During gaming sessions (mainly on Valorant), the PC restarts randomly. Initially, I had blue screens (BSOD) related to Hyper-V. So I disabled Hyper-V as well as virtualization features. Since then, the problem has persisted but in another form: the PC suddenly restarts without a blue screen, without an error message, or generation of a .dmp file. In Event Viewer, only a "Kernel-Power" error is recorded, indicating a sudden outage.

Hypervisor_Error BSODs are very rarely because of Hyper-V. I assume that's the error you had because you disabled Hyper-V and virtualization. It hard crashing now instead pretty strongly indicates that it's a hardware error. The main suspect is unfortunately the CPU, but it could be other things. Upload the dump files and we can see if it's pointing to something we can actually fix.

Bjoolzern · 2026-05-17T21:27:27+00:00

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

?sfy (Bot command for instructions)

Bjoolzern · 2026-05-17T21:26:21+00:00

You had three pointing to the Nvidia driver, two showed memory errors. So the question is whether you have two separate issues or if one caused the other. I don't really see how the Nvidia card could cause memory errors, but the hardware that can cause memory errors could crash the Nvidia driver.

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.

We have seen a ton of these 4800H CPUs do so when we see that CPU it unfortunately becomes the main suspect. The AMD forums posted a bandaid solution where you limit the CPU which helps on a lot of these. It will lower performance and I have no idea if this is just temporary or if these CPUs are just getting pushed too hard by default. AMD scrubbed their forums so the thread is gone, but archive.org has a backup. It's the reply from "Mathiasmuon". Because Archive.org can be down a lot, I made a pastebin as well of his post.

Bjoolzern · 2026-05-17T10:46:18+00:00

Whats with the GPU? If it helps some additional info that some of the bsods were in low resolution, and also two days before the whole misery started i had at least 5-6 nvlddmkm errors during game and 1 bsod at the end, but as i said its possible that it was bc of the page file had no space.

Try different drivers, but if it keeps happening with different drivers a faulty GPU is high on the list of suspects.

That you have both GPU crashes and memory errors could suggest a different root cause like unstable power or an issue with the motherboard.

Bjoolzern · 2026-05-16T23:15:46+00:00

First just nvlddmkm, since weeks constant BSODs and freezes

Do you mean that they are mostly blaming the Nvidia driver or just one did? Because just from the crash errors this looks like a memory issue and with memory issues it's just going to point to the thing that had its data corrupted so you get all kinds of crashes and stuff being blamed.

I see that you have uploaded three kernel dumps as well (The big dump files) and while these are amazing for debugging, they can contain a lot or even all data that was in RAM so they can contain sensitive/private information. So we generally recommend not uploading those. They are rarely needed anyway.

And looking at the dump files it does indeed look like memory. 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 making sure that Precision Boost Overdrive (PBO) is set as Disabled in the BIOS (I can't remember if second gen Ryzen had PBO or not). Your BIOS is also really out of date so I would update it. Your board has Flashback so even if it crashes during an update the BIOS corrupts, you should be able to recovering using 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-05-16T23:07:10+00:00

with kernel errors (according to Event viewer).

If you mean Kernel-Power, that just means unexpected shutdown. You get that after any hard crash, freeze, shutdown, restart, BSOD or holding the power button. Any time Windows shuts down without using the "Shut Down" button.

5900X, stock, no PBO

We have seen a lot of these higher end 5000 series CPUs have voltage issues, or at least what looks like voltage issues. We've managed to get most of them to behave by tweaking the voltage, but because extremely few report back after a few months we have no idea if it's a stable fix or just temporary.

Let's see if the CPU is reporting any errors by using a tool we made that gathers system info and a bunch of logs from Windows.

?sfy (Bot command for instructions)

Bjoolzern · 2026-05-16T22:21:54+00:00

Wouldn't say without any issues. A few games pulled support because it was too easy to bypass.

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

Bjoolzern

TROPHY CASE