Windows 8 and 8.1 Forums

BSOD Memory.dmp Error?

  1. #1


    Posts : 3
    Win 7

    BSOD Memory.dmp Error?


    Hey,

    I am trying to fix a friends Laptop for her, she keeps getting what I presume is BSOD in Windows 8(I haven't any experience with Windows 8)

    I have tried to look at the dump file but I have struggled to open it, so If I attach it here I would appreciate any help I can be given, cheers!


    EDIT: Just seen the thing I was supposed to read first, so bare with me.

      My System SpecsSystem Spec

  2. #2


    Hi

    Please post a Speccy snapshot of your system by following Speccy - Publish Snapshot of your System Specs - Windows 7 Help Forums
      My System SpecsSystem Spec

  3. #3


    Posts : 3
    Win 7


    Quote Originally Posted by Anshad Edavana View Post
    Hi

    Please post a Speccy snapshot of your system by following Speccy - Publish Snapshot of your System Specs - Windows 7 Help Forums
    http://speccy.piriform.com/results/j...6FCPcJ5nWuKbtR

    thank you
      My System SpecsSystem Spec

  4. #4


    Posts : 1,360
    Windows 8.1 Enterprise


    Hi John18,

    Please remove ASUS Live Update from the Control Panel.

    Also, manually run Live Update for Norton. The current version is 21.1


    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\User\Desktop\122713-18937-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    Machine Name:
    Kernel base = 0xfffff801`cd005000 PsLoadedModuleList = 0xfffff801`cd2d1a20
    Debug session time: Fri Dec 27 12:53:22.446 2013 (UTC - 5:00)
    System Uptime: 0 days 1:41:36.291
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7A, {4, 0, fffffa8003b3da40, 3060000}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+24cc6 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: 0000000000000004, lock type that was held (value 1,2,3, or PTE address)
    Arg2: 0000000000000000, error status (normally i/o status code)
    Arg3: fffffa8003b3da40, current process (virtual address for lock type 3, or PTE)
    Arg4: 0000000003060000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    
    ERROR_CODE: (NTSTATUS) 0 - STATUS_SUCCESS
    
    BUGCHECK_STR:  0x7a_0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  LiveUpdate.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff801cd11a08c to fffff801cd05f440
    
    STACK_TEXT:  
    fffff880`1b789808 fffff801`cd11a08c : 00000000`0000007a 00000000`00000004 00000000`00000000 fffffa80`03b3da40 : nt!KeBugCheckEx
    fffff880`1b789810 fffff801`cd0dbb67 : 00000000`00000002 fffff880`1b789970 fffffa80`03e9b568 fffff880`1b789960 : nt! ?? ::FNODOBFM::`string'+0x24cc6
    fffff880`1b7898f0 fffff801`cd099d8f : fffffa80`03ab9b00 fffffa80`03e9b568 00000000`c0033333 fffff880`1b789a40 : nt!MiIssueHardFault+0x1b7
    fffff880`1b7899c0 fffff801`cd05ceee : 00000000`00000001 00000000`08792b40 fffff880`1b789a01 fffff880`1b789b00 : nt!MmAccessFault+0x81f
    fffff880`1b789b00 00000000`6104c433 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0851f090 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6104c433
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+24cc6
    fffff801`cd11a08c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+24cc6
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51a966cd
    
    IMAGE_VERSION:  6.2.9200.16628
    
    BUCKET_ID_FUNC_OFFSET:  24cc6
    
    FAILURE_BUCKET_ID:  0x7a_0_nt!_??_::FNODOBFM::_string_
    
    BUCKET_ID:  0x7a_0_nt!_??_::FNODOBFM::_string_
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x7a_0_nt!_??_::fnodobfm::_string_
    
    FAILURE_ID_HASH:  {87ed9903-76d8-bd16-10fb-61b59edbe1ad}
    
    Followup: MachineOwner
    ---------
      My System SpecsSystem Spec

  5. #5


    Posts : 3
    Win 7


    Quote Originally Posted by ectech View Post
    Hi John18,

    Please remove ASUS Live Update from the Control Panel.

    Also, manually run Live Update for Norton. The current version is 21.1


    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\User\Desktop\122713-18937-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    Machine Name:
    Kernel base = 0xfffff801`cd005000 PsLoadedModuleList = 0xfffff801`cd2d1a20
    Debug session time: Fri Dec 27 12:53:22.446 2013 (UTC - 5:00)
    System Uptime: 0 days 1:41:36.291
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7A, {4, 0, fffffa8003b3da40, 3060000}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+24cc6 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: 0000000000000004, lock type that was held (value 1,2,3, or PTE address)
    Arg2: 0000000000000000, error status (normally i/o status code)
    Arg3: fffffa8003b3da40, current process (virtual address for lock type 3, or PTE)
    Arg4: 0000000003060000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    
    ERROR_CODE: (NTSTATUS) 0 - STATUS_SUCCESS
    
    BUGCHECK_STR:  0x7a_0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  LiveUpdate.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff801cd11a08c to fffff801cd05f440
    
    STACK_TEXT:  
    fffff880`1b789808 fffff801`cd11a08c : 00000000`0000007a 00000000`00000004 00000000`00000000 fffffa80`03b3da40 : nt!KeBugCheckEx
    fffff880`1b789810 fffff801`cd0dbb67 : 00000000`00000002 fffff880`1b789970 fffffa80`03e9b568 fffff880`1b789960 : nt! ?? ::FNODOBFM::`string'+0x24cc6
    fffff880`1b7898f0 fffff801`cd099d8f : fffffa80`03ab9b00 fffffa80`03e9b568 00000000`c0033333 fffff880`1b789a40 : nt!MiIssueHardFault+0x1b7
    fffff880`1b7899c0 fffff801`cd05ceee : 00000000`00000001 00000000`08792b40 fffff880`1b789a01 fffff880`1b789b00 : nt!MmAccessFault+0x81f
    fffff880`1b789b00 00000000`6104c433 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0851f090 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6104c433
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+24cc6
    fffff801`cd11a08c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+24cc6
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51a966cd
    
    IMAGE_VERSION:  6.2.9200.16628
    
    BUCKET_ID_FUNC_OFFSET:  24cc6
    
    FAILURE_BUCKET_ID:  0x7a_0_nt!_??_::FNODOBFM::_string_
    
    BUCKET_ID:  0x7a_0_nt!_??_::FNODOBFM::_string_
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x7a_0_nt!_??_::fnodobfm::_string_
    
    FAILURE_ID_HASH:  {87ed9903-76d8-bd16-10fb-61b59edbe1ad}
    
    Followup: MachineOwner
    ---------

    Hey have done both these things, thanks for giving me the dump text too, will leave this thread unresolved for 24hrs incase BSOD occurs again,thanks so much
      My System SpecsSystem Spec

  6. #6


    Posts : 1,360
    Windows 8.1 Enterprise


    Your welcome
      My System SpecsSystem Spec

BSOD Memory.dmp Error?
Related Threads
memory.dmp error in BSOD Crashes and Debugging
hi guys...my computer would not shutdown from windows command only with force button, and when i turn it on it says that memory.dmp error... here is my SF Debug Tool file...:) 57353
Hello there, Here is my logs; NELLOW-SWS-Mon_12_29_2014_170647_14.zip :: Free File Hosting - File Dropper: File Host for Mp3, Videos, Music, Documents. The thing is whenever it goes sleep and I try to wake it up, blue s*** of death happens. I even bought a new ram (a single 8gb ram) instead of...
*edit* Realized I did the crashdumps incorrectly, will do another one when it crashes again!
Hi guys. I've had my computer for around 4 years now and I have always had this bug that I have been unable to resolve. In the past, I had no idea what to do is the computer would just freeze up and not go to blue screen, However, since upgrading to Windows 8.1 it has been giving me a blue screen...
BSOD memory managemnt error starting up in BSOD Crashes and Debugging
My computer was fine one day then, today when I was just browsing the internet it crashes. The computer restarts and then tells me there was a problem, then when I log in I get nothing but a black screen but my mouse can still move around. sometimes when starting up it takes me to the page and asks...
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...
BSOD - memory dump error/crash in BSOD Crashes and Debugging
I haven't been able to catch the exact errors when it has happened but it has only started since I installed Windows 8. I assume it's some sort of driver issue but any help would be great. Thanks in advance, Brent
Eight Forums Android App Eight Forums IOS App Follow us on Facebook