Blue Screen Of Death Every Other Day, Memtest Fine

Any suggestions what to test next?

Built the PC 4.5 years ago, it has 4x 8GB = 32GB DDR4 3600 (poor by today's standard, I know). No problems until about a week ago and got BSOD, then again a couple of days later, then again earlier. Memtest has 0 errors after 4 hours of testing.

Always sleep, never shut down but had no problem prior to a week ago.

What is the error code for the BSOD?

you need to use windbg on the bluescreen file
system32 memory.dmp or system32/minidump if you have a fancier setup

inside windbg you really dont need to know what you are looking at only a guesstimate

itll point you at a driver or something and you can get a better idea

feed most of it into an ai like copilot and it will give you some pretty good pointers

come back with the main fault/error that pops up on the bluescreen

I mean. Whats the code on your BSOD. That's where you start.

3 posts in one minute all same answer. Well played fellas.

I guess I can expand. The 2 times I've had consistant bsods were the HDD was dying, and the psu was dying.

Don't remember the error for hdd, but the psu kept throwing kernal error.

I thought BSoD was always RAM related?

Seems to be something with BcastDVRUserService_b9d2a

Some *** game video recorder built into MS, time to find how to nuke it

? Option 1: Disable via Xbox Game Bar Settings
- Go to Settings > Gaming > Captures.
- Turn off "Record what happened" and other capture options.
- Go to Settings > Gaming > Xbox Game Bar and disable it.
? Option 2: Disable the Service (Advanced)
- Press Win + R, type services.msc, and press Enter.
- Look for Broadcast DVR User Service (with a suffix).
- Right-click > Properties > Set Startup type to Disabled.

do both, but I don't recall that name popping up when I was looking for gamebar. uh don't try to strip game bar out it doesn't go well.

also gamebar gives autohdr

Its easy to point at ram but when everything is in ram its not always that easy.

Bluescreens are the kernel's way of tell you something didn't line up as expected.

Do not be surprised if it happens again after this as this is a process and there are layers to peel back do not get discouraged

First thing I do to any install is to forcibly remove game bar.

Everything is already off, I want to nuke it for good.

Had already tried this and it can't find the program.

It also refused to let me turn it off in services, so will try regedit.

I have had BSoD from overheating. Mind you the CPU was half fried when this was happening and this was internet centuries ago.

In other news:

Windows is getting rid of the Blue Screen of Death after 40 years
Microsoft is saying hello to the Black Screen of Death error message instead.
Black somehow seems more appropriate.

Typically it's RAM related, but can also be memory controller on the CPU.



I've seen it thousands of times and always wondered why it wasn't red. I'd think that would be the obvious choice for errors /shrug

Can also be drive related. Had an issue with BSOD after computer came back up from sleep, turns out it was SDD that neded replacing.

I'd be more inclined to believe the problem was the ssd. Obviously after 4.5 years the whole thing is ancient technology (10th series intel...} so I need a new PC anyway. I just want to hold our for DDR6 for running LLM locally.

Time to set a budget and build a new one?

Just to clarify some things on BSOD. The screen is caused by your computer entering an irrecoverable state. That can be from basically any component in the computer or even any piece of software running on the computer. The BSOD is basically your OS/Kernel crashing. The error display indicates the cause of the crash and where the crash occurred. This doesn't mean that the place that it indicates the root cause though. A failing piece of hardware can cause a crash in another component leading you on a false trail.

As I mentioned software can also be to blame. Excel around 2010 had a beautiful bug where if you accidentally triple click to open excel the 3rd click (if you were slightly slow at clicking) would end up clicking on a cell before the app actually loaded causing a BSOD due to a null pointer. This was a 100% repro lol

I have money, I just really hate building a pc and it being out of date within 6 months. I feel like if I wait for DDR6 and also update GPU then it'll get a bit more time before being outdated.

I normally use two Apps to help find out what BSOD i have and they are
WhoCrashed and BlueScreenView