88 Comments
- redhatcat, on 10/12/2007, -9/+33"A problem was detected on your computer. You are running Windows."
- Mike89, on 10/12/2007, -1/+24"If somebody is getting BSOD's on their XP at this point they're doing something wrong or something is broken."
Somethings broken? You think? That's *THE* ***** reason BEHIND Blue Screens. - inactive, on 10/12/2007, -4/+21Erm... I use Windows fairly frequently (not as much as my OSX, Solaris or Linux boxes, but still...) -- and I have not run into a BSOD in perhaps four years. Hell, they don't even HAVE the BSOD anymore, do they?
- inactive, on 10/12/2007, -2/+14The BSOD can still be caused due to the following reasons:
1] Bad Drivers
2] Bad SMPS/Power Supply (I've been getting them recently :( )
3] Starforce (Yeah, this is actually true)
4] etc... - TehSuper, on 10/12/2007, -1/+13I haven't had a BSOD in about 4 years now also.
- therernospoons, on 10/12/2007, -4/+13screenie: http://www.23hq.com/fluxiontech/photo/845998/original
- theRIAA, on 10/12/2007, -1/+9...how about the "FLASHING RED SCREEN OF HAPPINESS"
- PacoDG, on 10/12/2007, -1/+8Just another "haven't had a bsod in years" comment.
Then again I run the best operating system in the world. Windows 2000 w/Service Pack 4!!!!1!! - lonnieh, on 10/12/2007, -0/+6@lotusleaf: Yeah, install linux on a bad drive. Way to go.
- vyoming, on 10/12/2007, -4/+9ya, it's been a while since i had a bsod too.Probably more than a couple of years
- marcusb, on 10/12/2007, -3/+8I've never had a BSOD in XP that was not caused by faulty hardware..
- stou, on 10/12/2007, -3/+7Yes they do, its usually caused by crappy drivers. I had a BSOD a few weeks back due to computer overheating (me thinks).
- aoeu, on 10/12/2007, -5/+9^ (can't edit after posting, apparently a bug).
My point was, that Windows itself is far more stable that all those Linux zealots say. - aoeu, on 10/12/2007, -5/+9Exactly.
I've got an uptime of 42 days at the moment on my work computer, that means programming, browsing, e-mail what-not every day. And I can still bear the speed of multitasking (switching resource hungry apps) after this uptime with only 512MB of RAM. - pixelmixer, on 10/12/2007, -1/+5The nvidia networking manager creates its fair share of BSODS... never got one till i built my new PC and it happened a few times while installing windows and while downloading large files due to the network manager.
- cam18, on 10/12/2007, -0/+4i like linux also, but zealots of any kind are really annoying
- inactive, on 10/12/2007, -0/+4"Anybody who says they use Windows and do not get blue screens is lying"
*****. The computer i'm on right now is running windows and It's been on for three weeks now. I have it set up to automatically record the World Cup games. I bought it a year and a half ago and while a couple of bug-prone programs have frozen (Democracy Player, Firefox, etc.) I haven't gotten a single blue screen during that time. - i440, on 10/12/2007, -5/+8The only time I ever got a BSOD on Windows XP was when I had file system problems. If you get a BSOD with any frequency at all, something is wrong on your end.
- robbh66, on 10/12/2007, -1/+4I wish you would have bet your left and right pinkies - that way you'd stop capitalizing random words in the middle of a sentence.
- TehSuper, on 10/12/2007, -1/+4And I'm on Windows and I've never gotten one.
- inactive, on 10/12/2007, -5/+8"can't edit after posting, apparently a bug"
Reboot? - redxii, on 10/12/2007, -1/+4That's for those of us who can't wait several years to view our customizations.
- hypercube33, on 10/12/2007, -0/+2The only BSoD I had on my last XP box was partly a driver problem -- the hardware literally gave out (Hard Drive controller.) After leaving a million and a half errors in my event log, the poor Promise66 PCI card finally choose to suicide taking my file system down with it! Somehow XP ran until the card failed completely (I couldnt get files off the drive ..xp was running off of it, but the swap was on the mobo IDE) brining the system down seconds later.
Blue screens are for crappy hardware. (Drivers are part of this.) - cyssero, on 04/18/2009, -1/+3Oh my God. It's like, since digg V3 - not only is there so many more spam "news" articles, all the users are now retards too (or there's been an influx of new ones).
R.I.P. Digg :(
Someone give me a Digg v2 using Digg v3 RSS feeds, PLEASE! - bobbles, on 10/12/2007, -3/+5The last time I had a BSOD was when nvidia released a broken driver (and then had it fixed the next day i believe) but being able to remember something like that at least shows how much better windows got with the move to XP... compared to BSODs every time you wanted to just *do* something on Win98
- robbh66, on 10/12/2007, -0/+2"If windows is so bad why has it been the most successfull OS over the years???"
Market penetration and people are used to it.
Look at passanger jetliners for example- they're flying tubes with wings. Blended wing bodies would make MUCH better passanger planes in terms of just about every major factor but there are two large problems with blended wing bodies: airports arent designed for them (no market penetration) and people will be scared to fly in them (people not used to the new idea). - mancat, on 10/12/2007, -0/+2I would like to find a way to return XP/2000/2003's BSOD screen to the much more descriptive one that was given in earlier NT releases. You could generally tell right away what program, driver, etc. caused the crash. In the rare cases where I do run into a BSOD (yes, it is rare for the majority of us) I would like to know instantly where to look without having to use Microsoft's Crash Analysis.
- robbh66, on 10/12/2007, -1/+3"My Hardware is Up to date"
Check those shiney new boxes. See if they have a windows, OSX, or tux logo on them.
Up to date? For windows perhaps...
PS- My three year old computer has no problems *chuckles* - jrbrewin, on 10/12/2007, -1/+3and your unbutu installation wont give you the same experience as running vista. What is it today? Obvious statement day, or what?
- FrogRacer, on 10/12/2007, -0/+2i have just done the mod to one of my vmware machines on my linux box and it works, to an extent, i get that a windows file has been modified crap and deletes the new file, then i one of the entries boots into a ***** install
- Agret, on 10/12/2007, -0/+2"My Hardware is Up to date, and Linux wont run on it...... But Windows XP Will"
Funny that Linux runs on a 486 yet your computer can run Windows XP - hypercube33, on 10/12/2007, -0/+1Finally something usefull! I only see BSoD's on my home-built machine because the motherboard is apperently defective (Thanks MSI!) and not compatable with SATA2.0 hard drives!
Can anyone see this exploited by a virus for advertising? :P - aerotive, on 10/12/2007, -0/+1I haven't had a BSOD in a LONG time, maybe 2 or 3 years. But I still have the occasional lockup, usually due to a bad driver. Last week my computer started locking up when I tried to copy MP3 files over to my MP3 player. So I resinstalled the driver for the player and all was well.
But a well-designed OS should not let a driver bug lockup/crash the system. I hope Vista doesn't let driver problems crash the whole machine. - collywolly, on 10/12/2007, -0/+1The guy over the other side of my partition is debugging drivers or upgrading them or something similar, and gets a BSOD around once a day.....
Some people do see them regularly. - DarkSorrow, on 10/12/2007, -5/+6interesting, i hate my BSOD with the same words, need some changes now i can.
- Dolomite, on 10/12/2007, -0/+1I see blue screens all the time when I run Windows. Windows is not stable.
- CBTF, on 10/12/2007, -0/+1anyone else having time posted troubles? it says that i replied 7 minutes ago, but in reality it was only 1 minute ago, or possibly less.. i tried to edit the typo, oh well.
- inactive, on 10/12/2007, -0/+1I love this hack, I have been wondering how to do this for years.
I still get about one or so BSOD a month under Windows 2000 but that is mostly due to my video card overheating and sometimes the cheap ram I have.
Now that I know how change the messages of the BSOD I would love to know how to stop it from dumping the memory to disk. - robbh66, on 10/12/2007, -1/+2Wont run Vista? How much would you like to bet?
Also, learn to use reply. - MrKite, on 10/12/2007, -0/+1I don't think I've gotten a BSoD since the day I upgraded to Windows XP, and that was a long time ago.
- rebz, on 10/12/2007, -0/+1i agree with jhatcher. modify or not, isn't the point of taking care of your system so that this DOESN'T happen? :)
- mancat, on 10/12/2007, -0/+1I know how to get the post-mortem information. What I'm saying is that I want to see it immediately when a panic occurs, like NT used to do..
- robbh66, on 10/12/2007, -1/+2Damn they need to change the comment editing back to what it used to be.
Anyways- forgot to mention that we've known about the benefits of BWB for nearly 50 years, but only now are they possibly designing some early prototype BWB passanger planes. - mancat, on 10/12/2007, -1/+2My 3 year old laptop runs Vista fine.
Move on troll. - robbh66, on 10/12/2007, -3/+3BTW - Windows Vista Upgrade Advisor disagrees with you on whether my computer will run Vista INCLUDING Aero-
http://thedervishclub.com/images/WILLRunVista.JPG
*nyuck nyuck nyuck* - hypercube33, on 10/12/2007, -2/+2Troll.
- SgtBeavis, on 10/12/2007, -0/+0One of the reasons that Microsoft took that information out is because it could be missleading. For instance, the old BSOD might say that the problem was NTOSKRN.EXE. However it you actually took a look at the stack trace, you would see that it was a 3rd party driver that was causing NTOSKRN.EXE to fail. Not to pick on anyone but one small example that I've seen is Symantec's SymEvent.sys filter driver. Symantec regularly updates this driver on their website but it doesn't automatically update on any individual system because it would require a reboot. Because of this, alot of people out there will have versions of this driver that are over two years old. I've seen many a crash that was actually caused by the older version of this driver, but the root cause was this driver....
BTW, if you want to get that old information, then learn how to use the Windows Debugging Tools. You can get all that old information (and more) by loading the dump in the debugger and simply running the "!analyze -v" command. Alot of the time that will point you in the right direction. You can learn more about debugging by reading "Windows Internals v.4" by Mark Russinovich and Bryce Cogswell (of SysInternals fame)
Windows Debugging Tools can be downloaded for free from here:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx - videogamechamp, on 10/12/2007, -0/+0I haven't had a standard BSoD in a while, but recently I had a physcial memory dump. Nothing to important lost though.
- arboc, on 10/12/2007, -0/+0Do you want to add some cool backgound image to the BSoD?
http://rootkit.com/gal_open.php?id=1955 - SgtBeavis, on 10/12/2007, -0/+0I'm changing all mine to purple. (same color as a kernel panic screen)
That'll give our Linux admin a heart attack. -
Show 51 - 87 of 87 discussions



What is Digg?
Digg is coming to a city (and computer) near you! Check out all the details on our