Windows 10: BSOD PAGE_FAULT_IN_NONPAGED_AREA (50) ntkrnlmp.exe Windows 10

Discus and support BSOD PAGE_FAULT_IN_NONPAGED_AREA (50) ntkrnlmp.exe Windows 10 in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi guys facing this issue in my PC, clean installation of Windows 10 and drivers, attached data from the memory dump Gigabyte B450M-DS3H Bios F42b... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by th3g3ntl3man, Aug 14, 2019.

  1. BSOD PAGE_FAULT_IN_NONPAGED_AREA (50) ntkrnlmp.exe Windows 10


    Hi guys facing this issue in my PC, clean installation of Windows 10 and drivers, attached data from the memory dump

    Gigabyte B450M-DS3H Bios F42b
    Ryzen 7 3700X
    RAM HyperX @ 2666 MHz 2 X 8GB
    Nvidia RTX 2060
    *No overclocking
    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    PAGE_FAULT_IN_NONPAGED_AREA (50)

    Invalid system memory was referenced. This cannot be protected by try-except.

    Typically the address is just plain bad or it is pointing at freed memory.

    Arguments:

    Arg1: ffffc20874ebc000, memory referenced.

    Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.

    Arg3: fffff8063ace23da, If non-zero, the instruction address which referenced the bad memory

    address.

    Arg4: 0000000000000000, (reserved)



    Debugging Details:

    ------------------





    Could not read faulting driver name



    KEY_VALUES_STRING: 1





    PROCESSES_ANALYSIS: 1



    SERVICE_ANALYSIS: 1



    STACKHASH_ANALYSIS: 1



    TIMELINE_ANALYSIS: 1





    DUMP_CLASS: 1



    DUMP_QUALIFIER: 400



    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



    DUMP_TYPE: 2



    BUGCHECK_P1: ffffc20874ebc000



    BUGCHECK_P2: 2



    BUGCHECK_P3: fffff8063ace23da



    BUGCHECK_P4: 0



    READ_ADDRESS: fffff8063b1713b8: Unable to get MiVisibleState

    Unable to get NonPagedPoolStart

    Unable to get NonPagedPoolEnd

    Unable to get PagedPoolStart

    Unable to get PagedPoolEnd

    ffffc20874ebc000



    FAULTING_IP:

    nt!RtlDecompressBufferXpressHuff+3aa

    fffff806`3ace23da f3a4 rep movs byte ptr [rdi],byte ptr [rsi]



    MM_INTERNAL_CODE: 0



    CPU_COUNT: 10



    CPU_MHZ: e09



    CPU_VENDOR: AuthenticAMD



    CPU_FAMILY: 17



    CPU_MODEL: 71



    CPU_STEPPING: 0



    CUSTOMER_CRASH_COUNT: 1



    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    BUGCHECK_STR: AV



    PROCESS_NAME: RuntimeBroker.exe



    CURRENT_IRQL: 2



    ANALYSIS_SESSION_HOST: DESKTOP-V3CS05D



    ANALYSIS_SESSION_TIME: 08-14-2019 15:49:51.0162



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    TRAP_FRAME: ffff948f5f2221f0 -- (.trap 0xffff948f5f2221f0)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=ffffc20874e9f465 rbx=0000000000000000 rcx=0000000000004465

    rdx=0000000000000100 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8063ace23da rsp=ffff948f5f222380 rbp=ffffc2087372e000

    r8=0000000000000000 r9=0000000000000000 r10=0000000000004502

    r11=0000000000008000 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei ng nz ac pe cy

    nt!RtlDecompressBufferXpressHuff+0x3aa:

    fffff806`3ace23da f3a4 rep movs byte ptr [rdi],byte ptr [rsi]

    Resetting default scope



    LAST_CONTROL_TRANSFER: from fffff8063ade21c1 to fffff8063adbfcc0



    STACK_TEXT:

    ffff948f`5f221f48 fffff806`3ade21c1 : 00000000`00000050 ffffc208`74ebc000 00000000`00000002 ffff948f`5f2221f0 : nt!KeBugCheckEx

    ffff948f`5f221f50 fffff806`3ac729df : 00000000`00000111 00000000`00000002 00000000`00000000 ffffc208`74ebc000 : nt!MiSystemFault+0x1d5601

    ffff948f`5f222050 fffff806`3adcdd20 : 0000002d`0000002d ffffc208`7372dfe0 ffffc208`74e6b000 00000000`00000000 : nt!MmAccessFault+0x34f

    ffff948f`5f2221f0 fffff806`3ace23da : ffffc208`7372e000 ffffc208`74ebb4c8 ffffc208`74e51d60 ffffc208`74e8b000 : nt!KiPageFault+0x360

    ffff948f`5f222380 fffff806`3ac5caf0 : 00000000`0000cd94 ffffc208`74e6b000 00000000`000504c8 fffff806`3b2e2116 : nt!RtlDecompressBufferXpressHuff+0x3aa

    ffff948f`5f2223d0 fffff806`3ac5ca1f : 00000000`00000000 ffffab0f`9095b560 00000000`00000000 00000000`00000000 : nt!RtlDecompressBufferEx+0x60

    ffff948f`5f222420 fffff806`3b1fe0ab : 00000000`00001429 00000000`00000000 ffff948f`5f222510 ffff948f`5f222520 : nt!SmDecompressBuffer+0xff

    ffff948f`5f2224c0 fffff806`3b1ffe7d : 00000000`00000000 00000000`00000003 ffffab0f`903723a0 fffff806`3ac3967d : nt!PfSnGetPrefetchInstructions+0x257

    ffff948f`5f222600 fffff806`3b201509 : ffffab0f`907f34c0 ffff948f`5f222710 ffff948f`00000000 00000000`00000000 : nt!PfSnBeginScenario+0x1f5

    ffff948f`5f2226a0 fffff806`3b201365 : 00000000`00000000 ffffab0f`907f34c0 ffffe780`fbeca180 ffffab0f`907f34c0 : nt!PfSnBeginAppLaunch+0x169

    ffff948f`5f2228a0 fffff806`3b20335a : ffffe780`fbeca180 00000000`00000000 ffffab0f`90372080 00000000`00000000 : nt!PfProcessCreateNotification+0x5d

    ffff948f`5f2228d0 fffff806`3adc767a : ffffe780`fbeca180 ffffab0f`90372080 ffffe780`fbedb440 00000000`00000000 : nt!PspUserThreadStartup+0x14a

    ffff948f`5f2229c0 fffff806`3adc75e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x2a

    ffff948f`5f222b00 00007ffa`069cce50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn

    00000059`937cf8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`069cce50





    THREAD_SHA1_HASH_MOD_FUNC: 4c1150ec55a6abdd5d2266612f84de0bcbbd1145



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: aed3012a5c9cfbcf931004eed3f2b59f427427ba



    THREAD_SHA1_HASH_MOD: 7f608ac2fbce9034a3386b1d51652e4911d30234



    FOLLOWUP_IP:

    nt!RtlDecompressBufferXpressHuff+3aa

    fffff806`3ace23da f3a4 rep movs byte ptr [rdi],byte ptr [rsi]



    FAULT_INSTR_CODE: 8b48a4f3



    SYMBOL_STACK_INDEX: 4



    SYMBOL_NAME: nt!RtlDecompressBufferXpressHuff+3aa



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    DEBUG_FLR_IMAGE_TIMESTAMP: 35707659



    IMAGE_VERSION: 10.0.18362.295



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 3aa



    FAILURE_BUCKET_ID: AV_INVALID_nt!RtlDecompressBufferXpressHuff



    BUCKET_ID: AV_INVALID_nt!RtlDecompressBufferXpressHuff



    PRIMARY_PROBLEM_CLASS: AV_INVALID_nt!RtlDecompressBufferXpressHuff



    TARGET_TIME: 2019-08-14T18:21:45.000Z



    OSBUILD: 18362



    OSSERVICEPACK: 295



    SERVICEPACK_NUMBER: 0



    OS_REVISION: 0



    SUITE_MASK: 272



    PRODUCT_TYPE: 1



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



    OS_LOCALE:



    USER_LCID: 0



    OSBUILD_TIMESTAMP: 1998-05-30 15:12:57



    BUILDDATESTAMP_STR: 190318-1202



    BUILDLAB_STR: 19h1_release



    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



    ANALYSIS_SESSION_ELAPSED_TIME: 1e1a



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:av_invalid_nt!rtldecompressbufferxpresshuff



    FAILURE_ID_HASH: {aa7b5878-1a5d-6544-4200-7ccaffe918b5}



    Followup: MachineOwner

    :)
     
    th3g3ntl3man, Aug 14, 2019
    #1

  2. BSOD PAGE_FAULT_IN_NONPAGED_AREA

    Hi,

    The stop code or blue screen error " PAGE_FAULT_IN_NONPAGED_AREA" is quite a unique error since it can be related to either hardware or software. As for the Windows kernel "ntoskrnl.exe", this handles all the driver requests, power management, and memory
    management on your device. For us to resolve your concern, kindly answer the questions below:

    • What other changes were made or updates were installed prior to the issue occurring?
    • What troubleshooting steps have you attempted?
    • What is the build and version of Windows 10 that is installed on your computer?

    As an initial recommendation, we suggest that you follow the steps on this
    link
    to complete the guided walkthrough on how to resolve blue screen errors.

    We look forward to your response to our queries.
     
    Jordan Dom, Aug 14, 2019
    #2
  3. BSOD UNEXPECTED_KERNEL_MODE_TRAP

    Hi, OttOiToto

    The problem is caused by (ntkrnlmp.exe)

    Check this link, I hope it helps

    https://www.thewindowsclub.com/fix-ntkrnlmp-exe...

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised
    on the site before you decide to download and install it.

    Let us know if these steps help you to resolve the issue.
     
    MaritzaCapiro, Aug 14, 2019
    #3
  4. axe0 Win User

    BSOD PAGE_FAULT_IN_NONPAGED_AREA (50) ntkrnlmp.exe Windows 10

    Page_fault_in_nonpaged_area (50)


    Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
    Please remove Daemon Tools and run the SPTD pass through remover.

    1. Uninstall Daemon Tools
    2. Download the SPTD standalone installer and follow these steps:
      • Double click the executable to open it
      • Click on the button shown below


    BSOD PAGE_FAULT_IN_NONPAGED_AREA (50) ntkrnlmp.exe Windows 10 [​IMG]


    If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window


    Please update or remove IObit, it is the cause of every crash and really old.
    Code:
    Code:
    6: kd> lmvm pffilterstart             end                 module name fffff801`f8250000 fffff801`f8278000   pffilter T (no symbols)                Loaded symbol image file: pffilter.sys     Image path: \??\C:\Program Files (x86)\IObit\Protected Folder\pffilter.sys     Image name: pffilter.sys     Timestamp:        Mon Nov 19 03:07:18 2012 (50A99456)     CheckSum:         000186DB     ImageSize:        00028000     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    The partitions C, D &G need more free space.
    Move files to other partitions to increase the free space to at least 10-15% free space.

    BSOD PAGE_FAULT_IN_NONPAGED_AREA (50) ntkrnlmp.exe Windows 10 [​IMG]
    Warning Less free space could cause BSOD's
     
Thema:

BSOD PAGE_FAULT_IN_NONPAGED_AREA (50) ntkrnlmp.exe Windows 10

Loading...
  1. BSOD PAGE_FAULT_IN_NONPAGED_AREA (50) ntkrnlmp.exe Windows 10 - Similar Threads - BSOD PAGE_FAULT_IN_NONPAGED_AREA ntkrnlmp

  2. BSOD: PAGE_FAULT_IN_NONPAGED_AREA (50), arg4:0000000000000002

    in Windows 10 BSOD Crashes and Debugging
    BSOD: PAGE_FAULT_IN_NONPAGED_AREA (50), arg4:0000000000000002: Greetings and Salutations; Scratching my head. Never in all the 25+ years of building pc's have I ever had this many BSOD's. RANDOM. RE-SET, RE-IMAGED, RE-INSTALLED WINDOWS SO MANY TIMES. Now I know why I don't this for a living anymore. I have installed windbg from sdk. I...
  3. [Windows 10][BSOD] PAGE_FAULT_IN_NONPAGED_AREA

    in Windows 10 BSOD Crashes and Debugging
    [Windows 10][BSOD] PAGE_FAULT_IN_NONPAGED_AREA: Right, so seemingly at random times my PC decides to BSOD and display a couple of codes from my recollection they have been PAGE_FAULT_IN_NONPAGED_AREA with Win32k.sys appearing below it and driver irql_less_or_not_equal these are the most frequent codes and the ones I...
  4. Bsod page_fault_in_nonpaged_area

    in Windows 10 BSOD Crashes and Debugging
    Bsod page_fault_in_nonpaged_area: Hi, I'm getting bsod at the very start of the laptop. Seems like the update of intel wifi and bluetooth driver caused it (using intel update utility). I used dm_log collector, it seems to run ok but it doesn't create any zip file (it was run as admin). Instead it...
  5. Page_fault_in_nonpaged_area (50)

    in Windows 10 BSOD Crashes and Debugging
    Page_fault_in_nonpaged_area (50): Hi! I getting this BSOD from today. I don't know what is the problem the PC crashes under 2-3 min frequently. What now? I can't attach any log beacuse of crash time... here it is what I can save quick. Uploaded the crash log corrrectly. 22796
  6. Windows 10 - BSOD : PAGE_FAULT_IN_NONPAGED_AREA

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 - BSOD : PAGE_FAULT_IN_NONPAGED_AREA: Hi! A few weeks ago I had to give my laptop in service (they had to replace the LCD Cable). Just before I gave it in I reinstalled Windows 10 64-bit and installed all drivers (I suppose) correctly. After some days I got it back, it crashed several times with BSOD -...
  7. Bsod page_fault_in_nonpaged_area

    in Windows 10 BSOD Crashes and Debugging
    Bsod page_fault_in_nonpaged_area: Hey, I've been getting a BSOD often on my laptop ever since I updated to Windows 10. I don't think it's caused by a certain program I run because they seem to happen pretty randomly. I'm not too tech savvy when it comes to these types of things but I did know what it was when...
  8. BSOD Windows 10 error page_fault_in_nonpaged_area

    in Windows 10 BSOD Crashes and Debugging
    BSOD Windows 10 error page_fault_in_nonpaged_area: Hi, I'm completly new to the forum and hoping someone can help out. Brand new dell xps13 that I've upgraded from 8.1 to 10 and have been getting random BSOD, no patter that I can see, not running anything in particular. debugs attached, hopefully someone can shed some...
  9. Bsod page_fault_in_nonpaged_area (fltmgr.sys)

    in Windows 10 BSOD Crashes and Debugging
    Bsod page_fault_in_nonpaged_area (fltmgr.sys): Any help would be appreciate.Attachment 32983 18142
  10. BSOD page_fault_in_nonpaged_area

    in Windows 10 BSOD Crashes and Debugging
    BSOD page_fault_in_nonpaged_area: Got a HP 8200 Elite SFF that I've installed Windows 10 on... it's been a bumpy ride trying to clear up driver related issues but now I'm stuck... I've had a few different BSOD over the last 2 days and I'm convinced it's some driver... maybe the usb driver....