Thread: Blue Screen of Death Help!

I have recently had a problem with a reoccuring blue screen of death. i have about 3-5 min to use the computer before it shows up again. there error code is 0x0000008e. also when i start my computer back up again it says this.

Window has recovered from an unexpected shutdown.
Window can check online for a solution to the problem.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 8AE67B40
BCP3: AEADBF6C
BCP4: 00000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\081311-24554-01.dmp
C:\Users\Michael ****\AppData\Local\Temp\WER-101322-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Any help is much much appreciated thx.

There could be many reasons for this, what are your specs? are you gaming or is your pc under load when it blue screens?

Is your pc full of dust and/or overheating?

You might try googling 0x0000008e. Ignore the first 3 results, they're a scam.

Run. Run quickly, before the blue screen of death escapes from your monitor and gets you!

Ummm, you didn't say what version of windows you had but I gather that this is Windows 7 SP1 from the error message.
0x0000008e .. KERNEL_MODE_EXCEPTION_NOT_HANDLED - kernel crashed on bug check
0xC0000005 .. STATUS_ACCESS_VIOLATION - memory access violation

Hmmm. Not so helpful, you're thinking? Well you didn't copy the all important dump (081311-24554-01.dmp file), so all I can do is guess. This is almost always a hardware compatibility issue. It could be something like bad or loose memory, loose video card or out of date BIOS. But much more likely, it will turn out to be a bad driver. Did you just install or uninstall something? Bad shutdown or did you click on an attachment that had a provocative name.. ?

I'd suggest..
1. Run a good antivirus and spyware scan. E.g. something like Malwarebytes for the spyware scan
2. Try reverting to a previous restore point. (Or reimage your drive, if you are one of the 7 people in the country that actually backs up their PC)
3. Try running system file checker to verify the windows system files (sfc /scannow from an administrative command prompt)
4. Consider whether you may have acquired a rootkit
5. As a last resort, consider an in-place windows install. Properly done, this should leave your programs intact and just reinstall windows system files.

And you might want to edit your full name out of your post as well..









__________________________
no good deed goes unpunished

Thanks for the help everyone. I really appreciate it.
Well see i actually don't know where to find the dump of the blue screen. But if you teach me i can link it to you guys. Right before this happened I installed League of legends and ventrilo. So i suspect its something to do with those drivers. Also something downloaded with that called pando media booster and that slowed my computer down a whole lot. Barely could load anything before the blue screen popped up. but i uninstalled that and everything is fairly fast again.


1. Did a scan with Maleware-bytes already. Said computer was clean of everything. So im pretty sure its not malware or a virus.
2. Already used restore point that didnt help either (I'm not one of those 7. I have all my essentials backed up on external but there a few things i have that i havent)
3.Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log Wasnt able to attach the log for some reason though.
4.Wouldn't malware bytes have found a rootkit if i had one?
5.This sounds dangerous and scary.

lol thats funny I've been having this problem all day long also, what a coincidence. I just installed a new OS yesterday so maybe I did something wrong with that, but I already went through the long process of logging in to all my accounts at all my trackers and I just don't want to go through all that hell again so I'm just gonna wait till it completely makes the desktop inaccessible and then I'll worry about it

Have you tried booting from your windows disc and choosing the repair option. This has fixed many many problems for me and its not something that many people know about.

Just go through the disk as though you are installing window again, then on the screen where you choose the drive to install windows to, there is an option at the bottom to repair windws. It wont delete or change any of your personal files such as documents, pictures, movies or music etc it just repairs broken windows files.

If not, try a system restore to before the error started? This also wont remove any files or programs, just windows settings.

Lol that is funny sayocean. OOOHH NOOO ITS AN EPIDEMIC! Thats i really good idea jamesG. So simple yet so brilliant. But uhhh bad news, Kinda lost my CD somewhere in my room. The good news is trackers are awesome and always got my back. Also for some reason i cant upload the dmp or the cbs log file. Maybe its because im in safe mode?

Sometimes you get a quick fix and sometimes you have to work through a list of possibilities.

The dump file will presumably be located in your windows directory i.e. C:\Windows\Minidump\081311-24554-01.dmp
The other log file would be helpful too. One corrupt system or driver file is often sufficient to cause grief
Malwarebytes is very good, but it can't detect or fix 100% of problems. No software can

The option that JamesG is suggesting is the same as the 'in place windows install' that I mentioned. It's a good option, but read the prompts carefully. If in doubt, Google or post questions here before proceeding. Most of the time it goes smoothly. But if at all possible, you should still back up your drive before doing any reinstall. Just in case something goes wrong & you end up with an unbootable configuration.





__________________________
no good deed goes unpunished