TechSpot

Server BSOD

By allyrussell77
Jul 9, 2008
  1. Hi everyone,

    Having an issue with one of our clients 2003 servers where blue screens several times a month. I have downloaded the debug tools and relevant symbols but am not experienced in reading the dump file. I think it may be a meory fault but really not sure. If anyone can have a quick look at the attached dump file and advise, that would be much appreciated.


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    nt!NtRequestWaitReplyPort+688
    80939795 8931 mov dword ptr [ecx],esi

    TRAP_FRAME: b9863c3c -- (.trap 0xffffffffb9863c3c)
    ErrCode = 00000002
    eax=e1a22098 ebx=8929e6c0 ecx=00000000 edx=e1f882c8 esi=8929e880 edi=e171ace8
    eip=80939795 esp=b9863cb0 ebp=b9863d50 iopl=0 nv up ei ng nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
    nt!NtRequestWaitReplyPort+0x688:
    80939795 8931 mov dword ptr [ecx],esi ds:0023:00000000=00000000
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR: 0x8E

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 80834d3f to 80939795

    STACK_TEXT:
    b9863d50 80834d3f 00000104 00148150 00148150 nt!NtRequestWaitReplyPort+0x688
    b9863d50 7c82ed54 00000104 00148150 00148150 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f30c 00000000 00000000 00000000 00000000 0x7c82ed54


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!NtRequestWaitReplyPort+688
    80939795 8931 mov dword ptr [ecx],esi

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!NtRequestWaitReplyPort+688

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 45ebe552

    FAILURE_BUCKET_ID: 0x8E_nt!NtRequestWaitReplyPort+688

    BUCKET_ID: 0x8E_nt!NtRequestWaitReplyPort+688

    Followup: MachineOwner


    Thanks
    Alistair
     
  2. raybay

    raybay TS Evangelist Posts: 7,241   +9

    Looks like you have a memory error or a driver error, or both. Change out memory to test.
    Something is quitting or being stopped.
    Can you figger out what Port _688 is?
    Run MemTest86 on each module, for four hours or 7 passes, whichever is longer... to find or rule out memory issued.
    What do you see in Device Manager? Any red or yellow flags? That can be a clue to driver issues.
     
  3. woody1191

    woody1191 TS Rookie Posts: 572

    Bugcheck 0x8E errors are almost always Hardware errors. You are right in thinking its a Memory error if you haven't already download one of these and run a memory test on the computer.
    Memtest86 - http://www.memtest.org/
    Windows Memory Diagnostic Tool - http://oca.microsoft.com/en/windiag.asp
    Then if the RAM passes this test move onto testing the HDD with the Manufacturers Test and running Check Disk (ChkDsk) as well.

    Edit - Just seen post above now.
     
  4. allyrussell77

    allyrussell77 TS Rookie Topic Starter

    Thanks for the adivce, I will try this and post my findings :)
     
  5. usasma

    usasma TS Rookie

    Try using Driver Verifier ( http://support.microsoft.com/kb/244617 ) and enable it for unsigned drivers first (to prevent a drastic slowdown of the system). It should generate a BSOD with the driver identified - this can happen immediately after the reboot, or it may take some time for another BSOD to show up.

    If it's an immediate BSOD, the chances are good that it'll ID the faulty driver. If not, then the chances decrease - but at least it's a trail to follow. :)

    Good luck!
     
  6. raybay

    raybay TS Evangelist Posts: 7,241   +9

    Interesting if true. Interesting if not true.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...