Blue Screen Of Dead Help

BlackBird.

Poster Extraordinaire
Joined
Jun 1, 2009
Messages
2,865
Hello everyone.

number1p.jpg


I know the Blue Screen of Death is a famous problem in windows XP and windows vista or 7 maybe..
And when I had them a lot in the past I decided to learn something more about it;
how to fix it ofcourse.

And that's what I'm gonna learn you guys.
This tutorial is just the simple way, it doesnt always work. There are also ways where you
have to delete "hard to find" files and edit "hard to find" files, but thats not what I am going to do.

What the most people probably have to do is this:

Start --> Control Panel --> System --> advanced --> Start up and recovery --> settings --> uncheck the box "automaticly restart of system failure/crash".

number2.jpg


After you done this you are ready to get the "Blue Screen of Dead!" (it won't disapear right away anymore)

The Blue Screen Shows 2 important things. 1: (name).sys. And 2: STOPx 0xXXXXXXXX. You need to get both names, write thim down or something.

number3m.jpg


Reset your computer. (Just press the reset button at your pc:P)

RonPaul's Help: LINK ISNT WORKING. WORKING ON IT.

Now you need to analyze the crash dump file. You can see that it is writing dump files to C:\Windows\Minidump (by default). Browse there and you will get a file for every BSOD you've come upon that was able to be written to a dump log.

To analyze the dump log, you need to download Windbg which is part of the Debugging tools (comes in x86 and x64 http://www.microsoft.com/whdc/Devtoo...g/default.mspx).

1. Open Windbg
2. Go to File > Symbol File Path and enter SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
3. Go to File > Open Crash Dump and browse to the minidump directory
4. It will open, spit out a bunch of text, scroll up to where it says "use !analyze -v", click that and you will get details about which process caused the BSOD, memory references, etc


Then take THAT data to google. That's how we do it in biz

If you still dont succeed in getting it fixed.

Place your problem and codes here, and i'll try to help you.

BlackBird.


P.S If the first picture is not allowed please tell me i delete it but please dont delete the whole thread, took a lot of time.
 
Last edited:
This is only half the solution. You need to analyze the crash dump file. You can see that it is writing dump files to C:\Windows\Minidump (by default). Browse there and you will get a file for every BSOD you've come upon that was able to be written to a dump log.

To analyze the dump log, you need to download Windbg which is part of the Debugging tools (comes in x86 and x64 http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx).
  1. Open Windbg
  2. Go to File > Symbol File Path and enter SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
  3. Go to File > Open Crash Dump and browse to the minidump directory
  4. It will open, spit out a bunch of text, scroll up to where it says "use !analyze -v", click that and you will get details about which process caused the BSOD, memory references, etc

Then take THAT data to google. That's how we do it in biz
 
and that is why i hate windows

on my suse boxes the worst thing i ever had was a X11 crash and the server has never went down and i keep it running 6 months at a time.
 
I thought it was Blue Screen of Death.... Good guide otherwise ;)
 
and that is why i hate windows

on my suse boxes the worst thing i ever had was a X11 crash and the server has never went down and i keep it running 6 months at a time.

And it hates you!



Kirkin' mac fanboys :P
*dives for cover*

Though it is a bit much to do :sleep:
 
I get it on my vista.....says serious error or what not. just restarts and everything is ok....... im on a mac so i cant try this method QQ
 
SUSE's linux, not mac?



lol my point was that windows is the most inefficient OS between the 3 it is based on an old kernel that doesn't support proper security, users, or networking than has all of that thrown on top as a afterthought. it will always be more unstable than other OS's and will also be loaded with tons of security holes until they make a new kernel deigned from the ground up for modern computer uses.
 

Latest posts

Back
Top