MEMORY.DMP

Diskutiere und helfe bei MEMORY.DMP im Bereich Windows 10 Probleme bei einer Lösung;

  1. ThomasEhmann
    ThomasEhmann Gast

    Hallo und gutes neues Jahr allerseits!


    Ich habe ein frisch installiertes Windows 10 Pro auf einem Intel Core i7 - 4770 (64Bit) PC.

    NVIDIA Grafikkarte

    Samsung SSD120 GB


    Hatte heute einen Blue Screen.


    Die DMP Datei habe ich mit Windows Driver Kit 10 über Open Crash DUMP geöffnet

    Kann aber den Fehler nicht genau erkennen und bitte deswegen um Hilfe!


    Bin für Unterstützung dakbar


    mfg


    Thomas


    Hier der DUMP:

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

    Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\ehman\Desktop\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 14393 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
    Machine Name:
    Kernel base = 0xfffff800`7e20a000 PsLoadedModuleList = 0xfffff800`7e50f060
    Debug session time: Thu Jan 5 12:49:25.177 2017 (UTC + 1:00)
    System Uptime: 1 days 14:38:25.340
    Loading Kernel Symbols
    ...............................................................
    .............................................................Page 104a43 not present in the dump file. Type ".hh dbgerr004" for details
    ...
    ......................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 0000008e`1d61d018). Type ".hh dbgerr001" for details
    Loading unloaded module list
    .....................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff8007e398f1a, ffffc4804ab3bea0, 0}
    Page 104a43 not present in the dump file. Type ".hh dbgerr004" for details
    Page 104a43 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3538a )
    Followup: MachineOwner
    ---------
    6: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff8007e398f1a, Address of the instruction which caused the bugcheck
    Arg3: ffffc4804ab3bea0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Debugging Details:
    ------------------
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    Page 1000 not present in the dump file. Type ".hh dbgerr004" for details
    DUMP_CLASS: 1
    DUMP_QUALIFIER: 401
    BUILD_VERSION_STRING: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
    SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
    SYSTEM_PRODUCT_NAME: B85-HD3
    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: F2
    BIOS_DATE: 04/24/2013
    BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
    BASEBOARD_PRODUCT: B85-HD3
    BASEBOARD_VERSION: x.x
    DUMP_TYPE: 1
    BUGCHECK_P1: c0000005
    BUGCHECK_P2: fffff8007e398f1a
    BUGCHECK_P3: ffffc4804ab3bea0
    BUGCHECK_P4: 0
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.
    FAULTING_IP:
    nt! ?? ::FNODOBFM::`string'+3538a
    fffff800`7e398f1a 488b5208 mov rdx,qword ptr [rdx+8]
    CONTEXT: ffffc4804ab3bea0 -- (.cxr 0xffffc4804ab3bea0)
    rax=0000000000000000 rbx=ffff838133e27040 rcx=ffff838133e27040
    rdx=0000000000000040 rsi=0000000000000000 rdi=ffff838133e27040
    rip=fffff8007e398f1a rsp=ffffc4804ab3c8b0 rbp=ffffc4804ab3c980
    r8=0000000000000001 r9=0000000000000000 r10=7fff83812f9bd500
    r11=ffffc4803c480180 r12=0000000000008000 r13=ffffffffffffffff
    r14=ffff8381306e2080 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
    nt! ?? ::FNODOBFM::`string'+0x3538a:
    fffff800`7e398f1a 488b5208 mov rdx,qword ptr [rdx+8] ds:002b:00000000`00000048=????????????????
    Resetting default scope
    CPU_COUNT: 8
    CPU_MHZ: d40
    CPU_VENDOR: GenuineIntel
    CPU_FAMILY: 6
    CPU_MODEL: 3c
    CPU_STEPPING: 3
    CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x3B
    PROCESS_NAME: MicrosoftEdge.exe
    CURRENT_IRQL: 0
    ANALYSIS_SESSION_HOST: DESKTOP-THOMAS
    ANALYSIS_SESSION_TIME: 01-05-2017 13:27:30.0479
    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
    LAST_CONTROL_TRANSFER: from fffff8007e6c63b0 to fffff8007e398f1a
    STACK_TEXT:
    ffffc480`4ab3c8b0 fffff800`7e6c63b0 : ffff8381`33e27628 00000000`00000000 0000008e`1d6fc000 ffff8381`33e27040 : nt! ?? ::FNODOBFM::`string'+0x3538a
    ffffc480`4ab3c940 fffff800`7e6c16be : 00000000`00000000 ffff8381`33e27040 00000000`00000000 ffff8381`306e2080 : nt!PspExitThread+0x328
    ffffc480`4ab3ca80 fffff800`7e6462a0 : ffff8381`33e27040 00000000`00000000 ffff8381`33e27040 00000000`00000000 : nt!PspTerminateThreadByPointer+0x96
    ffffc480`4ab3cac0 fffff800`7e35f393 : ffff8381`33e27040 ffffc480`4ab3cb80 00000000`00000010 ffff8381`2cf5c130 : nt!NtTerminateThread+0x44
    ffffc480`4ab3cb00 00007fff`0e6b6b34 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    0000008e`246ff798 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`0e6b6b34

    THREAD_SHA1_HASH_MOD_FUNC: ae9a019bd67f035486f0e8ec73779782813a4f11
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7922c12f7f08c3141d2280d12def08cfa661ff56
    THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84
    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+3538a
    fffff800`7e398f1a 488b5208 mov rdx,qword ptr [rdx+8]
    FAULT_INSTR_CODE: 8528b48
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+3538a
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 584a77f6
    STACK_COMMAND: .cxr 0xffffc4804ab3bea0 ; kb
    BUCKET_ID_FUNC_OFFSET: 3538a
    FAILURE_BUCKET_ID: 0x3B_nt!_??_::FNODOBFM::_string_
    BUCKET_ID: 0x3B_nt!_??_::FNODOBFM::_string_
    PRIMARY_PROBLEM_CLASS: 0x3B_nt!_??_::FNODOBFM::_string_
    TARGET_TIME: 2017-01-05T11:49:25.000Z
    OSBUILD: 14393
    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: 2016-12-09 10:23:02
    BUILDDATESTAMP_STR: 161208-2252
    BUILDLAB_STR: rs1_release_inmarket
    BUILDOSVER_STR: 10.0.14393.576.amd64fre.rs1_release_inmarket.161208-2252
    ANALYSIS_SESSION_ELAPSED_TIME: 5b0
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x3b_nt!_??_::fnodobfm::_string_
    FAILURE_ID_HASH: {5f10a9e9-c934-7c57-36ae-ae94b7494544}
    Followup: MachineOwner
    ---------

    Weiterlesen...
     
    #1 ThomasEhmann, 5. Januar 2017
Thema:

MEMORY.DMP