Page Fault in nonpaged area.

Sep 7, 2018
5
0
10
Hey! I've recently started getting a BSOD with the error code "PAGE FAULT IN NONPAGED AREA". I tried running scans and repairs in cmd but the problem persisted, so i ran memtest for 2 passes, with 0 errors detected. To try and mitigate any possible software problems, i reinstalled windows and there it was again. I suspect it could be a problem with my harddrive as the error occured once again exactly when selecting steam's download directory as the folder i had previously in my harddrive, so i ran windirstat and tried to scan for any errors and it said " Windows found errors on this drive that needs to be repaired". I dont know if its a credible lead, and am absolutely stumped and asking for any help that could aid me in resolving the issue. Thank you in advance.

:^)
zhely
 
Solution
Another possibility is if you are getting those errors during doing something specific (like playing a game). It's possible your anti-virus is blocking something causing the error. (This fix has been posted here before). If you have an AV installed, try disabling it and see if you get the errors again.
[Moderator note: moving post to Storage.]

What make and model hard drive? Run the applicable manufacturer's diagnostic software.

Do bear in mind that if the hard drive is having some problems then anything you do may cause further damage and/or loss of data.

Also post the drive information. Make, model, capacity, age, condition, etc..

A couple of the drive manufacturers do monitor Tom's from time to time and may offer additional suggestions and advice.
 
Another possibility is if you are getting those errors during doing something specific (like playing a game). It's possible your anti-virus is blocking something causing the error. (This fix has been posted here before). If you have an AV installed, try disabling it and see if you get the errors again.
 
Solution


You were right! I turned off all avast shields, observed that the BSOD didn't happen when watching youtube (unlike before), then narrowed it down to avast's Web Shield. I have no idea how this could be causing an error to do with the paging file, but i'm glad i discovered the root of the problem.