Endless BSODs on a new build

I built my PC in October (specs at bottom) and it has run like a champ until 3 days ago. I was playing Fortnite and it crashed. Soon after, I got a BSOD (SYSTEM THREAD EXCEPTION NOT HANDLED, FLTMGR.sys). From there I was getting a BSOD under any load and they were all random Stop Codes.

I don’t have a lot of personal files so I did a “Reset my PC” local reinstall of windows and it crashed/BSOD multiple times during installation.

After that, I did a fresh USB install of windows and although it did BSOD once during install, everything seemed to work after. I downloaded all my drivers. Ran some cinebench, 3d mark and everything scored great. Once again started playing some games and about an hour later the endless BSODs started again.

After that, I ran memtest86 and confirmed no issues with ram. I also ran Samsungs SSD test and confirmed no issues. Even with that data, I went to best buy and grabbed new RAM and a new m.2 SSD. Installed both, usb installed windows, and started her up. Ran benchmarks. Everything OK. A few minutes later, BSODs started again.

Most of the BSODs started with FLTMGR.sys and then kernels would follow. I also got a hypervisor error a few times as well as some other odd ones. I will attach a few that I pulled and still have.

The real oddity to me is when the BSODs start, they may do 4-5 in a row on start up and once I’m past the log in, it’ll be fine until I do anything that seems to load the computer.

I’m just so confused and frustrated. It’s essentially brand new.

CPU: Intel 13700k
MOBO: Asus Prime 790
GPU: RX 7900xt
SSD: 980pro
Ram: Gskill ripjaws ddr5 16gbx2
PSU: Corsair RM850x

Please see posting instructions:




How come the posting instructions were not seen or followed?

What webpage or website improvements could be made so that the posting instructions are seen and followed?

zbook said:

Please see posting instructions:

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

How come the posting instructions were not seen or followed?

What webpage or website improvements could be made so that the posting instructions are seen?

Click to expand...

In my case, I cannot get on my PC at the moment (due to BSODs) to provide exactly what is requested. I have pieces taken out to pull serials for RMA.

I just happen to have saved 5 dump files from crashes yesterday.

I apologize.

BSOD on new builds are almost always due to malfunctioning or incompatible hardware.

Indicate whether the installed RAM are or are not on the Qualified Vendor List (QVL).

zbook said:

BSOD on new builds are almost always due to malfunctioning or incompatible hardware.

Indicate whether the installed RAM are or are not on the Qualified Vendor List (QVL).

Click to expand...

It is on the QVL.

And my build worked perfectly from October till 3 days ago.

Boot the computer using a bootable Media Creation Tool (MCT) (Windows 11 iso) > Windows Recovery Environment (RE) > command prompt > search for these files > post share links

C:\windows\minidump
%systemroot%\minidump

C:\windows\memory.dmp
%systemroot%\memory.dmp

C:\windows\livekernelreports
%systemroot%\livekernelreports


Consider installing Ubuntu / Linux to check for malfunctioning hardware.

There are only two mistakes you can make when assembling a computer: Mounting the cooling system incorrectly or bending the pins on the socket.

Try disconnecting the dedicated graphics card.

Out of curiosity, try disabling virtualization support in BIOS if you don't use virtualization for anything. I've had BSOD issues with certain AMD GPU drivers when virtualization was enabled. Disabling support solved the issue for me and later I found a good driver that didn't have this issue and I could enable virtualization again.

SlicEnDicE said:

Out of curiosity, try disabling virtualization support in BIOS if you don't use virtualization for anything. I've had BSOD issues with certain AMD GPU drivers when virtualization was enabled. Disabling support solved the issue for me and later I found a good driver that didn't have this issue and I could enable virtualization again.

Click to expand...

I did this during the troubleshooting and didn’t solve the issue.

abactuon said:

There are only two mistakes you can make when assembling a computer: Mounting the cooling system incorrectly or bending the pins on the socket.

Try disconnecting the dedicated graphics card.

Click to expand...

This is one thing I haven’t done. None of the BSOD failures indicated a GPU issue but I will do it.

Yeah, since you have a CPU with integrated graphics...disconnect dGPU and everything else for that matter, except CPU, RAM and SSD (also remove any extra USB peripherals except KB and Mouse). Then test. Run apps like Furmark and Prime95 separately and then if system is still stable after 15 mins of each test, run them simultaneously for 15 minutes.
Make sure you have a tool that can monitor all temperatures and preferably also voltages.

If some test failed, make sure you don't have any XMP etc enabled. Bare minimum settings to test base stability.

If everything was great, reseat the dGPU and do the same tests, this time monitoring the GPU and CPU voltages and temps closely.

With these kinds of issues it is best to strip everything to bare bones. and go from there.

SlicEnDicE said:

Yeah, since you have a CPU with integrated graphics...disconnect dGPU and everything else for that matter, except CPU, RAM and SSD (also remove any extra USB peripherals except KB and Mouse). Then test. Run apps like Furmark and Prime95 separately and then if system is still stable after 15 mins of each test, run them simultaneously for 15 minutes.
Make sure you have a tool that can monitor all temperatures and preferably also voltages.

If some test failed, make sure you don't have any XMP etc enabled. Bare minimum settings to test base stability.

If everything was great, reseat the dGPU and do the same tests, this time monitoring the GPU and CPU voltages and temps closely.

With these kinds of issues it is best to strip everything to bare bones. and go from there.

Click to expand...

I will do this tonight.

Any suggestions for temp monitoring? The Samsung Magician monitors SSD temps, AMD software does GPU.

Here is the piece that is confusing me and tell me if I’m off base.

I put in new ram and SSD yesterday. Reloaded windows via USB. Ran some 3Dmark benchmarks and everything scored amazingly. GPU/CPU temps good. Then suddenly 30 mins later, BSODs started. If the hardware is bad, I’m confused how this is happening.

On Sunday, I reinstalled windows for like the 8th time and the computer was fine for 4 hours. Gamed on it. Benchmarked. Then it started again. Just seems odd that if it’s hardware, it’s fine sometimes and not fine others.

parkero1995 said:

On Sunday, I reinstalled windows for like the 8th time and the computer was fine for 4 hours. Gamed on it. Benchmarked. Then it started again. Just seems odd that if it’s hardware, it’s fine sometimes and not fine others.

Click to expand...

Ok, so after Windows is setup, In what order do you install latest drivers? Do you make sure both Windows Update and Windows Store has done all it's updates before installing any 3rd party apps? What software do you install? Any 3rd-party AV? Sounds to me the issues begin when some Windows maintenance service starts...could be WU/MSStore/Cleanup Service/File Indexing...etc...

Any Gaming KB or Mouse apps installed?

SlicEnDicE said:

Ok, so after Windows is setup, In what order do you install latest drivers? Do you make sure both Windows Update and Windows Store has done all it's updates before installing any 3rd party apps? What software do you install? Any 3rd-party AV? Sounds to me the issues begin when some Windows maintenance service starts...could be WU/MSStore/Cleanup Service/File Indexing...etc...

Click to expand...

My order is:

Install windows
Install Armoury Crate (ASUS Software) and update all drivers/sets for BIOS
Install AMD Software and update GPU drivers

When you say “make sure windows update and windows store is done” what does that mean? Are they doing something in the background that I should wait on?

parkero1995 said:

My order is:

Install windows
Install Armoury Crate (ASUS Software) and update all drivers/sets for BIOS
Install AMD Software and update GPU drivers

When you say “make sure windows update and windows store is done” what does that mean? Are they doing something in the background that I should wait on?

Click to expand...

Yeah, when you clean install, both Windows Update and MS Store Updates has unfinished business...

SlicEnDicE said:

Yeah, when you clean install, both Windows Update and MS Store Updates has unfinished business...

Click to expand...

Okay so I can do that.

Would that cause BSODs during fresh installs? Like in the middle of the set up? Because the computer will do that sometimes. I have fresh installed so many times last few days it’s hard to remember which codes I’m getting but it happens.

What you could do before anything else, is fire up Event Viewer. From there Expand Windows Logs and save Application, Security/Setup and System logs to their own files, then zip them up and post here. There may be some clues in there about where and when something went wrong.

parkero1995 said:

Would that cause BSODs during fresh installs? Because the computer will do that sometimes.

Click to expand...

Yeah, sometimes when you install manually some stuff and then WU and Store also want to update, they can conflict...

It is important to reboot between certain updates.

Chipset Driver is the foundation for everything so that one should be installed separately and manually rebooted before doing anything else.

SlicEnDicE said:

Yeah, sometimes when you install manually some stuff and then WU and Store also want to update, they can conflict...

It is important to reboot between certain updates.

Chipset Driver is the foundation for everything so that one should be installed separately and manually rebooted before doing anything else.

Click to expand...

I will reinstall windows today and do what you’ve suggested.

Do you have any suggestions on how I could rule out the CPU/Motherboard? I’ve already replaced the SSD and Ram without resolution.

The oddity to me is the BSODs during windows re-installation which indicates hardware. If it’s CPU, it’s odd that sometimes after install the computer runs fines for a couple of hours. If it’s MOBO, wouldn’t I expect other issues than just BSODs?

parkero1995 said:

Do you have any suggestions on how I could rule out the CPU/Motherboard? I’ve already replaced the SSD and Ram without resolution.

Click to expand...

Yes.

1. Remove dGPU
2. Reset BIOS to defaults (important)
3. Update BIOS to latest
4. Reset BIOS to defaults(even more important)
5. Predownload most MB drivers
6. Predownload Prime95
7. Predownload HWInfo or similar small tool to monitor temps.
8. Do a fresh Windows install (ensure it's pretty recent creation)
9. Install Chipset Driver
10. Reboot
11. Let Windows update install rest of the drivers
12. Reboot
13. Then install all still missing drivers
14. Run Prime95 for 10-15minutes and monitor CPU temps with HWInfo.

If you get a crash, take note of BSOD code, stop testing and grab crashlogs either by using the log collector found at this forum or at minimum at least export the main Event lists from Event Viewer.

Altermatively you can use Armory Crate, but that in it self could be an issue to consider. Thus manual install. You don't need HWInfo if you use AC, since that let's you monitor CPU temps.