BSOD improved for Vista

[lonestar]

Sweet, even if it would become the RSOD ). The "will connect to the internet and find a solutions" is nice, if it will work. Even though most BSOD problems that hit me where driver related or could have been solved running chkdsk.

 

[provenlogic]

this is actually a good thing. But that said, if you are still getting BSOD's with even XP, you're doing something WAAAAY WRONG.

 

[ElectricSuperstar]

The only time I've got a BSoD with XP was when my hard drive was slowly failing. Once I got a new drive and reinstalled XP it works just fine. Better BSoD error messages will be good, XP's can be a bit cryptic.

 

[davy]

um......






shouldn't the be more concerned with PREVENTING the blue (or red) screen of death than making it more handy?

 

[rotary]

if you are still getting BSOD's with even XP, you're doing something WAAAAY WRONG.

No kidding. I've been running XP for years and have never seen a BSOD. Much different story with Windows ME...that OS was a nightmare.

 

[Paws]

You can change the colour of the ____ screen of death in the registry somewhere since Windows 98.

And I can't remember if my XP system ever showed it.

 

[jordyy]

um......






shouldn't the be more concerned with PREVENTING the blue (or red) screen of death than making it more handy?

davy -
they do all they can to prevent it, but no OS is perfect, and it is impossible to account for all possible compatibility or hardware issues. people are hard on MS, but i think they truly try their best to make the OS as good as it can be.

 

[mike_n_herrin]

i've never seen it in XP. But from 95-Me...yeah saw it often enough to know i could never decipher what it said. instead of giving your the error in hexidecimal or whatever, why doens't it just tell you the driver that caused the error, or hardware or whatever? doesn't seem THAT hard to do....

 

[MidnightPrism]

I've never seen it with Win 95, 98, ME, 2K, or XP

 

[cityboy-stl]

An error occurred transferring exectuion.

Exectuion ???

 

[davy]

davy -
they do all they can to prevent it, but no OS is perfect, and it is impossible to account for all possible compatibility or hardware issues. people are hard on MS, but i think they truly try their best to make the OS as good as it can be.

i hate to say it:

but linux doesn't even have a blue screen of death.

 

[davy]

Actually, paws, you can change not only the color of the BSOD, but also the message displayed. Some suggestions I've read:

"Windows has suddenly decided to hate on you"

"A problem was detected on your computer. You are running Windows"

"nyuck, nyuck, nyuck"

roflmao

those r fuhnie

 

[provenlogic]

shouldn't the be more concerned with PREVENTING the blue (or red) screen of death than making it more handy?

Yes, and they do that, but the POINT is, for those of us that actually need to gleam a little information from that screen so we actually know how to fix what's gone wrong, having more info is A GOOD THING.

 

[provenlogic]

Yeah, something WAAAAY WRONG like try to run Windows under VMware. Or multitask it with OS X on a PC (it can be done). Or install it to a RAM disk.

Multiple OS's are not worth the trouble, if you try doing it, you're bound to have issues, so that's no surprise at all... So duh to that one .

 

[Corny]

oh i BSOD'd my XP quite often. it's easy ... I just needed to mess around with my graphics driver. I can still crash it today within a minute if I want to. But yes it is a bit rarer than in ME, because sometimes the computer just restarts, without a BSOD

 

[PrideGuy]

I think those guys who brag they never see BSODs are posting from Nursing Homes for Elderly Computer Scientists.

hehe funny. I agree i have had the BSOD a few times on my xp machine.

 

[provenlogic]

^ I agree, Corny. If you haven't BSOD'd Win XP quite a few dozens of times, you're not doing anything interesting with your computer.

I think those guys who brag they never see BSODs are posting from Nursing Homes for Elderly Computer Scientists.

Well if you call professional 3D graphics development and 3D modeling using multiple OGL graphics programs along with dedicated graphics manipulation software and post-render effects programs, coupled with hardcore gaming on your home-built graphics and gaming PC workstation "Nursing Home for Elderly Computer Scientist" work, then might I suggest you have a very twisted definition.

The bottom line is, if you are the slightest bit competent and know what the hell you are doing with computers and know enough to get things right the FIRST time, you won't get BSOD's with XP. So might i suggest that people, like me, who brag they rarely if ever get BSOD's with XP are merely more competent and better computer users than those who do get them more often.

 

[provenlogic]

oh i BSOD'd my XP quite often. it's easy ... I just needed to mess around with my graphics driver. I can still crash it today within a minute if I want to. But yes it is a bit rarer than in ME, because sometimes the computer just restarts, without a BSOD

Hey, you know you have to set XP to always display a BSOD right? If you do that whenever there's a hard crash it will always display a BSOD and hold there until you manually restart.

 

[Corny]

i know elsewise you only see the BSOD and it immediately reboots. what i was talking about is just a reboot - as if someone pressed the reset button.

and i think trying to make a relation between the user competence and the number of winxp BSODs is quite silly.