Pc keeps Blue Screening

[Fryered]

After installing and opening Minecraft mods from Curseforge (application not the browser), my pc kept blue screening. Even after going to Microsoft Support twice, both told me to wipe and reinstall W11, and getting a new M.2 ssd to install W11 on.
However the problem keeps persisting, even after the installs and the new M.2 SSD.

I've had this PC a month before all before this all these issues started.

Note: Also between replacing an ssd, i did also switch my old GPU with a new one.

I updated the bios and cleared the CMOS, still blue screen.

My pc has been to repairstore but the only thing they concluded is that it could be the motherboard being faulty or the graphics card (or that i accidentally have caused the cpu short circuit.) According to the guy that checked, he tested the motherboard without my GPU with another one, the BSOD did became less but did not go away.

I send the motherboard back to store where i bought it from for repairs, they said the motherboard had no issues when testing it and they also updated the bios. (However when i got it back, i couldnt install windows 11 anymore. doing every test in W10 now)
In the beginning it was fine but after running for a few hours and updating W10 + drivers. It started blue screening again.
I still get bluescreened even when im just starting up the PC.

I put a different cpu (12th gen instead 13) to test if it was the cpu causing the issues but then i get met with a black screen. So im stuck and I dont know what to do, any advice or tips is appreciated.

ZIP with 2 Minidumps
https://drive.google.com/file/d/126Vcuqr-EPRrPfqWy3gddduG0_57wIuE/view?usp=sharing

 

BSOD Codes:
beginning of the issue:
System service exception
Bad pool caller
Kmode exception not handled
IRQL not less or equal
Fltmgr

recent ones:
Page fault in non paged area
Bad Object Header
Bugcode NDIS driver
Driver irql not less or equal
system thread exception not handled


INFO:
x64 Based System
W11 installed myself
Built at the beginning of May

(currently running on W10)

CPU I7 13700K
NZXT Kraken Z53
Asus Prime Z790-P WIFI
G.Skill Trident Z neo 64 GB (2x 32GB) (both are memtested and passed)
Corsair RMx 1000W

(Old SSD) Samsung 970 EVO Plus 2TB
(New SSD) WD Black SN850X 2TB

Seagate Barracuda 6TB 3.5'' (only used to install games on)

(Old GPU) Sapphire Radeon 580
(New GPU) MSI Geforce RTX 4070

(I know this is way overpowered for modded Minecraft, but I was planning on playing God Of War or any of the recent Resident Evil games)

[ioletsgo]

Sounds like a driver problem. Did you DDU the Windows install?

[Fryered]

21 minutes ago, ioletsgo said:

Sounds like a driver problem. Did you DDU the Windows install?

I removed the windows installs with secure boot.

[ioletsgo]

1 minute ago, Fryered said:

I removed the windows installs with secure boot.

Try the Display Driver Uninstaller https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

[Bjoolz]

Doing any kind of analysis from just two dump files will not be super accurate so I'm going to list a few things. One looks just like RAM, nothing really blamed it just found a page fault which means that data in RAM was wrong. The other one was the Filter Manager driver finding something wrong. The Filter Manager driver's job is to make sure files are handled correctly which usually means a corruption or drive issue.

 

RAM and storage can look a lot like each other because low priority RAM is put on the storage drive in the page file. Where the bad data is detected will determine what it looks like, but you can't know where the corruption happened.

 

From this though, it looks like RAM or storage. Just from your other crashes that you listed it sounds more like RAM because you aren't getting any crashes that directly blame storage. 

 

Your RAM speed should not be an issue, 2666MT/s should work just fine especially with just two sticks. I know you ran Memtest, but memory testers are note really reliable with DDR4 and newer. I much prefer having the user use the machine normally with one stick at a time and see which one crashes. Please test both in case both crash or if both are stable when used alone as this changes the suspect. 

 

Also scan the OS for corruption using SFC. The OS can corrupt from crashes and if there is corruption you could still get crashes even when testing with just the good RAM stick which would ruin the testing. 

[Fryered]

On 7/30/2023 at 4:27 AM, Bjoolz said:

Doing any kind of analysis from just two dump files will not be super accurate so I'm going to list a few things. One looks just like RAM, nothing really blamed it just found a page fault which means that data in RAM was wrong. The other one was the Filter Manager driver finding something wrong. The Filter Manager driver's job is to make sure files are handled correctly which usually means a corruption or drive issue.

 

RAM and storage can look a lot like each other because low priority RAM is put on the storage drive in the page file. Where the bad data is detected will determine what it looks like, but you can't know where the corruption happened.

 

From this though, it looks like RAM or storage. Just from your other crashes that you listed it sounds more like RAM because you aren't getting any crashes that directly blame storage. 

 

Your RAM speed should not be an issue, 2666MT/s should work just fine especially with just two sticks. I know you ran Memtest, but memory testers are note really reliable with DDR4 and newer. I much prefer having the user use the machine normally with one stick at a time and see which one crashes. Please test both in case both crash or if both are stable when used alone as this changes the suspect. 

 

Also scan the OS for corruption using SFC. The OS can corrupt from crashes and if there is corruption you could still get crashes even when testing with just the good RAM stick which would ruin the testing. 

I tested with both sticks one at a time but both result in blue screening.

 

edit 1:

Also I tried the sfc scan however I get met with a "windows resource protection could not perform the requested operation"

 

I'm gonna try again when I get into the OS itself or safe mode with command prompt

 

 

Edit 2:

Managed to do an sfc scannow in safe mode w/ cmd, it did repair something. Also tried again with a single ram stick. It doesn't blue screen on start up anymore, but it takes a minute or 2 for it blue screen on home screen.

 

3 bsod codes:

2× BSOD code System thread exception not handled

1x system service exception

 

Edit 3:

Tried both as single ram again but still blue screens on both even on start up.

 

I went back in to get more Minidumps, i hope this helps:
https://drive.google.com/file/d/1l4TmaL0HSMLAxAYL1T8eEbtryOgSDlpa/view?usp=sharing

[Bjoolz]

8 hours ago, Fryered said:

I tested with both sticks one at a time but both result in blue screening.

 

edit 1:

Also I tried the sfc scan however I get met with a "windows resource protection could not perform the requested operation"

 

I'm gonna try again when I get into the OS itself or safe mode with command prompt

 

 

Edit 2:

Managed to do an sfc scannow in safe mode w/ cmd, it did repair something. Also tried again with a single ram stick. It doesn't blue screen on start up anymore, but it takes a minute or 2 for it blue screen on home screen.

 

3 bsod codes:

2× BSOD code System thread exception not handled

1x system service exception

 

Edit 3:

Tried both as single ram again but still blue screens on both even on start up.

 

I went back in to get more Minidumps, i hope this helps:
https://drive.google.com/file/d/1l4TmaL0HSMLAxAYL1T8eEbtryOgSDlpa/view?usp=sharing

Pretty much the same impression as before, but it looks more like RAM. This really gives us three possibilities in my mind.

 

1. The OS is broken and that's why it's crashing when using both sticks alone. Crashing can break the OS and you had some trouble running SFC. Ideally you would wipe the drive and clean install the OS and then test the RAM using the same method of one stick at a time as before. I know it can be a pain in the ass. 

 

2. The storage is broken and it's manifesting a bit weird. You have two crashes that have the Filter Manager driver involved and while these can indicate storage you usually get crashes that more directly say "storage is bad". 

 

3. The memory controller in the CPU is faulty. If this is bad it will just look like RAM. 

 

These three are not really in any kind ranking of most likely, except perhaps the first one. 

Updating the BIOS was worth a shot, I see that you are on the latest BIOS. 

[Fryered]

1 hour ago, Bjoolz said:

Pretty much the same impression as before, but it looks more like RAM. This really gives us three possibilities in my mind.

 

1. The OS is broken and that's why it's crashing when using both sticks alone. Crashing can break the OS and you had some trouble running SFC. Ideally you would wipe the drive and clean install the OS and then test the RAM using the same method of one stick at a time as before. I know it can be a pain in the ass. 

 

2. The storage is broken and it's manifesting a bit weird. You have two crashes that have the Filter Manager driver involved and while these can indicate storage you usually get crashes that more directly say "storage is bad". 

 

3. The memory controller in the CPU is faulty. If this is bad it will just look like RAM. 

 

These three are not really in any kind ranking of most likely, except perhaps the first one. 

Updating the BIOS was worth a shot, I see that you are on the latest BIOS. 

ive wiped the drives for installing windows a couple of times but i used secure boot to do that. Do you know a better way for a clean install?

might it also have to do something with Intel ME? because ive had issues installing the drivers for that in the past as well.

[Bjoolz]

31 minutes ago, Fryered said:

ive wiped the drives for installing windows a couple of times but i used secure boot to do that. Do you know a better way for a clean install?

Just deleting all the partitions while in the installer is enough, doing this is if anything overkill. 

 

31 minutes ago, Fryered said:

might it also have to do something with Intel ME? because ive had issues installing the drivers for that in the past as well.

I would have expected to see something from the Chipset driver if that was the case, but I don't. 

[Fryered]

19 minutes ago, Bjoolz said:

Just deleting all the partitions while in the installer is enough, doing this is if anything overkill.

Could that have an effect on the drive or no? Asking because im curious

[Bjoolz]

11 minutes ago, Fryered said:

Could that have an effect on the drive or no? Asking because im curious

I assume you meant secure erase and not secure boot. If that assumption is correct it should not affect the drive's health. 

[Fryered]

2 hours ago, Bjoolz said:

Pretty much the same impression as before, but it looks more like RAM. This really gives us three possibilities in my mind.

 

1. The OS is broken and that's why it's crashing when using both sticks alone. Crashing can break the OS and you had some trouble running SFC. Ideally you would wipe the drive and clean install the OS and then test the RAM using the same method of one stick at a time as before. I know it can be a pain in the ass. 

 

Did a clean install, but during the windows updates it blue screened. I had one ram stick in during this.

System service exception, fltrmsys

[Bjoolz]

4 hours ago, Fryered said:

Did a clean install, but during the windows updates it blue screened. I had one ram stick in during this.

System service exception, fltrmsys

Try the other stick as well. If you get a fltmgr.sys crash again then it's possibly storage, but it doesn't really feel like storage. 

[Fryered]

7 hours ago, Bjoolz said:

Try the other stick as well. If you get a fltmgr.sys crash again then it's possibly storage, but it doesn't really feel like storage. 

Tried the other stick, also still blue screen with fltmgr.sys

Minidumps from other stick:
https://drive.google.com/file/d/1_j82w0ZYA0VxxEiRH3SbWQsHimRWwByj/view?usp=sharing

[Bjoolz]

5 hours ago, Fryered said:

Tried the other stick, also still blue screen with fltmgr.sys

Minidumps from other stick:
https://drive.google.com/file/d/1_j82w0ZYA0VxxEiRH3SbWQsHimRWwByj/view?usp=sharing

Do you have a different storage drive you could try installing to? And please remove the other drive completely when doing this. 

[Fryered]

23 minutes ago, Bjoolz said:

Do you have a different storage drive you could try installing to? And please remove the other drive completely when doing this. 

I have it installed on the new M.2. But ill try again on the old one. also a M.2

[Fryered]

47 minutes ago, Bjoolz said:

Do you have a different storage drive you could try installing to? And please remove the other drive completely when doing this. 

During the install it also bluescreened on the other m.2

BSOD code:
IRQL not less or equal

[Bjoolz]

44 minutes ago, Fryered said:

During the install it also bluescreened on the other m.2

BSOD code:
IRQL not less or equal

Confusing. That it mentions FLTMGR.sys suggests that files are not handled properly, but you still crash on the other M.2. Different crash now though, could you try the other RAM stick with that other SSD? 

[Fryered]

3 hours ago, Bjoolz said:

Confusing. That it mentions FLTMGR.sys suggests that files are not handled properly, but you still crash on the other M.2. Different crash now though, could you try the other RAM stick with that other SSD? 

Tried the other stick, it was working fine for a few minutes until i restarted it and Blue screened again.

BSOD Apex_Index_mismatch
also a wdfilter.sys

[Bjoolz]

1 hour ago, Fryered said:

BSOD Apex_Index_mismatch
also a wdfilter.sys

I assume you mean APC_Index_Mismatch. It's a really generic crash that can be seen with a lot of stuff, wdfilter.sys is part of Windows Defender and has sort of the same purpose as FLTMGR.sys, but more isolated to working with Windows Defender. 

 

I don't really know what it could be. Perhaps the motherboard? It doesn't feel like the CPU, GPU or power. 

[Fryered]

2 hours ago, Bjoolz said:

I assume you mean APC_Index_Mismatch. It's a really generic crash that can be seen with a lot of stuff, wdfilter.sys is part of Windows Defender and has sort of the same purpose as FLTMGR.sys, but more isolated to working with Windows Defender. 

 

I don't really know what it could be. Perhaps the motherboard? It doesn't feel like the CPU, GPU or power. 

It's not the gpu because the gpu hasn't been in the rig during the tests. Also the motherboard doesn't have any indicator lights or something indicating for other parts, so it isn't really helpful.

[Fryered]

On 8/2/2023 at 1:08 AM, Bjoolz said:

I assume you mean APC_Index_Mismatch. It's a really generic crash that can be seen with a lot of stuff, wdfilter.sys is part of Windows Defender and has sort of the same purpose as FLTMGR.sys, but more isolated to working with Windows Defender. 

 

I don't really know what it could be. Perhaps the motherboard? It doesn't feel like the CPU, GPU or power. 

I replaced the motherboard, with a different one (from a Asus Prime Z790-P to a MSI B760 Tomahawk, this one does have debug lights) however i still get blue screens and no debug lights are lighting up for a faulty comp. Also it wont recognize my video card for some reason (well the repair guy said the video card might be faulty as well so, also i did remove the gpu from the rig, to see if anything changed but still bluescreen)

Im running driver verifier now, and rebooted the system but so far no blue screens.

Here are the minidumps:
https://drive.google.com/file/d/1ezvQWspG7aEqgloyNgVM6KrVO6qLXEMS/view?usp=sharing

[Bjoolz]

16 hours ago, Fryered said:

I replaced the motherboard, with a different one (from a Asus Prime Z790-P to a MSI B760 Tomahawk, this one does have debug lights) however i still get blue screens and no debug lights are lighting up for a faulty comp. Also it wont recognize my video card for some reason (well the repair guy said the video card might be faulty as well so, also i did remove the gpu from the rig, to see if anything changed but still bluescreen)

Im running driver verifier now, and rebooted the system but so far no blue screens.

Here are the minidumps:
https://drive.google.com/file/d/1ezvQWspG7aEqgloyNgVM6KrVO6qLXEMS/view?usp=sharing

It looks like RAM again. Page fault, Windows process, iGPU driver, the kernel, network driver. All over the place like you see with RAM.

 

RAM has been pretty much ruled out, perhaps it actually is the memory controller on the CPU and the string of different filter drivers you saw was just coincidence. Or because it was during the OS install and all that data has to pass through RAM before it's put on the disk it might be normal for the filter driver to catch it. Not sure. 

[Fryered]

4 hours ago, Bjoolz said:

It looks like RAM again. Page fault, Windows process, iGPU driver, the kernel, network driver. All over the place like you see with RAM.

 

RAM has been pretty much ruled out, perhaps it actually is the memory controller on the CPU and the string of different filter drivers you saw was just coincidence. Or because it was during the OS install and all that data has to pass through RAM before it's put on the disk it might be normal for the filter driver to catch it. Not sure. 

So i should replace the RAM? i'm not sure if i follow

[Bjoolz]

54 minutes ago, Fryered said:

So i should replace the RAM? i'm not sure if i follow

With the testing you did on the RAM it's very unlikely to be RAM and you have ruled out storage. That makes the next suspect the CPU.