Solving frequent BSoDs after Npsvctrig.sys and FileCrypt are loaded

Do you use a NAGA mouse and software to it by any chance?

If  you're asking me, Shplad, no, I do not. Thanks for asking.

Shplad:

As I mentioned earlier, my temps are stable at 74°C during 100% CPU usage stress tests post new cooler installation. Crashes have completely stopped so ultimately in my case improving the cooling system in my computer fixed the crashes that appeared to be related to "FileCrypt" and "npsvctrig". As you mentioned, this was most likely coincidental but that was all I had to work with in the event viewer.

technonymous:

I do not use a NAGA mouse if you are asking me.

Guys,

I was having this issue same as OP describe,  fileinfo>wof>filecrypt>"2 antivirus file"(not sure if it does anything in this)>npsvctrig> event 41,  but I believed I have fixed it as I found the same sequence but it didn't crash this time the sequence is now, fileinfo>wof>wdfilter(i switched  my antivirus to window's defender)>filecrypt>npsvctrig. However I am not sure which changes i did worked, so I am go to list them all, hope it can help getting down to the bottom of this.

one strange thing, it seems to only happen when i have games open, more specifically only when I run Path of Exile, the reboots never happen outside the game.................

Things I did (not in order, sorry I cant remember the order I did them in):

1: underclock my CPU to 3800mz(from 4000) and core voltage from 1.304 to 1.100

2: disabled PBO in my bios(Asus AMD user )

3: deleted all Ryzen power plan 

4: set my max cpu power to 75%  in power plan

5: backdated my chipset driver to the one from AMD site, (somehow window update has a newer version than the one on the website), I suspect this is the reason but cant prove it as i cant find that update in windows update anymore.  

6: I uninstalled my antivirus as the file was with the sequence

7: disable auto reboot

8: ran debloter 

9: run the app i used along with the game from desktop instead(i used to run it from desktop then I move it somewhere else as the app said it may cause unsuitability when ran from desktop, the crash seems to happen after I moved the app lol 

)

Will start undoing all the power relayed changes to see if it reboots, will update result.

* EDIT: I ran debloter it seems to have stop the issue completely as the event no longer being loged at all. 

* EDIT 2: it seems to be stable for now, all power is back to normal(no oc), been running the game for 2 hours and no reboots

Edited by steven_pang, 16 October 2019 - 09:09 AM.

Folks, I'm no expert in this subject, but I do highly recommend you read and re-read post #26 from this thread. The bottom line is that these crashes can be caused by many things; Just because we happen to see npsvctrig.sys in the post-mortem (after crash) dumps doesn't mean much. It only means that Windows considers some of these services critical, and so if they aren't loaded properly the machine may choose to reboot.

IOW, don't read into it more than it is. It is probably just a part of Windows sensitive to crashing because it's designed to be more critical than some other parts.

Folks, I'm no expert in this subject, but I do highly recommend you read and re-read post #26 from this thread. The bottom line is that these crashes can be caused by many things; Just because we happen to see npsvctrig.sys in the post-mortem (after crash) dumps doesn't mean much. It only means that Windows considers some of these services critical, and so if they aren't loaded properly the machine may choose to reboot.

 

IOW, don't read into it more than it is. It is probably just a part of Windows sensitive to crashing because it's designed to be more critical than some other parts.

I agree, an Event ID 41 is a just a generic report of a sudden power loss shutdown. I suspect a hardware device as the cause. It can be anything internal or external USB devices, shorts, bad PSU etc. When voltages get out of range the system will BSOD and report a error. It's doing what it's designed to do in the event of critical failure. This sort of thing is hard to diagnose, when a system reports normal and BAM! sudden power loss and no memory dump was created. it's necessary to take it into a computer shop as they are generally better equipped to find the problem. There are diagnostic cards that can pinpoint problems, just like a diagnostics port on a vehicle. When a computer has a unknown underlining issue these problems arise when the system is running a game. The cpu, gpu, memory, fans are all running full bore.

You wrote:

Umm...since when is it necessary? Maybe tens of thousands of people who've posted on this forum have had their problems resolved here. Clearly that is evidence suggesting otherwise.

Edited by Shplad, 16 October 2019 - 05:52 PM.

Solved my issue by updating my NVIDIA video cards' driver to latest.

File System Filter 'npsvctrig' (10.0, ‎2025‎-‎01‎-‎05T21:41:12.000000000Z) has successfully loaded and registered with Filter Manager.
(previously crashed here with a "Critical" error, instead now does not crash and goes directly to following line..)

Connectivity state in standby: Disconnected, Reason: NIC compliance

Edited by Uncreated, 01 March 2021 - 01:03 AM.

I spoke too soon.  Back to the drawing board.

It's best not to post in this thread. However, if you continue to experience BSoDs, or hangs/freezes, I suggest you

start your own thread in the BSoD subforum. There's lot of good help in there. We can probably fix it for you.

* EDIT: I ran debloter it seems to have stop the issue completely as the event no longer being loged at all. 

* EDIT 2: it seems to be stable for now, all power is back to normal(no oc), been running the game for 2 hours and no reboots

Steve, I know it's been awhile, but had your crashed completely stopped since you ran the debloater?

EDIT: Shplad, no worries.  I've done a load of research on this and I'm only posting here to confirm the results of what I did that solved the problem should anyone find this thread.

Edited by Uncreated, 02 March 2021 - 02:03 PM.

Hmmm..I've never tried Debloater. I'll have a look, though it could also be coincidence.

SOLVED.

Final verdict for me and apparently many others.

Since I last posted, my computer took a turn for the worse.  All the crashing destroyed one of my RAM modules and eventually left my machine unbootable so I had to reinstall Windows.  I am on good information drawing the conclusion that a flaky NVIDIA driver is responsible for destroying my hardware and not the other way around.

The issues persisted after the RAM module was removed and Windows was reinstalled. 

That is, until I found out about 'TDRDelay'.

Apparently it's a way for Windows to tell itself to pause a bit before taking any action in the event that a video driver crashes.  With 'TDRDelay' adjusted in the registry to a value around '8' to 'A' (hexadecimal), then Windows will give your video driver more time to recover before panicking and shutting the system down.  Personally I set mine to 'A' and haven't had a crash since.  It's as good as solved.

https://www.reddit.com/r/battlefield_4/comments/1xzzn4/tdrdelay_10_fixed_my_crashes_since_last_patch/

For those landing in here off the Internet especially.

Cheers.

It is physically impossible for software to destroy RAM. If the RAM was bad, it was defective all by itself,

not with the help of any software.

The TDR timing delay is a bandaid solution. It doesn't fix the underlying problem. It will, sometimes, however

stop the errors. I wish I could be more enthusiastic about your "fix".

Edited by Shplad, 04 March 2021 - 11:45 AM.

Simple causality to me.  My guess is better than an educated one--I repair computers for a living and have been doing so for two decades.  If a machine is constantly and violently power cycled as much as mine has been, something is bound to break.  That the crashes continued after the bad module was removed is further evidence of this, as far as I'm concerned.

Easiest bit of advice to those who doubt is "try it for yourself and see."