Solved Bsod page_fault_in_nonpaged_area

[Dave76]

The last crash is STOP 0x0000004E: PFN_LIST_CORRUPT.
Usual causes: Device driver, ?memory
This indicates that the page frame number (PFN) list is corrupted.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000003ddb1f, page frame number
Arg3: 0000000000000002, current page state
Arg4: 00000000003dd91e, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SnippingTool.e

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d06d7c to fffff80002c7dc40

STACK_TEXT:  
fffff880`0b567b88 fffff800`02d06d7c : 00000000`0000004e 00000000`00000099 00000000`003ddb1f 00000000`00000002 : nt!KeBugCheckEx
fffff880`0b567b90 fffff800`02c1fd8a : cc400003`ddb1f863 fffffa80`0b9915d0 00000000`00000000 000002d3`00000201 : nt!MiBadShareCount+0x4c
fffff880`0b567bd0 fffff800`02c6dec1 : fffff900`00000000 00000000`000003e8 fffff880`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4b26a
fffff880`0b567d30 fffff800`02da95b1 : fffff900`c3bcf010 00000000`00000000 00000000`00000001 00000000`00005c00 : nt!MiFreePagedPoolPages+0x12d
fffff880`0b567e80 fffff800`02dad557 : 00000000`00000000 fffff880`0b568050 fffff880`0b567fd0 00000000`00000001 : nt!MiFreePoolPages+0x2b1
fffff880`0b567f90 fffff960`00186038 : fffff900`c5c00238 fffff960`0018602e 00000000`35316847 00000000`00000000 : nt!ExFreePoolWithTag+0x7c7
fffff880`0b568040 fffff960`00186806 : fffff900`c00c0010 fffff900`c5c00000 00000000`00000000 fffff900`c5c00238 : win32k!FreeObject+0x58
fffff880`0b568070 fffff960`00186994 : ffffffff`00000000 fffff880`00000000 fffff900`c5c00000 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x58a
fffff880`0b5681c0 fffff960`00147669 : ffffffff`b3050ebf fffff900`c5c00000 ffffffff`b3050ebf 00000000`00000000 : win32k!bDeleteSurface+0x34
fffff880`0b5681f0 fffff800`02c7ced3 : fffffa80`109fc390 fffff880`0b5682a0 00000000`0185000f 00000000`00000020 : win32k!NtGdiDeleteObjectApp+0xd5
fffff880`0b568220 000007fe`fe34108a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0027f018 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe34108a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02d06d7c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME: [COLOR="Red"] memory_corruption[/COLOR]

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------

Let's remove the CPU OC and see what the effect is.
Step 1. Leave all the RAM settings as listed above and set your CPU OC back to stock settings, try to re-create the crash scenario.

Step 2. If that doesn't show any progress, leave the CPU at stock frequency and take out two RAM cards.
Check your motherboard manual for the correct RAM slots to leave the two RAM cards in.
This is just for stability testing, we'll put them back in later and get it stable.

The next step will be using Driver Verifier to look for a driver that might be causing these issues.

Do one step at a time and let us know the results before moving to the next step.

 

[TsAkira]

I think I found it. I removed 2 sticks of RAM and reverted to default OC settings. Then the constant BSODs started (it even crashed during start up repair)....I removed them and inserted the two other sticks and till now everything seems to be working faultlessly (I hope I don't jinx it). While I write this two full system scans (MSE, Antimalware), a fullHD movie and an audio CD is running. Do you reckon I should return my faulty memory to the shop I bought them right now or should I wait for example how my system performs during the weekend?

BTW, when I removed the two memory sticks and entered BIOS, I saw that when I set CPU I/O Voltage to auto it reported 1.04 V compared to 1.344 V when I was using four sticks and set to auto. Is this normal?
Do you think it is safe to to go back to my previous OC and leave CPU I/O to auto?

And I really want to say a great thank you for your help and patience. You gave me extremely detailed instructions on how to resolve this (hope it is resolved).

THANK YOU!!!

 

[Dave76]

First you need to test the suspect RAM, what DRAM and CPU I/O voltages were set when you took the first two RAM cards out?

Yes, the EUFI should compensate CPU I/O voltage for the number of RAM cards you install.

Did you re-set the CPU I/O back to auto when you took the first two RAM cards out?

Leave the DRAM and CPU I/O voltages at the settings I posted previously, even when there are only two RAM cards installed.

Let me know the EUFI RAM and CPU I/O voltage and timing settings on the last steps you have done.
Your 8GB RAM likely won't run stable when the settings are on 'Auto'.

 

[TsAkira]

Ok, I tested the faulty RAM with memtest and it found errors during the first pass. The bios setting for ram are unchanged from the ones you told me (RAM voltage 1.550 and CPU I/O 1.15 and timings 2-9-9-9-24). The two good sticks (even with my system OCed to 4.4 ghz with your recommended settings) are working perfectly in gaming, browsing, video encoding, basically everything. I think I'm going to return the faulty sticks back on monday and get new ones.

 

[Dave76]

If they won't pass memtest86+ then you should RMA them, they are faulty.

Let us know your progress.