none
Pantalla azul, reinicio de equipo aleatorio windows server 2008 R2 - crash dump RRS feed

  • Pregunta

  • Buenos días, tengo un servidor windows server 2008 xeon e3-1220 3.1GHZ con 8GB de RAM que uso fundamentalmente para hospedaje de sitios web.

    Desde hace unas semanas se producen aleatoriamente reinicios del sistema por errores no controlados, siempre es el mismo error pero no conseguimos dar con el origen ni resolverlo. En el visor de sucesos el error es:

    Nombre de registro:System
    Origen:        Microsoft-Windows-Kernel-Power
    Fecha:         23/01/2018 12:41:38
    Id. del evento:41
    Categoría de la tarea:(63)
    Nivel:         Crítico
    Palabras clave:(2)
    Usuario:       SYSTEM
    Equipo:        
    Descripción:
    Se reinició el sistema sin apagarlo limpiamente primero. Este error puede producirse si el sistema dejó de responder, se bloqueó o se interrumpió el suministro eléctrico de forma inesperada.
    XML de evento:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>2</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000002</Keywords>
        <TimeCreated SystemTime="2018-01-23T11:41:38.308004900Z" />
        <EventRecordID>134125</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer></Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">59</Data>
        <Data Name="BugcheckParameter1">0xc0000005</Data>
        <Data Name="BugcheckParameter2">0xfffff96000213b86</Data>
        <Data Name="BugcheckParameter3">0xfffff880048ffb70</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>

    Depurando el archivo memory.dmp observamos la siguiente traza:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff96000263c12, fffff88005a15b70, 0}
    
    Probably caused by : win32k.sys ( win32k!bGlyphOutOfBounds+56 )
    
    Followup:     MachineOwner
    ---------
    
    nt!KeBugCheckEx:
    fffff800`016c0e00 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff880`05a152b0=000000000000003b
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*
    0: 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: fffff96000263c12, Address of the instruction which caused the bugcheck
    Arg3: fffff88005a15b70, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 401
    
    BUILD_VERSION_STRING:  7601.23915.amd64fre.win7sp1_ldr.170913-0600
    
    SYSTEM_MANUFACTURER:  Supermicro
    
    SYSTEM_PRODUCT_NAME:  X9SCL/X9SCM
    
    SYSTEM_SKU:  To be filled by O.E.M.
    
    SYSTEM_VERSION:  0123456789
    
    BIOS_VENDOR:  American Megatrends Inc.
    
    BIOS_VERSION:  2.0b
    
    BIOS_DATE:  09/17/2012
    
    BASEBOARD_MANUFACTURER:  Supermicro
    
    BASEBOARD_PRODUCT:  X9SCL/X9SCM
    
    BASEBOARD_VERSION:  1.11A
    
    DUMP_TYPE:  1
    
    BUGCHECK_P1: c0000005
    
    BUGCHECK_P2: fffff96000263c12
    
    BUGCHECK_P3: fffff88005a15b70
    
    BUGCHECK_P4: 0
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%p hace referencia a la memoria en 0x%p. La memoria no se pudo %s.
    
    FAULTING_IP: 
    win32k!bGlyphOutOfBounds+56
    fffff960`00263c12 8b01            mov     eax,dword ptr [rcx]
    
    CONTEXT:  fffff88005a15b70 -- (.cxr 0xfffff88005a15b70)
    rax=fffff900c2869cc8 rbx=fffff88005a16690 rcx=0000000000000000
    rdx=fffff900c1d38280 rsi=fffff88004cbc640 rdi=fffff900c1d38280
    rip=fffff96000263c12 rsp=fffff88005a16540 rbp=fffff88005a16690
     r8=0000000000000694  r9=0000000000000000 r10=00000000000005b3
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000001 r15=fffff900c1d38280
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    win32k!bGlyphOutOfBounds+0x56:
    fffff960`00263c12 8b01            mov     eax,dword ptr [rcx] ds:002b:00000000`00000000=????????
    Resetting default scope
    
    CPU_COUNT: 4
    
    CPU_MHZ: c1c
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 2a
    
    CPU_STEPPING: 7
    
    CPU_MICROCODE: 6,2a,7,0 (F,M,S,R)  SIG: 28'00000000 (cache) 28'00000000 (init)
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  splwow64.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  
    
    ANALYSIS_SESSION_TIME:  01-25-2018 11:09:24.0886
    
    ANALYSIS_VERSION: 10.0.17061.1000 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff96000263cc9 to fffff96000263c12
    
    STACK_TEXT:  
    fffff880`05a16540 fffff960`00263cc9 : 000005b3`00000694 00000000`00000000 fffff880`04cbc640 fffff880`05a16960 : win32k!bGlyphOutOfBounds+0x56
    fffff880`05a16570 fffff960`0009308f : 00000000`00000000 fffff900`c1d38280 fffff880`05a166e8 fffff880`05a16690 : win32k!STROBJ_bEnumCheckBounds+0x6d
    fffff880`05a165e0 fffff960`00284cc9 : fffff900`00000001 00000000`00000000 fffff900`c2824010 fffff880`04cbc580 : win32k!EngTextOut+0xc1f
    fffff880`05a16960 fffff800`016c0093 : fffff880`05a16b60 fffff880`04cbc640 fffff900`c2824010 00000000`032700c8 : win32k!NtGdiEngTextOut+0x365
    fffff880`05a16a70 000007fe`fe086e0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`022ff618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fe086e0a
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  cb41e56ece8886c90aedc28993d030a8176d1434
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e88eadd749153d14cd6496c2c720b004f29800e4
    
    THREAD_SHA1_HASH_MOD:  2b93e0e28d307f72aaedad827627033d831ae4f8
    
    FOLLOWUP_IP: 
    win32k!bGlyphOutOfBounds+56
    fffff960`00263c12 8b01            mov     eax,dword ptr [rcx]
    
    FAULT_INSTR_CODE:  8d41018b
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  win32k!bGlyphOutOfBounds+56
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5a0e642f
    
    IMAGE_VERSION:  6.1.7601.23963
    
    STACK_COMMAND:  .cxr 0xfffff88005a15b70 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!bGlyphOutOfBounds+56
    
    BUCKET_ID:  X64_0x3B_win32k!bGlyphOutOfBounds+56
    
    PRIMARY_PROBLEM_CLASS:  X64_0x3B_win32k!bGlyphOutOfBounds+56
    
    TARGET_TIME:  2018-01-25T08:43:35.000Z
    
    OSBUILD:  7601
    
    OSSERVICEPACK:  1000
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  1296
    
    PRODUCT_TYPE:  3
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 7
    
    OSEDITION:  Windows 7 Server (Service Pack 1) TerminalServer SingleUserTS Blade
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2017-09-13 16:55:13
    
    BUILDDATESTAMP_STR:  170913-0600
    
    BUILDLAB_STR:  win7sp1_ldr
    
    BUILDOSVER_STR:  6.1.7601.23915.amd64fre.win7sp1_ldr.170913-0600
    
    ANALYSIS_SESSION_ELAPSED_TIME:  905
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x3b_win32k!bglyphoutofbounds+56
    
    FAILURE_ID_HASH:  {3e3f265e-19b2-b018-fd57-a4ab79288e69}
    
    Followup:     MachineOwner
    ---------
    
    

    ¿Alguien puede ayudarnos para identificar el problema y solucionarlo?

    Muchísimas gracias y un saludo.

    jueves, 25 de enero de 2018 10:20