BSOD Survival Guide

Terry Olaes

I Used to be the [H] News Guy
2FA
Joined
Nov 27, 2006
Messages
4,646
Maximum PC has a handy BSOD survival guide that should be helpful if you’re trying to figure out where that damn crash came from. There are 4 pages so keep looking if you don’t see your issue at first.

Though Blue Screens are difficult to decipher, all the information you need to figure out what caused it is right there in front of you in blue and white—and that’s where we come in. We’re going to show you how to dissect the blue screen error details, so you can fix the problem that’s causing them.
 
This guide is probably good if you're suffering from chronic BSODs and can't find the reason why.

Only time I ever see a blue screen in XP or Vista is when overclocking too far or using faulty hardware. Contrary to what Apple would have you believe with their ads, a healthy PC never "freezes", crashes or displays a BSOD without warning or reason.
 
This guide is probably good if you're suffering from chronic BSODs and can't find the reason why.

Only time I ever see a blue screen in XP or Vista is when overclocking too far or using faulty hardware. Contrary to what Apple would have you believe with their ads, a healthy PC never "freezes", crashes or displays a BSOD without warning or reason.

QFT.

I get so tired of some Microsoft bashers always blaming the OS for bluescreens when most of the time blue screens are caused by faulty hardware or drivers.
 
I can't remember the last time I had a BSOD. It must have been when I first used Vista and the Nvidia drivers blew. Once that crap was straightened out, it's been smooth sailing.
 
IRQL_NOT_LESS_OR_EQUAL has always been a hardware problem for me A bit more voltage and it goes away. I have never even seen the other messages listed in the article.
 
Haven't seen a BSOD due to anything other than trying a new overclock since.. hrm... Windows 2000 I think.
 
Vista can have a hanging BSOD the hardlocks the computer, it happened to my buddy earlier and actually it was an extremely bad one. This one had no information except that the NT Command Processor could not run. It persisted through CD re-installs (virus job) and my buddy did not know how to get around it, using the advanced options in the install, a quick format causes the NTFS MFT to be rewritten and allowed Vista to reinstall. Runs nicely now. BTW, Vista SP1 looks pretty and I actually liked how it installed nicely for him (I had Vista RTM with my machine which did not survive long enough for me to wait for SP1 to roll out... and I am very reluctant to blow away a working image, windows 7 will be trialed by USB before I dare modify my main HDD image).

At least I did not have to Low Level format as it was not an MBR/GPT virus.
 
I don't remember the last time I had a BSOD that wasn't related to overclocking, with the exception of nVidia drivers crashing from time to time, but it's been a while even since the last time that happened. Vista is really quite happy and stable.
 
I pretty much echo these guys above me, I haven't had a BSOD that wasn't my fault for ages.
Normally I'd still read the article but I hate MaxPC with a passion so none of that. :D
 
Yeah, the same here, I don't remember having any BSODs in a long time. Last time probably when overclocking and testing out different RAM configurations and timings.
 
Same here, only got BSODs when I push my RAM too hard, and the last time that happened was with my opteron 148 back in early 2006.
 
I get bluescreens for nothing in vista.
Same config, everything is the same, windows 7 or xp = works.

But i dont care about vista anymore, windows 7 works fine for me, and i still only use build 7000 :p
 
I get BSOD's every now and then mostly because I'm fucking around with my hardware and the fact that I'm also running Windows 7. 7 is quirky so I expected to come across BSOD's every now and then but it was easy to figure out what the hell was wrong with it.

It is dumb for those Microsoft bashers especially the linux/ubuntu lovers trashing it "LOL they still get BSOD" as if Linux/Ubuntu is immune. Especially it's a hassle having to find the drivers for those operating systems.

We have our niche, they have theirs.
 
IRQL_NOT_LESS_OR_EQUAL has always been a hardware problem for me A bit more voltage and it goes away. I have never even seen the other messages listed in the article.

A bit more voltage to what? RAM? Thx.
 
For some reason, Civ4 will blue screen my PC every time I load it ever since upgrading to 8GB of RAM. Other than that, all my the blue screens I've seen in the past two years are either related to overclocking, bad ram, or nvidia drivers (although no nvidia in past year)
 
Who only has a single PC? :p

I mean, if you have a second one (or more), you just Google your BSOD.
 
The easiest solutions are often the most overclocked, but they can also be the most effective
haha..I think this was supposed to be "The easiest solutions are often the most overlooked, but they can also be the most effective"
 
BSODs in reality tell you jack shit. It's the minidumps and event log that really lead to a solution. If you know what you're doing you can really pinpoint an issue using the Windows Debugger app and minidumps.
 
It's interesting that many people do not believe a BSoD exists in Vista. I guess that's a testament to the stability of Vista.
 
Yeah, I have had 0 full OS lockups on Vista since I started using it about 9 months ago. A couple of errors in bootup, but rebooting again fixed whatever the problem was.
 
Who only has a single PC? :p

I mean, if you have a second one (or more), you just Google your BSOD.

Exactly! :p

I have only ever had one BSOD in Vista and that was due to a memory failure. Had maybe two in all of the years that I ran XP and those were due to overheating from a family member not knowing that you should have your PC in at least some sort of ventilated area.
 
Back
Top