Windows 10 Page File-related BSODs

[MinecraftKid45]

So recently (like the last month or so.) I've been getting multiple BSODs randomly about something like "page_fault_in_nonepaged_area" or "Memory_Management" and sometimes "CORRUPT_PAGE_FAULTY_HARDWARE"

Mainly "MEMORY_MANAGEMENT" and the pagefault in nonpaged area, but this has only been happening since I re-installed Windows 10.

My last Windows 10 installation was flawless and worked perfect, until my Power Blinked and my HDD got corrupted and Windows wasn't working properly (very slow, some apps not even working) so I reinstalled and since have been having issues like this.

My system specifications are

CPU: Intel Core i5-7500 [Kaby Lake] @ 3.40Ghz
GPU: EVGA GeForce GTX 950 SC+ 2GB GDDR5
RAM: 16GB DDR4 G.Skill RipJaws V Series @ 2.8Ghz
Motherboard: GIGABYTE GA-B250-HD3
HDD: Western Digitial Blue 1TB @ 7200RPM [SATA of course]
OS: Windows 10 Home Single Language

BlueScreenView:
PAGE_FAULT: https://gyazo.com/fca2fa0c4e67b416cc172821e1a26d3e
MEMORY_MANAGEMENT: https://gyazo.com/6f6a4e16a12dc904270edcb6480598bf

Thanks! I have run a memory test and it found no issues, so I have absolutely no clue!

 

[frostedtim]

Pagefile and Virtual memory management usually are usually written to the boot drive unless you changed some of its settings. Now if you have some hardware issues with the HDD after power related event, that could explain the behavior you are seeing. You might have some bad sectors developing because the magnetic fields of the platters were messed with, or even the motor or actuator arm that reads the disk may have been damaged. If you can reinstall on a different drive and test, that may well give you your answer.

 

[MinecraftKid45]

I personally doubt the HDD is damaged due to it working absolutely fine and there is no corruption. The Page File issue from what I have seen is basically when Windows attempts to read something from the RAM and it's not there, or the one with NONPAGED_AREA is when the file it is looking for is in an area that is not Paged.
I do not have another HDD that would work in this PC, so that's gonna be annoying to buy an HDD and it not be why.

 

[frostedtim]

The page file is the extended, virtual memory, or RAM, which gets writen to the HDD, not the physical RAM. It acts as extra active memory when the normal physical RAM is full. It is much slower and can act funky if corrupted or there are bad spots on the disk it is allocated to.

I understand not having another drive to test makes my first recommendation difficult. You said you did a reinstall of Windows. Did you do a clean reinstall where you wiped the disk, or was it just over the top of the previous install. If you havent done a clean install, I would try that first.

 

[MinecraftKid45]

The last install was a Clean Install. I backed up all my files to OneDrive and MEGA, and wiped my drive and re-installed.

Maybe I should disable Page File, as I have 16GB of RAM, so I don't think I even need it.. I know multiple people say it's a bad thing to do, but I am going to try it because I can always enable it again.

 

[frostedtim]

Dont turn it off, but you can reduce the amount used. Instead, just lower it to about 1GB. Follow this guide if you need help:

https://www.geeksinphoenix.com/blog/post/2016/05/10/how-to-manage-windows-10-virtual-memory.aspx

 

[MinecraftKid45]

Already reduced the size, did not help. I have googled this and done everything I've seen to fix it. Disabling it seems like something I can try however, to see if I do get anymore BSODs about this issue [to further inspect]

 

[MinecraftKid45]

No Luck, did a memtest86 test, got only one error on Test #6 (1934 errors, wut?)
Guess another re-install of Windows 10? Wish I could go back to Windows 7..damn 7th gen

EDIT: I have heard that Modem drivers in Windows 10 can cause such issues..I am going to be honest I put an old 56K dialup modem in my PC for fun from an OLD PC to see if it worked (it did!)
Researching..I see that this can ACTUALLY make this happen [idk how but ok?]

 

[MinecraftKid45]

Issue was with one of my RAM sticks. Filed an RMA with G.Skill to get it replaced. Use memtest86 with the bad stick causes errors in test #6.
The other one does not have any errors whatsoever. To anyone also having this issue, I recommend testing each RAM stick with memtest86 if you get an error with both inserted. If you don't get any issues with all your RAM inserted, don't worry about it being your RAM