| 0x0000008e (0xc0000005, 0x00000000, 0xb3816850, 0x00000000) |
Problem Event Name: BlueScreen
BCCode: 8e
Cause of STOP 0x0000008E Errors
STOP 0x0000008E errors are usually caused by memory hardware failures and more rarely by device driver issues, viruses, or hardware failures other than your RAM.
If STOP 0x0000008E isn't the exact STOP code you're seeing or KERNEL_MODE_EXCEPTION_NOT_HANDLED isn't the exact message, please check my Complete List of STOP Error Codes and reference the troubleshooting information for the STOP message that you are seeing.
Resolution
Restart your computer if you haven't already done so. The STOP 0x0000008E blue screen error might be a fluke.
Did you just install new hardware or make a change to some hardware or a hardware driver? If so, there's a very good chance that the change you made caused the STOP 0x0000008E error.
Undo the change you made and test for the 0x8E blue screen error.
Depending on what change you made, some solutions might include:
Remove or reconfigure the newly installed hardware.
Startup with Last Known Good Configuration to undo related registry and driver changes.
Use System Restore to undo recent changes.
Roll back any device drivers you've installed to versions prior to your update.
Test your RAM. The most common cause of the STOP 0x0000008E error is memory that is damaged or has stopped working properly for some reason.
Replace any nonworking memory modules if your tests show a problem.
Verify that the system memory is properly installed. Memory that's installed in some way other than that suggested by your motherboard manufacturer could cause STOP 0x0000008E errors and other related problems.
Note: If you have any doubt about the proper memory configuration in your computer, please consult your computer or motherboard manual. All motherboards have fairly stringent requirements on the types and configurations of RAM modules.
Return BIOS settings to their default levels. Overclocked or misconfigured memory settings in BIOS have been known to cause STOP 0x0000008E errors.
Note: If you've made several customizations to your BIOS settings and don't want to load the default ones then at least try returning all BIOS memory timing, caching, and shadowing options to their default levels and see if that fixes the STOP 0x0000008E error.
Apply all available Windows updates. Several service packs and other patches have specifically addressed STOP 0x0000008E issues.
Note: This particular solution is likely to solve your problem if your STOP 0x0000008E error is accompanied by a mention of win32k.sys or wdmaud.sys, or if it occurred while making changes to the hardware acceleration on your graphics card.
If STOP error 0x0000008E is followed by 0xc0000005, as in STOP: 0x0000008E (0xc0000005, x, x, x), applying the latest Windows service pack will likely fix your issue.
Perform basic STOP error troubleshooting. If none of the specific steps above help fix the STOP 0x0000008E error you're seeing, take a look at this general STOP error troubleshooting guide. Since most STOP errors are similarly caused, some of the suggestions might help.
Please let me know if you've fixed a blue screen of death with the STOP 0x0000008E STOP code using a method that I don't have above. I'd like to keep this page updated with the most accurate STOP 0x0000008E error troubleshooting information as possible.
Applies To
Any of Microsoft's Windows NT based operating systems could experience the STOP 0x0000008E error. This includes Windows 7, Windows Vista, Windows XP, Windows 2000, and Windows NT.
Still Having STOP 0x0000008E Issues?
Let a community of computer support enthusiasts help out! Post the details of your STOP error in the PC Support Forums. Be sure to let us know the that you're seeing the 0x0000008E STOP code and also what steps, if any, you've already taken to resolve it.
Also, please make sure you've looked at my general STOP Error Troubleshooting Guide before posting.
If STOP error 0x0000008E is followed by 0xc0000005, as in STOP: 0x0000008E (0xc0000005, x, x, x), applying the latest Windows service pack will likely fix your issue.
Buried in there was one thing in it I didn't know. This note:
...-40hz (July 11, 2011, 03:56 PM)
STOP 0x0000008E errors are usually caused by memory hardware failures and more rarely by device driver issues, viruses, or hardware failures other than your RAM.
CPU: Intel core 2 duo e4400 tray 2048kb, lga775, 64bit
100,60 €
Mobo: Msi p35 neo-f, intel p35, atx
90,75 €
CPU fan: Arctic freezer 7 pro sockel 775
14,17 €
Memory: 2048Mb-kit ddr2 mdt , pc6400/800, cl5
70,91 €
Box: Coolermaster centurion5 schw. Cac-t05-uw no PSU
44,49 €
PSU: Atx-netzteil corsair vx450w 450 watt
65,00 €
Graphic card: ASUS GF-7100GS Silent, 128MB, Nvidia 7100GS, PCIe
36,50 €
Harddrives:
Samsung hd321kj 320gb serial ata-ii, 7200 upm, 16mb
60,40 €
Samsung hd321kj 320gb serial ata-ii, 7200 upm, 16mb
60,40 €
DVD burner: Samsung sh-s183l bare schwarz
35,38 €
Floppy Laufwerk 1.44 Mb,3.5" Schwarz
4,99 €
Sound: Terratec aureon 5.1 Pci
16,40 €
Modem: Devolo microl. 56K pci (bulk) pci
11,55 €-tomos (August 09, 2007, 08:08 AM)
What model/brand motherboard?-Cloq (July 11, 2011, 07:47 PM)
Do you know if you have sata set to ahci mode?-Cloq (July 11, 2011, 07:47 PM)
Do you know if you have sata set to ahci mode?-Cloq (July 11, 2011, 07:47 PM)
I have no idea (!) any tips how I might check?-tomos (July 12, 2011, 03:28 AM)
well, I bought a can of compressed air and just used up the most of it on the inside of the machine-tomos (July 12, 2011, 03:37 PM)
BE CAREFUL with that stuff! You can do a lot of damage inadvertently.
Don't let that 'freezing' propellant get near to anything.
Also, lock the blades of the fans somehow before blasting them, you don't want to rev them faster than they're designed to go.
If you don't already, turn off all power to the machine and let the entire thing stand for a while.-cranioscopical (July 12, 2011, 04:38 PM)
You'd be better off using straws and soft-bristle, artist-style paint brushes.do I have to suck up the dust through the straw :tellme:-cranioscopical (July 12, 2011, 04:38 PM)
Also, lock the blades of the fans somehow before blasting them, you don't want to rev them faster than they're designed to go.-cranioscopical (July 12, 2011, 04:38 PM)
You'd be better off using straws and soft-bristle, artist-style paint brushes.-cranioscopical (July 12, 2011, 04:38 PM)
That said, I still feel uncomfortable about using compressed air.-cranioscopical (July 12, 2011, 05:25 PM)
Years later I had to completely disassemble a server, and scrub it down with baking soda, water, and a tooth brush. to get the surprisingly corrosive insecticide out of it after the bug guy sprayed it to death.-Stoic Joker (July 12, 2011, 05:40 PM)
Years ago I worked soldering/stuffing board for a local manufacturer. It amazed me to no end that the completed boards were run through what amounted to a small car-wash. The liquid (mostly water) didn't hurt the board in the slightest. It's only an issue if the board is wet and energized at the same time (It's a potential problem...).
Years later I had to completely disassemble a server, and scrub it down with baking soda, water, and a tooth brush. to get the surprisingly corrosive insecticide out of it after the bug guy sprayed it to death.
Sun dried and reassembled it booted and ran just fine for another 3 years.-Stoic Joker (July 12, 2011, 05:40 PM)
WRT, the compressed air, (not trying to pick a fight SJ, just a different perspective :) ), I still use a vacuum cleaner mainly because I prefer to pull dust away from pins rather than push dust toward them. Side benefit: it's cheaper-4wd (July 13, 2011, 04:11 AM)
I take it you've vetted your hard drives, checked their S.M.A.R.T. status and have done a surface scan. Likewise, I hope/assume you have looked into giving your memory at least one full cycle of MemTest86(+) tests.
...
Also, test the voltages your power supply gives off, especially when being stressed. (Prime95 and some benchmarking tools are nice for that.) A flakey power supply is also a good culprit for instability issues like yours.-worstje (July 14, 2011, 04:46 AM)
If memtest86+ got that far without the screen turning red...chances are the memory is fine.
Run this next: Samsung HDD Tool (http://www.samsung.com/global/business/hdd/support/downloads/support_in_es.html)
If the manufacturer's diag give the drives a green light, it's probably the power supply.-Stoic Joker (July 14, 2011, 11:43 AM)
Or just for fun disable all the onboard USB stuff and see what happens...it is the last thing it was loading before it go poof.-Stoic Joker (July 14, 2011, 03:54 PM)
^ yeah, memtest did three full passes without errors...Or just for fun disable all the onboard USB stuff and see what happens...it is the last thing it was loading before it go poof.-Stoic Joker (July 14, 2011, 03:54 PM)
:D
how do I disable USB? Physically - unplug cables?-tomos (July 14, 2011, 05:00 PM)
Addendum: did a little research. Under Linux, this error is most commonly caused by bad cache on the CPU according to one source. See here (http://adamstechblog.com/2008/01/01/cpu2-cpu3-machine-check-exception/).-40hz (July 14, 2011, 06:06 PM)
| The Machine Check Exception looks like this: CPU 3: Machine Check Exception 0000000000000005 Bank 0: b200004010000400 Bank 5: b200121020000400 On Windows systems a MCE (Machine Check Exception) could also mean bad RAM, Motherboard or Processor. Reseating the processor is also another good option if you experience this error message. |
how do I disable USB? Physically - unplug cables?-tomos (July 14, 2011, 05:00 PM)
I was thinking more along the lines of a BIOS option to disable them, or at least cut them back to a lower speed and making sure nothing is plugged into them.-Stoic Joker (July 14, 2011, 06:17 PM)
^Sounds like a golden opportunity to further your education playing with it if you're getting something else to work with. :Thmbsup:-40hz (July 15, 2011, 09:58 AM)
So if you're not going to go with an "enthusiast" or "hard-core gamer" build, why bother? At least with current pricing.-40hz (July 15, 2011, 11:09 AM)
There were two apps that gave info about my CPU. The second said I had a virus in memory I think. I was photographing everything and guess what, the SD card no longer works (two weeks old, what's going on here :huh:). [/li]
[/list]
So I tried a anti-virus boot disk from c't magazine here - it's ubuntu based. Downloads latest av info from 4 different AV's.
Tested the partition that kept getting checked on reboot - clean
Tested C: crashed twice-tomos (July 15, 2011, 07:03 AM)
Sorry guys, curiosity's got me...
...
Can you try rerunning that with the drives disconnected and see what happens? Basically strip the mahine down to the bare essentials CPU, Mboard, Memory, power, and video. No modem, sound, or other cards, and no FDD/HDDs to draw power. Just to see if it'll make it far enough into the CPU test to (get a better error message, if any...and) hazzard a guess at a conclusion.-Stoic Joker (July 15, 2011, 11:59 AM)
Most people/manufacturers skimp on the power supply because they overlook the importance of it.-Shades (July 15, 2011, 12:42 PM)
Electronics behave very strange when they do not get the juice they need, leading into all kinds of strange and unrelated errors.-Shades (July 15, 2011, 12:42 PM)
If you're going to replace the motherboard/CPU, might as well just get a new machine, hehe.-JavaJones (July 15, 2011, 07:36 PM)
I'll probably bring it to the local shop...-tomos (July 17, 2011, 02:47 PM)