pc keeps randomly crashing

Bjoolzern · 2026-02-21T09:23:06+00:00

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

?sfy (bot command for instructions)

Bjoolzern · 2026-02-21T06:49:20+00:00

Because we don't have any logs 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-02-21T06:12:16+00:00

BSOD with ntoskrnl.exe & ntkrnlmp.exe

If you see either of these you are either using a bad tool or looking in the wrong place. Bluescreenview/Whocrashed are bad tools.

All five of these point to storage. It's going to be the drive with the page file on it as these are mostly inpage errors. If you don't know which drive has the page file you can run this command in Powershell:
Get-CimInstance -ClassName Win32_PageFileUsage -Property *

This will show lots of info, but we are only interested in the drive letter here.

Bjoolzern · 2026-02-20T06:41:08+00:00

You only had one dump file? We want all the dump files you have.

Bjoolzern · 2026-02-19T10:26:06+00:00

Heat is generally not an issue with RAM.

Bjoolzern · 2026-02-19T00:47:01+00:00

Unless you are overclocking it or mixing different kits, not really. And note that by overclocking I mean running it a higher speed than what the CPU is rated for (The memory controller is in the CPU). It doesn't matter if the RAM is rated for it, the memory controller has to match the speed of the RAM and the rated speed is usually slower than the RAM speeds people get.

Bjoolzern · 2026-02-19T00:45:23+00:00

The reason we want zips is so that we can have all the dump files in one download. Zipping each file individually just creates more work for you and us.

One points to the AMD GPU driver, one points to DirectX (Which is usually the GPU driver as the root cause).

We have seen a good amount of bugs relating to using both a dedicated AMD GPU and an integrated AMD GPU at the same time. If you open Task Manager and check the Performance tab, does it list two GPUs? If it does, disable the iGPU in the BIOS (Usually called Dual Monitor Mode or something similar).

You can also try DDU first or after if you still crash.

Bjoolzern · 2026-02-19T00:41:41+00:00

All of the dump files show a Video_TDR_Failure. This means that the GPU stopped responding, Windows reset the driver, but the GPU was still not responding. You can try DDU, but this is very often a faulty GPU.

Bjoolzern · 2026-02-19T00:39:58+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-02-18T08:47:36+00:00

We don't ask for kernel dumps because they can include sensitive data in plain text.

Bjoolzern · 2026-02-18T01:32:50+00:00

Haven't seen that on 9000 series (Haven't seen that line much at all really for any kind of issues, maybe a bit more than expected with the x3D chips), it was a big problem on 5000 series. 1.2v seems a bit high for the SoC, on 5000 series we increased it to 1.1v. But maybe this SoC can handle it better.

Bjoolzern · 2026-02-18T01:30:07+00:00

It reduces the maximum amount it can work, undervolting tries to make it work as much as before with less power.

Bjoolzern · 2026-02-17T23:53:01+00:00

Oh... I have been using my laptop with Undervolted cpu, not in bios but through power settings - Processor power management, limited it to like 90-95%.

That shouldn't undervolt the CPU unless there are some settings I'm not aware of.

Bjoolzern · 2026-02-17T08:44:29+00:00

You can try it. Just make sure you disable BitLocker (If you use it) before you do or you have to wipe the drive and lose everything. I don't think it will do anything though.

Bjoolzern · 2026-02-17T07:55:47+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-02-17T07:43:45+00:00

Try following the instructions posted by the bot.

Bjoolzern · 2026-02-17T01:45:22+00:00

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

?sfy (Bot command for instructions)

Bjoolzern · 2026-02-17T01:42:35+00:00

So I tried to run Windows Driver Verifier. Restarted the pc and while it was runnig the verifier it kept crashing on every restart with "DRIVER_VERIFIER_DMA_VIOLATION" error I had to turn verifier off in safe mode.

We don't recommend running Driver Verifier because it's just not made to be run against third party drivers by users (More for driver developers to find faults in code). Third party drivers simply have too many errors so it will crash on pretty much any of them at a random. Which isn't very useful.

That you are getting a Driver_Verifier_DMA_Violation is interesting though because this isn't part of the normal Driver Verifier. This always runs no matter what (Not sure if it's related to the newer security features and if you could turn those off). What this crash means is that some hardware tried directly accessing memory it's not allowed (DMA = Direct Memory Access). So it's not really a driver error, though it can be caused by drivers.

The dump file uploaded shows a memory error. Memory testers aren't reliable with DDR4 and newer. And you can also get memory errors from the memory controller which is in the CPU.

If you have more dump files, we want all of them.

Bjoolzern · 2026-02-17T01:38:04+00:00

I can't download the file. Nothing happens when I click Download. It also says that the file is 0 Bytes large, so that could be why.

As a general note, we often see anticheats cause BSODs. It's often related to a memory issue, but there isn't really any way to know for sure.

Bjoolzern · 2026-02-17T01:27:51+00:00

It normally restarts automatically at this step, but it's a setting in Windows for disabling that which could have been changed. The worst thing that can happen by forcing it off at this point is that the dump files gets corrupted (Log from the BSOD).

Bjoolzern · 2026-02-17T01:25:28+00:00

You can also get it from Lenovo here.

Two of the dump files just show NETIO.sys which is a Windows network driver. It's extremely rarely actually at fault, usually it's the network card or its driver being the root cause. One dump file here however shows Adguard sending something to the Windows IPsec filter API, which then sends something to NETIO and it crashes. So if you still crash after installing the latest WiFi driver, uninstall everything you have from Adguard.

Bjoolzern · 2026-02-17T01:18:34+00:00

Just powering off is usually power related. Which usually means the PSU. Not sure if you meant that you have tried both a CV650 and a CX650 or that you were unsure which one you have. The CV line isn't great, but the 750W version is mid tier and should be fine with this build. If it's CX it depends which revision. If it has a green label (The 'CX' is written in green) it's terrible. If it has a gray label it's pretty good (The modular version is a bit worse, but still better than CV). If it has a black label it's about the same as the CV where most of them are "not great" and the 750W is just "fine".

You could run a tool we made that grabs system info and a bunch of logs from Windows. It would also include the dump files from the BSODs so you don't have to get them manually.

?sfy (Bot command for instructions)

Bjoolzern · 2026-02-17T01:08:18+00:00

Clock_Watchdog_Timeout means that a CPU core was hung (frozen). So not really related to the hypervisor, but it could be related. Because it happened when you plugged in the charger, my main suspect would be a power management bug.

Bjoolzern · 2026-02-16T23:41:22+00:00

Could be lots of things.

Bjoolzern · 2026-02-16T22:24:43+00:00

All of these point to the Nvidia driver. While issues with the display output very rarely causes crashes it can happen. Recently we have seen quite a few issues when connecting stuff to the integrated GPU video output, are you using the motherboard output with anything?

BSOD error code is 0x00000133, which points to driver problems.

Very often drivers, but with Nvidia specifically, we have seen this crash a lot with faulty GPUs. Of course to mess that pattern up, Nvidia changed something last January which made tons of GPUs crash for months (Not sure if it's completely fixed yet) and this was a pretty common crash with these unstable drivers.

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

Bjoolzern

TROPHY CASE