Windows 10: BSOD Memory Management

Discus and support BSOD Memory Management in Windows 10 Drivers and Hardware to solve the problem; What is my Problem: in the last time i got several Blue Screens: -PAGE_FAULT_IN_NONPAGED_AREA -MEMORY_MANAGEMENT -FAULTY_HARDWARE_CORRUPTED_PAGE... Discussion in 'Windows 10 Drivers and Hardware' started by WolfgangR_98, Dec 3, 2018.

  1. WOLFGANGR_98
    WolfgangR_98 Win User

    BSOD Memory Management


    What is my Problem:

    in the last time i got several Blue Screens:

    -PAGE_FAULT_IN_NONPAGED_AREA

    -MEMORY_MANAGEMENT

    -FAULTY_HARDWARE_CORRUPTED_PAGE

    When I am not gaming the errors occur every 1-2 weeks. When i play CS:GO they occur a little more frequently.

    The last week I played the ANNO 1800 Technical Test they occurred every 30-50 min on high settings. On Low settings i did not get an Blue Screen (Only could test this for two hours)

    What have I tried:
    -I used several memory checking tools(Windows’ Memory Diagnostic Tool, MemTest86...) with no errors found.

    -SFC-SCAN

    -CHKDSK /f /r

    -Reinstalled Windows

    -Updated drivers

    -set page file max size to constant

    -tried to analyse .dmp files

    -swapped ram with a 8GB kit of the same type of ram

    -Ran several stress test (GPU, CPU, RAM) without any issues



    What are my questions:
    -Is this issue probably caused by bad graphic memory (I tested it to... But I am interested if it is possible)

    -should i try this: Driver Verifier

    -Is it possible that it is a motherboard related issue?

    -Is it maybe a heat related issue? (one ram stick almost touches the CPU cooler)

    -red marked parts in dmp analyse(see below)


    My Build:

    Motherboard: MSI G45 Z87

    CPU: i7-4770

    GPU: MSI GTX 970 Gaming 4G

    RAM: DDR3 Corsair Vengance 12 GB

    SSD: Samsung 840 EVO 500 GB

    OS: Windows 10 Pro (Windows 8 Upgrade)



    DMP FILE:

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)

    Online Crash Dump Analysis Service

    See http://www.osronline.com for more information

    Windows 8 Kernel Version 17763 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 17763.1.amd64fre.rs5_release.180914-1434

    Machine Name:

    Kernel base = 0xfffff803`73e9f000 PsLoadedModuleList = 0xfffff803`742be990

    Debug session time: Mon Dec 3 09:26:04.668 2018 (UTC - 5:00)

    System Uptime: 0 days 1:40:19.353

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

    * *

    * Bugcheck Analysis *

    * *

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


    MEMORY_MANAGEMENT (1a)

    # Any other values for parameter 1 must be individually examined.

    Arguments:

    Arg1: 0000000000041792, The subtype of the bugcheck.

    Arg2: ffffcdbfffc7b958

    Arg3: 0000080000000000

    Arg4: 0000000000000000


    Debugging Details:

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


    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2


    BUGCHECK_STR: 0x1a_41792


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT Why is it WIN8?


    PROCESS_NAME: chrome.exe always a different process


    CURRENT_IRQL: 2


    LAST_CONTROL_TRANSFER: from fffff803740914f8 to fffff80374050040


    STACK_TEXT:

    ffffca85`d04b7ce8 fffff803`740914f8 : 00000000`0000001a 00000000`00041792 ffffcdbf`ffc7b958 00000800`00000000 : nt!KeBugCheckEx

    ffffca85`d04b7cf0 fffff803`73ee9fb7 : ffffca85`d04b7e89 00000800`00000000 0000007f`fffffff8 0a000001`4edbb867 : nt!MiDeleteVa+0x1a1ba8

    ffffca85`d04b7e00 fffff803`73eea3aa : ffffca85`d04b8320 ffffcde6`00000000 ffffca85`00000000 0a000001`00000000 : nt!MiWalkPageTablesRecursively+0x2c7

    ffffca85`d04b7ef0 fffff803`73eea3aa : ffffca85`d04b8320 00000000`00000000 ffffca85`00000001 8a000002`00000000 : nt!MiWalkPageTablesRecursively+0x6ba

    ffffca85`d04b7fe0 fffff803`73eea3aa : ffffca85`d04b8320 00000000`00000000 ffffca85`00000002 ffffcde6`00000000 : nt!MiWalkPageTablesRecursively+0x6ba

    ffffca85`d04b80d0 fffff803`73ee986a : ffffca85`d04b8320 00000000`00000000 0000007f`00000003 ffffca85`00000000 : nt!MiWalkPageTablesRecursively+0x6ba

    ffffca85`d04b81c0 fffff803`73eec17d : ffffca85`d04b8320 fffff803`00000001 00000000`00000000 ffffd08c`00000000 : nt!MiWalkPageTables+0x1ea

    ffffca85`d04b82b0 fffff803`73eeccd5 : 00000000`00000000 ffffd08c`3fbeb3f0 ffffca85`00000001 00000000`00000000 : nt!MiDeletePagablePteRange+0x1dd

    ffffca85`d04b84f0 fffff803`743b4391 : fffff803`742e0940 00000000`00000000 ffffd08c`3e879870 ffffd08c`3b6288b0 : nt!MiDeleteVad+0x7c5

    ffffca85`d04b8660 fffff803`743b3f78 : ffffd08c`3e879870 ffffd08c`3b6288b0 ffffd08c`41e0c080 00000000`00000000 : nt!MiUnmapVad+0x49

    ffffca85`d04b8690 fffff803`74436097 : ffffd08c`42648060 ffffd08c`42648060 ffffd08c`3e879870 ffffd08c`3b6288b0 : nt!MiCleanVad+0x30

    ffffca85`d04b86c0 fffff803`7441206d : ffffffff`00000000 ffffffff`ffffffff ffffca85`d04b8901 ffffd08c`3fbeb080 : nt!MmCleanProcessAddressSpace+0x113

    ffffca85`d04b8740 fffff803`7442f9b8 : ffffd08c`3fbeb080 ffffba0e`1e71f060 ffffca85`d04b8959 00000000`00000000 : nt!PspRundownSingleProcess+0x129

    ffffca85`d04b87c0 fffff803`743bc5f3 : ffffd08c`00000000 fffff803`730f0801 000000f7`64d94000 ffff1b0e`3de3adfb : nt!PspExitThread+0x5c8

    ffffca85`d04b88c0 fffff803`73f66240 : fffff803`730ed180 00000000`00000000 ffffd08c`41e0c080 fffff803`73f63948 : nt!KiSchedulerApcTerminate+0x33

    ffffca85`d04b8900 fffff803`74054460 : ffffd08c`41e0c001 ffffca85`d04b89c0 00000000`00000002 ffffca85`00000000 : nt!KiDeliverApc+0x470

    ffffca85`d04b89c0 fffff803`7406132f : ffffd08c`41e0c080 000000f7`659ff5c8 ffffca85`d04b8ad8 ffffd08c`3c33be20 : nt!KiInitiateUserApc+0x70

    ffffca85`d04b8b00 00007fff`8ff8e614 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f

    000000f7`659ff598 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fff`8ff8e614



    STACK_COMMAND: kb


    FOLLOWUP_IP:

    nt!MiDeleteVa+1a1ba8

    fffff803`740914f8 cc int 3


    SYMBOL_STACK_INDEX: 1


    SYMBOL_NAME: nt!MiDeleteVa+1a1ba8


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nt


    IMAGE_NAME: ntkrnlmp.exe


    DEBUG_FLR_IMAGE_TIMESTAMP: 3eeaaca9


    FAILURE_BUCKET_ID: X64_0x1a_41792_nt!MiDeleteVa+1a1ba8


    BUCKET_ID: OLD_IMAGE_ntkrnlmp.exe


    Followup: MachineOwner



    I hope someone can help with this issue.

    Thank You!


    EDIT: Had to do an empty post first before i could change this one... I don't know whats the issue

    :)
     
    WolfgangR_98, Dec 3, 2018
    #1
  2. ARGEL OBM
    Argel Obm Win User

    BSOD- memory management

    Upon checking the dump file, the issue is being caused by ntoskrnl.exe. Ntoskrnl.exe is the one responsible for memory management that is why you're having the Memory Management error. We suggest that you follow the steps found in the link that we provided
    in our last reply to resolve the issue. Please take note that if you're overclocking your processor or video card, kindly reset their settings to default.

    Let us know the outcome after performing the provided steps.
     
    Argel Obm, Dec 3, 2018
    #2
  3. COLD STORM
    Cold Storm Win User
    IRQ memory BSODS, device manager, memory range?

    The only time I've seen that type of BSOD for myself is when I fried the PCI-e slots on my Striker 2 board... There wasn't anything that I could do, try and rma and go on.. I would suggest the steps that MilkyWay has said.. But, if you really don't know much about Bios's... I wouldn't play with Irq's... That can mess up everything on your board. USB, ethernet, ram, chip... But, that's just me on playing with irq's... To much of a hassle IMHO..
     
    Cold Storm, Dec 3, 2018
    #3
  4. YULITSYPIN
    YuliTsypin Win User

    BSOD Memory Management

    memory management bsod

    Your suggested fixes seemed to have stopped the persistent BSODs, but I still tried several fixes for the ones seemingly caused by transferring files and other operations.

    I updated the chipset, the bluetooth drivers, audio drivers, and went through the Device Manager updating every single driver there.

    It seemed to have solved the "Memory_Management" BSODs, although I have received two "Whea_Uncorrectable_Error" BSODs(one of which was orange), probably caused by "hal.dll" since.

    EDIT: I may have spoken a little too prematurely, tried putting a little more load on the system by running a game and it crashed it again..Memory Management..

    Latest Dumps: https://1drv.ms/f/s!AikxcPr2QN10gxQ6UelOz5REGLd
     
    YuliTsypin, Dec 3, 2018
    #4
Thema:

BSOD Memory Management

Loading...

  1. BSOD Memory Management - Similar Threads - BSOD Memory Management

  2. Memory Management BSOD

    in Windows 10 Gaming
    Memory Management BSOD: I just got a BSOD maybe 30 seconds after waking from sleep, here is the dump file. Any help is appreciated. Thanks.Dump filehttps://easyupload.io/1l3sl7 https://answers.microsoft.com/en-us/windows/forum/all/memory-management-bsod/d54c3525-bfc7-49c7-b9fb-00d1a08283da

  3. BSoD memory management

    in Windows 10 BSOD Crashes and Debugging
    BSoD memory management: I Keep Getting BSoD memory management and I don't know what to do sfc /scannow keeps giving me an error with something like windows resource protection couldn't perform the requested operation and chkdsk won't work! I've tried sfc scannow even is safe mode. I can barley use...

  4. Memory Management BSoD

    in Windows 10 Software and Apps
    Memory Management BSoD: I often get the Memory Management BSoD. But only in Call of Duty and i cant explain why. I tried various methods, i found online, but nothing worked. Changed every Ram too. Updated all drivers.... please help me i dont know what to do..All Infos from the...

  5. BSOD: Memory Management

    in Windows 10 BSOD Crashes and Debugging
    BSOD: Memory Management: I am having issues with the aforementioned error for Windows 10. The motherboard and CPU are new but the RAM is from a different mobo/CPU that I have had for 4 years now.I first encounter the BSOD when changing after a user name but 'sfscan /scannow' fixed that. Yet, after an...

  6. Memory Management BSOD

    in Windows 10 BSOD Crashes and Debugging
    Memory Management BSOD: Hi, I've started getting Memory Management BSOD randomly. I've tried all the usual troubleshooting methods e.g. memory diagnostic, sfc and chkdsk all found no issues. I finally gave up and did a Windows reset however this has not fixed my issue. please find attached the...

  7. Memory Management BSOD

    in Windows 10 BSOD Crashes and Debugging
    Memory Management BSOD: I know there have been tons of Q and A about this situation. re: the Memory Management BSOD Mine usually occurs (but not exclusively) when I reboot or shut down the PC. So let me list what I've done so far: Microsoft Memory Diagnostics Tool (tested clean) Dell Memory...

  8. BSOD Memory Management

    in Windows 10 BSOD Crashes and Debugging
    BSOD Memory Management: For the past week I've had a BSOD Memory Management when I turn my PC off, but not while it's running otherwise. I've attached the report generated by "log collector v2-beta17". What advice can you give me, please? Cheers Ralph 128150

  9. MEMORY MANAGEMENT BSOD

    in Windows 10 BSOD Crashes and Debugging
    MEMORY MANAGEMENT BSOD: Keep receiving the memory management BSOD and must reboot by holding the power button down, this is happening multiple times a day. https://answers.microsoft.com/en-us/windows/forum/all/memory-management-bsod/10a0fd4f-6176-46a8-ab20-035fa86762a2

  10. BSOD Memory management ?

    in Windows 10 BSOD Crashes and Debugging
    BSOD Memory management ?: Been getting this weird bluescreen just in the last few days, I don't think it's ram because I've ran memtest and 0 errors 47492