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

Okay, so I've finally managed to get into safe mode and my account and ran tuneup again - it still produces the same error at the end, failing to create a zip file. I have, however, run all of the commands it comprises manually but the crashes have not stopped.

Take pictures > post share links (all steps)(including all scripts, commands, error messages, error codes, test results, etc.)

Post a new V2 share link into the newest post.

Welp, after taking a bunch of photos this time around, it actually managed to create the log file successfully at the end. Here is the content!
Alternatively, a Dropbox link

Microsoft Windows 11 Home Version 24H2 (OS Build 26100.2894) ================================================================== Started on Mon 03/10/2025 at 14:49:06.76 [SFC /ScanNow] Beginning system scan. This process will take some time. Results: Windows Resource Protection did not find any integrity violations. ================================================================== Started on Mon 03/10/2025 at 14:49:59.87 [DISM /online /cleanup-image /ScanHealth] Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.2894 The component store is repairable. The operation completed successfully. ================================================================== Started on Mon 03/10/2025 at 14:50:40.71 [DISM /online /cleanup-image /RestoreHealth] Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.26100.2894 Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ================================================================== The second "SFC /ScanNow" was skipped, as the first output the following: Windows Resource Protection did not find any integrity violations. ================================================================== Started on Mon 03/10/2025 at 15:02:58.11 [ChkDsk /Scan] The type of the file system is NTFS. Volume label is Volume. Stage 1: Examining basic file system structure ... 1203456 file records processed. File verification completed. Phase duration (File record verification): 3.63 seconds. 15859 large file records processed. Phase duration (Orphan file record recovery): 3.87 milliseconds. 0 bad file records processed. Phase duration (Bad file record checking): 0.02 milliseconds. Stage 2: Examining file name linkage ... 329 reparse records processed. 1535964 index entries processed. Index verification completed. Phase duration (Index verification): 7.35 seconds. 0 unindexed files scanned. Phase duration (Orphan reconnection): 1.13 seconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.06 milliseconds. 329 reparse records processed. Phase duration (Reparse point and Object ID verification): 2.43 milliseconds. Stage 3: Examining security descriptors ... Security descriptor verification completed. Phase duration (Security descriptor verification): 15.96 milliseconds. 166255 data files processed. Phase duration (Data attribute verification): 0.02 milliseconds. CHKDSK is verifying Usn Journal... 41624240 USN bytes processed. Usn Journal verification completed. Phase duration (USN journal verification): 36.75 milliseconds. Windows has scanned the file system and found no problems. No further action is required. 976068607 KB total disk space. 650518512 KB in 588640 files. 584452 KB in 166256 indexes. 0 KB in bad sectors. 1346255 KB in use by the system. 65536 KB occupied by the log file. 323619388 KB available on disk. 4096 bytes in each allocation unit. 244017151 total allocation units on disk. 80904847 allocation units available on disk. Total duration: 12.19 seconds (12191 ms). ================================================================== Started on Mon 03/10/2025 at 15:03:16.01 ================================================================== [Set AutoReboot = False] ================================================================== ================================================================== ================================================================== [Set DebugInfoType = 7] ================================================================== ================================================================== [WMIC PageFile list] ================================================================== ================================================================== [Set AutomaticManagedPagefile = True] ================================================================== ================================================================== [BcdEdit /enum {badmemory}] RAM Defects ----------- identifier {badmemory} ================================================================== Finished on Mon 03/10/2025 at 15:03:16.34 It took 14 minutes and 10 seconds to complete the operations.

1) Open administrative command prompt and copy and paste:

dism /online /Add-Capability /CapabilityName:WMIC~~~~

Post a share link.


2) Rerun Tuneup plus > post a share link


3) Download to a new desktop folder:




4) Indicate progress fixing password and pin


5) Make free or pay backup images

(Acronis, Aoemi, EaseUS, Hasleo, Macrium, Paragon, etc.)