Announcement

Collapse
No announcement yet.

BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

    Hi all,

    I have a problem with a windows XP computer.
    I got several BSOD.

    I ran the windows debugging tools, all contains exacly the same message.


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Documents and Settings\dvoijen.SYSTEMEC\Bureaublad\Minidump\Mini052209-03.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: C:\symbols
    Executable search path is: 
    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_gdr.090206-1234
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
    Debug session time: Fri May 22 09:01:07.671 2009 (GMT+2)
    System Uptime: 0 days 0:00:52.234
    Loading Kernel Symbols
    ...............................................................
    .....................................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!ObInsertObject+1ad )
    
    Followup: MachineOwner
    ---------
    
    kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 8056db30, The address that the exception occurred at
    Arg3: aec83a48, Trap Frame
    Arg4: 00000000
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ("%s") op het geheugen is mislukt.
    
    FAULTING_IP: 
    nt!ObInsertObject+1ad
    8056db30 8b4e1c          mov     ecx,dword ptr [esi+1Ch]
    
    TRAP_FRAME:  aec83a48 -- (.trap 0xffffffffaec83a48)
    ErrCode = 00000000
    eax=aec83bb8 ebx=00000000 ecx=89b3d000 edx=00000000 esi=00000001 edi=00000000
    eip=8056db30 esp=aec83abc ebp=aec83b8c iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    nt!ObInsertObject+0x1ad:
    8056db30 8b4e1c          mov     ecx,dword ptr [esi+1Ch] ds:0023:0000001d=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  3
    
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  cmd.exe
    
    LAST_CONTROL_TRANSFER:  from 8058b685 to 8056db30
    
    STACK_TEXT:  
    aec83b8c 8058b685 8987db28 aec83bb8 001f0fff nt!ObInsertObject+0x1ad
    aec83ce4 8058b82f 0012f114 001f0fff 00000000 nt!PspCreateProcess+0x635
    aec83d38 804dd99f 0012f114 001f0fff 00000000 nt!NtCreateProcessEx+0x7e
    aec83d38 7c90e514 0012f114 001f0fff 00000000 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f780 00000000 00000000 00000000 00000000 0x7c90e514
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ObInsertObject+1ad
    8056db30 8b4e1c          mov     ecx,dword ptr [esi+1Ch]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!ObInsertObject+1ad
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  498c19b5
    
    FAILURE_BUCKET_ID:  0x8E_nt!ObInsertObject+1ad
    
    BUCKET_ID:  0x8E_nt!ObInsertObject+1ad
    
    Followup: MachineOwner
    ---------
    Does anyone know what to do?
    Could it be a memory dimm problem?

  • #2
    Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

    Those type of errors are normally related to failing RAM. If windows tries to write to a portion of memory that isnt available the result is the BSOD. Try this tool from MS:

    http://oca.microsoft.com/en/windiag.asp

    It creates a bootable .iso and runs on startup. It does an exhaustive check for memory errors. Saying that RAM is cheap these days. Whack in a new stick and see how the machine responds.

    Comment


    • #3
      Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

      I prefer memtest for memory checking but thats just me i need to be different

      I would update all your drivers as well.

      Comment


      • #4
        Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

        The problem is 0x8e errors are quite broad. 9 times out of 10 there always memory related as there memory violation errors. But thats probably not a bad idea updating the drivers althought the faulting module is listed as cmd.exe.. Id start by updating the BIOS and swapping out those sticks.
        Last edited by scurlaruntings; 3rd June 2009, 22:53.

        Comment


        • #5
          Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

          Ok, i will swap the memory sticks and keep posted here....

          Thanks so far....

          Comment


          • #6
            Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

            No luck, there were 2 DIMMS.

            I removed one, problem still there.
            Put it back and removed the other, still problem.

            Swaped them, pulled one out again, other way.
            No luck, still have BSOD

            I have attached several dump files, maybe someone can help with this...
            Attached Files

            Comment


            • #7
              Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

              Were there any hardware, software, driver, or update changes right before the problem started?

              Comment


              • #8
                Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

                Nope, no changes at all...

                That's also why i thougth of a harware issue.

                Comment


                • #9
                  Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

                  Originally posted by danny230681 View Post
                  Nope, no changes at all...

                  That's also why i thougth of a harware issue.
                  You might want to check for rootkits. I seem to remember that one of them would throw that error code.

                  Here is a link to guide to check over. http://icrontic.com/forum/showthread.php?t=50966

                  Comment


                  • #10
                    Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

                    Have you updated your drivers yet???

                    Comment


                    • #11
                      Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

                      Ok, the memory dimms are ok, i wil lcheck drivers and the rootkit..

                      Comment


                      • #12
                        Re: BSOD BugCheck 1000008E, {c0000005, 8056db30, aec83a48, 0}

                        Hi all,

                        Problem is solved.

                        It was strangely enough problem with rights.

                        The user had user rights, after an upgrade of user rights to main user rigths the problem was solved.

                        Comment

                        Working...
                        X