Stop Error 0x0000008E- Need Help

By sikora4480
Dec 12, 2006
Topic Status:
Not open for further replies.
  1. Stop Error 0x0000008E- Could someone help me

    I have read the previous posts and sticky's about the various stop errors and what to do and have yet to succeed in fixing my computer, I did the things it said to and I am pretty sure it is a driver issue but am unable to locate which one. I built the computer myself and know it's not a windows issue and was wondering if it could be caused by an older hard drive. I just bought used memory and a p4 motherboard as well as a brand new hard drive and they are all in good condition. I have an older hard drive as a slave hooked up and didn't know if that could be a problem, or older IDE cables, or a built in RAID card not setup. I have uploaded an everest report of my computer and my minidumps, and am hoping someone could help me.
    Here is what happens:
    I think it is a driver issue because I can boot up in safe mode in diagnostic mode in msconfig which usually works.
    -When I boot up it most often gives me the error
    0x0000008E and dumps the physical memory
    Sometimes it will say Win32k.sys error in it as well
    -Other times it will give me IRQL_NOT_LESS_OR_EQUAL (0x0000000A)
    with a dump of mem
    -It will also give PAGE_FAULT_IN_NONPAGED_AREA (0x00000050)
    -Address BF80E70B base at BF800000 Date Stamp: 41107F7A
    -When in safe-mode and used Everest I got a stop error
    PFN_LIST_CORRUPT 0x0000004E
    -Shutting down I sometimes got MEM_MANAGEMENT 0X0000001A with a
    Win32k.sys error
    -Booting up I also got an odd stop error C000021A 0XC0000005 with an NTFS.sys error
    -Another one was BAD_POOL_HEADER 0x00000019
    P.S. sorry about the long post :) and thanks a lot for whoever can help me
    if you have significant information for me my email is sikora4480@yahoo.com
    View attachment 11520

    View attachment 11521
  2. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

  3. sikora4480

    sikora4480 Newcomer, in training Topic Starter

    I wasn't using everest to determine what the problem was but to show whomever could help me what the specs of my computer are
  4. sikora4480

    sikora4480 Newcomer, in training Topic Starter

    can anyone help me?
  5. sikora4480

    sikora4480 Newcomer, in training Topic Starter

    Can anyone read my minidumps for me
  6. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    Hi,

    Your second post did not mention you re-attach the minidumps to the first post hence I miss it. Your windows are crashed without any pattern and no installed software at your windows has known software problem. All of the crashes are related to memory problem,. Probably the culprit is faulty ram.


    Mini120906-01.dmp BugCheck 10000050, {bbe21384, 0, bf80d2c5, 2}
    Probably caused by : win32k.sys ( win32k!_InnerGetClassPtr+18 )

    Mini120906-02.dmp BugCheck 1000008E, {c0000005, 80585490, b8d59bd0, 0}
    Probably caused by : ntoskrnl.exe ( nt!CmpDereferenceNameControlBlockWithLock+40 )

    Mini120906-03.dmp BugCheck 24, {1902fe, b81924ec, b81921e8, f8b7385c}
    Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+165 )

    Mini120906-04.dmp BugCheck A, {38003f, 2, 0, 804fb48a}
    Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+6b )

    Mini120906-05.dmp BugCheck 50, {c3c51980, 0, bf80e70b, 0}
    Probably caused by : win32k.sys ( win32k!HMAllocObject+14d )

    Mini121006-01.dmp BugCheck 4E, {99, 0, 0, 0}
    Probably caused by : memory_corruption ( nt!MiDeleteValidAddress+123 )

    Mini121006-02.dmp BugCheck 1000008E, {c0000005, 8054ba39, f7c1e110, 0}
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+fd )
  7. sikora4480

    sikora4480 Newcomer, in training Topic Starter

    what do you suggest i do, I had this problem before and I got new, but used, memory and didn't think that was the problem. When I boot up in diagnostic mode and disable all unecessary processes it works.
  8. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    According to finding, your problem is related to memory error (ie RAM, L2 cache memory of CPU or video memory). Since your windows work fine at safe mode, the culprit may be nVidia Display Card Driver as safe mode use standard Microsoft video driver. Your version of nVidia display card is very new and I have several cases still open and they are related to this version of nVidia Display card driver. Upgrade or downgrade nVidia Display Card driver.

    If you think it is not related to nVidia graphical driver, report the problem to MicroSoft.
  9. sikora4480

    sikora4480 Newcomer, in training Topic Starter

    thanks, ill try getting a new driver and see if that works, if not ill let you know.
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.