none
BSOD Windows Server 2008 caused by driver ntoskrnl.exe

    Question

  • Hi guys please you can help me with this BSOD.


    ADDITIONAL_DEBUG_TEXT:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
    
    MODULE_NAME: nt
    
    FAULTING_MODULE: fffff80001a0f000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.
    
    FAULTING_IP: 
    nt+b57cc
    fffff800`01ac47cc 8808            mov     byte ptr [rax],cl
    
    CONTEXT:  fffff88005292be0 -- (.cxr 0xfffff88005292be0)
    rax=0000000001efb000 rbx=fffff88005293658 rcx=fffff880058f6a74
    rdx=fffff88005293910 rsi=fffff88005293910 rdi=fffff88005293658
    rip=fffff80001ac47cc rsp=fffff880052935c0 rbp=fffff880058f6a07
     r8=fffff88005293658  r9=fffff88005293658 r10=0000000000000000
    r11=fffff88005293910 r12=00000000ffffff9a r13=fffff880052939e0
    r14=0000000000000c80 r15=fffff880058f4877
    iopl=0         nv up ei pl nz ac pe cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010213
    nt+0xb57cc:
    fffff800`01ac47cc 8808            mov     byte ptr [rax],cl ds:002b:00000000`01efb000=??
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
    
    BUGCHECK_STR:  0x3B
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80001ac47cc
    
    STACK_TEXT:  
    fffff880`052935c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0xb57cc
    
    
    FOLLOWUP_IP: 
    nt+b57cc
    fffff800`01ac47cc 8808            mov     byte ptr [rax],cl
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt+b57cc
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  ntoskrnl.exe
    
    STACK_COMMAND:  .cxr 0xfffff88005292be0 ; kb
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner



    Monday, September 30, 2013 3:36 PM

Answers

  • Hi

    Start by a memory scan ot be sure the memory is ok, after please update all firmware & drivers.

    Regards


    MCP | MCTS - Exchange 2007, Configuring | Member of TechNet Wiki Community Council | French Moderator on TechNet Wiki (Translation Widget)

    Wednesday, October 02, 2013 2:57 AM
  • Hi,

    According to the description, the operation system is Windows Server 2008. Would you please let me know you have updated the sever 2008 Service Pack 2? If not, please try to install it as Service Pack will help upgrade system files which may help fixing the issue.

    Would you please let me know the recent change performed on this server before first BSOD occurs? Is there any software and or driver installed? As Yagmoth555 says, please check whether there is any update available.

    Based on the Bug Check 0x3B, this error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code. Please check whether there are some errors in application/system event logs before server crashing, see if the server has excessive paging.

    For more details, please refer to the following article.

    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

    http://msdn.microsoft.com/en-us/library/ff558949(v=vs.85).aspx

    By the way, troubleshoot this kind of kernel crash issue, we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.

    To obtain the phone numbers for specific technology request, please refer to the web site listed below:

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

    Hope this helps.

    Best regards,

    Justin Gu

    Wednesday, October 02, 2013 11:46 AM

All replies

  • Hi

    Start by a memory scan ot be sure the memory is ok, after please update all firmware & drivers.

    Regards


    MCP | MCTS - Exchange 2007, Configuring | Member of TechNet Wiki Community Council | French Moderator on TechNet Wiki (Translation Widget)

    Wednesday, October 02, 2013 2:57 AM
  • Hi,

    According to the description, the operation system is Windows Server 2008. Would you please let me know you have updated the sever 2008 Service Pack 2? If not, please try to install it as Service Pack will help upgrade system files which may help fixing the issue.

    Would you please let me know the recent change performed on this server before first BSOD occurs? Is there any software and or driver installed? As Yagmoth555 says, please check whether there is any update available.

    Based on the Bug Check 0x3B, this error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code. Please check whether there are some errors in application/system event logs before server crashing, see if the server has excessive paging.

    For more details, please refer to the following article.

    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

    http://msdn.microsoft.com/en-us/library/ff558949(v=vs.85).aspx

    By the way, troubleshoot this kind of kernel crash issue, we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.

    To obtain the phone numbers for specific technology request, please refer to the web site listed below:

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

    Hope this helps.

    Best regards,

    Justin Gu

    Wednesday, October 02, 2013 11:46 AM