Recurring Windows 10 Page Fault w/ Minidump - Feedback Greatly Appreciated

Toggle sidebar Toggle sidebar
christopherjames86

christopherjames86

May 21, 2018
7
0
10
This is my first time using this forum, and I came here because I feel like I'm out of my depth. I built my PC about two years ago and it has recently begun to bluescreen frequently. I'm typically getting "Paged Fault in Non Paged Area" and "IRQL Not Less or Equal" error messages.

About a month ago, I installed a new CPU fan that had a higher power draw. The system became unstable either that night or the next day. I opened the case up again and discovered I had accidentally plugged the CPU fan into the chassis fan port. I fixed that, but the issue persisted.

I've tried multiple things to identify/fix the problem, including:
-Stress testing the CPU with Prime95
-Running a MemTest (although I think I want to try it again overnight) Edit: Ram seems fine for now. Did 8 passes of MemTest today.
-Running Chkdsk
-Running SFC
-Running DISM
-Installing Windows updates
-Reinstalling the OS twice, most recently was a full, clean reinstall
-Using the driver verifier (which seemed to fix the issue until I turned it back off after a few days
-Replacing the PSU with a more powerful one (Windows crashed a couple minutes after boot with new PSU)
-Carefully updated all mobo/GPU/etc drivers
-Updated BIOS firmware to latest revision

System specs are:
Windows 10 Home 64-bit
ASRock Motherboard Mini ITX DDR4 NA (H170M-ITX/AC)
Intel i5-6600 @ 3.3GHz
Corsair 2x 4GB RAM, DDR3
Zotac GTX 970
650 watt PSU (up from 500 watt)

Here is the minidump, please let me know if I've posted the correct file:
Minidump
 
Solution
Colif
that is the driver verifer guide i would have given you. Its possible you didn't get a dump file as windows hadn't started enough to make the dump file... there are a number of reasons, I assume your page file is on C drive?

you should have run the scans of memtest on 1 stick at a time, as if you had received any errors, you wouldn't have known which stick it was. And would have had to start again to figure it out.

What hdd do you have? just curious as it might be the hdd causing the corruption,

I wish the dumps said more than just memory corruption as that doesn't tell us a great deal. Its been like that for a year now.

try this:
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its...
Sort by date Sort by votes
I have asked someone to look at dump files,

Both of those errors can be drivers, so driver verifer found no errors? its odd it fixed the errors as its meant to cause bsod, its job is to test them. Very bizarre they return when its not on, but don't show when it is.

Non paged area is ram but that doesn't mean it was the ram causing it, could just be a badly behaving driver.
 
Upvote 0 Downvote
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/5DO2.html

File: 052318-6015-01.dmp (May 24 2018 - 00:59:19)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: RazerCentralService.exe)
Uptime: 0 Day(s), 14 Hour(s), 10 Min(s), and 32 Sec(s)

File: 052118-5093-01.dmp (May 21 2018 - 16:43:46)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: dwm.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 17 Sec(s)

Motherboard: http://www.asrock.com/mb/Intel/H170M-ITXac/
As you stated, you have the latest available BIOS installed.

I can't help you with this. Wait for additional replies. Good luck.
 
Upvote 0 Downvote


When I first turned on driver verifier, I couldn't boot. Then I saw suggestions that said I should turn off DDI Compliance Checking so I turned that off. PC booted and ran for a few days and I left it on through a system refresh. I was fairly confident that I had eliminated the problem so I turned off the driver verifier again and crashed within minutes if I'm recalling correctly.
 
Upvote 0 Downvote


I'll do you one better. I'm going to leave Synapse uninstalled because I don't trust it at this point. It's not the first time I've seen it mentioned in the crash report.

Razer tries so hard to reinstall Synapse anytime I update Windows or reinstall. I really don't like how it tries to install itself before I've even finished installing the OS.
 
Upvote 0 Downvote
i have used synapse before, i remember it trying to install drivers during a windows update and messing itself up. Its a shame you can't change any settings on razer mice/kb without synapse running and being logged in to razer servers.

DDI Compliance means it doesn't check for drivers that are signed by Microsoft to work with windows 10, but apart from web cam drivers, all yours are new enough to have the right signature, With it on the PC won't run the drivers that aren't signed. I wonder if its still off?

Your oldest drivers running are for your logitech web cam but as they probably don't have an update yet (gardenman may know answer to that) you have no choice but to run them
 
Upvote 0 Downvote
To be honest, I didn't like the newer Logitech software so I reinstalled the old software/drivers for my Logitech Webcam Pro 9000. If you want to try the new software (and possibly updated drivers) and if you don't already have it, look for Logitech Webcam Software about 3/4th's of the way down on this page: http://support.logitech.com/en_us/downloads Have your original install disc nearby just in case you don't like the new stuff. Will this fix your BSODs? Unlikely but there's always the chance.

Did you ever do additional RAM testing? Did you check the RAM modules one at a time? You have 2 modules (sticks). You did use memtest86 and not the Windows Memory Diagnostic test correct?

images
 
Upvote 0 Downvote

I'll definitely give the logitech drivers a shot. I did use memtest86. I ran it on both sticks together for 11 hours and 8 passes without an error.
 
Upvote 0 Downvote
Thanks for all the help guys. I'm planning to turn driver verifier back on but I'm having trouble finding consistent information on it's usage. What checks should I enable? Should I be testing all drivers or just non-Microsoft drivers?

EDIT: I've decided to test driver verifier with the settings I found in this MS guide: https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

Initial results are promising but unhelpful. Windows refuses to boot (DRIVER_VERIFIER_DETECTED_VIOLATION). However, in two BSODs, no driver was identified and it seems to have failed to produce a minidump. I'm not entirely sure how to proceed.
 
Upvote 0 Downvote
that is the driver verifer guide i would have given you. Its possible you didn't get a dump file as windows hadn't started enough to make the dump file... there are a number of reasons, I assume your page file is on C drive?

you should have run the scans of memtest on 1 stick at a time, as if you had received any errors, you wouldn't have known which stick it was. And would have had to start again to figure it out.

What hdd do you have? just curious as it might be the hdd causing the corruption,

I wish the dumps said more than just memory corruption as that doesn't tell us a great deal. Its been like that for a year now.

try this:
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files that SFC uses to compare system files, re run SFC if it failed to fix all files and restart PC
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom