Windows 8 and 8.1 Forums


BSOD "MEMORY MANAGEMENT" Error

  1. #1


    Posts : 6
    Windows 8.1

    BSOD "MEMORY MANAGEMENT" Error


    Hello, I apologize in advance for the cluttered nature of my dump folder, BSODs have been occurring very frequently in my computer over time (I recently finished a custom build for Christmas). I'm not versed enough to read my own dump files, so I was wondering if anyone would be able to help me figure out this "MEMORY MANAGEMENT" error I receive, this is the crash I see most frequently. They happen very sporadically, and I have not been able to pin point a specific thing that i'm doing when these crashes occur.

    I've read some things about changing the RAM voltage (I'm running 16 GB) and that had no success.
    The dump in question is the last in the list, "021415-4812-01.dmp" made 2/14/15 at roughly 12:47.

    Thank you so much in advance, and let me know if i can provide anymore information.

      My System SpecsSystem Spec

  2. #2


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Orients & Welcome to the forums ^_^,

    I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

    Code:
    **************************Sat Feb 14 23:13:38.915 2015 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\021415-4812-01.dmp]
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
     
    System Uptime: 0 days 11:20:49.564
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Probably caused by : ntoskrnl.exe ( nt+1509a0 )
     
    BugCheck 1A, {41793, fffff68000026ff8, 1ba, 1b9}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
     
    Arguments: 
    Arg1: 0000000000041793, The subtype of the bugcheck.
    Arg2: fffff68000026ff8
    Arg3: 00000000000001ba
    Arg4: 00000000000001b9
    BUGCHECK_STR:  0x1a_41793
     
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3499
     
      BIOS Version                  P1.30
     
      BIOS Release Date             05/23/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Baseboard Manufacturer        ASRock
     
      Product Name                  To Be Filled By O.E.M.
     
      Baseboard Product             Z97 Extreme4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Feb 14 09:46:30.873 2015 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\021315-7359-01.dmp]
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
     
    System Uptime: 0 days 0:16:55.526
     
    Probably caused by : Pool_Corruption ( nt!ExFreePool+b8b )
     
    BugCheck 139, {3, ffffd00025a607c0, ffffd00025a60718, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
     
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd00025a607c0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd00025a60718, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
     
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x139_3_nt!ExFreePool
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3499
     
      BIOS Version                  P1.30
     
      BIOS Release Date             05/23/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Baseboard Manufacturer        ASRock
     
      Product Name                  To Be Filled By O.E.M.
     
      Baseboard Product             Z97 Extreme4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Feb 14 09:00:18.688 2015 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\021315-7125-01.dmp]
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
     
    System Uptime: 0 days 0:07:16.336
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Probably caused by : ntoskrnl.exe ( nt+1509a0 )
     
    BugCheck 1A, {5003, fffff58010804000, 688, 68a0000d30}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
     
    Arguments: 
    Arg1: 0000000000005003, The subtype of the bugcheck.
    Arg2: fffff58010804000
    Arg3: 0000000000000688
    Arg4: 00000068a0000d30
    BUGCHECK_STR:  0x1a_5003
     
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3499
     
      BIOS Version                  P1.30
     
      BIOS Release Date             05/23/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Baseboard Manufacturer        ASRock
     
      Product Name                  To Be Filled By O.E.M.
     
      Baseboard Product             Z97 Extreme4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Feb 14 08:52:35.978 2015 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\021315-4671-01.dmp]
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
     
    System Uptime: 0 days 0:12:28.626
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    *** WARNING: Unable to verify timestamp for win32k.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
     
    Probably caused by : win32k.sys ( win32k+3bd8a )
     
    BugCheck 3B, {c0000005, fffff96000200d8a, ffffd00029c4b250, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
     
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff96000200d8a, Address of the instruction which caused the bugcheck
    Arg3: ffffd00029c4b250, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3499
     
      BIOS Version                  P1.30
     
      BIOS Release Date             05/23/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Baseboard Manufacturer        ASRock
     
      Product Name                  To Be Filled By O.E.M.
     
      Baseboard Product             Z97 Extreme4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Feb 14 04:34:58.042 2015 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\021315-5109-01.dmp]
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
     
    System Uptime: 0 days 1:01:34.691
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+a4 )
     
    BugCheck 139, {3, ffffd00024afa3c0, ffffd00024afa318, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
     
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd00024afa3c0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd00024afa318, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3499
     
      BIOS Version                  P1.30
     
      BIOS Release Date             05/23/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Baseboard Manufacturer        ASRock
     
      Product Name                  To Be Filled By O.E.M.
     
      Baseboard Product             Z97 Extreme4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Feb 14 03:22:08.402 2015 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\021315-4765-01.dmp]
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
     
    System Uptime: 0 days 0:17:07.051
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Probably caused by : ntoskrnl.exe ( nt+1509a0 )
     
    BugCheck 1A, {3300, ffffc000b825d000, c3e0000328ebf321, 0}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
     
    Arguments: 
    Arg1: 0000000000003300, The subtype of the bugcheck.
    Arg2: ffffc000b825d000
    Arg3: c3e0000328ebf321
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_3300
     
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3499
     
      BIOS Version                  P1.30
     
      BIOS Release Date             05/23/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Baseboard Manufacturer        ASRock
     
      Product Name                  To Be Filled By O.E.M.
     
      Baseboard Product             Z97 Extreme4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Feb 14 01:10:28.722 2015 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\021315-4953-01.dmp]
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
     
    System Uptime: 0 days 16:06:52.376
     
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
     
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
     
    Probably caused by : ntoskrnl.exe ( nt+acb66 )
     
    BugCheck 3B, {c0000005, fffff803b4cacb66, ffffd0002239a990, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
     
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff803b4cacb66, Address of the instruction which caused the bugcheck
    Arg3: ffffd0002239a990, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3499
     
      BIOS Version                  P1.30
     
      BIOS Release Date             05/23/2014
     
      Manufacturer                  To Be Filled By O.E.M.
     
      Baseboard Manufacturer        ASRock
     
      Product Name                  To Be Filled By O.E.M.
     
      Baseboard Product             Z97 Extreme4
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Many of the dump files are severely corrupt.
    Below is a list of 3rd party drivers present on your system -
    Code:
    **************************Sat Feb 14 23:13:38.915 2015 (UTC + 5:30)**************************
    AsrAppCharger.sys           Tue May 10 13:58:46 2011 (4DC8F73E)
    GEARAspiWDM.sys             Fri May  4 01:26:17 2012 (4FA2E2E1)
    AsrDrv101.sys               Tue Jan 15 11:55:51 2013 (50F4F66F)
    AsrRamDisk.sys              Thu May  9 14:20:45 2013 (518B6365)
    cfosspeed6.sys              Wed May 29 22:17:24 2013 (51A6311C)
    IOMap64.sys                 Tue Jul  2 13:57:47 2013 (51D28F03)
    SYMEVENT64x86.SYS           Sat Jul 27 07:56:58 2013 (51F32FF2)
    RTKVHD64.sys                Tue Jul 30 17:36:46 2013 (51F7AC56)
    SYMDS64.SYS                 Wed Jul 31 04:59:08 2013 (51F84C44)
    intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
    ccSetx64.sys                Tue Sep 24 09:28:04 2013 (52410DCC)
    asmtxhci.sys                Thu Jan  9 14:46:37 2014 (52CE68F5)
    asmthub3.sys                Thu Jan  9 14:46:42 2014 (52CE68FA)
    ikbevent.sys                Fri Jan 10 23:22:53 2014 (52D03375)
    imsevent.sys                Fri Jan 10 23:22:53 2014 (52D03375)
    ISCTD.sys                   Thu Jan 23 01:07:35 2014 (52E01DFF)
    dump_asstor64.sys           Mon Jan 27 15:00:34 2014 (52E6273A)
    asstor64.sys                Mon Jan 27 15:00:34 2014 (52E6273A)
    e1d64x64.sys                Tue Feb  4 14:44:25 2014 (52F0AF71)
    SYMNETS.SYS                 Thu Feb 13 16:55:14 2014 (52FCAB9A)
    SYMEFA64.SYS                Fri Feb 28 05:02:07 2014 (530FCAF7)
    TeeDriverx64.sys            Thu Mar 13 23:51:52 2014 (5321F740)
    INETMON.sys                 Thu Apr  3 22:20:43 2014 (533D9163)
    Ironx64.SYS                 Wed May 21 03:57:42 2014 (537BD6DE)
    SRTSPX64.SYS                Fri Jun 13 22:57:22 2014 (539B347A)
    mwac.sys                    Wed Jun 18 07:37:00 2014 (53A0F444)
    SRTSP64.SYS                 Thu Aug 21 02:26:53 2014 (53F50B95)
    mbam.sys                    Wed Sep  3 23:20:25 2014 (540754E1)
    MBAMSwissArmy.sys           Sat Sep 20 03:44:07 2014 (541CAAAF)
    nvhda64v.sys                Thu Oct  9 22:32:27 2014 (5436BFA3)
    EX64.SYS                    Sat Nov 15 14:44:03 2014 (5467195B)
    ENG64.SYS                   Sat Nov 15 14:45:33 2014 (546719B5)
    nvvad64v.sys                Thu Nov 20 21:03:54 2014 (546E09E2)
    eeCtrl64.sys                Wed Nov 26 01:45:44 2014 (5474E370)
    EraserUtilRebootDrv.sys     Wed Nov 26 01:45:44 2014 (5474E370)
    NvStreamKms.sys             Mon Jan 12 23:26:42 2015 (54B40ADA)
    BHDrvx64.sys                Fri Jan 23 06:16:20 2015 (54C199DC)
    IDSvia64.sys                Wed Jan 28 05:10:22 2015 (54C821E6)
    nvlddmkm.sys                Thu Feb  5 23:31:37 2015 (54D3B001)
    nvvadarm.sys                Thu Feb  5 23:54:46 2015 (54D3B56E)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Feb 14 09:00:18.688 2015 (UTC + 5:30)**************************
    iqvw64e.sys                 Thu Nov 14 20:52:43 2013 (5284EAC3)
    http://www.carrona.org/drivers/driver.php?id=AsrAppCharger.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    http://www.carrona.org/drivers/driver.php?id=AsrDrv101.sys
    http://www.carrona.org/drivers/driver.php?id=AsrRamDisk.sys
    http://www.carrona.org/drivers/driver.php?id=cfosspeed6.sys
    http://www.carrona.org/drivers/driver.php?id=IOMap64.sys
    http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=SYMDS64.SYS
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
    http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
    http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
    http://www.carrona.org/drivers/driver.php?id=ikbevent.sys
    http://www.carrona.org/drivers/driver.php?id=imsevent.sys
    http://www.carrona.org/drivers/driver.php?id=ISCTD.sys
    dump_asstor64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=asstor64.sys
    http://www.carrona.org/drivers/driver.php?id=e1d64x64.sys
    http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
    http://www.carrona.org/drivers/driver.php?id=SYMEFA64.SYS
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=INETMON.sys
    http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
    http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
    http://www.carrona.org/drivers/driver.php?id=mwac.sys
    http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
    http://www.carrona.org/drivers/driver.php?id=mbam.sys
    http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=EX64.SYS
    http://www.carrona.org/drivers/driver.php?id=ENG64.SYS
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
    http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
    http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    nvvadarm.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys

    Kindly follow the below steps -
    1. Please remove the ASUS Bloatware present on the system since it is known to cause problems.
    2. Are you using any RamDisk? If so, then please disable it.
    3. Please remove Norton & MalwareBytes till the time we are troubleshooting using this **TOOL** and **TOOL**.
    4. Please test your RAM by following this **GUIDE**.



    Let me know how it goes ^_^

    -Pranav
      My System SpecsSystem Spec

  3. #3


    Posts : 6
    Windows 8.1


    Hello!

    It appears the "Memory Management" BSOD has been fixed.
    I appreciate it so much!
      My System SpecsSystem Spec

  4. #4


    Posts : 6
    Windows 8.1


    On a different note, I've not begun to receive various BSOD, but whenever i try to run the program to get them into the ZIP file, they are not there. Is this something that has happened before?
    The 3 I've received (all when trying to download something) are
    "Reference By Pointer"
    "BAD_POOL_HEADER"
    and "SYSTEM_SERVICE_EXCEPTION"
    do I simply have to do something different to receive the dumps afteriv'e already run the program, or is there something specific wrong with my computer?
      My System SpecsSystem Spec

  5. #5


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by Orients View Post
    On a different note, I've not begun to receive various BSOD, but whenever i try to run the program to get them into the ZIP file, they are not there. Is this something that has happened before?
    The 3 I've received (all when trying to download something) are
    "Reference By Pointer"
    "BAD_POOL_HEADER"
    and "SYSTEM_SERVICE_EXCEPTION"
    do I simply have to do something different to receive the dumps afteriv'e already run the program, or is there something specific wrong with my computer?
    Hi Orients ^_^,

    Could you try that in Safe Mode?
    If that does not work then kindly go to the below path on your system -
    Code:
    C:/Windows/Minidumps
    Kindly copy the files inside that folder and then paste them over at Desktop else you would get Permissions error. Once you have pasted on the Desktop, kindly ZIP up the files and then upload them over here so that those could be analysed

    Let me know how it goes ^_^

    -Pranav
      My System SpecsSystem Spec

  6. #6


    Posts : 6
    Windows 8.1


    Attached is the most recent blue screen that I've experienced. Thank you.Attachment 58254
      My System SpecsSystem Spec

  7. #7


    Code:
    2: kd> .bugcheck
    Bugcheck code 0000004E
    Arguments 00000000`00000099 00000000`0032748c 00000000`00000000 00000000`002f508c
    
    2: kd> kn
     # Child-SP          RetAddr           Call Site
    00 ffffd000`24db8488 fffff800`fd214e3f nt!KeBugCheckEx //Bugcheck, memory corruption
    01 ffffd000`24db8490 fffff800`fd0a8e52 nt!MiBadShareCount+0x4b //The share count is bad
    02 ffffd000`24db84d0 fffff800`fd13db71 nt!MiLockAndDecrementShareCount+0x6e //Lock and decrement the share count for that page
    03 ffffd000`24db8500 fffff800`fd13efae nt!MiConvertStandbyToProto+0x4e5 //Trim memory, invalidate page and point the PTE to prototype PTE
    04 ffffd000`24db85c0 fffff800`fd4ffb9b nt!MiSharePage+0x8b2 //Share the page accross multiple processes
    05 ffffd000`24db86e0 fffff800`fd500021 nt!MiProcessCrcList+0x14f  //Internal function, possible cyclic redundancy checks to check for errors
    06 ffffd000`24db8760 fffff800`fd42cb1d nt!MmCombineIdenticalPages+0x401 //Combine identical pages in memory (non dirty)
    07 ffffd000`24db88a0 fffff800`fd1731b3 nt!NtSetSystemInformation+0x431 //Set system information
    08 ffffd000`24db8b00 00007ff9`3007264a nt!KiSystemServiceCopyEnd+0x13 //Transition to Kernel mode
    09 00000097`b445fde8 00000000`00000000 0x00007ff9`3007264a //User mode
    
    2: kd> !pfn 32748c
    Unable to get PFN database address fffff800fd37a0e8
    
    //Context not saved
    
    2: kd> dt nt!_MMPFN 32748c
       +0x000 u1               : <unnamed-tag>
       +0x008 u2               : <unnamed-tag>
       +0x010 PteAddress       : ???? 
       +0x010 VolatilePteAddress : ???? 
       +0x010 Lock             : ??
       +0x010 PteLong          : ??
       +0x018 u3               : <unnamed-tag>
       +0x01c NodeBlinkLow     : ??
       +0x01e Unused           : ??
       +0x01e VaType           : ??
       +0x01f ViewCount        : ??
       +0x01f NodeFlinkLow     : ??
       +0x020 OriginalPte      : _MMPTE
       +0x028 u4               : <unnamed-tag>
    
    //No information at all... helpful...
    Well, we can't find out what went wrong because we only have a minidump.
    Taking an educated guess, and looking at the callstack it's most likely physical memory was corrupted and therefore invalidated a PTE.
    I cannot say for certain, I am only guessing.
    To be honest though, this is most likely bad RAM, especially with your other errors (0x1A, arg 1: 0x5003).



    Code:
    0: kd> .bugcheck
    Bugcheck code 0000001A
    Arguments 00000000`00005003 fffff580`10804000 00000000`00000688 00000068`a0000d30
    
    0: kd> k
    Child-SP          RetAddr           Call Site
    ffffd000`2533c5a8 fffff803`cf57a501 nt!KeBugCheckEx //Memory corruption, bugcheck
    ffffd000`2533c5b0 fffff803`cf451ed3 nt!MiAllocateWsle+0xe651 //Allocate memory for the working set of this process
    ffffd000`2533c610 fffff803`cf4503d9 nt!MiCompleteProtoPteFault+0x1d3 //Finish the prototype PTE fault
    ffffd000`2533c6c0 fffff803`cf47c5ab nt!MiResolveTransitionFault+0x409 //Change PTE state from transition to valid
    ffffd000`2533c760 fffff803`cf47a7fb nt!MiResolveProtoPteFault+0x20b //Prototype fault, the page was marked invalid becuase it was removed from the working set, set the PTE to point to the address
    ffffd000`2533c800 fffff803`cf475b0f nt!MiDispatchFault+0x2bb 
    ffffd000`2533c940 fffff803`cf565c2f nt!MmAccessFault+0x54f //Page fault handler
    ffffd000`2533cb00 00007ff8`616465dd nt!KiPageFault+0x12f //Page fault
    00000067`fc11ce50 00000000`00000000 0x00007ff8`616465dd
    Okay, so this might look complex, but lets break this down...
    We tried to access memory which wasn't in the process' working set, we walk the page table entries to find the page and bring it into the working set (soft page fault). Right, so the ProtoPteFault essentially means when the page is no longer in the working set of a process, it's marked as invalid (even though the contents are still valid), its state becomes a transition state. Now, when we try to access that page and place it in the working set, the page fault handler usually checks the page frame number in the PTE, yet this won't work because we don't know whether the page is in memory, or whether it's in use by another process. So, the current PTE points to a prototype PTE which points to the PFN, the page fault handler checks the PFN by accessing the prototype PTE.
    Okay, so we resolved the fault by finding the page (which was present in memory still), the contents are still valid and working correctly, so now all we have to do is allocated memory from RAM for the working set of the process to put the page in, we then find corruption and crash .Almost certainly, this is caused by a failure in the physical address we tried to allocate, because that page was empty, and the memory we tried to assign to that address was fine, so the only cause is RAM. There might be special cases that I don't know of which might invalidate this cause, yet from what I know, it's almost always bad RAM.

    Have you tried running Memtest86+? If not, I suggest you run it for 8 passes to confirm my theory.
      My System SpecsSystem Spec

  8. #8


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Wao Mysers. Fantastic explanation. I wish I could rep you more but sadly can't

    Seems like the allocation of working set did not go through as predicted and hence the system crashed, right? I just wonder how many steps, Windows takes to ensure that data is not corrupted...
      My System SpecsSystem Spec

  9. #9


    Posts : 6
    Windows 8.1


    Thank you so much for the replies.
    I haven't gotten a chance to run the memtest completely yet, but I will get back asap.

    I appreciate all the help.
      My System SpecsSystem Spec

  10. #10


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by Orients View Post
    Thank you so much for the replies.
    I haven't gotten a chance to run the memtest completely yet, but I will get back asap.

    I appreciate all the help.
    Sure thing. Let us know how it goes ^_^

    -Pranav
      My System SpecsSystem Spec

BSOD "MEMORY MANAGEMENT" Error
Related Threads
Greetings, I'm having "kernel data inpage error" on this computer almost from the beginning. It seems to occur randomly (totally 6 times): watching video, reading pdf, working in 3d modeling program, playing a game, browsing internet. I've read some posts earlier and tried this: 1. run...
Hi Everyone, First post here, allow me to thank you in advance for your good help - people like me who have limited information on diagnostics and repair owe a deep debt of gratitude for your service. :) I own an Acer Aspire V5-571P-6815, which has put up the Recovery blue screen of death,...
Hello, Following the forum guidelines I am posting a compressed file from your SF Diagnostic tool. This was done shortly after a BSOD. Thanks for your support in helping me understand what is the cause of those frequent BSOD. Joce
Hi! I have very little experiance dealing with these types of errors, the full message I recieve is "DRIVER_IRQL_OR_EQUAL (tcpip.sys)". This began a few days ago, and appears to happen at very different rates. I've tried numerous things but none seemed to have helped. Here is the minidump...
BSOD Memory Management error please help in BSOD Crashes and Debugging
I'm going crazy and need some help with this. I have replaced every piece of hardware on this build and I cant get rid of the memory management bsod. It happens randomly. During games, installations, boot up, basically whenever it feels like it. I've tried everything I can think of and would really...
Hello, I re-installed Windows 8 , everything worked fine until today I started having BSOD's saying I have "Memory Management" , "IRQL Not Less Or Equal" , "kernel security check failure" , "DPC Watchdog Violation", So... I attached the files from the Diagnostic Tool, I hope you will help me on...
Hi all, When my notebook is running on battery and I plug-in the charger or when the charger is plugged-in and I want to run on battery and unplugged it, it crashed with a BSOD "ATTEMPTED_EXECUTE_OF_NON_EXECUTED MEMORY".'' The same behavior can be observed when I try to change the brightness...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook