locked
Windows 2012 r2 Blue Screen Error RRS feed

  • Question

  • May someone please help me,

    We have a windows 2012 r2 which is running Exchange 2013, GFI and Acronis backup agent.

    The computer restarts and gives the following information:

    your computer run into a problem and restarted. Mostly and clicking on send, to send the error to microsoft.

    the memory error dump is shown below:


    Microsoft (R) Windows Debugger Version 10.0.15063.468 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [\\unity-dcp\profiles$\Mbikon\Desktop\100217-37546-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is: 
    Windows 8.1 Kernel Version 9600 MP (20 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS
    Built by: 9600.18758.amd64fre.winblue_ltsb.170707-0600
    Machine Name:
    Kernel base = 0xfffff803`f8611000 PsLoadedModuleList = 0xfffff803`f88e3650
    Debug session time: Mon Oct  2 23:00:00.968 2017 (UTC + 2:00)
    System Uptime: 1 days 22:47:18.914
    Loading Kernel Symbols
    .

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.

    ..............................................................
    ................................................................
    .....................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7A, {fffff6e8008571f0, ffffffffc00000c0, 438ab6be0, ffffd0010ae3e000}

    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+245e9 )

    Followup:     MachineOwner
    ---------

    14: 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: fffff6e8008571f0, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc00000c0, error status (normally i/o status code)
    Arg3: 0000000438ab6be0, current process (virtual address for lock type 3, or PTE)
    Arg4: ffffd0010ae3e000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

    Debugging Details:
    ------------------


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  6.3.9600.18758 (winblue_ltsb.170707-0600)

    SYSTEM_MANUFACTURER:  Dell Inc.

    SYSTEM_PRODUCT_NAME:  PowerEdge R730

    SYSTEM_SKU:  SKU=NotProvided;ModelName=PowerEdge R730

    BIOS_VENDOR:  Dell Inc.

    BIOS_VERSION:  2.4.3

    BIOS_DATE:  01/17/2017

    BASEBOARD_MANUFACTURER:  Dell Inc.

    BASEBOARD_PRODUCT:  072T6D

    BASEBOARD_VERSION:  A05

    DUMP_TYPE:  2

    BUGCHECK_P1: fffff6e8008571f0

    BUGCHECK_P2: ffffffffc00000c0

    BUGCHECK_P3: 438ab6be0

    BUGCHECK_P4: ffffd0010ae3e000

    ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.

    BUGCHECK_STR:  0x7a_c00000c0

    CPU_COUNT: 14

    CPU_MHZ: 960

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 4f

    CPU_STEPPING: 1

    CPU_MICROCODE: 6,4f,1,0 (F,M,S,R)  SIG: B00001F'00000000 (cache) B00001F'00000000 (init)

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_SESSION_HOST:  MBIKON-PC

    ANALYSIS_SESSION_TIME:  10-03-2017 07:47:35.0848

    ANALYSIS_VERSION: 10.0.15063.468 x86fre

    LAST_CONTROL_TRANSFER:  from fffff803f87938b9 to fffff803f875eda0

    STACK_TEXT:  
    ffffd001`02954698 fffff803`f87938b9 : 00000000`0000007a fffff6e8`008571f0 ffffffff`c00000c0 00000004`38ab6be0 : nt!KeBugCheckEx
    ffffd001`029546a0 fffff803`f869b764 : 00000000`00000002 ffffd001`029547c8 fffff803`f8964ec0 ffffe001`00000000 : nt! ?? ::FNODOBFM::`string'+0x245e9
    ffffd001`02954790 fffff803`f8656d3a : fffff803`f8964ec0 ffffe001`906a0040 00000000`00000001 fffff803`f8761caf : nt!MiIssueHardFault+0x184
    ffffd001`02954810 fffff803`f86d540c : 00000000`00000001 00000000`00000002 00000000`00000000 fffff803`f86bdf46 : nt!MmAccessFault+0x5ba
    ffffd001`029549d0 fffff803`f874418f : ffffe001`99784158 00000000`00000080 ffffe001`991da158 00000000`00000000 : nt!MiInPageSingleKernelStack+0x150
    ffffd001`02954ba0 fffff803`f8678074 : ffffe001`906a0040 ffffe001`906a0040 00000038`00010017 00000400`00000188 : nt!KeSwapProcessOrStack+0xb3
    ffffd001`02954c00 fffff803`f87653c6 : ffffd001`02540180 ffffe001`906a0040 ffffd001`0254f1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd001`02954c60 00000000`00000000 : ffffd001`02955000 ffffd001`0294f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND:  kb

    THREAD_SHA1_HASH_MOD_FUNC:  a0341fc67153271856ef0a04893423f5dff5bcc1

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  44779c14eeb59b59d947252a05b95c522c8ad182

    THREAD_SHA1_HASH_MOD:  cb5f414824c2521bcc505eaa03e92fa10922dad8

    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+245e9
    fffff803`f87938b9 cc              int     3

    FAULT_INSTR_CODE:  3fff81cc

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+245e9

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  595f98b0

    IMAGE_VERSION:  6.3.9600.18758

    BUCKET_ID_FUNC_OFFSET:  245e9

    FAILURE_BUCKET_ID:  0x7a_c00000c0_nt!_??_::FNODOBFM::_string_

    BUCKET_ID:  0x7a_c00000c0_nt!_??_::FNODOBFM::_string_

    PRIMARY_PROBLEM_CLASS:  0x7a_c00000c0_nt!_??_::FNODOBFM::_string_

    TARGET_TIME:  2017-10-02T21:00:00.000Z

    OSBUILD:  9600

    OSSERVICEPACK:  18758

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  272

    PRODUCT_TYPE:  3

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 8.1

    OSEDITION:  Windows 8.1 Server TerminalServer SingleUserTS

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2017-07-07 16:20:32

    BUILDDATESTAMP_STR:  170707-0600

    BUILDLAB_STR:  winblue_ltsb

    BUILDOSVER_STR:  6.3.9600.18758

    ANALYSIS_SESSION_ELAPSED_TIME:  849

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0x7a_c00000c0_nt!_??_::fnodobfm::_string_

    FAILURE_ID_HASH:  {90f07b7f-b6ca-d03a-b3d4-2f5aff8f8644}

    Followup:     MachineOwner
    ---------

    may somebody please assist me.

    Tuesday, October 3, 2017 5:57 AM