What is the blue screen of death?

  • Thread starter Shannon
  • 53 comments
  • 1,208 views
XP doesn't give you a BSOD, it gives you an "error report" or just simply restarts. A BSOD is just a message that tells you that Windows has crashed, it doesn't do anything to your computer.
 
Originally posted by Klonie Gun
What exactly does a BSOD do to your computer?

It reports the settings of certain important values immediately prior to the fatal error, but this information is probably only of use to developers. It also tells you what the error was, and which file caused it, which can give you a reasonable heads-up on how to fix the problem.

Finally (and this is the bit that takes the time), it writes the entire contents of memory to disk, for the purposes of debugging. You can find this file at c:\winnt\memory.dmp.
 
Which, if you run into problems of disk space after a crash, look into deleting that file. It's usually the same size as your physical ram, if I remember correctly.
 
Originally posted by Viper Zero
XP doesn't give you a BSOD, it gives you an "error report" or just simply restarts. A BSOD is just a message that tells you that Windows has crashed, it doesn't do anything to your computer.

Error reports are for programs that crash. Explorer doesn't take the system down with it any more (it just restarts explorer, usually leaving your programs intact.)
I've had many Blue Screen of Deaths under XP. It does take more to get there than older OS' though.
 
Originally posted by AltF8
Wow, you're unlucky. ;)

Been running XP for months, 0 BSoDs.

I wouldn't call it unlucky... let's just say I've been known to run more things than you can shake a stick at. ;)
 
Originally posted by Tom M


I wouldn't call it unlucky... let's just say I've been known to run more things than you can shake a stick at. ;)

Fair enough.

(Although I usually run Photoshop, Visual Interdev, Outlook, Trillian, and at least one copy of IE at the same time on my P2-550 at work. ;))
 
Originally posted by AltF8
Wow, you're unlucky. ;)

Been running XP for months, 0 BSoDs.

Win2K Pro at home: 2 years, 4 months, 1 BSOD (on day of delivery when I installed a rogue driver).

Win2K Pro at work: 4 months, 0 BSOD.
 
Originally posted by AltF8


Fair enough.

(Although I usually run Photoshop, Visual Interdev, Outlook, Trillian, and at least one copy of IE at the same time on my P2-550 at work. ;))

Every once in a while video encoding takes it down with oddball Avi codecs, and sound card updates are usually hell, but I've been known to have MS office, GTP (or other websites) in a window, MSN conversations, Quake 3/ RTCW type games windowed, Newsbin downloading, and someone FTPing off my HD.
I think it's MSN that puts me over the top. ;)
 
Originally posted by RVDNuT374
Since 98SE was installed last year, about 15 blue screens.

Windows 98 doesn't handle its resources properly, whereas the later OSes (including NT4) do, which means that 98 is prone to crashing in unexpected circumstances, usually down to the fact that you're running conflicting apps, or apps which are resource hogs.

Also, it's the same with hardware, which is much better managed under 2000/XP. 98 had USB support, but since 98 is basically Windows 95, and 95 had to have USB support 'bolted on' at OSR2, it's never really worked. Plus 98 cannot do interrupt sharing, which is another huge problem for the OS.
 
I thought my old computer (Windows 98 - plain 98) had a bug or something because it kept on getting BSODs...and now I find out that it was because 98 is ****house ata handling its resources. :grumpy:

Win2K Pro kicks most arse. Yet to try XP.
 
Never had this problem thankfully... Don't use PC's

But i've seen it happen on a few of my mates PC's some of which have resulted in totaly reformating the HD which can take up a lot of time then having to reinstall all the drivers and OS etc

Sod that
 
Originally posted by Eddy
I thought my old computer (Windows 98 - plain 98) had a bug or something because it kept on getting BSODs...and now I find out that it was because 98 is ****house ata handling its resources. :grumpy:

Win2K Pro kicks most arse. Yet to try XP.

Ah, well, that's because you're talking to an experienced professional! ;) :cool:

I agree with your second statement. I believe 2K Pro to be the best OS that Microsoft have done in a long time, although I admit that my 2hrs on XP when it absolutely WOULD NOT do what I wanted it to, because it thought it knew better, didn't really help!
 
Well, lots of computer pros have said that Win2K Pro is the best OS so I won't bother with the huge XP download. Plus, I rather like Win2K Pro - its icons and stuff.
 
Originally posted by   
get XP, youll never get a blue screen.


My friend has XP Pro and he drove it into the ground and got the blue screen. He was tryin to edit some video from our class senior trip. :reallyodd

says it's the only time he's gotten it though
 
It's kind of interesting hearing this from the other side of the fence, per se. :)

In the Mac community, the blue screen of death is slightly different. Instead of containing an error log, it's just a screen that comes up instead of the desktop that is, well, all blue.

Actually, it's a lot worse for an OSX user to have one than a Windows user... usually, one only gets it due to a major perephriel (sp?) problem, or, in most cases, because of hacks.

However, most OSX users will just see the occasional application crash (usually IE), and the rare kernel crash (which entails nothing more than a restart). :)
 
Originally posted by GilesGuthrie
So they don't show the bombs any more?
Nope! :D (lol, I had totally forgotten about those... I had to think for a minute on what you were talking about :P)
 
They were certainly much more rare on a Mac than on the Atari ST, which would bomb quite frequently. But perhaps that had more to do with the software I was running, which was sometimes less than strictly legit!

I still remember it on the ST: Two bombs was a page fault (memory access error), and three bombs was Illegal Instruction.
 
Back