Fix the 0×0000008E BSOD once and for all

Robert Hallock (Thrax)

February 18, 2009 3:46 PM ET in Articles, Column,

Windows does not boot to safe mode with networking

You will need working installation media for Windows XP — a recovery CD will not do — and three CDs prepared with the following utilities:

HitachGST’s Drive Fitness Test (DFT) CD image
Seagate’s SeaTools for DOS CD image
Memtest86 CD image

To freely burn these utilities to CD, Icrontic has prepared a guide to accomplish the task. Once all three CDs are ready, proceed with each of the following steps in sequence. If you uncover a problem at any step, it is imperative that you remedy the issue before moving on. You may also find that resolving an intermediary issue eliminates the 0×0000008E stop error, so be sure to test Windows before continuing with additional steps.

  1. Evaluate the condition of your PC’s memory by testing it with Memtest86. If this fails, you need to replace your system memory and continue.
  2. Evaluate the condition of your hard drive by testing it with Drive Fitness Test. Should DFT fail to correctly function on your system, perform a long scan with SeaTools. If this fails, you need to replace your hard drive after archiving your information. If simple archival fails, Icrontic has prepared an emergency data recovery guide to account for this issue. Replacing your hard drive will require that you reinstall Windows.
  3. Evaluate the output of your power supply by testing it with a digital multimeter (DMM). If the power supply is producing insufficient voltages, it must be replaced.
  4. If all prior components have been replaced or given a clean bill of health, we have narrowed down the roster of possible culprits to three: A bunged up operating system, a faulty motherboard, or a faulty processor. It is rather unlikely that the processor or motherboard are to blame, so we must turn to the operating system.
  5. If you’re at this point, it is a safe assumption that an inaccessible installation of Windows is the source of your troubles. If you are stuck in such a situation, your only choice is to reload Windows from scratch and reconfigure it. Please follow the “Windows does not load and/or does not appear to be installed” section of Icrontic’s reformatting guide. This guide will walk you through the process of backing up your data and reloading Windows XP.
  6. If you are still confronted with the 0×0000008E error after a reformat, you must now suspect your motherboard and processor. Each component must be replaced with an identical part to eliminate the possibility of fault without introducing new instability through introducing differing hardware.

« PreviousNext page »

Share |

18 Comments:

  1. Excellent. Thanks, Thrax.

  2. Wonderfully thorough post. I've never seen anybody try to tackle the 0x8E blue screen with such in depth troubleshooting. Looks like you covered all the bases, bravo!

  3. Excellent Thrax!

    Great Guide!

  4. Very nice, and an EXCELLENT use of many of the other guides!! Go Icrontic!!1

  5. Well done, well done.

  6. Asif

    I actually went and bought all new PC parts thinking it was my PC or my raptor hard drives. Got whole new spec parts AM2 CPU, DDR ram etc and the other day boom! blue screen again! So I took out the ram replaced it one by one and its all good because my pc would not even go into windows let alone show the bios!
    So now thinking its the powersupply I went and got a new PSU, from a Hiper 500w to a Hiper 630w. Hope that does something good!

  7. Broozm

    Hmm... Nowhere in the [excellent] long threads I have read has this step been suggested..If you can boot linux CD and access the info on the harddrive, then it has to be the operating system on the hard drive and possibly the drivers that load when the OS loads...? Correct?

  8. KC

    I can't believe you advised to check EVERY box in HiJackThis.
    That is NOT what that program is for.
    MOST of the entries are valid, you must know which ones are invalid.

    DO NOT TAKE THIS PARTICULAR ADVICE

  9. In this case, that is what the program is for, and there's nothing that can be deleted with HJT that cannot be run from the start menu. The 0x0000008E issue can arise as a result of executables that aren't playing nicely with the system. It happens all the time.

    Thank you for your comment, but you are unfortunately incorrect.

  10. Many thanks to Rob Hallock whose article helped me into fixing a recurrent BSOD issue on a newly assembled PC.
    I ran Memtest86 : OK,
    I ran HighjackThis : 8 suspect register entries and 2 suspect extras, which were fixed.

    The 2 following sites helped in indetifying those entries:
    http://www.merijn.nu/htlogtutorial.php
    http://www.sysinfo.org/bholist.php

    I stopped at that step of the curing process, as the issue proved to be solved.
    The problem encountered was a reboot when attempting to login as admin or regular user on an AMD PC running XP Pro SP3.

    Great article.

  11. Add to my previous post
    Unfortunately, BSOD occurred again after 5 days of normal run.
    So:
    I ran HighjackThis again : OK
    I ran SmitfraudFix : some suspect entries that were fixed (after Register backup)
    I ran CCleaner and fixed incorrect entries
    Still erratic BSOD.
    BSOD indicated faulty portcls.sys : even if this is not the only possible cause, I disabled Onboard Sound in BIOS yesterday.
    So far, the PC run OK.

    PC configuration is:
    GA-MA790FXT UD5P mb
    Phenom II x4 955, no oc
    2x1Gb DDR3 12800 OCZ Platinum
    HDD WD RE3 250Gb

    Next step: I'll update Sound drivers (new version 2009/07/09)
    Some useful stuff there:
    http://www.maximumpc.com/article/features/blue_screen_survival_guide?page=0%2C0

  12. As a conclusion:
    I upgraded Realtek driver for onboard audio from Gigabyte support page (http://www.gigabyte.com.tw/Support/Motherboard/Driver_Model.aspx?ProductID=3005&ost=xp#anchor_os) and then re-enabled onboard audio.
    The PC runs OK and sound is OK too.
    So, for GA-MA790FXT UD5P owners encountering BSOD at login (XP SP3), I recommend the upgrade of Realtek driver, in the case onboard sound is enabled.
    Thanks for the valuable information I found here.

  13. I'm glad you ofund a solution Herrmann! I'm glad -- even if it was a pain for you -- that you also helped prove that this BSOD can be a result of anything.

  14. Imants

    These all steps we can make after system restore in safe mode! But thanks anyway...

  15. I noticed pages 2 and 3 are strangely similar

  16. That's because the processes are similar for the scenarios outlined at the beginning of each page.

Troll-free since 2003 ®