1.    2 Weeks Ago #1
    Join Date : Nov 2017
    Posts : 2
    Microsoft Windows 10 Home 32 bits

    Hi,here is my memory.dmp information,what is next?


    Last tuesday I have problems with one of my disk and this was the memory.dmp info:

    Code:
    Microsoft (R) Windows Debugger Version 10.0.16299.15 X86Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
    
    Symbol search path is: srv*
    Executable search path is: 
    Windows 10 Kernel Version 15063 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    Machine Name:
    Kernel base = 0xfffff801`5028a000 PsLoadedModuleList = 0xfffff801`505d65c0
    Debug session time: Wed Nov  1 14:29:29.195 2017 (UTC - 6:00)
    System Uptime: 0 days 0:00:14.874
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    ....................
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck EF, {ffffb40865da3580, 0, 0, 0}
    
    Probably caused by : ntdll.dll ( ntdll!NtTerminateProcess+14 )
    
    Followup:     MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_PROCESS_DIED (ef)
            A critical system process died
    Arguments:
    Arg1: ffffb40865da3580, Process object or thread object
    Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 401
    
    BUILD_VERSION_STRING:  15063.0.amd64fre.rs2_release.170317-1834
    
    SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.
    
    SYSTEM_SKU:  To Be Filled By O.E.M.
    
    SYSTEM_VERSION:  To Be Filled By O.E.M.
    
    BIOS_VENDOR:  American Megatrends Inc.
    
    BIOS_VERSION:  P1.90
    
    BIOS_DATE:  07/11/2013
    
    BASEBOARD_MANUFACTURER:  ASRock
    
    BASEBOARD_PRODUCT:  H61M-VG3
    
    BASEBOARD_VERSION:                        
    
    DUMP_TYPE:  1
    
    BUGCHECK_P1: ffffb40865da3580
    
    BUGCHECK_P2: 0
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 0
    
    KERNEL_LOG_FAILING_PROCESS:  
    
    PROCESS_NAME:  wininit.exe
    
    CRITICAL_PROCESS:  wininit.exe
    
    EXCEPTION_CODE: (Win32) 0x65da1200 (1708790272) - <Unable to get error code text>
    
    ERROR_CODE: (NTSTATUS) 0x65da1200 - <Unable to get error code text>
    
    CPU_COUNT: 4
    
    CPU_MHZ: bb1
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3a
    
    CPU_STEPPING: 9
    
    CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 1B'00000000 (cache) 1B'00000000 (init)
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0xEF
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  MARIO2-PC
    
    ANALYSIS_SESSION_TIME:  11-03-2017 12:22:09.0780
    
    ANALYSIS_VERSION: 10.0.16299.15 x86fre
    
    LAST_CONTROL_TRANSFER:  from fffff8015096a151 to fffff801503f6580
    
    STACK_TEXT:  
    ffffcb81`04cdc9c8 fffff801`5096a151 : 00000000`000000ef ffffb408`65da3580 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    ffffcb81`04cdc9d0 fffff801`508a705d : 00000000`00000000 00000000`00000000 ffffb408`65da3580 00000000`00000000 : nt!PspCatchCriticalBreak+0xc9
    ffffcb81`04cdca20 fffff801`50784009 : ffffffff`00000000 00000000`00000000 ffffb408`65da1200 00000000`00000000 : nt!PspTerminateAllThreads+0x122e01
    ffffcb81`04cdca90 fffff801`50401413 : ffffb408`65da3580 ffffb408`65da1200 ffffcb81`04cdcb80 00000000`00000000 : nt!NtTerminateProcess+0x199
    ffffcb81`04cdcb00 00007ffc`f07b5924 : 00007ffc`f075d29b 00000000`000036b1 00000000`000036b1 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000081`08fafcd8 00007ffc`f075d29b : 00000000`000036b1 00000000`000036b1 00000000`00000000 00007ffc`ecc12810 : ntdll!NtTerminateProcess+0x14
    00000081`08fafce0 00007ffc`ede9c0da : 00000000`000036b1 00000081`08fafdb0 00000000`00000000 00000000`00000000 : ntdll!RtlExitUserProcess+0x5b
    00000081`08fafd10 00007ffc`ed5861f4 : 00000000`00070001 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!ExitProcessImplementation+0xa
    00000081`08fafd40 00007ffc`ed58617b : 00000000`000036b1 00000000`00000000 00007ffc`ed586100 00000081`08fafd90 : ucrtbase!exit+0xf4
    00000081`08fafd70 00007ffc`ed584b60 : 00000000`000036b1 00000000`00000000 00000000`00000000 00000000`00000001 : ucrtbase!exit+0x7b
    00000081`08fafdc0 00007ff7`f2c3c0c1 : 00000000`000036b1 00000000`00000000 00000000`00000000 00000000`00000000 : ucrtbase!__crt_state_management::wrapped_invoke<void (__cdecl*)(int),int,void>+0x20
    00000081`08fafdf0 00007ffc`ede92774 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : wininit!__scrt_common_main_seh+0x125
    00000081`08fafe30 00007ffc`f0780d51 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14
    00000081`08fafe60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  c4ae3caaed5413b8dc6cb9e106e408a5ef763cee
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c6367ddd39a1d02d6238a1d4dc77878e2ec810d4
    
    THREAD_SHA1_HASH_MOD:  75dc4621d5fdb5febfcc7ab5de679ec629c0b75e
    
    FOLLOWUP_IP: 
    ntdll!NtTerminateProcess+14
    00007ffc`f07b5924 c3              ret
    
    FAULT_INSTR_CODE:  c32ecdc3
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  ntdll!NtTerminateProcess+14
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ntdll
    
    IMAGE_NAME:  ntdll.dll
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  14
    
    FAILURE_BUCKET_ID:  0xEF_wininit.exe_BUGCHECK_CRITICAL_PROCESS_65da1200_ntdll!NtTerminateProcess
    
    BUCKET_ID:  0xEF_wininit.exe_BUGCHECK_CRITICAL_PROCESS_65da1200_ntdll!NtTerminateProcess
    
    PRIMARY_PROBLEM_CLASS:  0xEF_wininit.exe_BUGCHECK_CRITICAL_PROCESS_65da1200_ntdll!NtTerminateProcess
    
    TARGET_TIME:  2017-11-01T20:29:29.000Z
    
    OSBUILD:  15063
    
    OSSERVICEPACK:  0
    
    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:  2017-09-04 23:09:34
    
    BUILDDATESTAMP_STR:  170317-1834
    
    BUILDLAB_STR:  rs2_release
    
    BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834
    
    ANALYSIS_SESSION_ELAPSED_TIME:  1145
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xef_wininit.exe_bugcheck_critical_process_65da1200_ntdll!ntterminateprocess
    
    FAILURE_ID_HASH:  {a038da76-968d-f8d8-a346-ed52b33195dd}
    
    Followup:     MachineOwner
    ---------
    What is next?
      My ComputerSystem Spec
  2.    2 Weeks Ago #2
    Join Date : Apr 2017
    Posts : 8,703
    windows 10 professional version 1607 build 14393.969 64 bit

    1) run the DM log collector and post a zip into the thread.
    Use English as the default language so that the files can be scanned and read for the troubleshooting.
    BSOD - Posting Instructions - Windows 10 Forums

    2) Update the system specs in the "My Computer" section.
    How To Fill Out Your System Specs
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums General Tips Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
Stop System Volume Information on USB Memory Stick?
Hello ALL: I keep seeing "solutions" to not having my system...64 Bit Win 10 PRO...create a System Volume Information Folder. I only want to do this on USB Memory Sticks so that when I use them in our cars the folder is not there. It keeps adding...
Customization
Memory Leak or Faulty Memory Use Reporting? Needing some expert opinio
Afternoon ladies n' gents, so here's the deal: Under task manager it reports that my processes are using 48% of my memory. Now, after taking a moment to fire up the ol' calculator and adding up all the individual reported memory usage for each...
Performance & Maintenance
Slow Memory leak memory is increasing slowly after 1 week is 90%
we have windows 10 of a new hp pc prodesk 400 g3 mt business pc. we cannot identify the problem.. we used the hp drivers software and fully updated windows 10 and the latest drivers. Please recommend troubleshooting steps what is causing the...
Performance & Maintenance
High Memory Usage/ Low Memory Popup on Win10 8gb Laptop
It seems that I've been getting low memory issues ever since upgrading to Win10, but I'm not 100% certain if thats the issue. I thought about uprading to 16gb ram, but I'd like to know if theres some other fix for this. I can't multitask as I used...
Performance & Maintenance
High memory usage / Memory leak caused by Intel driver
Hello, I'm running a 64 bit Windows 10 laptop. On idle, the System process is showing a high memory usage of more than 150 MB, usually more than 200 MB. Using poolmon the pooltag SpDN showed up with a memory leak. It leads to the Intel Matrix...
Performance & Maintenance
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 09:10.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums