[SOLVED] Blue Screen PAGE_FAULT_IN_NONPAGED_AREA when booting from sleep

[degialloldongs]

Hey guys, I am getting random BSODs from my ntoskrnl. I posted another thread earlier this month about crashes coming from ntoskrnl but different addresses. This one I got when booting up my computer from sleep mode:

Crash time: 2/17/2019 7:19:42 PM
Bug check string: PAGE_FAULT_IN_NONPAGED_AREA
Bug check code: 0x00000050
Parameter 1: fffffffffffff927 Parameter 2: 0000000000000000
Parameter 3: fffff802481b345b Parameter 4: 0000000000000002
Caused by driver: ntoskrnl.exe
Caused by address: ntoskrnl.exe+1b3440
File Descripition: NT Kernel & System
Operating System: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File Version: 10.0.17763.253 (WinBuild.160101.0800)
Processor: x64
Crash address: ntoskrnl.exe+1b3440
Processor count: 12
Major version: 15
Minor version: 17763

Dx diag: https://drive.google.com/file/d/1qxec1Lrfqe_xyEG5fOwRvCm2pMHuJcHx/view?usp=sharing

Dmp file: https://drive.google.com/file/d/13wtDqNmDy_t6utZIwaT-nICfMSw3TxKA/view?usp=sharing

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/XIjV.html

File information:	021719-31125-01.dmp (Feb 17 2019 - 22:19:42)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: Steam.exe)
Uptime:	3 Day(s), 1 Hour(s), 07 Min(s), and 22 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/b450m-mortar
There are BIOS updates available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[Darkbreeze]

I'd probably look at the PSU, first, and likely replace it regardless since it's a known low quality model. I'm actually surprised as heck it's lasted this long with no issues and maybe it hasn't. If you were having problems with your old build that prompted you to upgrade it could easily have been related to that PSU in the first place.

Those old CX units are probably the MOST crippling component (Short of even worse no name or generic power supplies) we have historically seen here added to builds on a regular basis by a company that is a well known name brand that has a trackable record of causing any number of problems across a variety of systems. The fact that is is also old, simply compounds the problem. Obviously I can't guarantee that this is the source of your issue, but it would be highly advisable to do this ANYHOW, even if you were not having any problems, and stands a good chance of BEING the problem because the power supply itself can mimic or cause problems with any other system it is attached to since those systems cannot operate correctly without good, clean, stable power.

The Mortar series of motherboards, and MSI in general, especially on their budget boards, also have a really bad track record. The Mortar and Krait boards, I've probably seen more problems on those series of boards (Both AMD and Intel) than most other boards except the very lowest end entry level boards in each chipset category. The MSI "Pro" boards for example, are usually pretty terrible. That B450m Mortar doesn't even come with heatsinks on some of the VRMs, which is something we typically haven't seen on most mainstream boards since the old AMD chipsets for AM3+, again, except on the very cheapest boards or business class chipsets and sometimes even those have them if they are a decent board. These days, most boards have them.

I think I'd try a new PSU, a good quality unit, first, and then go from there. You don't lose anything by doing so and you may solve your problem without further need to mess with anything. If you don't, at least you will know you've eliminated the most probable cause and can move on to more direct problem solving.

 

[gamerk316]

Highly doubt its incompatibility, its likely the GPU is just failing. That type of incompatibility just doesn't happen with modern components.

Agreed, sounds like VRAM is failing to me.

 

[Colif]

I will get someone to convert the dump file into a format I can read

@gardenman

ntoskrnl = windows kernel. Its not the cause, just what crashed.

 

[degialloldongs]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/XIjV.html

File information:	021719-31125-01.dmp (Feb 17 2019 - 22:19:42)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: Steam.exe)
Uptime:	3 Day(s), 1 Hour(s), 07 Min(s), and 22 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/b450m-mortar
There are BIOS updates available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

Hey, thanks again for doing this. You ran the dmp file through the debugger for the last thread I created and it said it was probably caused by memory_corruption (Process: steamwebhelper.exe) .

Should I reinstall Steam and see if that will work? Seems like such a simple solution that I'm not sure if that idea is laughable or not.

Thanks again for you the help you two!!!

 

[gardenman]

Usually software doesn't cause a BSOD, it's either caused by drivers or hardware. Since you said that steamwebhelper.exe was mentioned before, and now Steam, the one thing both of those likely use is the internet. I would look for driver updates for your network card. This may or may not help, but it's a good start.

The driver doesn't seem that old. It's from Aug 28 2018. Still check for an update. https://www.realtek.com/en/ I see that the VPN also has a driver. Check for updates for it. Those are just (somewhat educated) guesses.

@Colif should reply later and he may have more ideas.

 

[degialloldongs]

Usually software doesn't cause a BSOD, it's either caused by drivers or hardware. Since you said that steamwebhelper.exe was mentioned before, and now Steam, the one thing both of those likely use is the internet. I would look for driver updates for your network card. This may or may not help, but it's a good start.

The driver doesn't seem that old. It's from Aug 28 2018. Still check for an update. https://www.realtek.com/en/ I see that the VPN also has a driver. Check for updates for it. Those are just (somewhat educated) guesses.

@Colif should reply later and he may have more ideas.

looks like im up to date there. i can only find drivers for july on the website. i uninstalled the VPN so we'll see what happens with that

 

[Colif]

there is a newer lan driver just on the MSI website, saves trying to figure out the new realtek web site.

https://www.msi.com/Motherboard/support/B450M-MORTAR#down-driver&Win10 64

could just as easily run MSI Live update 6 which you can find on utility page of above link

 

[gamerk316]

Whenever is see that BSOD message, I immediately assume there's either a misbehaving driver, or bad RAM. It's unlikely memory corruption is going to happen any other way.

So lets run a simple test: Download run memtest86+ and see if your RAM pops up with any errors.

 

[degialloldongs]

there is a newer lan driver just on the MSI website, saves trying to figure out the new realtek web site.

https://www.msi.com/Motherboard/support/B450M-MORTAR#down-driver&Win10 64

could just as easily run MSI Live update 6 which you can find on utility page of above link

Thanks for the direct link, I will try this. MSI Live Update 6 has always been a little...funky for me.

Whenever is see that BSOD message, I immediately assume there's either a misbehaving driver, or bad RAM. It's unlikely memory corruption is going to happen any other way.

So lets run a simple test: Download run memtest86+ and see if your RAM pops up with any errors.

I thought it was my RAM too. I tested them a few months back before I made these threads and they both tested okay. Hopefully it is the driver.

 

[degialloldongs]

Well, this is unfortunate. Installed the new LAN driver, restarted the computer, BSOD probably less than 5 minutes after the restart with a new stop code “IRQL NOT LESS OR EQUAL”. I will run Memtest86 again just to be sure, but here is the dump file if anyone is interested

Dump file: https://drive.google.com/file/d/104pHOtnbIkrXMwKov47FM4Fk69Mgaugm/view?usp=sharing

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/BUNm.html

File information:	021919-30187-01.dmp (Feb 19 2019 - 21:52:15)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	ntkrnlmp.exe (Process: MSI_LiveUpdate_Service.exe)
Uptime:	1 Day(s), 23 Hour(s), 31 Min(s), and 13 Sec(s)

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[degialloldongs]

Hey guys, so I was a bit confused earlier. I actually never ran MemTest86, just ran Windows Memory Diagnostic tool which showed no errors. I burned MemTest to a CD and ran it, it just completed and there were no errors. So I'm quite relieved when I say it doesn't look like my RAM is messed up. Since @gardenman posted the dump file and it looks like it was caused by MSI_LiveUpdate, which also uses internet, could it be this pesky LAN driver again?

Does anyone have any ideas about how I can proceed from here or should I just do the nuclear option (complete restore of Windows)? These seem to be happening more frequently now, not sure what is going on but I really want to fix this. It actually Blue Screened as I was typing this with a new stop code this time. I'm honestly not even sure if it's worth it at this point to post another dump file but I'll do it just in case it helps.

Dump: https://drive.google.com/file/d/1oTErRtVyvna3Q3uH_JO-7Zey13c3sciH/view?usp=sharing

DxDiag for ----- and giggles (maybe the LAN driver didn't install properly? Idk..): https://drive.google.com/file/d/1dMmTnjkB9Jc8UqUK920PJFi-0LqUBuGA/view?usp=sharing

I really appreciate the time everyone is giving me, thanks so much!!

 

[Colif]

Sorry, i been busy.

before you go nuclear, try this

Before doing anything:

1) search for “Create a restore point” and create a restore point

2) Create a bootable USB of Win 10 installer to use as a boot drive. download the Windows 10 media creation tool and use it to make a win 10 installer on USB

Try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, upload the minidump file and we see what it shows us.

Steps 1 & 2 are just precautions as sometimes driver verifer can put you in a boot loop. If this happen, follow these steps to get out of it

change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore and roll system back to restore point created in step 1. PC should boot normally.

 

[degialloldongs]

Sorry, i been busy.

before you go nuclear, try this

Before doing anything:

1) search for “Create a restore point” and create a restore point

2) Create a bootable USB of Win 10 installer to use as a boot drive. download the Windows 10 media creation tool and use it to make a win 10 installer on USB

Try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, upload the minidump file and we see what it shows us.

Steps 1 & 2 are just precautions as sometimes driver verifer can put you in a boot loop. If this happen, follow these steps to get out of it

change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore and roll system back to restore point created in step 1. PC should boot normally.

Absolutely no problem at all. I was actually doing a bit of research and decided to comb through event viewer and noticed something interesting...I was having the same two events happen before almost every blue screen I’ve gotten in the last few months. These were specifically:

• Event 1:
• Source: FilterManager
• Event ID: 6
• Level: Information
• General: File System Filter 'FileCrypt' (10.0, ‎2070‎-‎12‎-‎15T19:13:56.000000000Z) has successfully loaded and registered with Filter Manager.
• 
  
• Event 2:
• Source: FilterManager
• Event ID: 6
• Level: Information
• General: File System Filter 'npsvctrig' (10.0, ‎2094‎-‎02‎-‎20T06:14:30.000000000Z) has successfully loaded and registered with Filter Manager.
• 
  
• Event 3:
• Source: Kernel-Power
• Event ID: 41
• Level: CRITICAL
• General: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

So I did a bit of digging on google, found a post on reddit where this guy used Windows 10 Debloater (powershell script) and it fixed his issue. I’m going to try this and see what happens since I have nothing to lose at this point. I’m also going to try to run sfc /scannow and chkdsk /f when I get home just to be on the safe side. If all is okay on that front and my issue is still not resolved I will go ahead and try this and post my dump file in this thread after following your steps.

Again thanks so much for all your guys help!

EDIT: Well, that did not last very long....lol. I am going to follow these steps tomorrow as I need to purchase a Flash Drive. I will update the thread when I do it

 

[degialloldongs]

Sorry, i been busy.

before you go nuclear, try this

Before doing anything:

1) search for “Create a restore point” and create a restore point

2) Create a bootable USB of Win 10 installer to use as a boot drive. download the Windows 10 media creation tool and use it to make a win 10 installer on USB

Try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, upload the minidump file and we see what it shows us.

Steps 1 & 2 are just precautions as sometimes driver verifer can put you in a boot loop. If this happen, follow these steps to get out of it

change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore and roll system back to restore point created in step 1. PC should boot normally.

Hi, so I ran a chkdsk scan when I got home, when it was done my computer rebooted and instantly blue screened. So I followed your steps, created a restore point and installation media, ran verifier and got an instant blue screen when restarting after running verifier. I tried turning it off in elevated prompt, no luck, and when I am trying to do system restore I am getting the message “to use system restore, you must specify which windows installation to restore. Restart this computer, select an operating system, and then select system restore.”

Is my windows corrupted now?? If I have to start from scratch I don’t mind too much but am wondering if there is a way around this. My USB is first in my boot order.

EDIT: I could not restore no matter what I did. Tried googling the above error and seen some people suggest running bootrec commands...so I tried running them and got to bootrec /fixboot where I got access denied. Tried multiple solutions to this but kept getting access denied or windows telling me it could not find the file specified when pointing to my HDD partition or my USB stick...so I just said screw this, I am tired of going down the rabbit hole. I relaunched and ran through with the media I created but I deleted everything on my hard drive and did a fresh install of windows. Rebooted again, started going through the set up and Blue Screen....so it seems this damn problem is still not solved yet. Luckily after rebooting I was able to finish the Win 10 install and I am now here writing this. Here is the dump file, unfortunately because of me getting stuck after running verifier and having no way out I do not have the dumps for that...my apologies...I hope this works but I would prefer not to run verifier again after getting stuck in that headache with no way out.

Dump: https://drive.google.com/file/d/1_JNtRu1RM6gcIea8vMsvsdbu95I9cRx3/view?usp=sharing

I am now getting more BSODS with stop code UNEXPECTED KERNAL TRAP. I really don’t want to keep bugging you guys with dump files....do you still think it’s software Related ? Do you think it could be mobo or HDD ? My CPU mobo and RAM are all new

 

[Colif]

The error is usually triggered by two situations that occur in the kernel mode: either the CPU generated a condition that the kernel is not allowed to catch or the condition is an unrecoverable error. The most common cause is hardware failure, mostly due to faulty or mismatched memory.

It could be the ram type, you have F4-2400C15D-16GFX installed, the only 2400 speed Ram from GSkill on the memory listing on motherboard web site is F4-2400C15S-4GNT, and rysen is said to be picky when it comes to ram.

 

[gamerk316]

Well, the fact you basically re-installed Windows and the problem remains indicates something is wrong with the memory subsystem. Either the RAM settings are incorrect for your motherboard, or the RAM itself is faulty.

If all else fails, you can try running with one stick and see if the problem follows a specific stick of RAM. This could also help isolate a problem with more then one stick installed (typically a motherboard/setting problem), or even the possibility one of the RAM slots itself is bad (unlikely if memtest passed).

 

[degialloldongs]

It could be the ram type, you have F4-2400C15D-16GFX installed, the only 2400 speed Ram from GSkill on the memory listing on motherboard web site is F4-2400C15S-4GNT, and rysen is said to be picky when it comes to ram.

Dude I’m going to scream if this is the issue...I knew ryzen was picky with RAM abut god forbid I got a C15D instead of a C15S....what a bunch of fricking crap....is there anything else I can do before I eat this 100 dollar loss? Gardenman said there were BIOS updates available, could that possibly help? I know I’m grasping at straws here, but god I don’t want to spend another 100 dollars on RAM! I feel so stupid, I actually did research on what RAM i should get, but I guess it wasn’t enough....ugh

EDIT: you know what I think you’re right...I’m looking on Newegg and it looks like the ram I got is compatible for AMD X370 / B350 / A320 and my chipset is B450....I feel so angry at myself and so stupid...idk how I could’ve missed this, but I guess I am learning a 100 dollar lesson today thank you everyone for your help, I appreciate it, sorry the problem all along was my own ignorance and not an actual software problem

 

[Colif]

I will get a 2nd opinion before you do anything

reads edit... i will still confirm it is likely cause.

 

[degialloldongs]

I will get a 2nd opinion before you do anything

Okay, thank you so much man

 

[Rogue Leader]

Colif called me. Before you go nuclear and spend money on ram, please go to the MSI website for your board and update the BIOS. Ryzen WAS picky about ram - 2 years ago. Updated chipsets and BIOS updates have largely cleared that. So yeah I would do a BIOS update first before freaking out. Also leave your ram at dead stock settings in the BIOS, no XMP or anything like that.

Now unfortunately with everything you have been doing and all these crashes, you may have corrupted windows and its hard to tell where the original issue ends and new issues begin. If its not too much trouble, after BIOS updating I'd consider doing a clean fresh install and see whether the issue remains.

IF (and thats a big IF) your memory is causing your issues next time get 3000 mhz ram, 2400mhz is handicapping your performance anyway.

 

[degialloldongs]

Colif called me. Before you go nuclear and spend money on ram, please go to the MSI website for your board and update the BIOS. Ryzen WAS picky about ram - 2 years ago. Updated chipsets and BIOS updates have largely cleared that. So yeah I would do a BIOS update first before freaking out. Also leave your ram at dead stock settings in the BIOS, no XMP or anything like that.

Now unfortunately with everything you have been doing and all these crashes, you may have corrupted windows and its hard to tell where the original issue ends and new issues begin. If its not too much trouble, after BIOS updating I'd consider doing a clean fresh install and see whether the issue remains.

IF (and thats a big IF) your memory is causing your issues next time get 3000 mhz ram, 2400mhz is handicapping your performance anyway.

Thanks a lot. I’ll definitely try this when I get home tonight. I did a fresh install of windows yesterday, so everything is deleted, so I definitely don’t mind doing it again lol. I’ll keep you guys updated and let you know if this fixes it or not. Thanks again

 

[Darkbreeze]

I was just coming to say you need to make sure you have the MOST recent BIOS installed, but I see RL already informed you of that. WITH the newer BIOS versions installed, there is MUCH less problems with memory compatibility, even on first gen Ryzen skus. There is still SOME however, so even with the latest bios there could be issues remaining but the memory listed on the QVL list for the motherboard should definitely not be the go to factor.

There are always plenty of modules that will work with any given board that are not listed on their QVL list, AND memory listed on the QVL that is higher speed than whatever the default is for a given board (2133mhz for Ryzen) are not guaranteed by the QVL list to run AT that speed, only that those kits WILL work on that board. They may only work at the default speed. There are a few other user verified threads across the web with more accurate depiction of what modules actually work AT the advertised speeds on Ryzen such as this one:

Thread for "Clearing up any B-die confusion on Ryzen"



But most enthusiast grade memory works fine now on most Ryzen platforms, especially at the default speed. You may need to do some tinkering in the bios or use the Ryzen calculator to dial those sticks in if the bios update doesn't cure the issue, which there is a good chance it will.