Question W10 getting corrupted frequently inevitablely ending in a BOSD

[King Zapata]

Hello everyone

So basically my PC sudenly wents totally nuts.

i have an already "old" PC wich was working fine, i ran games at 4k, softwares like premiere and photoshop and some others.

one day i turned on the PC and it says the files were corrupted so i turned it off and on and this time it worked fine, this lasted for days and it was good until one day it basically did the same, turned it off and on and again it worked but this time it gave me a BSOD some seconds lates just after log in the PC.

i reset the pc and tried again it worked fine for some hours now and then again BSOD.

i honestly didnt know exacly what was happening and i would say which BSOD error it gave but trust me, it probably gave me 10 different BSOD errors so far that i lost memory of the errors names,

i decided to do a clean install, downloaded all windows updates and the gpu nvidia driver and worked fine for a whole day i was like ok then, probably a virus or something, NOPE, next day the same Blue screen stating my pc is corrupted and that i will make some repairs, it did worked fine for some time and then again BSOD.

i decided to test the ram and turned it out it did placebo me cause the pc worked fine after i remove 2 sticks and left 2 8gb sticks only, 16 instead of 32, worked fine i was like, could it be that it was the ram, well no, cause when i started the pc next day CORRUPTED FILES WINDOWS WILL TRY TO REPAIR, but now instead of errors of BSOD it says something about strail.txt

I was like ok, probably the SSD is faulty so i decided to do a new clean install now in another SSD, did the whole process again, downloaded w updates and nvidia and some games to try and now it worked for a while but midgame the game crashes, no error, no message, just PFF back to the desktop you go, try to start the game in steam, click play button and it go to runnung then auto cancel back to the play button, wont let me launch games

is started gaving me BSOD no stop each time i do anything, browser some times closes itself or steam, or anything, BSOD 1 ,2 ,3 4 ,5 times, different errors each time.

did a final clean install and downloaded w updates and nvidia drivers, but now i did a sfc /scannow and it says there were error which could not be solved so i DSIM CLEAN AND RESTORE, detected and solved the error and the pc worked fine, turned the pc off to see if it solved the start up problems and it kinda did but i ran the SFC /SCANNOW again and you guess it, it found corrupted files again, so i did another scanhealt and restore and the problems were solved again but i bet when i turn the pc off and on in about an hour or 2 there will the the corrupted files again.

is like my PC is ill and everytime i dsim restore it it kinda gets better for a day just to get ill next morning.

any suggestions? or ideas?

 

[Colif]

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

 

[SkyNetRising]

any suggestions? or ideas?

List full specs of your system.
Diagnose storage devices.

How are you turning off your pc?
By normal shutdown or by holding down power button?
You should always use shutdown or file system corruption may occur.

 

[ubuysa]

Upload all mindumps (in C:\Windows\Minidump) to the cloud with a link to them here. Ensure they are publicly accessible (no need to login)

 

[King Zapata]

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

Hey thans for replying

I tested the 2 rams sticks i am currently using the way you suggested and after 4 passes i got no errors on each one

 

[King Zapata]

Upload all mindumps (in C:\Windows\Minidump) to the cloud with a link to them here. Ensure they are publicly accessible (no need to login)

minidump.rar

drive.google.com

thanks for replying, here is the link to the minudump, had to made a rar cause drive didnt let me upload the dmp file

 

[King Zapata]

List full specs of your system.
Diagnose storage devices.

How are you turning off your pc?
By normal shutdown or by holding down power button?
You should always use shutdown or file system corruption may occur.

PC specs

Asus rampage extreme iv
intel i7 4820k
2 x 8gb ddr3 g skill ripjaw series x (DDR3, 8192 MB, 64-bit, 1333 MHz F3-12800CL10-8GB)
3 sdd, samsung and kingston
2060 rtx gpu
PSU seasonic x ss 1050xm

i ve chkdsk the ssd but dont know if there is another way to diagnose them

yes pc turned off as should be , only hard reset when the pc stuck in a BSOD which for a reason doesnt end

 

[ubuysa]

I see that you have run Memtest86 on each stick, though personally I generally like to run it twice for a total of 8 iterations.

One dump (30th Nov) is a fairly common SYSTEM_SERVICE_EXCEPTION bugcheck. This indicates that the kernel took an exception and triggered the BSOD. The dump shows that the exception was a 0xC0000005, which indicates a memory access violation. This is an attempt to access memory that is either not allocated, is paged out (when page faults are not allowed), or the RAM holding that page is bad. The process in control was msedge.exe (the MS Edge browser) and the bugcheck occurred in the Windows fltmgr.sys driver - this is the filter manager driver and it manages many lower-level third-party filter drivers (which we don't see in the dump). I suspect that the most likely cause here may be a misbehaving extension in Edge, they do sometimes fail badly enough to cause a BSOD. Try starting Edge with all extensions disabled and monitor what happens.

The other dump (1st Dec) is unusual. It's an INTERRUPT_EXCEPTION_NOT_HANDLED bugcheck, which means that an exception occurred in the kernel interrupt manager. That could well be down to a bad ISR (interrupt Service Routine) from a misbehaving driver - it could even be the potentially bad Edge extension seen in the other BSOD. However, the fltmgr.sys driver was not involved in this BSOD, but the Nvidia graphics driver nvlddmkm.sys was. The exception code in the bugcheck was a 0xC000001D, which is an illegal instruction attempt caused by a misplaced instruction pointer. The Nvidia graphics driver might be at fault here, since it's called in the lead-up to the bugcheck, but it's also possible that nvlddmkm.sys failed due to an error by another driver that was called some time ago, which we don't see in the dump, and which caused the instruction pointer to be corrupted in a later function call.

All that said, based on what you describe in your origional post a hartdware cause of your troubles in way more likely and the dumps are strongly suggesting that bad RAM may be the cause. Are you sure that your RAM is on the QVL for the motherboard? If it's not that doesn't mean it won't work, but it does mean it's not been validated as compatible.

Try removing on stick and run on just one for a day or two, then swap sticks.

 

[King Zapata]

I see that you have run Memtest86 on each stick, though personally I generally like to run it twice for a total of 8 iterations.

One dump (30th Nov) is a fairly common SYSTEM_SERVICE_EXCEPTION bugcheck. This indicates that the kernel took an exception and triggered the BSOD. The dump shows that the exception was a 0xC0000005, which indicates a memory access violation. This is an attempt to access memory that is either not allocated, is paged out (when page faults are not allowed), or the RAM holding that page is bad. The process in control was msedge.exe (the MS Edge browser) and the bugcheck occurred in the Windows fltmgr.sys driver - this is the filter manager driver and it manages many lower-level third-party filter drivers (which we don't see in the dump). I suspect that the most likely cause here may be a misbehaving extension in Edge, they do sometimes fail badly enough to cause a BSOD. Try starting Edge with all extensions disabled and monitor what happens.

The other dump (1st Dec) is unusual. It's an INTERRUPT_EXCEPTION_NOT_HANDLED bugcheck, which means that an exception occurred in the kernel interrupt manager. That could well be down to a bad ISR (interrupt Service Routine) from a misbehaving driver - it could even be the potentially bad Edge extension seen in the other BSOD. However, the fltmgr.sys driver was not involved in this BSOD, but the Nvidia graphics driver nvlddmkm.sys was. The exception code in the bugcheck was a 0xC000001D, which is an illegal instruction attempt caused by a misplaced instruction pointer. The Nvidia graphics driver might be at fault here, since it's called in the lead-up to the bugcheck, but it's also possible that nvlddmkm.sys failed due to an error by another driver that was called some time ago, which we don't see in the dump, and which caused the instruction pointer to be corrupted in a later function call.

All that said, based on what you describe in your origional post a hartdware cause of your troubles in way more likely and the dumps are strongly suggesting that bad RAM may be the cause. Are you sure that your RAM is on the QVL for the motherboard? If it's not that doesn't mean it won't work, but it does mean it's not been validated as compatible.

Try removing on stick and run on just one for a day or two, then swap sticks.

Thanks for taking your time to reply

well i am not really sure if the ram is QVL for the motherboard, i ve been using this rams sticks since i built the pc almost 6 years already and never had a problem, in fact the only problem i had before was a burnt gpu (1080ti) which i replaced with a 2060rtx.

i will try to run the memtest 8 iterations and run the pc with a single ram as you suggested.

i want to add something

yesterday i continued making my own trial and error checks to see what could be failing and i remembered long time ago a generic chinese bluetooth dongle gave me a BSOD as soon as i plugged it in, it never happened me again like for months so never thought about it, the thing is that after i remember that i noticed that most of BOSD in the new clean installs started happening as soon as i started playing games which matches with the action of plugging the bluetooth dongle to connect my dualshock 4 to play this games (the bluetooth included with the mobo is really bad).

anyway i removed and uninstalled the bluetooth dongle from the device manager and i have not encountered any BOSD so far, nor corruptions, no more repairs after turning on the PC, it basically just work as it used to work before any problems ocurred, i know this could be a coincidence so i need to continue observing how the pc handles.

does this make any sense? or seems like a coincidence?

~~~~~~~~~~~~~~~EDIT~~~~~~~~~~~~~~~~~~
The usb dongle was a coincidence apparently

Today i turned on the PC and it didnt want, it shutdown itself after a few seconds with a solid red color next to the ram sockets.

after that i readjusted the ram sticks and the PC turned on with the corrupt data message, i did the 8 passes with memtest and it doesnt found error which makes me think that the problem is in the ram sockets, could it be a hardware failure? or just need some cleaning?

i am using the pc with just one stick at the moment as you suggested.

 

[ubuysa]

Test each RAM stick on its own in the correct slot for one DIMM - check your motherboard manual to be sure its in the correct slot. We want to eliminate the RAM before moving on.

From what you said in your original post, this does sound very much like a hardware issue.

 

[King Zapata]

Test each RAM stick on its own in the correct slot for one DIMM - check your motherboard manual to be sure its in the correct slot. We want to eliminate the RAM before moving on.

From what you said in your original post, this does sound very much like a hardware issue.

yeah seems hardware failure to me too.

ill go ahead and run the pc in one stick configurations along the whole days to see how it handles anyway, ill come back soon with an update, thanks.