BSOD - constant crashes in newly built PC

First of all, thank you in advanced. I've been getting random crashes in my newly built PC (winver 24H2 OS Build: 26100.3775), this is still not OC'ed yet. The crashes either at the start or it lets me get in for a long time then it crashes. It seems that once it crashes it keeps on crashing constantly, even before logging in.

Normally I would go to the minidump but it does not get generated (stays at 0%). I have the proper page file, verified folders, settings to get created, etc nothing. The error I get for the minidump is Dump file creation failed due to error during dump creation. BugCheckProgress was: 0x00060049
...whatever...
I still can't seem to be able to pinpoint the CRITICAL_PROCESS_DIED BSOD error.

SPECS:
CPU: AMD Ryzen 7 9800X3D 8-Core Processor, 4700 Mhz, 8 Core(s), 16 Logical Processor(s)
Mobo: TUF GAMING X870-PLUS WIFI
GPU: Nvidia GeForce RTX 5070ti
PSU: 1050w Gamemax 80 plus gold
RAM: 64Gb
Windows: 24H2 OS Build: 26100.3775


V2 log collector here

Things I've done:
- Reviewed Event viewer --> in ID41 I get: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
- ran MEMTEST86, 4 hour run, standard passes (4) and tests (all but the experimental), Successful (Results Here, Log Here)
- ran dism /online /cleanup-image /restorehealth
- ran sfc /scannow
- ran chkdsk /f
- updated drivers, especially for the NVIDIA RTX 5070ti and the mobo, everything is latest
- tried to fix startup but it doesn't let me
- tried to start in safe mode but it gives me a dumb error with my PIN not available.

Again, thank you for your help on this one!

Hello and welcome to Eleven forums.

First of all, you should update the Motherboard BIOS and FIRMWARE components to the latest. Your BIOS seems to be the original this MB got at launch.

If this did not help at all, then we have to look closer.

Many V2 files were missing.

Uninstall all non-Microsoft AV and firewall then post a new V2 share link into the newest post.

While troubleshooting, it's very important that Windows is as clean as possible and not having any third party apps and tools that mess with the system/OS itself.

That’s fair, I can uninstall some of the apps including the AV but my problem is that this thing is temperamental… there’s not a pattern of when is it going to crash… sometimes it lets me use it for hours, sometimes it just crashes at the beginning of the session… sometimes I don’t even get to enter my pin… sometimes when I click on the mouse, sometimes without even doing anything… and also it’s crashing in Safe Mode w/ networking which is weird. I’m at my wits end.

At least I was able to update the BIOS to the latest, so can confirm it is not that.

I appreciate you guys for the help, as soon as I have a decent “session” I’ll uninstall most of the apps.

This is not a solution, but just some information I want to put out here. I've noticed a pattern lately. Most Windows 11 issues among many users with random BSODS have been on 24H2 builds. Many users can't upgrade from 23H2 to 24H2, including myself.

I've got 2 machines, that can't even install 24H2, no matter what I try. Both with unsupported CPUs, but this should absolutely NOT matter, since the CPU generations supported, compared to mine, only has one advantage and that is hardware hash support which only affect Windows AV performace, not compatibility. 23H2 runs perfectly stable on all my systems. Haven't had a single crash, unless the computer has been on for over a month without rebooting and I probably did something that caused the instability in the first place.

This issue could be as simple as Windows tries to look for something in the BIOS/UEFI that should be implemented but hasn't been done so properly, even on latest hardware.

This might have nothing to do with OPs issues, but wanted to put it out there.

it doesn't matter what I'm doing, it keeps crashing always and not enough time to capture the V2 log collector. Luckily I have another M.2 SSD so I am reinstalling Windows there and trace my steps back I suppose... this is so frustrating because it is not creating the minidump at least to know why this is happening. ugh... more to come and thank you guys

Please see posting instructions > post a new V2 share link (with all files)

zbook said:

Please see posting instructions > post a new V2 share link (with all files)

Click to expand...

Believe me, I am trying my hardest and doing my best... it crashes even in Safe Mode, not long enough to start properly the V2. I am typing this now in the other M.2 SSD and so far no crashes. Not sure what it means at this stage but my guess is that is probably related to an application...? I'll keep trying. Thank you guys!!

Firstly, Im sorry you are having these issues - Ive been building a new PC since December 26th 2024 and only now have a stable PC. I was unfortunate enough to get 3 faulty motherboards (well, 2 faulty motherboard and one motherboard with the worst bios issues Ive ever encountered) and its taken months to go through RMA, re-build and then troubleshooting steps.

Is the PC stable in BIOS?

Cant you just clear the slate and do a clean install of W11 on your SSD and then take it from there in terms of understanding whether a fresh install is stable?

What is the PC spec? (motherboard, ram, cpu, GFX) out of curiosity?

is that ram installed on the approved list for the motherboard? do you have other usb devices plugged in besides mouse and keyboard?

retiredat44 said:

is that ram installed on the approved list for the motherboard? do you have other usb devices plugged in besides mouse and keyboard?

Click to expand...

Exactly what I was thinking. This feels like RAM instability (but he has confirmed no OC which is good news). However is the RAM at the stock speed or have you lifted it to the XMP profile speed? To me an OC is taking it beyond XMP speed.

Going single stick in slot A2 would be my next query.

Also rather jealous of your retirement at 44!

how long into running does it get before bsod??? or reboot?

I'm with Method, I'd be making sure the hardware is solid before moving on to time consuming software installations and debugging.