Page_fault_in_non_paged_area 0x00000050

Please restart WDV with these customized tests:

zbook said:

Please restart WDV with these customized tests:

Code:

[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Click to expand...

here they are, my pc now runs sluggishly

Microsoft Windows [Version 10.0.22631.3085]
(c) Microsoft Corporation. Alle rettigheder forbeholdes.

C:\Users\andre>verifier /querysettings

Verifier Flags: 0x0395e010

Standard Flags:

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[X] 0x00002000 Invariant MDL checking for stack.
[X] 0x00004000 Invariant MDL checking for driver.
[X] 0x00008000 Power framework delay fuzzing.
[X] 0x00010000 Port/miniport interface checking.
[X] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[X] 0x00800000 Kernel synchronization delay fuzzing.
[X] 0x01000000 VM switch verification.
[X] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Verified Drivers:

iastoravc.sys
nvlddmkm.sys
teedriverw10x64.sys
rtcx21x64.sys
nvvad64v.sys
nvmoduletracker.sys
nvvhci.sys
nvhda64v.sys
rtkvhd64.sys
sshid.sys
dump_dumpstorport.sys
dump_stornvme.sys
dump_dumpfve.sys
iomap64.sys
cpuz157_x64.sys

C:\Users\andre>

That's an extremely bad stop code! Usually means RAM or RAM slot problem. Could very well be because you need to reseat the RAM.
This one is a classic for loss of RAM/RAM subsystem-related stability. It can also mean a RAM slot problem and possibly a CPU RAM controller problem, which means CPU replacement required, as the RAM controller is integrated into the CPU.

The RAM controller has been integrated into the CPU, since first-gen Core i-series.

I dealt with this stop code, back in 2019, with socket 1366, just because I changed the motherboard to another one that was related and actually a better tier, which should have been stable, I was using the same DDR3 SDRAM sticks! With used motherboards, it's likely time to clean the RAM slots with isopropyl alcohol.

Pretty much nothing makes me panic more than "PAGE_FAULT_IN_NON_PAGED_AREA" stop code.

RJARRRPCGP said:

That's an extremely bad stop code! Usually means RAM or RAM slot problem. Could very well be because you need to reseat the RAM.
This one is a classic for loss of RAM/RAM subsystem-related stability. It can also mean a RAM slot problem and possibly a CPU RAM controller problem, which means CPU replacement required, as the RAM controller is integrated into the CPU.

Click to expand...

So i may need to replace the RAM and/or CPU?

RJARRRPCGP said:

That's an extremely bad stop code! Usually means RAM or RAM slot problem. Could very well be because you need to reseat the RAM.
This one is a classic for loss of RAM/RAM subsystem-related stability. It can also mean a RAM slot problem and possibly a CPU RAM controller problem, which means CPU replacement required, as the RAM controller is integrated into the CPU.

The RAM controller has been integrated into the CPU, since first-gen Core i-series.

I dealt with this stop code, back in 2019, with socket 1366, just because I changed the motherboard to another one that was related and actually a better tier, which should have been stable, I was using the same DDR3 SDRAM sticks! With used motherboards, it's likely time to clean the RAM slots with isopropyl alcohol.

Click to expand...

I have tried reseating them.

Regarding the isopropyl alchohol. Do i use Q-tips?

SnowmanDK said:

I have tried reseating them.

Regarding the isopropyl alchohol. Do i use Q-tips?

Click to expand...

Or the motherboard, because of the slots. I would be extra careful with Q-tips, at least make sure you don't have pieces stuck in there. Stuff stuck in there, of course can cause the problem.

There was only 1 BSOD mini dump file.



1) Restart WDV with all customized tests except:

[ ] 0x00000004 Randomized low resources simulation.




2) Run the tool for 24 - 48 hours.




3) If there is no immediate BSOD after starting WDV then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.



4) For any BSOD post a new V2 share link into the newest post

zbook said:

There was only 1 BSOD mini dump file.



1) Restart WDV with all customized tests except:

[ ] 0x00000004 Randomized low resources simulation.




2) Run the tool for 24 - 48 hours.




3) If there is no immediate BSOD after starting WDV then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.



4) For any BSOD post a new V2 share link into the newest post

Click to expand...

should i leave my PC on for the next 24-48 hours?

Microsoft Windows [Version 10.0.22631.3085]
(c) Microsoft Corporation. Alle rettigheder forbeholdes.

C:\Users\andre>verifier /querysettings

Verifier Flags: 0x03bfefbb

Standard Flags:

[X] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[X] 0x00000020 Deadlock detection.
[X] 0x00000080 DMA checking.
[X] 0x00000100 Security checks.
[X] 0x00000800 Miscellaneous checks.
[X] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[X] 0x00000200 Force pending I/O requests.
[X] 0x00000400 IRP logging.
[X] 0x00002000 Invariant MDL checking for stack.
[X] 0x00004000 Invariant MDL checking for driver.
[X] 0x00008000 Power framework delay fuzzing.
[X] 0x00010000 Port/miniport interface checking.
[X] 0x00040000 Systematic low resources simulation.
[X] 0x00080000 DDI compliance checking (additional).
[X] 0x00200000 NDIS/WIFI verification.
[X] 0x00800000 Kernel synchronization delay fuzzing.
[X] 0x01000000 VM switch verification.
[X] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Extensions:

wdm: rules.all
ndis: rules.default

Verified Drivers:

iastoravc.sys
nvlddmkm.sys
teedriverw10x64.sys
rtcx21x64.sys
nvvad64v.sys
nvmoduletracker.sys
nvvhci.sys
nvhda64v.sys
rtkvhd64.sys
sshid.sys
dump_dumpstorport.sys
dump_stornvme.sys
dump_dumpfve.sys
iomap64.sys
cpuz157_x64.sys
ndis.sys
netadaptercx.sys
mbbcx.sys
wificx.sys
wdiwifi.sys

If there are no BSOD after running WDV continuously for 24 - 48 hours then that will conclude the troubleshooting.

zbook said:

If there are no BSOD after running WDV continuously for 24 - 48 hours then that will conclude the troubleshooting.

Click to expand...

will keep you posted after 48 hours

And thank you all for your time so far :)

RJARRRPCGP said:

That's an extremely bad stop code! Usually means RAM or RAM slot problem.

Click to expand...

That's not always the case and is simply dangerous scare mongering.

no BSOD so far.
the uptime was below 48 hours, but at least least 24 hours till now.

x BlueRobot said:

That's not always the case and is simply dangerous scare mongering.

Click to expand...

I'm not scare mongering. Because if not the RAM or the slot, then it very well could be IMC or traces to RAM on motherboard. Maybe a socket pin problem for the IMC circuit. (integrated memory controller)

Note that I said usually. The other issues, even if not caused by the RAM itself, is very bad in many cases. It's very often related to memory hardware subsystem. It can mean the above. In another words, very often hardware-level. I sometimes wish it were just a software issue, but it very often goes away, if I remove a RAM module.

@SnowmanDK Any other crashes since? If not, then probably safe to mark this thread as solved.