Solving frequent BSoDs after Npsvctrig.sys and FileCrypt are loaded

Then I guess what you meant is that the software problems caused crashes

and you believe that power cycling the machine tons of times to recover from

the crashes damaged your RAM? I don't think that's really a feasible scenario either.

The important thing is that you fixed it. Best wishes.

Edited by Shplad, 05 March 2021 - 10:10 AM.

A bit of a necro post, but I'd like to just braindump some info on this in my experiences.
I've been plagued with crashes and bluescreens for the better part of two years with this PC I've built. Infuriating frankly. I've resorted to doing insane things to try and see if I stumble upon a cause or fix like changing my clock from 24 hour to 12 hour.
Total insanity. Completely neurotic stuff at this point.
Not sure if they are related, but there are a few different versions of crashes/bsod I see. Sometimes it's just a hard crash that leaves my 3 monitors with solid color screens (although different colors between the 3 of them). Sometimes I get a legitimate bluescreen with the most generic crash information (ntoskrnl.exe, kmode_exception, pagefault in nonpaged area, etc)

It does seem to happen most frequently when playing a game or doing something fairly intensive with computing resources or media in general (e.g. editing video, playing games, watching videos, emulating android)
I have noticed that it tends to not happen while I'm away from my computer or while it is mostly idle (machine stays on overnight and basically 24/7) but I'm not sure I could say a crash/bsod has never occurred during these times.

Let me get some of the things I've commonly found as "solutions" out of the way;
"Fixing" win10 with de-bloat didn't work for me.
No amount of RAM/Memory testing has ever resulted in finding any errors (still not sure it isn't somehow hardware related).
Painstakingly ensuring that all of my drivers are properly selected/updated hasn't stopped it.
Reinstalling windows entirely hasn't fixed it (which is why I can't necessary trust that it isn't hardware, but of course it could always be the common software configurations I tend to fall back on even after starting with a clean slate)
I've tried tinkering with things like the hiberfile and pagefile without any noticeable changes

I don't have an nvidia graphics card so the solution isn't my graphics drivers
In case you would think it is then my AMD GPU then know i'm almost always up to date on that front.

That takes me to my next bit of info - the machine itself.
threadripper 1950x on an MSI x399 mobo
Vega 64 GPU
32gb ram
nvme drives installed and used for operating system and storage (no traditional sata drives at all).


I don't have any particular reason to believe any of the data provided above somehow specifically would lead anyone to understanding this npsvctrig.sys/filecrypt trend and the possibly related crashes and bsods, but any data folks can dump in a common location such as this could lead to the discovery of a pattern that takes us to the root of whatever the issue is.

If by some chance someone gets an email notification for this post being created in this thread, and you notice something about my post that sounds similar to your issue then please speak up (and I mean other than what's already in the thread title of course).

This has basically equated to a hard interruption of computer activities once per day for almost 2 years.
Losing my mind.
Thanks for reading.

What I ultimately found out that led to my crashing issues is that one of the power cables to my video card was jarred out of position when I moved my PC.  It was literally either an electrical short or lack of proper voltage to my GPU that kept causing my BSOD errors.

One dead RAM module removed and ultimately replaced, I simply snapped the power cable to the video card firmly back into place and my issues disappeared.

As time went on, I became more and more convinced that

there is no one solution to this problem, and the problem is not

caused by npsvctrig.sys itself.

You can always post your own thread in the appropriate forum

here, and chances are, we'll help you resolve your issue.

We've solved some pretty difficult cases here.

Hello!

This problem has been my bane ever since I assembled a new computer. The same pattern with FileCrypt as described in this thread. I tried many things to try to get rid of it but everything failed (as for almost everybody else).

However, I managed to eliminate any suspicions about hardware. Meaning - it's not hardware itself that causes the crashes.

I've been daily driving Linux Fedora Workstation 36 on the same machine for about a month now. Not a single crash, not a single freeze. I game on it and it's been rock solid. Windows used to crash at least once per day.

I am a layman here and cannot provide any meaningful thoughts other than - it's Windows. Linux is ROCK solid on the same hardware.

For specs - neofetch in the attachments.

Cheers and have a nice day,

szakipus

Edited by szakipus, 27 December 2022 - 02:57 PM.

Yep. It definitely sounds like a software problem in your case. I'm glad I don't have these symptoms any more. It drove me crazy for a while.

Hello... 

I stumbled across this thread as I myself am having this problem on 2 machines both running Windows 10 LTSC version.

edit: I missed that the Win 10 Debloater was already discussed here. I edited the post and removed the information, since I cannot simply remove the post. I will edit back when I have any more information to describe my setup and if the Debloater helped or not.

Edited by kubislav, 31 January 2024 - 03:42 PM.

Hello... 
 
I stumbled across this thread as I myself am having this problem on 2 machines both running Windows 10 LTSC version.
 
edit: I missed that the Win 10 Debloater was already discussed here. I edited the post and removed the information, since I cannot simply remove the post.