Windows 8 'npsvctrig.sys' causing BSOD on Windows 8.1

NerferMC · Apr 15, 2019

I'm starting to get frequent Bluescreens, always having an error code PAGE_FAULT_IN_NONPAGED_AREA.
I checked the event viewer, before the bluescreen, there is an event called 'npsvctrig.sys' with FilterManager

File System Filter 'npsvctrig' (6.3, ‎2013‎-‎08‎-‎22T12:10:04.000000000Z) has successfully loaded and registered with Filter Manager.
Event ID: 6

and Critical stop with an exact date and time from the minidump file.

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event ID: 41
Edit: April 12, 2019 .dmp file have an error code ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY during the bsod.
I cannot type long more because I was avoiding bsod at this point.

kemical · May 8, 2019

Hi,

I went over both dump files although no driver (third party) was mentioned.

It's a little difficult as to what to suggest due to your current set up, I'll explain:

As your probably aware laptops/netbooks have to use drivers supplied by the manufacturer otherwise issues can occur.

The trouble with your machine is that your manufacturers support page only carries drivers for Windows 7.

Your currently running Windows 8.1.

This means you have zero driver support apart from the drivers that windows already carries.

Please don't feel tempted to use an app to find drivers as these often cause issues than cure.

You could of course try re-installing windows 8.1 or even going back to Windows 7.

Before you do that why not try running...

Neemobeer · Apr 15, 2019

Upload your dump files

NerferMC · Apr 15, 2019

~~I cannot have access to upload and zip .dmp files while I am on Administrator. Can I get some help?~~
Nevermind, I zipped them by copying .dmp files to desktop.

Neemobeer · Apr 15, 2019

Just right click the Minidump folder > send to > compressed (zipped) folder upload the zip file created

NerferMC · Apr 15, 2019

Another BSOD occured
KERNEL SECURITY CHECK FAILURE
(uploaded with android phone)

Another .dmp file after the bsod

kemical · Apr 16, 2019

I took a quick look and you may have some corruption within the system. Try running these scans:

File scans
Open an 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

NerferMC · Apr 16, 2019

kemical said:
I took a quick look and you may have some corruption within the system. Try running these scans:

File scans
Open an 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

Oh, Thanks! The repair is complete...
BUT...I am observing the computer for 1 week if there are no more errors!

kemical · Apr 16, 2019

Please post back with new dump files if errors continue.

NerferMC · Apr 19, 2019

kemical said:
Please post back with new dump files if errors continue.

I got another BSOD. I will upload .dmp files when I logged in to my computer.
It happened while I update my Visual Studio version.
I checked the event viewer, npsvctrig.sys still triggering the bsod.

kemical · Apr 20, 2019

Hi,
can you confirm your notebook is the EME528 model?

I check the E machines website for your model as your drivers are very old. All I could find were drivers for Windows 7 64bit and of course your running Win 8.1.
Notebooks and laptops need to use driver supplied by the manufacturer otherwise bugs can appear.

Did you update or install anything new recently?

NerferMC · Apr 20, 2019

kemical said:
Hi,
can you confirm your notebook is the EME528 model?

I check the E machines website for your model as your drivers are very old. All I could find were drivers for Windows 7 64bit and of course your running Win 8.1.
Notebooks and laptops need to use driver supplied by the manufacturer otherwise bugs can appear.

Did you update or install anything new recently?

Yes, EME528 is my Computer Model

I installed a RAM last year (1 GB RAM) and I was having no problems at all. I didn't update any drivers. and I didn't install any new software before the bluescreens.

kemical · Apr 20, 2019

Try running these batch of basic tests in order to check the system over.

Open a admin command prompt and type:

chkdsk/f

Press enter (you may need to reboot) and this will scan the HDD for errors.

Test your RAM.

This very basic guide will show you how:
How to Test PC RAM with MemTest86

Uninstall any old apps you no longer use, check your add and remove section.

Have you run windows updates recently as the file causing the error is a windows file.

NerferMC · Apr 29, 2019

NerferMC said:
I got another BSOD. I will upload .dmp files when I logged in to my computer.
It happened while I update my Visual Studio version.
I checked the event viewer, npsvctrig.sys still triggering the bsod.

Another Bluescreen Occurred:
KMODE_EXCEPTION_NOT_HANDLED

kemical · Apr 30, 2019

Hi,

it may be the case that a driver is causing npsvctrig.sys to bsod although nothing is mentioned in the dump file.

Try running the driver verifier.

This tests the system drivers on boot up and if something is suspect the system will blue screen and the culprit noted in a dump file.

However, this process can sometimes cause a bsod boot loop. If this occurs you need to enter safe mode and turn the verifier off.

This guide will help:
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

Please post any resulting dump files.

NerferMC · May 6, 2019

Another 2 BSODs occured. But the event log says Dump file saving failed.

First BSOD: Occured while using the PC.
(KERNEL_AUTOBOOST_INVALID_LOCK_RELEASE)
Second BSOD: Occured during reboot
(KERNEL_MODE_EXCEPTION_NOT_HANDLED)

EDIT: I found the .DMP files in C:/Windows and not in a minidump folder. It has 307MB Size! I don't think if I can upload it.

kemical · May 6, 2019

Please run the tests outlined in post #12

EDIT: I found the .DMP files in C:/Windows and not in a minidump folder. It has 307MB Size! I don't think if I can upload it.

Sounds like your saving a full memory dump. Check your settings are like below:

Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go

NerferMC · May 8, 2019

Another Two bluescreens:

BSOD 1: (8:56 AM) KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION 157
BSOD 2: (5:26 PM) KMODE_EXCEPTION_NOT_HANDLED 1e

kemical · May 8, 2019

Hi,

I went over both dump files although no driver (third party) was mentioned.

It's a little difficult as to what to suggest due to your current set up, I'll explain:

As your probably aware laptops/netbooks have to use drivers supplied by the manufacturer otherwise issues can occur.

The trouble with your machine is that your manufacturers support page only carries drivers for Windows 7.

Your currently running Windows 8.1.

This means you have zero driver support apart from the drivers that windows already carries.

Please don't feel tempted to use an app to find drivers as these often cause issues than cure.

You could of course try re-installing windows 8.1 or even going back to Windows 7.

Before you do that why not try running the driver verifier outlined in a thread earlier? This could show us the culprit but it's up to you..

NerferMC · May 13, 2019

kemical said:
Hi,

I went over both dump files although no driver (third party) was mentioned.

It's a little difficult as to what to suggest due to your current set up, I'll explain:

As your probably aware laptops/netbooks have to use drivers supplied by the manufacturer otherwise issues can occur.

The trouble with your machine is that your manufacturers support page only carries drivers for Windows 7.

Your currently running Windows 8.1.

This means you have zero driver support apart from the drivers that windows already carries.

Please don't feel tempted to use an app to find drivers as these often cause issues than cure.

You could of course try re-installing windows 8.1 or even going back to Windows 7.

Before you do that why not try running the driver verifier outlined in a thread earlier? This could show us the culprit but it's up to you..

I tried to run it and I didn't found any dump files after the Driver Verifier test (The Previous BSOD dump files were cleaned up with disk cleanup)

NerferMC · May 13, 2019

Today, I tried to Dual-boot Windows 7 from my Windows 8.1 computer (to test driver due to seperate bsod problem)

After I shutdown Win7, I logged on to windows 8.1 and it crashes like minutes with all the same error "PAGE_FAULT_IN_NONPAGED_AREA".
It usually happens when I play a video.

My PC supposed to be crashing 3-4 days but not every minutes.

(litterally all the same error and error codes)
can't send .dmp files due to errors.
(This thread is written in Android)

Windows 8 'npsvctrig.sys' causing BSOD on Windows 8.1

Well-Known Member

Attachments

Cloud Security Engineer

Well-Known Member

Attachments

Cloud Security Engineer

Well-Known Member

Attachments

Essential Member

Well-Known Member

Attachments

Essential Member

Well-Known Member

Attachments

Essential Member

Well-Known Member

Essential Member

Well-Known Member

Attachments

Essential Member

Well-Known Member

Attachments

Essential Member

Well-Known Member

Attachments

Essential Member

Well-Known Member

Well-Known Member

Attachments

Similar threads