BDOS caused by NTFS.sys

[wshaghoury]

Here are the specifics provided by BlueScreenView
Image: https://ibb.co/k3AVKy
BDOS was caused by the NTFS.sys file, I don't know if it was corrupted or if I got a virus or it could be an overload of some dump files I'm not too sure
What do I do next?

 

[Colif]

can you go to c:\windows\minidump
copy the files from here to another folder
upload copies from that site to a file sharing web site and show a link here. I will ask someone to read/convert dumps to see what drivers were running at time of crash.

Its likely caused by a driver
ntoskrnl = windows kernel
ntfs = new technology file system.

 

[wshaghoury]

can you go to c:\windows\minidump
copy the files from here to another folder
upload copies from that site to a file sharing web site and show a link here. I will ask someone to read/convert dumps to see what drivers were running at time of crash.

Its likely caused by a driver
ntoskrnl = windows kernel
ntfs = new technology file system.

here is the file dump
https://drive.google.com/open?id=1M6M53d86guOhX6AGpBeuaOB6KKl06puE

 

[gardenman]

Hi, the dump file was partially corrupt or my debugger couldn't read it. I gave the debugger 20 minutes before canceling. It usually only takes a few minutes for each dump file. Results: https://pastebin.com/SXkEwNsi

Error: BugCheck 34
CACHE_MANAGER (34)
https://docs.microsoft.com/windows-hardware/drivers/debugger/bug-check-0x34--cache-manager
System Uptime: 4 days 9:49:28.331

I can't help you with this. Wait for additional replies. Good luck.

Edit: I tried again and got a little better result. It's still bugged though. Results: https://pste.eu/p/mGDB.html

 

[wshaghoury]

Hi, the dump file was partially corrupt or my debugger couldn't read it. I gave the debugger 20 minutes before canceling. It usually only takes a few minutes for each dump file. Results: https://pastebin.com/SXkEwNsi

Error: BugCheck 34
CACHE_MANAGER (34)
https://docs.microsoft.com/windows-hardware/drivers/debugger/bug-check-0x34--cache-manager
System Uptime: 4 days 9:49:28.331

I can't help you with this. Wait for additional replies. Good luck.

Edit: I tried again and got a little better result. It's still bugged though. Results: https://pste.eu/p/mGDB.html

Zipping the file may have caused a problem, so here is the file directly, also, here is a screenshot from the view reliability history (however the memory dump it mentions is gone)
https://drive.google.com/open?id=1fVnYsjJzxEO_J3SH_bIzJoc_pPJfzBFL
https://ibb.co/kctnHJ

 

[Colif]

No old drivers, some unknown (to me) such as wise unlock. Wonder why its running. Do you need it running all the time, its just meant to let you delete files. - https://www.wisecleaner.com/wise-force-deleter.html

The error could be a memory leak caused by a driver, once ram fills up its got no where to go.Even with a normal page file you run out of resources eventually. If driver keeps eating resources you can only go so far.

Have you changed your page file size?

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

nonpaged pool is ram

Another thought is test your ram with memtest86, 1 stick at a time. Up to 8 passes, Any error count higher than 0 is too many, replace/remove sticks with errors.

 

[gardenman]

Same result on the new upload. Zipping it didn't hurt, its just either a bad file (possible) or my debugger doesn't like it (highly likely). I have this problem with many dump files so it's probably my debugger and problems with the symbols.

Try the RAM test Colif suggested.

 

[wshaghoury]

No old drivers, some unknown (to me) such as wise unlock. Wonder why its running. Do you need it running all the time, its just meant to let you delete files. - https://www.wisecleaner.com/wise-force-deleter.html

The error could be a memory leak caused by a driver, once ram fills up its got no where to go.Even with a normal page file you run out of resources eventually. If driver keeps eating resources you can only go so far.

Have you changed your page file size?

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

nonpaged pool is ram

Another thought is test your ram with memtest86, 1 stick at a time. Up to 8 passes, Any error count higher than 0 is too many, replace/remove sticks with errors.

So to test 1 stick at a time I would have to remove the other? Or does memtest86 let me choose between the 2

 

[gardenman]

memtest86 won't let you choose, it can't do that. You do have to physically remove one stick and test only 1 stick at a time. I know it's a pain, but if errors are detected on one RAM module and not the other, then we know exactly what is causing the BSODs.