Help me with this BSOD minidump

By coolink
Mar 25, 2008
  1. Hi, I´m having this intermittent 8E BSOD and I want a help to decifer this minidump.

    I´m running XP Pro SP2 with all the latest drivers. I´ve already ran Prime95 for 10 hours with 0 errors, Memtest86 for 10 hours (8passes) with errors.

    Attached Files:

  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Your minidump was unreadable -- it could not load the proper symbols which points to a hardware issue.

    Also, if you are getting 0x8E errors as you list they are nearly always caused by hardware (and sometimes by a device driver).

    The question is what hardware? We don't have enough info to determine at this time. So...

    1. Run MemTest of your RAM for a minimum of 7 passes.

    2. Run a full harddrive diagnostics.
  3. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    Probably caused by : pci.sys

    You must wait for WinDbg to finish
  4. coolink

    coolink TS Rookie Topic Starter Posts: 34

    As I said, I ran memtest for more than 8 passes and no errors, ran Prime95 for more than 8 hours with 0 errors. I don´t know what is happening. I´ve tried to open the minidump and appears that it pointed to pci.sys. I´m trying to roll back from AHCI to Normal ATA mode to test but I don´t know how to do it..
  5. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    NT Plug and Play PCI Enumerator

    Go to Device Manager and up date the driver
    First try Automatic (from MS)

    If it still fails
    Manually, "Don't search, I have the driver" and install that one (which hopefully should work)
  6. Rage_3K_Moiz

    Rage_3K_Moiz Sith Lord Posts: 5,431   +28

    Try updating your chipset drivers and your video card driver, especially if you have a PCI video card.
    Also, you might have an IRQ conflict somewhere, most likely with a PCI device such as a PCI video card or another add-on card. Try removing all your PCI devices and then running the PC. If there is an IRQ conflict somewhere, look here to see how to resolve it.
  7. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    This is hardware problem. The most useful diagnostic information of this dump is NT Status code (ie Bugcheck Parameter 1) 80000004. Usually it is related to faulty CPU or compatibility CPU with the Motherboard. I have resolved a similar problem at another forum.

    Mini031708-01.dmp BugCheck 1000008E, {80000004, 80728ac9, b6972330, 0}
    Probably caused by : pci.sys ( pci!PciReadWriteConfigSpace+38 )

    Attach more minidumps here if you have.
  8. coolink

    coolink TS Rookie Topic Starter Posts: 34

    It is a Dell Notebook. How can I diagnose exactly what is the problem. I´ve ran all kinds of diagnostic software with 0 errors.. Here is another minidump. the only BSOD is 8E but after I restart the computer, another minidump is generated. EA
  9. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    ok I didn't read that, just the end part !

    So now it's:

    Update NT Plug and Play PCI Enumerator (Automatic or Manual)
    Check the IRQ's
    CPU (possible hardware fault)

    There's all 3 (actually I've heard faulty ps2 keyboards can give cpu faults)

    Probably more MiniDumps required

    By the way, there's always system restore (to a date/time before it was recorded faulty) this may eliminate the software part.

    oh another MiniDump
  10. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    Probably caused by : igxpdv32.DLL


    Good call Rage_3K_Moiz
  11. coolink

    coolink TS Rookie Topic Starter Posts: 34

    All latest driver (Graphics, Chipset and Matrix Storage) from Intel website are installed... This BSOD is intermittent. It doesn´t happens everyday...
  12. Rage_3K_Moiz

    Rage_3K_Moiz Sith Lord Posts: 5,431   +28

    That's the Intel onboard video driver. Please provide the model number of your notebook so we can help you better. Also, try rolling back the drivers to the previous versions.
    Also kimsland, why don't you try editing your posts rather than having multiple ones in a row.
  13. coolink

    coolink TS Rookie Topic Starter Posts: 34

    It a Dell D630 965GM chipset with T7100 processor.
  14. Rage_3K_Moiz

    Rage_3K_Moiz Sith Lord Posts: 5,431   +28

    Have you updated the BIOS? Try that and see what happens.
  15. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Refer the following problem. The symptom is very similar to your problem. It problem owner does not confirm whether the problem is related to device driver or not.

    The crashing instructon of your problem is hal!WRITE_PORT_ULONG+0x9 and the instruction is related to CPU.

    Your 2nd minidump is crashed with bugcheck code EA. BC EA may be to related to faulty ram, faulty CPU, viedo card driver or video card. You can simuate the problem by running video burn-in test.

    The video card driver is very current (Feb 09 2008). If your problem occurs after you upgrade video card driver, fallback it to the original version.

    bf012000 bf024000 igxprd32 igxprd32.dll Sat Feb 09 01:50:39 2008 (47AC966F)
    bf024000 bf04f000 igxpgd32 igxpgd32.dll Sat Feb 09 01:50:39 2008 (47AC966F)
    bf04f000 bf269dc0 igxpdv32 igxpdv32.DLL Sat Feb 09 01:50:48 2008 (47AC9678)
    bf26a000 bf580000 igxpdx32 igxpdx32.DLL Sat Feb 09 01:50:43 2008 (47AC9673)
  16. coolink

    coolink TS Rookie Topic Starter Posts: 34

    Latest Bios version A08. All latest drivers.

    What test can I run to know if this is a defective CPU? I´ve ran all types of tests (prime95, Sandra, Everest) and no problems. This passmark link shows that possibly that the intel IGP is causing the problem. Does the IGP has anything related to pci.sys?
  17. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    The link does not confirm that it is graphical card device driver error. There have no reliable tools to test CPU and RAM.
  18. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    Sounds like the best advice
  19. coolink

    coolink TS Rookie Topic Starter Posts: 34

    Any ideas why this EA minidump is always generated after the 8E BSOD?
  20. jobeard

    jobeard TS Ambassador Posts: 9,343   +622


    PROCESS_NAME: taskmgr.exe

    LAST_CONTROL_TRANSFER: from bf06ecec to bf04faa0

    b6972840 bf03fd34 e5d7b6e0 00000000 00000000 igxpgd32+0x1167b
    b6972854 bf019c2e e5d7b6e0 00000000 00000000 igxpgd32+0x1bd34
    b6972870 bf8bd8db e5d7b6e0 00000000 00000000 igxprd32+0x7c2e
    b69728ac bf8056b7 e5d7b6e0 00000000 00000000 win32k!xxxPrintWindow+0x7b
    b69728c0 bf839c20 e5d7b6e0 00000000 00000000 win32k!HANDLELOCK::vLockHandle+0x4a
    b6972adc bf80a4ef e9a59018 e104a008 00000000 win32k!NtGdiAlphaBlend+0xbcc
    b6972b70 bf85d4fc e9a59008 bf9a55c0 e79d95b0 win32k!DC::bSetDefaultRegion+0x5e
    b6972bd4 bf82abf8 bbed5708 000001c5 03010036 win32k!NtGdiFrameRgn+0x16a
    b6972c3c bf829053 bbe606e8 bf9aaf60 bf9aaf60 win32k!GreSetDIBitsToDeviceInternal+0x7f1
    b6972c84 bf8276bf bf9aaf60 00000000 bbed5708 win32k!ESTROBJ::vCharPos_H1+0x183
    b6972cdc bf82a3da 00000001 00000000 00000000 win32k!vSolidFillRect1+0x132
    b6972cfc bf83910d bbed5708 00000000 00000000 win32k!NtGdiExtTextOutW+0x22c
    b6972d30 bf839486 00000000 00000057 b6972d64 win32k!xxxCalcMenuBar+0x51
    b6972d54 804dd99e 002b03a6 00000005 0007ff5c win32k!NtUserSetFocus+0x26
    b6972d5c 00000000 0007ff5c 7c90eb94 badb0d00 nt!ZwQueryEvent+0x13

    A system process (TaskMgr) ->Print request->graphic fill operation

    Also investigate your print driver -- was it / has it been updated recently?
  21. coolink

    coolink TS Rookie Topic Starter Posts: 34

    No, there is no printer or printer driver installed...
  22. coolink

    coolink TS Rookie Topic Starter Posts: 34

    Any idea why this EA minidump always appear after the 8E BSOD?
  23. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    The device driver is spinning in an infinite loop, most likely waiting for
    hardware to become idle. This usually indicates problem with the hardware
    itself or with the device driver programming the hardware incorrectly.
    If the kernel debugger is connected and running when watchdog detects a
    timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
    and detailed message including bugcheck arguments will be printed to the
    debugger. This way we can identify an offending thread, set breakpoints in it,
    and hit go to return to the spinning code to debug it further. Because
    KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
    information in this case. The arguments are already printed out to the kernel
    debugger. You can also retrieve them from a global variable via
    "dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
    On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
    interrupted by hardware interrupt and ISR or DPC routine is running at the time
    of the bugcheck (this is because the timeout's work item can be delivered and
    handled on the second CPU and the same time). If this is the case you will have
    to look deeper at the offending thread's stack (e.g. using dds) to determine
    spinning code which caused the timeout to occur.
    Bugcheck code is usually caused by graphical device driver, video card or ram problem.
  24. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    cpc2004 can you break that paragraph up a bit!

    I didn't read it
  25. coolink

    coolink TS Rookie Topic Starter Posts: 34

    Fresh minidumps to be analyzed.

    It is always like that in this order. First, the BSOD with 8E error, than restart and a minidump with the 8E error is generated, restart again and the minidump with EA error is generated.
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...