Repeating BSODs mostly upon launch

Hello, everyone,

New to this forum, so not 100% as to how much of the system info section I've filled out will be visible to the reader here. I'm just going to skip the listing of my PC specs in this text body for now.

Context: Earlier this month, I undertook a big hardware upgrade of my Windows 10 desktop computer where I manually uninstalled almost every old part from my case and assembled the new parts. After that, I upgraded from Windows 10 to Windows 11 on my then boot drive. After figuring I couldn't just move that Windows installation to the new M.2 SSD, I manually installed Windows 11 on said new SSD using a USB flash drive with the Win11 ISO which went just fine. Then I formatted the old boot drive and selected the new one as the boot drive in Windows settings (for some reason, the BIOS itself wouldn't list that drive as a boot option despite recognizing the drive itself in other option menus; BIOS still thinks we are booting from the old boot drive).

For the first few days, the PC ran without any issues whatsoever. Then, it started frequently crashing giving me blue screens. Interestingly enough, it never crashed under load of a highly resource-intensive application/ game. Most of the crashes appeared right after booting to the log-in screen or right after logging into my user profile. After the initial crashes, the PC would immediately restart, seemingly using some form of secure boot mode (deducting this as, upon restarting, the log-in screen only featured a default blue background without info panels instead of the usual randomly fetched image with trivia surrounding it). After that restart, the PC would not crash again at all. Shut it down for the day and normally start it anew the following day, and it would be a coin toss whether or not it would repeat the pattern.

I have already tried running the PC without XMP enabled in BIOS which surprisingly led to it not crashing again for a day or two but now, we are back to the same old.

Any ideas on what to do? I have already run an sfc /scannow and Windows's built-in RAM diagnosis tool, the latter for two runs/ cycles, and neither of them reported any issues.

Side note: The crash logs surprisingly state that my OS is apparently Windows 10 when it is actually Windows 11.

V2 Log collection is too big to upload here, so have a dropbox link instead! Dropbox

Thank you so much in advance!

Please use English as the default language during the troubleshooting so that files can be scanned and read.

Okay, changed the system language settings and ran V2 again. Here is the updated archive Dropbox

Please perform the following steps:




1) Run Tuneup plus > post a share link








2) Run get memory configuration > post a share link







3) Run Memtest86+ for 8 or more passes > take pictures > post images or share links

Memtest86+ | The Open-Source Memory Testing Tool

Just 1 error is a test fail and testing can be aborted.

The more the passes the better the testing conditions.

It sometimes takes passes into the 20's to detect malfunctioning RAM.

The RAM can be tested all at one time or one at a time in the same DIMM.

Memtest86+ | The Open-Source Memory Testing Tool

MemTest86+ - Test RAM

I will look into those. What does the first script you linked do, though? I cannot make sense of all the commands listed in the related forum entry and would feel more comfortable knowing what it does as it seemingly touches system settings and how to revert back to old settings after. Thanks in advance.

These check the integrity of the operating system and component store.
If there are integrity violations they attempt repairs.

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow


This superficially checks the integrity of the drive file system

chkdsk /scan


These check and modify the startup and recovery system failure and virtual memory / page file settings to reduce the likelihood of missing BSOD.

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot

wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list

wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
wmic Computersystem where name="%computername%" get AutomaticManagedPagefile


This checks to see if Windows had predicted memory failure and blocked RAM regions.

bcdedit /enum {badmemory}

Thank you for your swift feedback. One more question remains unanswered: How to revert back to original settings afterwards? I see there is a line that alters the restart behavior in case of a blue screen. I imagine simply running that block of commands again simply changing the false argument to a true one will suffice to revert that to its former state; are there any other settings this changes that I will want to reset after troubleshooting and if so, how do I do it?

Okay, followed all the steps, here are the links:

Tune up has been producing an error at the end of its runtime and thus not outputting a file: Dropbox

Memory config: Dropbox

MemTest: Dropbox and Dropbox and Dropbox

For tuneup plus > run in safe mode > post a share link

For Memtest86+ please use the links in post #4 step #3.

Does it really make a difference if I use the memtest application from the memtest or memtest86 website?

They are different software.

Having trouble with tuneup plus still as safe boot is giving me the "pin is unavailable" issue and using my password returns a wrong password message even though using that same password got me logged in in my browser, however, here is the memtest result Dropbox

Memtest86+
32 GB RAM
G Skill
8 passes
Test pass


Please open a separate thread to fix: password and pin as needed