BSOD on PC <1 year old persisting after fresh install of Windows 11

Title: Persistent BSODs on clean install (Wdf01000.sys, Ntfs.sys, 0x1000007E) - Need Help

Hi everyone,

I am dealing with recurring BSODs on my iBUYPOWER desktop and could really use some expert eyes on my dump files to help me figure out what is failing.

The Issue & Triggers:I had been getting random BSODs related to driver errors since I got the PC in December 2025. I had been getting intermittent BSODs and used whocrashed to work with Ibuypower on resolving the issues. They believed the issues were graphics card related and I also had a noisy cooler. iBUYPOWER sent me a replacement graphics card and a replacement AIO liquid cooler under warranty back in March 2026, which I installed myself. Problems persisted but less frequently. Three weeks ago I had two BSODs impact work (one was a crash on a meeting I was leading, the other a random act of BSOD.) Two weeks ago I completely wiped the drive (deleted all partitions) and performed a clean installation of Windows 11.

Unfortunately, the BSODs have already returned on the fresh OS. My two crashes since the fresh install both show Bugcheck 0x1000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M):

• Crash 1 (10/7/2026): Parameter 1: 0xFFFFFFFFC0000005. No specific driver blamed, but analysis flagged potential memory corruption.
• Crash 2 (10/13/2026): Parameter 1: 0xFFFFFFFFC0000005. This crash explicitly failed in Ntfs.sys (NT File System Driver). The analysis tools suggest this could point to a malfunctioning drive, corrupted disk, or faulty RAM causing memory corruption.

Overclocking Status: No changes made on my end. I am a bit of a novice so I am not sure where to find this.

System Age & Warranty History:This is an iBUYPOWER pre-built system. Back in March, I was experiencing issues and iBUYPOWER sent me a replacement graphics card and a replacement AIO liquid cooler under warranty, which I installed myself.

System Specs See the google drive link or my profile Computer Dumps - Google Drive

Since this issue survived a total drive wipe and clean install, and is now throwing Ntfs.sys errors on a fresh format, it seems like it could be a physical hardware fault (maybe the storage drive or RAM). However, I am not confident in anything at this point. I really need help, all options are on the table, and I am completely open to any troubleshooting steps you recommend. I have the V2 Log Collector files and my system info on the google drive link

Thank you in advance!

Computer Dumps - Google Drive

Please perform the following steps:




1) Run admin PS > post share links displaying each command with results





2) Run admin PS > post share links displaying each command with results





3) Create a new restore point:






4) Run the V2 log collector > post a share link

zbook said:

Please perform the following steps:




1) Run admin PS > post share links displaying each command with results

Code:

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow
chkdsk /scan
fltsmn

2) Run admin PS > post share links displaying each command with results

Code:

Get-CimInstance -ClassName Win32_OSRecoveryConfiguration | Select-Object AutoReboot
Get-CimInstance -ClassName Win32_OSRecoveryConfiguration | Set-CimInstance -Property @{AutoReboot=$false}
Get-CimInstance -ClassName Win32_OSRecoveryConfiguration | Select-Object AutoReboot

Get-CimInstance -ClassName Win32_OSRecoveryConfiguration | Select-Object DebugInfoType
Get-CimInstance -ClassName Win32_OSRecoveryConfiguration | Set-CimInstance -Property @{DebugInfoType=7}
Get-CimInstance -ClassName Win32_OSRecoveryConfiguration | Select-Object DebugInfoType

Get-CimInstance -ClassName Win32_PageFileUsage | Format-List *

Get-CimInstance -ClassName Win32_ComputerSystem | Select-Object AutomaticManagedPagefile
Get-CimInstance -ClassName Win32_ComputerSystem | Set-CimInstance -Property @{AutomaticManagedPagefile=$true}
Get-CimInstance -ClassName Win32_ComputerSystem | Select-Object AutomaticManagedPagefile

bcdedit /enum '{badmemory}'

3) Create a new restore point:

Create System Restore Point in Windows 11

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

4) Run the V2 log collector > post a share link

Download attachment

www.elevenforum.com

Click to expand...

On it now -- thank you. I will add to the google drive link in the main post (and will update here once complete). I really appreciate your help. I like to tinker but this level of troubleshooting is beyond me.

Hi @zbook I'm back with some results. I have added all the necessary screenshots to the google drive folder. Two items you asked for errored (see below)

1) I could not run "fltsmn" from an admin powershell. Error is attached but said

PS C:\WINDOWS\system32> fltsmn
fltsmn : The term 'fltsmn' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fltsmn
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: (fltsmn:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


2) Very similar error trying to run v2 Log Collector

& : The term '.\resources\main.ps1' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:2
+ &'.\resources\main.ps1'
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (.\resources\main.ps1:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


Computer Dumps - Google Drive


Thank you so much for helping!!!

Please run fltmc > post a share link

For V2 > before running > view the menu bar > click extract all > wait for the pop up > then run V2 > post a share link




The BIOS Version/Date American Megatrends International, LLC. 1.K0, 6/24/2025

Upgrade the BIOS: K0 > M3

Both are uploaded into the google drive. I will do the bios update after my meeting in an hour. Thank you so much!

Please run administrative command prompt: > post share links

wevtutil epl Application "%userprofile%\Desktop\application.evtx"

wevtutil epl System "%userprofile%\Desktop\system.evtx"

fltmc



For any new BSODs or unexpected shutdowns and restarts post a new V2 share link into the newest post.