PAGE FAULT IN NONPAGED AREA

[ToddeSwe]

Hi

My son has gotten this bluescreen with the code Page fault in nonpaged area yesterday and some time before.
The first time he got it i removed the memory sticks and dusted them and checked them to see if there was any visable fault. This was a couple of months ago now but yesterday it happened again. So instead of doing the same thing again i wanted to ask you if we should be worried about this or is it badly written software / games like roblox seems to trigger bluescreen on his computer.

 

[Colif]

page fault in non paged area can just be a driver error.
what are details of his PC? (what parts are in it apart from a 2060)

Can you ask him to follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

After the error:

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

I see if its an easy one, I like easy ones... they so rare.

Page faults are actually normal. Any operating system that uses Virtual memory will have them.
They are badly named operations. They happen when CPU discovers it needs information of RAM. Thats it, not a error in itself. the errors occur when drivers tell the CPU to look in the wrong place.
the non paged area is an area of ram that drivers run in.

 

[ToddeSwe]

page fault in non paged area can just be a driver error.
what are details of his PC? (what parts are in it apart from a 2060)

Can you ask him to follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

After the error:

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

I see if its an easy one, I like easy ones... they so rare.

Page faults are actually normal. Any operating system that uses Virtual memory will have them.
They are badly named operations. They happen when CPU discovers it needs information of RAM. Thats it, not a error in itself. the errors occur when drivers tell the CPU to look in the wrong place.
the non paged area is an area of ram that drivers run in.

Hi and many many thanks for this, i found the minidump from the last bluescreen and archived it with winrar i hope that works. I couldn't find system winzip.

Here you can download the minidump: https://www.dropbox.com/s/un80omyb51k9t4p/081722-12000-01.rar?dl=0

Hope this doesn't include some info about how to get inside my sons computer.

Sorry i forgot to include his computerdetals:

AMD Ryzen 2600 and MSI B450 Tomahawk motherboard. 1 TB harddrive and a 250 SSD for the system.
16 GB memory.

 

[Colif]

I have to ask a friend to convert dumps, he will give me the results soon but I don't know when. He is working on a van he wants to restore and its the right time of year for him to get some work done. So doing dumps is not a priority for him now... I am meant to be leaning how to do it myself but life keeps getting in the way.

once we look at dumps, I will suggest some ideas.

Can you download and run Driverview - http://www.nirsoft.net/utils/driverview.html

All it does is looks at drivers installed; it won't install any (this is intentional as 3rd party driver updaters often get it wrong)

When you run it, go into view tab and set it to hide all Microsoft drivers, will make list shorter.

Can you take a screenshot from (and including)Driver name to (and including)Creation date.

upload it to an image sharing website and show link here
this shows how to link images - https://forums.pcgamer.com/threads/using-the-pc-gamer-forum-features.1664/#post-190344

 

[ToddeSwe]

I have to ask a friend to convert dumps, he will give me the results soon but I don't know when. He is working on a van he wants to restore and its the right time of year for him to get some work done. So doing dumps is not a priority for him now... I am meant to be leaning how to do it myself but life keeps getting in the way.

once we look at dumps, I will suggest some ideas.

Can you download and run Driverview - http://www.nirsoft.net/utils/driverview.html

All it does is looks at drivers installed; it won't install any (this is intentional as 3rd party driver updaters often get it wrong)

When you run it, go into view tab and set it to hide all Microsoft drivers, will make list shorter.

Can you take a screenshot from (and including)Driver name to (and including)Creation date.

upload it to an image sharing website and show link here
this shows how to link images - https://forums.pcgamer.com/threads/using-the-pc-gamer-forum-features.1664/#post-190344

Thanks we'll wait and see how it develops.

Will download the driverview and post a list when his computer is available.

Thanks!

 

[Colif]

if my friend replies in the next few hours, it will include a list of drivers running at time of crash. Driver view shows everything, not just what is running.

 

[ToddeSwe]

I have to ask a friend to convert dumps, he will give me the results soon but I don't know when. He is working on a van he wants to restore and its the right time of year for him to get some work done. So doing dumps is not a priority for him now... I am meant to be leaning how to do it myself but life keeps getting in the way.

once we look at dumps, I will suggest some ideas.

Can you download and run Driverview - http://www.nirsoft.net/utils/driverview.html

All it does is looks at drivers installed; it won't install any (this is intentional as 3rd party driver updaters often get it wrong)

When you run it, go into view tab and set it to hide all Microsoft drivers, will make list shorter.

Can you take a screenshot from (and including)Driver name to (and including)Creation date.

upload it to an image sharing website and show link here
this shows how to link images - https://forums.pcgamer.com/threads/using-the-pc-gamer-forum-features.1664/#post-190344

Hi

Here's the screenshot of his drivers loaded execpt for the windows ones.

Dropbox

www.dropbox.com

 

[ToddeSwe]

Here's is an update of his memorytype and brand:

He have two of this:

Crucial BLS8G4D26BFSBK8FD 8GB DDR4 PC4-21300U DDR4-2666 (16-18-18-38 4-61-20-7)

Today it crashed again after he had played Bloons TD 6

 

[ToddeSwe]

Me again, this windows pops up when he is trying to start Valorant.

Dropbox

www.dropbox.com

 

[Colif]

Vanguard thinks it owns the PC you install it on, so it wants you to remove inpoutx64.sys from PC before it will let you play Valorant.
I have often wondered what that driver does. its an open source driver so it isn't just a matter of looking its name up.
I don't know what program that driver is part of, but we can use this to stop it from running, not sure if thats enough for Vanguard though
run this - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
this program shows everything that runs at startup with windows.
look on drivers tab, I think you find that driver there (screenshot of the driver showing its full image path would be helpful

unticking a driver should stop it running at startup. It doesn't stop a program running it after startup but it might be enough for Vanguard.
If not, the image path will tell me what its part of and we can see if its actually needed. If not, we can remove program.

Curious to me is that driver doesn't show on the 3rd party driver list (driver view)

He could update Razer Synapse
update chipset drivers - https://www.amd.com/en/support/chipsets/amd-socket-am4/b450
I assume its windows 10
Download Win10 Auto Installation Program (NDIS) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

Did the BSOD only start after adding GPU?

If so, run this in safe mode, remove current Nvidia drivers, load back into normal mode and reinstall Nvidia drivers - https://forums.tomshardware.com/thr...n-install-of-your-video-card-drivers.2402269/

 

[Colif]

ZenTimings uses the inpoutx64 kernel driver from highrez.

ZenTimings

www.overclock.net

i see that inpoutx64.sys driver tied to motherboard he has... what MSI programs has he got installed?
seems its also part of a few RGB programs, Jacknet, MSI RGB, Openrgb - I don't see any in driver listing though.
this is a work around:

Those of you are facing the same problem, you can ->

1. Go to Settings
2. Search in "Windows Security" ; open the same
3. Go to Device Security
4. Click on Core isolation details
5. Enable Memory integrity

It will prompt you to reboot your system, but once you've done that you're good to go!

PS - Vanguard will still show the same error dialogue, but as of now it isn't blocking MSIRGB from functioning
PPS - You need to have virtualization enabled on your BIOS and resolve any incompatible drivers for memory integrity to work


It worked for me, hope it works for you all too!

Issue with Valorant anti-cheat system Vanguard blocking process · Issue #115 · ixjf/MSIRGB

Hi there, I'm new to GitHub and I wanted to say I absolutely love what you've done with MSIRGB script which is infinite times better than the Mystic Light on my MSI Z370 PC PRO motherboard. However...

github.com

 

[ToddeSwe]

Vanguard thinks it owns the PC you install it on, so it wants you to remove inpoutx64.sys from PC before it will let you play Valorant.
I have often wondered what that driver does. its an open source driver so it isn't just a matter of looking its name up.
I don't know what program that driver is part of, but we can use this to stop it from running, not sure if thats enough for Vanguard though
run this - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
this program shows everything that runs at startup with windows.
look on drivers tab, I think you find that driver there (screenshot of the driver showing its full image path would be helpful

unticking a driver should stop it running at startup. It doesn't stop a program running it after startup but it might be enough for Vanguard.
If not, the image path will tell me what its part of and we can see if its actually needed. If not, we can remove program.

Curious to me is that driver doesn't show on the 3rd party driver list (driver view)

He could update Razer Synapse
update chipset drivers - https://www.amd.com/en/support/chipsets/amd-socket-am4/b450
I assume its windows 10
Download Win10 Auto Installation Program (NDIS) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

Did the BSOD only start after adding GPU?

If so, run this in safe mode, remove current Nvidia drivers, load back into normal mode and reinstall Nvidia drivers - https://forums.tomshardware.com/thr...n-install-of-your-video-card-drivers.2402269/

Thanks so much, he restarted the computer and tried again and then he was allowed to play the game.

Will take a look at the razer chipset thingy. THANKS!

No he have hade BSOD before but just with roblox <--- not sure of the spelling.
My idea was that i was just with badly made games...
We did made a live update for the motherboard yesterday. But i will take a look at the razer stuff anyway.

 

[Colif]

good to know gpu weren't cause of errors.

I am going to have to learn how to convert dumps myself. I guess I do that tomorrow.
My friend will be happy as he wants to stop anyway.

 

[Colif]

Finally worked out how to get this myself

File: 081722-12000-01.dmp (Aug 17 2022 - 07:59:16)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 10 Hour(s), 30 Min(s), and 21 Sec(s)

Comment: The overclocking driver "NTIOLib_X64.sys" was found on your system. (MSI Afterburner or other MSI software)

I see memory corruption on almost every BSOD. So that doesn't necessarily mean RAM.
Dump text doesn't point at a particular driver, that is so normal I am amazed when it does.

there is a newer bios version but its unlikely to help

reinstall should fix it.

seems he has something called windivert.sys on pc. Its hacking software -
WinDivert Network Packet Capture & (Re)Injection driver (Basil Projects)