Stop:: 0x0000008e

Solutions to Stop: 0x0000008E Error (Blue Screen Of Death, BSOD)

When Stop: 0x0000008E Occurs

The Stop: 0x0000008E error message with BSOD (Blue Screen Of Death) appears when Windows encounters such a serious error that it has to terminate.

• You can get “Stop: 0x0000008E” and the Blue Screen during shutdown or restart.
• Stop: 0x0000008E and BSOD may appear randomly: you get the blue screen from time to time without an apparent reason. Eventually the 0x0000008E code appears more and more often until Windows won’t start at all.
• The Stop: 0x0000008E and BSOD may respond to certain actions performed on your computer: viewing contents of a CD/DVD, starting a game or gaming.
• Sometimes 0x0000008E starts nagging you after RAM of graphic card upgrade, of updating driver for your devices.
• There are cases of Stop: 0x0000008E and BSOD appearance after installation of Windows service packs.

Most Typical Causes of Stop: 0x0000008E

Registry problems, faulty RAM, hardware failure, driver incompatibility, viruses.

Below we review some cases of Stop: 0x0000008E error, BSOD and possible fixes.

However, if you are not a computer expert we recommend to ask for professional help.

---

Rustock rootkit 

Another site was talking about posting minidumps for them to look at, so I looked into one of the minidumps and found:
Rustock rootkit v 1.2
Z:\NewProjects\spambot\new\driver\objfre\i386\driver.pdb
A little more Google revealed that this Rootkit, once installed is undetectable by anything, quite the amazing little piece of code...
Symantec's info on the Rustock Rootkit

This was it the B version... I followed the directions on Symantec's site to remove it by booting into recovery console from an XP CD. (You cannot detect it in Safe Mode)
Once there I used "Disable pe386" to shut off the rootkit... I looked while in safe mode for this service and it WAS NOT there... Since it loads with kernel / driver data, it hides everything about itself...
Symantec's Cleanup Instructions...
Rebooted in Normal mode and no more BSOD, reinstalled NAV and started it scanning when I left the shop... I will run ADSSpy again and see if it finds the alternate data stream now...
I realize that this is not the only cause of 0x8e errors but this was my problem, and since there were two machines in the shop with the same problem, I can see more of these coming in for repair...
Hope this helps those who have just recently developed STOP: 0x0000008E errors.
troll

Use of dump files

Source

To configure startup and recovery options to use the small memory dump file, follow these steps.
1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. In the Write debugging information list, click Small memory dump (64k).

The file created should appear in the root of the drive where Windows is installed. As for being "easy to read and understand", it may be, but it might just look like gibberish unless you know what you're looking for. You can attach a copy of the dump file here and we'll have a look.

You could also try right-clicking My Computer, then go to Properties>>Advanced>>Startup and Recovery Settings, then uncheck Automatically Restart.
It will produce a BSOD with an error code. Let us know what it is and we'll try and help.

Stop Errors

Windows XP Stop Errors

Stop errors can be caused by just about anything, including poor quality audio drivers, incompatible video drivers, bad or corrupt hard disks, and faulty hardware such as bad RAM, dying motherboards, failing power supplies, etc. Stop errors may be triggered by an event such as plugging in a USB device, or they may appear to occur at regular intervals, or in association with some other event. Sometimes a stop error might appear to be completely random. If a stop error identifies a driver, the fault may not lie with the driver that was reported. Worse still, some errors can mask other critical errors, which means you fix one stop error and get another in return. In short, a stop error may be a symptom of some other problem. The real problem is to find the root cause.

http://www.aumha.org/win5/kbestop.htm
http://www.mvps.org/msauer/

Special freeware

• My Favorite Freeware
• Other Freeware Recommendations