none
Систематические BSODы. Не понятно в чем причина RRS feed

Все ответы

  • Здравствуйте,

    Согласно последнему дампу, Вам нужно смотреть в сторону проверки оперативной памяти RAM и винчестеров HDD, однозначно не ясно. Также уточните что у Вас фиксируется в системных событиях (Eventlogs -System)

    Анализ последнего дампа:

    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffa801b9aa010, 2, 1, fffff80001d850b6}
    
    Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )
    
    Followup: MachineOwner
    ---------
    
    8: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffa801b9aa010, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80001d850b6, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001f02100
     fffffa801b9aa010 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`01d850b6 480fb328        btr     qword ptr [rax],rbp
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  dfsrs.exe
    
    TRAP_FRAME:  fffff8800c93ff40 -- (.trap 0xfffff8800c93ff40)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa800b9aa010 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80001d850b6 rsp=fffff8800c9400d0 rbp=0000000080000000
     r8=fffff8800c940100  r9=00000000ffffffff r10=ffffffffffffffff
    r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiReleaseConfirmedPageFileSpace+0x86:
    fffff800`01d850b6 480fb328        btr     qword ptr [rax],rbp ds:0570:fffffa80`0b9aa010=00ee00000000354f
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80001cc4e69 to fffff80001cc58c0
    
    STACK_TEXT:  
    fffff880`0c93fdf8 fffff800`01cc4e69 : 00000000`0000000a fffffa80`1b9aa010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0c93fe00 fffff800`01cc3ae0 : 00000000`00000008 fffff880`0c93ffc0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`0c93ff40 fffff800`01d850b6 : 00000000`00000000 00000000`00000000 fffffa80`0b869520 fffffa80`0c87c010 : nt!KiPageFault+0x260
    fffff880`0c9400d0 fffff800`01d4349d : 80000000`00000000 fffff680`0008f000 fffff680`0008f0d0 000fffff`00000005 : nt!MiReleaseConfirmedPageFileSpace+0x86
    fffff880`0c940150 fffff800`01cb2b12 : fffffa80`00000001 00000000`00005dd2 fffffa80`0c1af6c0 fffffa80`0c1afa58 : nt! ?? ::FNODOBFM::`string'+0x45c56
    fffff880`0c9409e0 fffff800`01cc4b53 : ffffffff`ffffffff 00000000`0301f688 00000000`0301f680 00000000`00004000 : nt!NtFreeVirtualMemory+0x382
    fffff880`0c940ae0 00000000`7735dd9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0301f648 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7735dd9a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReleaseConfirmedPageFileSpace+86
    fffff800`01d850b6 480fb328        btr     qword ptr [rax],rbp
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+86
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  553e7b7b
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
    
    BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+86
    
    Followup: MachineOwner
    ---------
    
    Уточните если на сервер используется контроллер raid, фиксируются какие-то ошибки?


    Best Regards, Andrei ...
    Microsoft Certified Professional

    • Изменено SQxModerator 7 июня 2015 г. 22:32 исправлено
    7 июня 2015 г. 22:26
    Модератор
  • Вот анализ предпоследнего дампа, различен от последнего:

    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 0000000000000020, a pool block header size is corrupt.
    Arg2: fffffa800b111000, The pool entry we were looking for within the page.
    Arg3: fffffa800b111090, The next pool entry.
    Arg4: 0000000004090000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x19_20
    
    POOL_ADDRESS:  fffffa800b111000 
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80001df7cbe to fffff80001cc18c0
    
    STACK_TEXT:  
    fffff880`0213f788 fffff800`01df7cbe : 00000000`00000019 00000000`00000020 fffffa80`0b111000 fffffa80`0b111090 : nt!KeBugCheckEx
    fffff880`0213f790 fffff800`01cd5e24 : 00000000`00000000 fffff880`0213f968 00000000`63426343 fffff8a0`1093af08 : nt!ExAllocatePoolWithTag+0x1a2a
    fffff880`0213f840 fffff800`01ca759b : fffffa80`07573430 fffff880`0213f968 00000000`00000001 fffffa80`07573430 : nt!CcUnpinFileDataEx+0x404
    fffff880`0213f8c0 fffff800`01d031eb : 00000000`005277eb fffff880`0213fb18 00000000`000df000 00000000`00000000 : nt!CcReleaseByteRangeFromWrite+0xa7
    fffff880`0213f910 fffff800`01d06ac6 : fffffa80`06953448 fffffa80`00000001 fffff880`00000001 00000000`000df000 : nt!CcFlushCache+0x64b
    fffff880`0213fa10 fffff800`01d07488 : fffff880`00000000 fffff880`0213fb18 fffffa80`085f10a0 fffff800`01ecd978 : nt!CcWriteBehind+0x1c6
    fffff880`0213fac0 fffff800`01ccb4b5 : fffffa80`05218530 fffff800`01fb6c00 fffff800`01ecd980 fffffa80`00000002 : nt!CcWorkerThread+0x1c8
    fffff880`0213fb70 fffff800`01f5b456 : 0073da65`0073da65 fffffa80`051fcb50 00000000`00000080 fffffa80`051ea040 : nt!ExpWorkerThread+0x111
    fffff880`0213fc00 fffff800`01cb32c6 : fffff880`02065180 fffffa80`051fcb50 fffff880`020701c0 0073da65`0073da65 : nt!PspSystemThreadStartup+0x5a
    fffff880`0213fc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ExAllocatePoolWithTag+1a2a
    fffff800`01df7cbe cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!ExAllocatePoolWithTag+1a2a
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  553e7b7b
    
    FAILURE_BUCKET_ID:  X64_0x19_20_nt!ExAllocatePoolWithTag+1a2a
    
    BUCKET_ID:  X64_0x19_20_nt!ExAllocatePoolWithTag+1a2a
    
    Followup: MachineOwner
    ---------
    



    Best Regards, Andrei ...
    Microsoft Certified Professional

    7 июня 2015 г. 22:33
    Модератор
  • Raid'ов никаких нет. хорошо.поменяю память.проверю..расскажу