MEMORY_MANAGEMENT ntoskrnl.exe


  1. Posts : 13
    windows 7 Ultimate x64
       #1

    MEMORY_MANAGEMENT ntoskrnl.exe


    iv been getting alot of deffrent bsod but i reinstaled windows and now am only getting MEMORY_MANAGEMENT as of yet
    win 8.1 pro 64
    6 gb ram memtest 10 hr all pass
    nvidia geforce gts 250 1gb
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi master91090.

    The carsh dumps are not providing enough information about the BSODs, but a stop 0x1A is a memory management BSOD. That means either the RAM is failing or any driver is passing bad information the the memory.

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes.

    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    If it does not show any error, enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any.
    ____________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41201, fffff6806e450010, 92c00000def7b847, ffffe0009dfc5180}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2aebd )
    
    Followup: MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041201, The subtype of the bugcheck.
    Arg2: fffff6806e450010
    Arg3: 92c00000def7b847
    Arg4: ffffe0009dfc5180
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_41201
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  WWAHost.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff80075d9536d to fffff80075d59fa0
    
    STACK_TEXT:  
    ffffd000`cd54d868 fffff800`75d9536d : 00000000`0000001a 00000000`00041201 fffff680`6e450010 92c00000`def7b847 : nt!KeBugCheckEx
    ffffd000`cd54d870 fffff800`75cae458 : 92c00000`def7b847 00000000`00000000 00000000`00000000 fffff800`7600ddc6 : nt! ?? ::FNODOBFM::`string'+0x2aebd
    ffffd000`cd54d8e0 fffff800`75cadfb7 : ffffe000`9a5a12c0 ffffe000`9a4db880 ffffe000`9a4dbd68 00000000`00000002 : nt!MiQueryAddressState+0x218
    ffffd000`cd54d9e0 fffff800`7600957b : 00000000`00000002 ffffd000`cd54dcc0 000000dc`8601a730 ffffd000`00000004 : nt!MiQueryAddressSpan+0xe3
    ffffd000`cd54da50 fffff800`760090f6 : 000000dc`8600a700 ffffe000`9a4dbd58 ffffe000`9a5a12c0 00000000`00000000 : nt!MmQueryVirtualMemory+0x47f
    ffffd000`cd54db80 fffff800`75d657b3 : 00000000`00000000 000000dc`8601a958 00000000`f00019ff ffffffff`ffffffff : nt!NtQueryVirtualMemory+0x22
    ffffd000`cd54dbd0 00007ffd`a63eadba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000dc`8601a6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`a63eadba
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+2aebd
    fffff800`75d9536d cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2aebd
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53085af2
    
    IMAGE_VERSION:  6.3.9600.17031
    
    BUCKET_ID_FUNC_OFFSET:  2aebd
    
    FAILURE_BUCKET_ID:  0x1a_41201_nt!_??_::FNODOBFM::_string_
    
    BUCKET_ID:  0x1a_41201_nt!_??_::FNODOBFM::_string_
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x1a_41201_nt!_??_::fnodobfm::_string_
    
    FAILURE_ID_HASH:  {48c83227-3944-10a1-bf0f-11b43dc9c13b}
    
    Followup: MachineOwner
    ---------
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:39.
Find Us