Windows 10 BSOD since april (plis help)

Hello guys!, I'm here needing of help and I hope to contribute someday and return the help.
First of all sorry for my english, it's not my native language.
My PC
Windows 10 pro 20h2 and partition Windows 7 ultimate. win 10 900GB and Windows 7 with 100GB.
I7 4790 3.60Mhz

Gigabyte GA-H97-Gaming 3 (3 PCI, 2 PCI-E x1, 2 PCI-E x16, 1 M.2, 4 DDR3 DIMM, Audio, Video, Gigabit LAN)

G Skill RipjawsX 16GB en total (2 modulos iguales de 8GB)

WDC black 1 1000gb 7200rpm

EVGA Geforce GTX 1070 SC GAMING

PSU Thermaltake Smart 650w 80 Plus Bronze Modular.

I'll try to explain in short words the problem because this is from Months.
The BSOD Started in 04/18/202 while I was playing assassins creed valhalla (btw is Always while I'm playing any game).
After that I tried to play again and at the 5 min again BSOD.

That Day I "fixed" the problem doing this
_Uninstall drivers with DDU.
_Installed the new ones.
_and Clear CMOS.

It worked for a week, then again BSOD, after that in microsoft forum an admin recommend me to use the commands dism
in this order (Honestly I dont know if is ok or if the same)
dism /online /cleanup-image /StartComponentCleanup
dism /online /cleanup-image /CheckHealth
dism /online /cleanup-image /ScanHealth
dism /online /cleanup-image /RestoreHealth
and after that
sfc /scannow

at the next 7 days again happened and again and again.
Until one day in the BSOD Appeared "kmode exception not handled"
with iaStorA.sys was the error.
So I discovered was intel rapid storage technology ( I never had a problem before and I had Win 10 since 2019 installed with that so I dont know why suddenly started to work bad)
----------------------------------------------------------------------------------------------------------------
All fixed until the last 06/23/2021 when I wanted to upgrade like always I did my Windows 20h2 to 21h1 through windows update.

everything was fine, restart the PC, ect ect...after that also installed the optional KB5003690 (something I never do btw).
and after that I installed the nvidia drivers 471.11 because I was with the 466.11 and wanted to upgrade.

After that all my problems back.
After 20 min playing a game again and always the BSOD. I'm going to explain short because this part is more long.
1_ uninstalled with DDU the nvidia 471.11 and installed 466.63.
2_uninstalled the update so back to Windows 20h2.
3_All worked fine after that...but how im a f*/3k genius, I decided to install again windows 21h1, but how its not possible from Windows update like the first time, I use app assistant to update.
4_after that all going to hell again, I wanted to kill myself.
5_I did a rollback to windows 20h2 and after a sfc /scannow and use dism command all "worked" again fine.

Until the last 07/02/2021 when the only thing I did was to install a game (blair witch from the epic game store).
and again the BSOD back, after 20 min with every game (I had 2 installed now Jurassik park and f1 2020)

I "fixed" the problem (honestly I dont know) with a
chkdsk c: /r
and all worked for until today when I writting this message.
but honestly I dont know if is fixed.

and btw I have a few doubts before to use the tool of re installa windows.
1_After uninstall the IRST now appear "controladora SATA AHCI estandar" like in this image.



but in windows 7 appear like this "Intel(R) chipset family SATA AHCI controller


Maybe is that the problem?
BTW I tested the HDD with the CrystalDisk and is all "good" blue. and I tested again with another program named Victoria and only appear one sector as "orange" the criticals are red and blue but I have not any of those.

It would be great a if someone help me with a guidance if there's no other way to re install windows. especially the part of install drivers again, due I think that's exactly what got me here. Thanks.

 

You would gain bonus info on BSODs with the help of such tools as BlueScreenView or WhoCrushed

 

Do you know from where it's possible to download those tools?
to avoid virus.
btw this link contain 1 of my latest BSOD

"kmode exception not handled" FLTMGR.SYS

https://1drv.ms/u/s!Aqw-LiNtQrt6kF3sBcS1U1QdKS-X?e=CNPJ94

 

This is likely damaged memory corrupting the state of the storage driver/filters.

Win-raid has a thread that advises on the best drivers to use for the various vendor ahci/raid hosts.

i believe z97 does as far as 14.8.18.10660

The crash is not in fltmgr, its being triggered due to an exception while reading xpress compacted file system data, either something that shouldn't be has been forcibly compacted or memory is faulty

STACK_TEXT:
ffff988e`1828b1d8 fffff805`1de3b905 : 00000000`0000001e ffffffff`c0000005 fffff805`1fdbc3b2 00000000`00000000 : nt!KeBugCheckEx
ffff988e`1828b1e0 fffff805`1de08cac : 00000000`00001000 ffff988e`1828ba80 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x1b5985
ffff988e`1828b8a0 fffff805`1de04e43 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffff988e`1828ba80 fffff805`1fdbc3b2 : ffff988e`18286000 ffff988e`1828c000 00000000`00000000 fffff805`1fdcd440 : nt!KiPageFault+0x443
ffff988e`1828bc10 fffff805`1fdb4244 : ffffb18f`2732a548 00000000`00000000 00000000`00000000 ffff988e`1828be30 : FLTMGR!FltpFreeMdlChain+0x12
ffff988e`1828bc40 fffff805`20831a8b : ffffb18f`2732a5d8 ffff988e`1828be30 ffff988e`1828bda0 ffffb18f`2732a548 : FLTMGR!FltFreeCallbackData+0x74
ffff988e`1828bc80 fffff805`208314ee : ffff988e`1828bda0 00000000`00001000 00000000`00000000 00000000`00000004 : Wof!FileProvCompleteRead+0x8b
ffff988e`1828bcb0 fffff805`2083123e : ffff988e`1828bda0 ffffc588`78b73590 00000000`00001000 00000000`00000000 : Wof!FileProvReadCompressedCompletionWorker+0x17e
ffff988e`1828bce0 fffff805`2084fcaa : 00000000`00001000 ffff988e`1828bda0 ffffc588`78b73590 00000000`00000000 : Wof!FileProvReadCompressedCompletion+0x3e
ffff988e`1828bd20 fffff805`2084f3cd : ffffb18f`2732a548 00000000`00000001 00000000`00000004 00000000`00001000 : Wof!FileProvReadCompressed+0x1da
ffff988e`1828bd80 fffff805`2084f8ca : 00000000`00000000 ffffc588`78b73590 ffffc588`78b735b0 ffffc588`782fe000 : Wof!FileProvBuildChunkTable+0x14d
ffff988e`1828bec0 fffff805`2083547e : ffffb18f`267e0000 ffff988e`182c9150 ffff988e`182c8f02 00000000`00000001 : Wof!FileProvReadCompressedOnNewStack+0x2ca
ffff988e`1828bf50 fffff805`1ddfa46e : ffff988e`182c9280 ffff988e`1828bfd0 00000000`00000000 00000000`00000000 : Wof!FileProvReadCompressedCallout+0xe
ffff988e`1828bf80 fffff805`1ddfa42c : ffff988e`1828bfd0 ffffb18f`1dceb080 ffff988e`1828c000 fffff805`1dc98efd : nt!KxSwitchKernelStackCallout+0x2e
ffff988e`1874d840 fffff805`1dc98efd : ffff988e`1828bfd0 ffffb18f`1dceb080 ffff988e`1874d900 000000ff`00000000 : nt!KiSwitchKernelStackContinue
ffff988e`1874d860 fffff805`1dc98cf2 : fffff805`20835470 ffffb18f`2751c7d8 00000000`00000002 00000000`00000000 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x19d
ffff988e`1874d900 fffff805`1dc98b53 : ffffb18f`272a0548 ffffb18f`2751c7d8 fffff805`00000000 ffffb18f`1e345010 : nt!KiExpandKernelStackAndCalloutSwitchStack+0xf2
ffff988e`1874d970 fffff805`1dc98b0d : fffff805`20835470 ffffb18f`2751c7d8 fffff805`20846800 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x33
ffff988e`1874d9e0 fffff805`20851e53 : ffffb18f`2751c7d8 00000000`00000000 ffffffff`00000010 00000002`ffffffff : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffff988e`1874da20 fffff805`20851c7e : ffffb18f`2751c7d8 ffffb18f`272a0548 00000000`00000000 fffff805`208503ad : Wof!FileProvReadCompressedSwitchStacks+0x53
ffff988e`1874da60 fffff805`208325e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wof!FileProvCbRead+0x12e
ffff988e`1874dac0 fffff805`1fdb608b : ffff988e`1874ddb0 00000000`00000001 ffffb18f`00000000 ffffc588`78b73550 : Wof!WofPreReadCallback+0x270
ffff988e`1874db80 fffff805`1fdb5b37 : ffff988e`1874dd00 00000000`ffffff03 ffffb18f`27653200 00000000`00000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x36b
ffff988e`1874dca0 fffff805`1fdb4b46 : ffff988e`18750000 ffff988e`1874a000 00000000`00000000 ffff988e`1874ddc0 : FLTMGR!FltpPassThroughInternal+0xc7
ffff988e`1874dcf0 fffff805`1fdb48bb : 00000000`00000000 00000000`00000000 ffffeb80`05ffee90 ffff988e`1874e181 : FLTMGR!FltpPassThrough+0x1d6
ffff988e`1874dd90 fffff805`1dd18545 : ffffb18f`26a3a560 fffff805`1dc27bd5 00000000`00000000 00000000`00000000 : FLTMGR!FltpDispatch+0x8b
ffff988e`1874ddf0 fffff805`1dc27e97 : 00000000`00000000 ffffb18f`26a3a560 ffffb18f`230fd2a0 ffffb18f`27653210 : nt!IofCallDriver+0x55
ffff988e`1874de30 fffff805`1dc5e04a : 00000000`00000006 fffff805`1dc295f2 ffffb18f`230fd2b0 ffffb18f`230fd270 : nt!IoPageReadEx+0x1d7
ffff988e`1874dea0 fffff805`1dc5bb4d : 00000000`00000002 ffff988e`1874df30 ffff988e`1874e0a8 ffffb18f`230fd250 : nt!MiIssueHardFaultIo+0xb6
ffff988e`1874def0 fffff805`1dd28208 : 00000000`c0033333 00000000`00000000 00000236`2ac70000 ffffc588`73a131b0 : nt!MiIssueHardFault+0x29d
ffff988e`1874dfb0 fffff805`1dc486fa : 00000000`00044069 ffffc588`79ee0510 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x468
ffff988e`1874e150 fffff805`1e006a6c : 00000000`00000000 ffffb18f`1dceb080 00000000`00000000 ffff988e`00000000 : nt!MiPrefetchVirtualMemory+0x28a
ffff988e`1874e250 fffff805`1de085b8 : ffffc588`731fc198 ffffb18f`1dceb080 fffff805`1ff45080 ffff988e`1874e640 : nt!NtSetInformationVirtualMemory+0x64c
ffff988e`1874e5c0 fffff805`1ddfa9f0 : fffff805`1ff4ac93 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
ffff988e`1874e7c8 fffff805`1ff4ac93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
ffff988e`1874e7d0 fffff805`1ff4ba37 : ffff988e`1874e9b0 ffffc588`731fc150 00000000`0000800c 00000000`00000000 : CI!I_MapCatalog+0x3cb
ffff988e`1874e8c0 fffff805`1ff4b5e3 : 00000000`00000000 ffffc588`79e85670 ffff988e`1874ea21 00000000`00000054 : CI!I_ReloadCatalog+0x263
ffff988e`1874e940 fffff805`1ff4b2b1 : 00000000`00008001 ffff988e`00000000 00000000`00000000 00000000`00000001 : CI!I_ReloadCatalogDirectory+0x297
ffff988e`1874ea70 fffff805`1ff4971a : 00000000`00000000 ffff988e`00000001 ffff988e`1874ebe0 00000000`00000004 : CI!I_ReloadCatalogs+0x1ad
ffff988e`1874eae0 fffff805`1ff494c1 : ffff988e`00001000 ffff988e`1874ee54 ffffb18f`23560010 fffff805`1dd198c7 : CI!I_FindFileOrHeaderHashInCatalogs+0x24a
ffff988e`1874ec40 fffff805`1ff55442 : 00000000`0000800c ffffc588`6f89f010 ffff988e`1874edc0 ffffb18f`1bd0e7f0 : CI!MinCrypK_FindPageHashesInCatalog+0xb1
ffff988e`1874ecf0 fffff805`1ff50fbc : ffffc588`0000006f 00000000`00000000 00000000`00000000 00000000`00000004 : CI!CiVerifyPageHashInCatalogs+0x192
ffff988e`1874edf0 fffff805`1ff523b2 : 00000000`00000000 ffff988e`1874f131 00000000`00000000 ffffc588`6f89f010 : CI!CipGetPageHashesForFile+0x190
ffff988e`1874ef50 fffff805`1ff518bb : ffffc588`6f89f010 ffffb18f`26f3c840 ffffb18f`262ec080 ffffc588`77cfb000 : CI!CipValidatePageHash+0x2b2
ffff988e`1874f040 fffff805`1ff4fc63 : 00000000`00000084 00000000`00000000 ffffb18f`26f3c840 ffffc588`77cfb000 : CI!CipValidateImageHash+0x10f
ffff988e`1874f180 fffff805`1e09c4dd : 00000000`68496d4d fffff805`1dd154ef 00000000`00000517 ffffc588`77cfb000 : CI!CiValidateImageHeader+0x783
ffff988e`1874f300 fffff805`1e09bfe8 : 00000000`00000008 ffffb18f`222cac00 ffffb18f`222cac00 00000000`00001000 : nt!SeValidateImageHeader+0xd9
ffff988e`1874f3b0 fffff805`1e00604f : ffff988e`1874f560 00000000`00000240 00000000`00000000 00000000`00000000 : nt!MiValidateSectionCreate+0x438
ffff988e`1874f590 fffff805`1e005f7d : ffff988e`1874f840 ffff988e`1874f840 00000000`00000002 00000000`00000002 : nt!MiValidateSectionSigningPolicy+0xab
ffff988e`1874f5f0 fffff805`1dffa52f : 00000000`00000001 ffff988e`1874f840 ffffc588`6f5ecf50 ffffb18f`222cac00 : nt!MiValidateExistingImage+0x371
ffff988e`1874f6a0 fffff805`1dffb2ed : 00000000`00000000 ffff988e`1874f840 ffffb18f`1dceb080 ffffb18f`26f3c840 : nt!MiShareExistingControlArea+0xc7
ffff988e`1874f6d0 fffff805`1dffaa64 : ffffb18f`222cac00 00000000`00000000 ffffb18f`26f3c840 00000000`00000000 : nt!MiCreateImageOrDataSection+0x1ad
ffff988e`1874f7c0 fffff805`1dffa847 : 00000000`01000000 ffff988e`1874fb80 00000000`00000001 00000000`00000010 : nt!MiCreateSection+0xf4
ffff988e`1874f940 fffff805`1dffa62c : 00000085`40cc7a78 00000000`0000000d 00000000`00000000 00000000`00000001 : nt!MiCreateSectionCommon+0x207
ffff988e`1874fa20 fffff805`1de085b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateSection+0x5c
ffff988e`1874fa90 00007ff8`f7b0d764 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000085`40cc7a28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`f7b0d764


SYMBOL_NAME: Wof!FileProvCompleteRead+8b

MODULE_NAME: Wof

IMAGE_NAME: Wof.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 8b

FAILURE_BUCKET_ID: 0x1E_c0000005_R_Wof!FileProvCompleteRead

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c6b2f8c8-2c51-0e9e-524f-69ff321eb2a6}

Followup: MachineOwner
---------

Turn CompactOS off for starters.

The HardFaults are illegal in that stack, so something has double freed or the data is damaged.

 

Disable the compact stuff as Astyanax says. Also, do you have core isolation/memory integrity enabled? If yes, try to turn it off (it should not directly related but I saw you have logitech joystick stuff installed, and they are well known to trigger random BSOD with memory integrity enabled).

 

on 2xhx memory integrity now scans for incompatible drivers and refuses to enable in their presence.

 

I have only a Logitech G502 Mouse and Genius GX K6 as a keyboard,
the logitech software version is 8.90.117



The keyboard is using the default drivers windows provide.

I'll try first with core isolation/memory integrity and disable.

about turn off CompactOS, I have a few questions first if you dont mind. and thanks, lets see what happen first with disabling core isolation/memory integrity

Oh BTW I would like to know more about what you said before

"Win-raid has a thread that advises on the best drivers to use for the various vendor ahci/raid hosts"

This is my motherboard
https://www.gigabyte.com/mx/Motherboard/GA-H97-Gaming-3-rev-10#ov

 

x99 and z97 should both be on 14.8.18.10660 at the minimum unless using RSTe mode.

 

Ok I've been checking

First_ core isolation/memory integrity was already disabled, and I think it was all this time disabled. So I guess the problem its not there.
second_ I found this https://downloadcenter.intel.com/es...og-a-de-almacenamiento-Intel-Rapid-Intel-RST-
is 14.8.16.1063
unfortunately when I uninstalled the last time I didn't check the version before, so I dont know which version was installed before.
There's other ones more new but honestly I dont know if more new means much better or free of troubles.

Third_ I've found some of info about turn off CompactOS and I think its not a good idea.
If in the process the electricity is gone, windows its not going to start anymore. and where I living lately electricity is not your best friend.

I would like your advice

Last time I did an chkdsk with this command chkdsk C: /r but I've found its possible to write chkdsk C: /f /r and its more complete...or its the same with /r only ??
and after that execute sfc /scannow
and then
1º dism /online /cleanup-image /CheckHealth
2º dism /online /cleanup-image /ScanHealth
3º dism /online /cleanup-image /RestoreHealth

in that order is ok?
so in that way I''l be sure I did everything possible before to RE install windows.

After that test again with a few games already installed and if everything works fine. Going to proceed to install a new game like before and test if still working without a problem.

If again the BSOD appear, I could try to install the RSTe 14.8.16.1063 and check again with the games.
and If the problems continue, I'll need to star to think in RE install windows and I hope it works.

what you think?

 

I bet it's a compact bug.

 

After yesterday I'm planning to re install windows through the tool that windows provide (I hope it works)
I was playing f1 2020 and suddenly after 5 min again a BSOD...and thats nothing, after reebot the PC at the beggining while the SO were starting again another one, and thats never happened to me before with any SO.... so Im pretty sure this is a mess after the update, uninstall, try to install again and then rollback, The SO is a mess and honestly I feel like is a little bit slower than before of all I did.... so I guess is the only way.

The only Thing I request is help later with the drivers to not make a mess again.

 

BTW
I found this tool to help me with drivers, what do you think guys? its safe?

1_Intel-Driver-and-Support-Assistant-Installer
2_Driver booster

 

Don't use suck "tools". To be honest, you should find 99% of the time drivers via Windows Update. Using specific sata/raid and network drivers is necessary most of times only if you want access to additional chipset features not available via the common WDM interface.

 

I agree with you completely but the problem is when you have a PC with 5 year old, you have no idea if is good an updated version or better the old and probably more stable.
I had to use Driver booster to find one for my chipset, the interesting thing is the program show you all the updated and non updated drivers you have and let you choose or not.

For now I re installed Windows and since yesterday im testing what happen. I hope it works, for now is all ok.

 

Hey guys, one thing I remember before all this happen, I think it was in january when started. One day I tried to defragment my HDD like always I did it when I install a new game or a big update and I use O&o Defrag, that day when I defragmented the HDD 1 of files (It was for Cyberpunk2077) it was not possible to defrag, something weird that never happened before but the PC was running well on those days, but after that I uninstalled another game and after that, the O&o defrag was able to defrag that file, then later happened the same with assasins creed valhalla, one of the files it was not possible to defrag and it always was a file of between 11 to 13gb and my HDD wasnt full i bet it was with 328 GB free from 830gb aprox.

I remember to had the HDD with 229GB of free space and the O&O defragmented perfectly all the files.

so what thats mean when a defragment program cannot defrag a file who actually defragmented before and only is possible to defrag if you delete another files probably with the same weight.?

 

BSOD's are 90% caused by unstable Ram and or Ram settings in the bios....could be not stable at wanted timings or ram speed and this could also be linked to the current bios version in use on your motherboard. In some cases increasing ram voltage helps but not always. reinstall windows will help for a while, at least until it starts crashing again. pc is either stable or its NOT. Yours is clearly NOT at the moment.

 

if the file is too big and there is no enough free contiguous space for move it it will not be defragged even if you force it.