[2003SP1] Regular bluescreens on domaincontroller.

Discussion in 'Windows Server' started by Reinder Gerritsen, Jan 18, 2007.

  1. For some time now I get bluescreens and reboot on one of our domain
    controllers.
    The server crashes and reboots. During login an unexpected shutdown is
    displayed, but no crashdata is entered. Also nothing is shown in the
    Eventlog regarding this crash.

    I've set the recovery options to write a Kernel Memorydump, but every time
    the server goes down there is no dump written, just as if someone pulled the
    powerplug.

    HP iLO registers the crash though, which were:

    Blue Screen Trap (BugCheck, STOP: 0x0000007E (0xC0000047, 0x8085B006,
    0xB7BE76D4, 0xB7BE7404)) 1/18/2007 0:19AM
    Blue Screen Trap (BugCheck, STOP: 0x0000008E (0xC0000047, 0x8085B006,
    0xB77EE6D0, 0x00000000)) 1/4/2007 4:45AM
    Blue Screen Trap (BugCheck, STOP: 0x0000007E (0xC0000047, 0x8085B006,
    0xB75356CC, 0xB75353FC)) 12/21/2006 4:33PM
    Blue Screen Trap (BugCheck, STOP: 0x0000007E (0xC0000047, 0x8085B006,
    0xB81026CC, 0xB81023FC)) 11/20/2006 11:28PM
    Blue Screen Trap (BugCheck, STOP: 0x0000007E (0xC0000047, 0x8085B006,
    0xB980B6CC, 0xB980B3FC)) 10/13/2006 8:22AM
    Blue Screen Trap (BugCheck, STOP: 0x0000008E (0xC0000047, 0x8085B006,
    0xB8A52540, 0x00000000)) 9/12/2006 6:44AM

    Unfortunately the iLO does not list what module or driver this happened in,
    and without memory dump it's getting realy hard to find the cause. The only
    regularity I find is that it alway's seems to happen during the backup.

    The server in question is a
    HP DL380 G4
    Windows 2003 Standard edition with SP1 installed
    - Active Directory installed
    - IIS installed (FTP Services only)
    - acts as file and printserver
    - has Veritas Backup Exec 9.1 installed

    Anyone a suggestion how I might be able to find the root cause to this (or
    at least help me getting proper memory dumps?)
     
    Reinder Gerritsen, Jan 18, 2007
    #1
    1. Advertisements

  2. It coud be some of that :

    • Incompatible video adapter drivers.
    • Damaged RAM.
    • A damaged device driver or system service.

    try to update all device drivers and replace ram.
     
    Dragos CAMARA, Jan 18, 2007
    #2
    1. Advertisements

  3. Hi,

    To locate the exact problem of the stop error, we need to analyze the crash
    dump file. Unfortunately, we cannot help you analyze the dump file in
    newsgroup. To trouble shoot this problem efficiently, I suggest that you
    speak directly with a Microsoft Support Professional so that the crash dump
    can be analyzed. Here are some articles that will help prepare you for this
    call:

    Blue Screen Preparation Before Contacting Microsoft
    ID: 129845.KB.EN-US
    http://support.microsoft.com/?id=129845

    Gathering Blue Screen Information After Memory Dump in Windows 2000 or
    Windows NT
    ID: 192463.KB.EN-US
    http://support.microsoft.com/?id=192463

    For a complete list of Microsoft Customer Service and Support (CSS) phone
    numbers and information about support costs, please go to the following
    address on the World Wide Web:
    <http://support.microsoft.com/directory/overview.asp>

    I hope that the above information can be of assistance.

    Best regards,

    Vincent Xu
    Microsoft Online Partner Support

    ======================================================
    Get Secure! - www.microsoft.com/security
    ======================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others
    may learn and benefit from this issue.
    ======================================================
    This posting is provided "AS IS" with no warranties,and confers no rights.
    ======================================================



    --------------------
     
    Vincent Xu [MSFT], Jan 19, 2007
    #3
  4. I'd love to contact MS, but unfortunately the biggest issue is that there
    isn't any memory.dmp after the crash. When it crashes it almost looks as if
    someone pulled the powerplug. The only proof that it actually was a BSOD is
    because HP iLO catches the crash string.


     
    Reinder Gerritsen, Jan 19, 2007
    #4
  5. Reinder Gerritsen

    NeilH Guest

    Could you have a PSU problem?

     
    NeilH, Jan 19, 2007
    #5
  6. I fint that rather hard to believe, given the fact that the iLO board
    captures a bluescreen trap error, as posted in the original list: BugCheck,
    STOP: 0x8E (0xC0000047, 0x8085B006, 0xB77EE6D0, 0x0). If the PSU would fail,
    it's 'just another' power failure...

    Anyway, I've now moved the paging file back to the system drive hoping this
    will aleviate the issue of not writing a crashdump. For now no crashes, so
    it's waiting to see if it worked.

    Thanks for thinking with me though.

     
    Reinder Gerritsen, Jan 22, 2007
    #6
  7. Reinder Gerritsen

    Terry Hines Guest

    Having a simular problem will meoving the page file back to c allow a crash dump?
    What network adapter are you running?

    EggHeadCafe.com - .NET Developer Portal of Choice
    http://www.eggheadcafe.com
     
    Terry Hines, Jan 28, 2007
    #7
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.