Slashdot Mirror
Longhorn: Fewer BSODs, More RSODs
Jan Theofel writes "Windows Loghorn will present you less BSOD. Joi Ito reports that Windows Longorn will get additional ROSD (red screen of death) for 'really bad errors.' So you will get less BSOD but some new RSOD. You can find a ROSD screenshot in a virtual machine in his weblog entry."
It's always nice to see Microsoft adding new "features". Now they can tout Longhorn's decreased BSOD occurrences. Although I'd think they'd wanna avoid red screens as they are angry colors.
Microsoft Sucks, F/OSS Rocks. I get mod points now right?
I guess thats one way of getting rid of the BSOD
To think is to engineer, to engineer is to become God
no screen of death....
So where are the yellow and orange? Looks like MS has been taking advice from Tom Ridge.
Let that be a leeson for the losers that keep claiming that Microsoft never
innovates!
Wow that was quick... Already /.ed...
And there's no posts yet... ouch... i bet ya the box has already been bsoded...
I've not seen one of those in a long, long time.
An error occurred transferring exectuion. I guess M$ isn't even using developers who know English?
Every time you post an article on Slashdot, I kill a server. Think of the servers!
Does ROSD=RSOD or is it some twisted lack of spellchecking?
Parents all over America are concerned that these new 'Red' screens of death are very stressful for their children and are pushing for microsoft to change this color immediately.
Microsoft was unavailable for comment at this time.
Marge, get me your address book, 4 beers, and my conversation hat.
They could use green, or yellow, and avoid IP lawsuits. (So long as they don't use the RGB value D7D7D7 (which is patented by a well known controversial website) they should be OK.
Dont forget NetworkMirror :)
. ito.com/archives/2005/05/07/bsod_upgrades_to_rsod_ in_longhorn.html
http://www.networkmirror.com/adYJGbG8ajC3f55y/joi
Am I the only one not getting the joke?
Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
I guess they've FINALLY fixed the last issue that casues a blue screen of death with Longhorn. :)
What exactly is a really bad error? I mean, a bad error versus a really bad error? That warrants a color change, anyways?
Frankly, I think customers ought to get rsod's for actually buying the damn product. That seems like a really bad error to me.
Now people will have heart attacks instead of just saying, "What the heck?" and getting frustrated.
Blues (and greens) are generally more soothing/comforting (which is why blue or green are most frequently favorite colors), whereas reds are more jarring (which is why it's used for stop signs, warning labels, etc.).
Rainbow Screen of Death?
:)
Wow man.
...that Microsoft changed the color of the crash screen, ie: they became communists
You can find a ROSD screenshot in a virtual machine in his weblog entry.
Not anymore, heheheh....
Funny how this is a "feature" Long-time reader, first time poster. YEAH!
Well, here's a link to the pic... til I get slashdotted... http://209.193.18.52/RedScreen.jpg
Microsoft Sucks, F/OSS Rocks. I get mod points now right?
Also more information is always bad.
Honestly, a little more information clearly rendered for my decision making would be nice when Linux craps out unexpectedly. It's not that I don't like the occasional puzzle, it's that I don't want to be surprised with one that I have to solve before I can move on with my work.
If Microsoft is really smart (*cough* did I say somthing bad *cough*), they would allow admins to change the color of the Screen Of Death anyway they like. Personally, I like amber text on a black background. It reminds of the days when I had an amber monochrome monitor for my Commodore 64 when I was a little lad.
In case some smart aleck replies "Oh, you must be using Linux."
Who edits these things? I'm glad I don't pay to read this site, the editing is horrible. Slightly more on topic, I never see the BSOD anymore unless it's a hardware problem. Maybe I'm not trying hard enough...
Is there heaven? Is there Hell? Is that a Tuna Melt I smell?-Primus
Longhorn is red-shifting... the release date must be receeding!
Since last night, I get this gem.
My own RSOD
As of 10/06/03, I hate COBOL developers.
Ito and Lessig basically gave their stump speeches (Lessig about the need to reform copyright laws for balance, Ito about the fact that there's plenty of opportunity for artists and businessmen to make money out of a less-punitive IP landscape), but they're such great stump speeches you hardly mind. They're definitely worth hearing, and they got a pretty enthusiastic response from the crowd there (and I don't think this was entirely from preaching to the converted).
Any sufficiently advanced technology is indistinguishable from a rigged demo
--Andy Finkel (J. Klass?)
The actual article
Just the screenshot from Virtual PC
Gates once proclaimed that Windows 3.1 fixed the UAEs that plagued Windows 3.0 once and for all. It simply renamed them GPFs.
If you are seeing BSODs almost daily, you either have faulty hardware or some seriously buggy drivers. Honestly folks, XP, and even 2000, BSOD very rarely.
...fucked the MFT (master file table) of my windows partition and I lost everything. I can't imagine what a 'really bad errors' RSOD will make.
I can imagine it, instead printing really useless data about the error, it will say:
Owned!
"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former" - Albert Einstein.
I see Linux crash on our cluster of 100 Sun Opteron boxes daily.
The hardware is rock solid because it originally shipped with Solaris. The Sun reps said that we are one of their few customers running 64-bit Linux because it isn't stable enough.
Speaking of reliability, I was just thinking how Microsoft could reduce the complexity of the next version of Windows, Longtooth, due in 2009.
Longtooth will include a tremendous amount of new features implemented in completely new code. Many, but not all, existing features would be reimplemented in VisualBasic.NET just for the heck of it, even if mature versions are already implemented in C or C++. Programmers making the new VisualBasic.NET code would not be allowed to look at the code that already exists, so that new ideas might be better implemented. The features will be chosen by random for reimplementation.
All Microsoft code would assume that any Microsoft code (the OS and any Microsoft applications) is secure. This code will always execute with no checks to make it run faster. All other code will be subject to Longtooth's new security system, dubbed Microsoft Longtooth Security Center 2003. This feature will give users more control over processes that execute in their computers. I will explain some of its features here:
To maximize security, Microsoft Longtooth Security Center 2003 will make certain assumptions about the user. For example, users who use Microsoft products are assumed to know what they are doing. However, users of 3rd party applications not made by Microsoft are always assumed to be complete idiots. Therefore, all user interface events occurring outside of Microsoft applications will trigger a safety mechanism.
For example, each time the user moves the mouse in an area not controlled by a Microsoft application, the user will see crosshairs moving across the screen to indicate where the mouse will be located. When the user stops moving the mouse, an authentication window will appear and state: "The user has requested that the mouse be moved to the location on the screen indicated by the crosshairs. This area of the screen is controlled by untrusted code that may cause damage to your computer, your documents, or your network. Do you wish to allow the mouse to move to this location?" Buttons for "yes", "no", "details", and "help" will be displayed.
Selecting "no" will cause the mouse cursor to remain at its previous location. Selecting "yes" will bring up another window, requesting the user's password to authenticate the movement of the mouse. If the user enters the correct password, the mouse cursor movement will be authenticated to that user and the cursor will be placed at the new location. Selecting "details" will display the X and Y coordinates of the new position, followed by warnings against using untrusted rogue code such as Linux.
For additional protection, clicks, keys pressed on the keyboard, items selected in a menu, or other input events will trigger similar security mechanisms. Since Microsoft code is considered secure, these checks will not occur in windows owned by Microsoft code. Also, the mouse may be used to click on the above buttons and fields during mouse movement authentication. If any such movement of the mouse takes place during the authentication process, the mouse will still be moved to the location indicated by the crosshairs, but a bug in Windows will cause the cursor to immediately "bounce" back to the location where it was last used during authentication. Microsoft will refuse to fix the bug unless Linux is outlawed in all countries, even those countries that have no computers.
Many other authentication checks will be made by Windows. I'll return to this topic in a moment. First, let me mention that Clippy, the talking paperclip, along with other Microsoft characters, will appear during this proces
Well, now that I see that it's not a BSOD replacement, I appreciate some variety of *SOD colors.
How long until the Green Screen of Death, the Orange Screen of Death, and the fearsome Black Screen of Death?
Seriously, if it turns out to be a good debugging tool, then I'm happy; however, far, far too many products ship from MS with the debugging tools tightly integrated into the product. Ctrl-Alt-Delete, BSOD, regedit, etc. And now some of that behavior is required for correct product operation (see the history of Ctrl-Alt-Delete).
green: its the common errors you used to get before
orange: beware, it might be a big one (read Windows can deal with it.. but its a tuff one
Red: OMG, we forgot to fix that error, watch out for the next SP #45585
black: Longhorn died, dont sob.. it was expected
Well, yeah. Evidently, some people lack the knowledge/skill to set up an XP box correctly.
"Windows -Loghorn- will present you less BSOD. Joi Ito reports that Windows -Longorn- will"
Will this feature be available in both products?
Red screen reminds me of the infamous Amiga "Guru Meditation" error. I always said the Amiga was ahead of its time.
My drives and iRiver h10 are NEW and operating fine. I checked them.
Its NTFS.sys, HTTP.sys and the TCPIP stack thats bolloxed big time in XP wheras 2000 was fine. Rock solid, XP has is way more unstable than 2000 but we all know that.
Comment removed based on user account deletion
Very true, i was getting annoyed by frequent BSODs. They were random, seemed to pop up without warning and always at the wrong moment.
They've all gone away after my PSU blew and i replaced it with a decent one that didn't come with the case and weigh less than an empty cardboard box.
is add a Green Screen of Death. Then they'll be able to add together death colors to get much needed functionality for TrueColor Screens of Death.
now the links give a SSOD (Slashdotted screen of death)
Large image of the red screen mirrored:
g
http://www.goodgoing.org/slashmirror/redscreen.jp
...so this is absolutely nothing new! :-)
These posts express my own personal views, not those of my employer
Looks like that site has gotten a SSOD. Slashdot Screen of Death.
If you are seeing BSODs almost daily, you either have faulty hardware or some seriously buggy drivers. Honestly folks, XP, and even 2000, BSOD very rarely.
Exactly. I have never seen my XP machine at home BSOD, even when the video card was failing to the point that it was adding random horizontal lines across the display.
At work, I saw 2000 BSOD on several servers when we applied an MS hotfix that conflicted with some sort of secret kernel patch they'd given us a few years previously for those same machines.
I saw 2k bluescreen one other time, when a workstation had a zip drive and the user installed drivers for it from 1997 or so.
Other than that, the only time I've seen it happen is if I make an OS image on one machine and then try and use it on another with different hardware. That's still stupid, but at least I know how to avoid it.
This is in an environment with close to 1000 Windows servers and about 25,000 Windows workstations.
"...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
Maybe I'm dyslexic, but I count not one, but 2 errors. Is this the kind of panic we can expect from a Red Error screen? Spelling errors? We already have an internet full of kids who can't type LOLZ h4X0rz ROTFLMAO!!!!1111oneoneone I can forsee Microsoft patenting the RSOD and fighting Red Hat for the right to use the word "red".
One has to wonder how stable Longhorn is going to be when they decide they need a new color for their screw ups.
Always good to see M$ broadaning it's horizions. This time it took art class, and is successfully making it's way through the color wheel. Way to pass 2nd grade M$!!
Even drives laptops quite nicely.
I think what the OP means is that he did that tweak to change the SOD colour, perhaps to a pleasant, relaxing green?
Got time? Spend some of it coding or testing
Here, here! The (rare) times I got a BSOD in XP, I could pinpoint them back to some stupid tweak I did (normaly on the BIOS)...
"A sysadmin is a cross between a detective, a police officer, a gardener, a doctor and a fireman"
I see BSODs a lot, almost daily, on Windows XP.
Well, yeah. Evidently, some people lack the knowledge/skill to set up an XP box correctly.
And evidently some people can't grasp that it isn't supposed to require significant knowledge or skill to set it up correctly.
nice to know gifs have finally benn outlawed.
"Honestly folks, XP, and even 2000, BSOD very rarely."
That's exactly why I think this is strange. My Win2K installation has BSOD'd maybe three times in two years. So doesn't that mean any Screen of Death indicates a serious/exceptional error? Or are they planning on introducing more errors into Longhorn?
"Live as if you'll die tomorrow." Ridiculous. You could die later today.
Thank you for shopping with Microsoft(TM) the choice of a new generation
I second that. I rarely have blue screens if ever unless there is a problem with drivers or hardware.
I used an A8N-SLI motherboard and was getting a blue screen with, but I traced the problem to a bios update that conflicted with one of my hard drives. The orginial bios (1001) is fine and runs stable.
Outside of that issue, which was not the fualt of windows, I've hardly ever had a blue screen of death on XP or 2k for that matter.
In America we are imprisoned by our fear of them.
I really wonder if there was no other story that could've been published than the fact that the Windows error screen has changed its background color. Seriously.
Looks like his webserver just BSOD'd.
S-
At last, Microsoft come up with a panic screen that accurately reflects what many British users say when it pops up: "Argh, sod!"
this is more like linspire(lindows) "the imitator linux".
That's innovation for you!
Engineering is the art of compromise.
You brain dead moron. Microsoft takes advantage of the next generation directx 9 3d acceleration hardware available in all longhorn-supporting computers to blend the blue and red into a dark, rich purple using sophisticated algorithms, lighting effects, and large textures.
they ran outta blue...
bullshit, last time I checked it was very easy to get 2000 to BSD simply by running certain java programs (freenet comes to mind, dont remember which version it was though). it's not hardware either, i've done it on multiple boxes.
Who chose those colors? They should make it possible for the user to change them.
Cheers,
RoadkillBunny
In case you were wondering, we know this because we stole a prerelease copy of Longhorn at musketpoint.
Is it related to this:
http://www.bbc.co.uk/wales/rsod/
In the geek community blue screens are assumed to be hardware faults but in the general community I don't think this is the case. I'm wondering if the introduction of the RSOD is designed to blame hardware rather than MS.
I usually see XP BSOD if Linux does something to an NTFS file that it doesn't like or if I change the partition it sits on and on reboot from the BSOD, it runs chkdsk and then goes back to normal. Other than that, rarely.
If my grammar and spelling are off, I am [distracted/tired/careless] (take your pick)
Red screens are just too agressive. An error message already is very irritating, why the hell do we need it to be red ? I'd almost hate the Sarge installer because of that...
Good read though. =)
There! There!
Sorry, it looks like you are the dope this time. ;)
It takes a special kind of person to have a WinXP box that bluescreens 'almost daily'.
Thats because your computer by default automatically resets when it gets one.
However I must say the only time I've ever had one on XP was with some faulty ram. And even more impressive the knowledge base artical about the error message was correct in telling me I had bad ram.
I have a webcam that will crash XP every time I try to use it. Every single time. Doesn't work on Linux either. But Linux gives me a message which I can ignore, it doesn't crash!
At work, I saw 2000 BSOD on several servers when we applied an MS hotfix that conflicted with some sort of secret kernel patch they'd given us a few years previously for those same machines.
I saw 2k bluescreen one other time, when a workstation had a zip drive and the user installed drivers for it from 1997 or so.
For a while I had Win2k reproducibly bluescreening whenever I cared to. It was a laptop with a manufacturer install on Win2k, so we can presume drivers are not likely to be an issue, and the nature of it didn't imply any hardware issues.
In general Win2k was very solid for the time I was using it but I have had issues with it at times. I expect the problem I had got cleared up with the next service pack, but I wasn't using Win2k by then, so it wasn't of concern to me.
I have personally witnessed far more Win2k and XP Blue Screens than I have Linux or Solaris kernel panics (and I have seen all of the above at various times, and yes, hardware was the issue for at least some in each category).
Jedidiah.
Jedidiah.
Craft Beer Programming T-shirts
I'm sure they'll be promoting the "fewer BSODs!" thing in a big way, conveniently not mentioning the color change for some errors.
It's gonna be just like when they "reduced boot time" in XP; they just made the desktop and icons appear sooner than usual in the process, so it *looks* like it has booted faster. Meanwhile, the disk continues to thrash as more shit loads in the background, and the computer completely ignores user input until it's god damned good and ready to accept it. This is on a home-built Athlon XP 2600. While I'm ranting, I'd like to touch on the miserable perceived GUI responsiveness on Windows. The Athlon XP machine was thoroughly embarassed by my G4/733 in that department, and looks even more ridiculous in comparison to my dual G5/2.5.
this reminds of when Windows UAE's were finally addressed once and for all.
I wonder how long til I can get my RSOD t-shirt from ErrorWear I already got my "Bad Command or File name" shirt.
So, BSODs and RSODs...one thing's for certain, the server admin is probably seeing one of these right about now!
Ah.... I see that you are familiar with ATI's Catalyst drivers* then. Either that, or VIA's Hyperion drivers*. :-)
* Disclaimer: I use the term "drivers" very loosely.
Bullshit. I do tech support for your shitty operating system and it blue screens quite regularly. Stop the god damn astroturfing on Slashdot you Microsoft stooges.
Why, oh why, didn't I take the blue screen?
blog
But it's good to see Microsoft puts so much effort in their errors. If we have to look at them all the time, they might as well be colored.
Bored? Browse Slashdot with a +6 modifier for Troll comme
that is all I can say.
I guess this will firmly put to rest the claims that MS is not a source of cutting edge innovation.
An RSOD, that is the kind of forward thinking genius that makes America great!
I sure hope they patented it and will fight tooth and nail the sure to come attempts by lesser european, californian, etc. OSs to copy this great leap forward in interface design.
Don't forget that the default behavoir in XP is to automatically restart instead of showing the BSOD. My Computer Properties > Advanced > Startup and Recovery Setting, under system failure automatically restart is checked by default. So that's the main reason you don't see them as often. Although I have only ever seen one when I had some faulty RAM installed in my system.
Rimmer: Step up to red alert! Kryten: Sir, are you absolutely sure? It does mean changing the bulb.
I see that Microsoft remains reluctant to provide any information on their error screens that might help an average user understand what went wrong. Color me unimpressed.
Since Joe Sixpack can't set it up reliably, XP is not ready for the desktop. Simple! Thanks for that insight!
Got time? Spend some of it coding or testing
We should be criticising the spelling in your post instead. Oh, and if you're a Yank, that's "criticizing".
Got time? Spend some of it coding or testing
...that Asian languages and RTL suppoort will work properly for the first time in Shorthorn Office?
Got time? Spend some of it coding or testing
Why would you spend so much time changing the color of an error screen that, if your computer is config'd properly, will never appear?
My other Sig is
That would make sense, except I don't see XP reboot like that either.
"...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
You mean restart AFTER showing it. It's still clearly visible, if only for a few seconds.
I've been testing Longhorn on two different PCs for about a week by now and on both I am getting in average one BSOD every other hour which is really annoying and at least 3-4 RSODs a day!
I get the feeling that Microsoft is again trying to downplay some severe problems they are having with their code base. In terms of overall impression I am very disappointed with Longhorn to say the least, especially with the issue of stability.
xbox has a green screen of death already....
...anything that causes you to install Linux on the machine.
Got time? Spend some of it coding or testing
1. Indoctrinate the children.
...
2. Warn parents of danger of children being indoctrinated.
3. Offer beta anti-indoctrination software as free download.
4. Profit!
Are they just trying to make Longhorn more appealing to Chinese officials?
Anyone else remember how Microsoft claimed that Windows 3.1 was better than Windows 3.0 because it did away with the dreaded "Unexpected Application Error" (UAE)? All the same errors typically occured -- it was just that Microsoft had renamed the error from "Unexpected Application Error" to "General Protection Fault" (GPF).
Unfortunately, now just as then PHB's fall for it.
Yaz.
"I don't know what scares me more - lost nuclear weapons or that it happens so often you have a name for it."
Got time? Spend some of it coding or testing
I wonder if they'll patent it?
You can find a ROSD screenshot in a virtual machine in his weblog entry.
(If you happened to see this story within the first 5 seconds of being posted).
https://www.eff.org/https-everywhere
uh, ok. maybe if you are running pre-sp1 windows xp.
yeah, like Dell.
Stop using broken hardware and unpatched software.
Microsoft are reverse engineering AI from the future!
Yea, I agree with others that the BSODs don't happen near as much as they did on 2K which had them much less than NT, never used 95-ME at home.
That said, XP is way crashier than 10.3-10.4 are.
How the hell do you expect to get a warning before your kernel crashes?
"WARNING: Your kernel will crash in ten seconds. Owing to the very nature of the event, there is nothing you can do about it."
there's more than one way to do me.
Edit your system.ini file as follows:
Under the [386Enh] header, add these two lines:
MessageTextColor=B
MessageBackColor=3
That will give you a bright cyan text on dark cyan background screen of death. Feel free to substitute other colors 0-F as desired. This works in 95, 98, and Me, at least. Red's in there somewhere - don't remember exactly where - just try a pair of values, wait the usual 15 minutes for a SOD, and see if you like the combination. I can honestly say I haven't seen a BSOD on my screen in months.
Who is John Cabal?
Wow! I'm going to change my applications to have the question icon on yes/no boxes to exclaimation and repackage it- I'll make millions :)
First off, why is this news? Why is this worthy of Slashdot? Microsoft creates new error message screen *gasp*. Microsoft changes colour of text-only screen *gasp*. Who cares!
So a list of error codes now has a new colour- yippie.
-M
when you see the word 'Linux', drink!
I've used the Catalyst drivers with every new version since christ.. 03 and not had a single BSOD. More than likely it's the Hyperion drivers
cheese logs keep my wang warm at night.
So there's actually a lot of BSODs that are 'preventative' in nature. That is, the kernel says "uh oh, that call should never have been made, the system *might* become unstable, shut it *all* down before any real damage is done".
Then there's "Boot disk not found", or "Boot disk failure", which are in fact real serious, because it's the end of the line for the machine.
Maybe they've broken down errors that are likely Kernel driver programming mistakes, and errors that indicate the system is severely damaged.
As a server administrator I'm now looking forward to the days when we get delivered the Rainbow Screen Of Death which will give the double effect of; - Letting you know that absolutely positively NOTHING went right. - Showing you a pretty image that may, if just for a second, distract you from how horrible your life is about to become.
Red vs. Blue
Longhorn: Vaporware which now contains fewer instances of the Blue Screen of Death.
Did they file for a patent yet?
I have seen Windows XP BSOD for friends using video editors like Adobe Premiere. I still run the copy of Win2K I got back around the week it first came out. I have had 3 BSODs on it, from when I was trying to install a combo Video Input/Motion JPEG Encoder/SCSI port PCI card using outdated drivers. Other then that, it has had no problems despite how much I have abused it. Honestly, the only people I know that still talk about BSOD are Mac users that haven't touched a PC since Win95.
1 (short ton / firkin) = 89.1432354 slugs / keg
-AT
Working in a DevOps shop is like playing in a band made up entirely of keytarists.
For those ludacris errors
Life is not for the lazy.
Red has been now more or less been programmed into us to mean "something bad", which is probably the reason for the red screen.
:)
My comment is that a good portion of the population (especially males) is colour blind and can't tell colours properly (or at the very least shades of many colours).
Did the UI designers take this into account or did they simply choose it because in Western culture it means "stop" or "status bad"? It should be noted that some cultures (e.g. Chinese) view red differently. Anyone know if any of these factors played a role in the decision of the colour?
P.S. I'm Canadian so that's why I spell it with a 'u'.
It takes a special kind of person to have a WinXP box that bluescreens 'almost daily'.
No, it doesn't. I've watched XP BSoD first boot after express install, and first boot after the application of SP2 right after that, on a brand new PC owned and operated by a local computer store owner. He then tried a custom install with the same results. He is an MCSE, CCIE and Compaq Master ASE. It took him two days on the phone with Microsoft and assorted manufacturer support techs to get it sorted out. You don't have to do anything wrong or special to experience the same, just have the misfortune of discovering a problematic combination of drivers. And no, there is NO OS for PCs that doesn't bring with it the chance to experience something similar.
I wonder how long it'll be before Miguel de Icaza decides that this new RSOD is a True Microsoft Innovation (tm) and that Linux *must* have something like this in order to be competitive?
If your drivers are good, and your hardware is good, you shouldn't be getting bluescreens.
Really I have got less then 10 in the past 4 years of using XP. Do the rest of you readers still get them all the time or is the BSOD just some old issue people refuse to let go even tohugh it's all but dead?
So now, instead of seeing the blue screen, representing a slight hope of recovering anything I was working on, I'm going to see a red one, which means that I'm now completely out of luck.
"Windows Loghorn will present you less BSOD. Joi Ito reports that Windows Longorn will get additional ROSD (red screen of death) for 'really bad errors.' So you will get less BSOD but some new RSOD. You can find a ROSD screenshot in a virtual machine in his weblog entry."
Am I the only one bothered by the weird acronymming going on in the post? That's just weird.
Direct away from face when opening.
They're called a "Comp Lusa" costomer ;)
;) ah well.. the board Does overclock pretty good ;) well as good as it runs non-overclocked anyways...
Seriously though those cheap $500 systems from worst buy, comp lusa, circuit shitty etc.. will BSOD daily if you re-enable blue screens. the ram, or the psu, or the dvd-burner will cause most of them, usually when the dvd-burner can't draw enough power from the 230 watt psu they've got in there it'll cause a nice solid blue screen. sometimes it'll go away, but hey... you only paid $500 for the pos craputer... and it came with monitor printer, etc etc..
But it's not restricted to complusa users, sadly I have a board from asus thats total crap, and will kernel panic linux in about 4 hours (less if you run gimp filters the whole time) and bsods windows if you try to game on it... *sigh* buying a computer without researching it is just plain stupid. I read 2 stupid review sites that take bribes and call that 'research enough' and get suckered into the crappiest motherboard purchase ever
https://www.gnu.org/philosophy/free-sw.html
Lotus Notes has been giving a red pop-up box on killer errors since 4.x (1999 or earlier), maybe longer.
Other than that, the only time I've seen it happen is if I make an OS image on one machine and then try and use it on another with different hardware. That's still stupid, but at least I know how to avoid it.
:-)
I don't really consider that "stupid". I've moved my Linux install through several motherboards, the most I've had to do was occasionally install a new kernel or driver. (Like when I moved to ATA/100).
Yet Windows has had problems moving between motherboards for years now... it seems like it's just an accepted thing that you have to fully re-install for it.
It's a motherboard, not a bloody processor architecture!
I dunno, I guess I got too sick of reinstalls (both at home, and supporting ~250 machines with 8 different images
I've seen XP go and BSOD on several people. The common culprit is either a failing harddrive, or crappy RAM. Not much other than those hardware problems, and some spyware/virus infections.
Having it happen daily? That's a whole different thing. You'd think that the user would try to track it down and fix it, rather than having it bluescreen 'almost daily'.
Now I had win XP running on them and did see a BSOD once. Before that Win 98 Id get once every few months.
I will say though Windows ME is a piece of shit that everyoen should return to MS for a refund. How anyone could sell shuch a shitty product and get away with it is beyond me.
http://www.anologger.com/PS2 DESIGN RIP OFF _ LONG LIVE ATARI
by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
I remember when Windows 3.0 crashed, you would get a 'UAE', which I think stood for Unrecoverable Application Error. Then it changed to GPF (General Protetion Fault) in Windows 3.1. Windows 95 started the BSOD ("A fatal exception xx has occurred at ..."), and now we're getting RSODs.
On another note, Windows 2000 and XP are fairly stable. I don't remember the last time I had a BSOD on my home machine. You're really unlikely to see one unless you get a bad driver or bad hardware.
I sometimes see the windows UI "reboot" itself if it has problems. Still a sign that there are problems, but at least I can continue working. And sometimes an application locks up and I can't exit it or get back to windows. Pushing the power button does nothing, so I have to hold it down until I get a reboot (or hit reset).
Linux seems to have roughly the same stability as Windows now. I've had X lock up on me, and that would have forced a reboot if I couldn't SSH in to kill it. But the base operating system almost never crashes (it has happend a couple of times, but very rare).
Operating system stability is very good now. My major concern now is security, and also application stability.
http://toastytech.com/news/bsod.html
Wh47 d1d j00 541, 31337 15n't t3h r0xor5 ne m0r3???
The Sun reps said that we are one of their few customers running 64-bit Linux because it isn't stable enough.
The vendor amd64 distros aren't great yet, which I guess you're using, however very good results are being had with debian (alioth) and gentoo amd64.
This doesn't mean amd64 linux is 'unstable'.
Malike Bamiyi wanted my assistance.
I see BSODs a lot, almost daily, on Windows XP.
Why was this modded redundant? Seriously. Back in 2003 I was working on my thesis. I developed a small simulation program, based on a previous student's work, in Linux and FreeBSD and used mingw32 cross-compile to tools to make windows binaries from within Linux. However, as part of my data collection, I needed to performance test in Windows.
I went to the software support folks at school and checked out the following CDs: Windows XP, Office XP (needed to test the earlier version of the simulation from before I ported it), and Visual Studio.NET 2003.
Here is what I did:
To answer the questions that will surely come:
I could never figure why it did that. I eventually used VS.NET on a lab machine to turn my code into a VS project and brought that over to my machine. For some reason, VS didn't choke if I opened the files from within the project.
Today Microsoft is pleased to announce the addition of two new products to our Windows stable:
Windows Loghorn [sic], with patented new Reduced BSOD features. Increase your total return per BSOD with Windows Loghorn today.
Windows Longorn [sic] sports additional ROSD [sic] (red screen of death) Transposition Engines (pat. pending.) With the expansion of auto-correct functionality to system critical events the TCO is even lower. Upgrade your Windows today.
Seriously though guys. How hard is it to spend 30 seconds reading your own typing?!
Patent litigation: A doctrine of Mutually Assured Destruction... in which everyone seems willing to push the button
Microsoft should add a new button to the extended keyboard. This button would dismiss any Screen Of Death that occurs.
I propose that this be named the "SOD Off" button.
Joi Ito's blog clearly mentions that Microsoft's Michael Kaplan posted the information first. So, why does the post say "Joi Ito reports..."?
take the blue pill!
"The world is a construct of forceful imagination. Those who don't know walk around in the reailties of those who do"
you can have an E for effort. Unfortunately for you, XP still shows the bluescreen BEFORE it reboots. So unless you aren't at the computer when it BSOD's, you'll still see it. Next.
And M$ says OSS is communist, what a bunch of hippocrites!
Check journal for info on Anti-TextBook, an idea by me.
Another replier here suggested green, so maybe the colour on my TV is off. I had the Splinter Cell Chaos Theory demo on an OXM disc, and sometimes it would crash during a quicksave: the screen would flicker, then finally just show solid cyan and I would have to reboot. Take that as an anecdote or a joke--in any case, the MS guy was right, from a certain point of view.
I read Slashdot for the articles.
Actually, you can't even presume that. Some manufacturers are especially good at writing drivers that suck, so it's entirely possible that they could ship a laptop with dodgy drivers. The other problem is that a lot of the drivers they ship with aren't written by them - I'm working on an HP laptop with an HP build (stupid) that has Intel, Synaptics & Realtek drivers...
If MS wants to REALLY spice things up, they need a color scheme for "BSOD". Red=really really bad Yellow=really bad Blue=bad etc...
Actually a friend of mine who knows so much about doing weird things with Windows it's scary, has moved his WinXP install across multiple motherboards with different chipsets (via, sis, nForce and Intel). He wrote a small tutorial with lots of pictures on how to do it and it's not exactly hard - I don't know the link off-hand.
It's all in the preparation, if you don't install Generic IDE/Chipset drivers (Windows is smart enough to use the correct drivers without requiring the generic ones when it installs) Windows can't read from the HDD and obviously fails to boot. Just like if you removed Generic IDE chipset support from your Kernel and tried to boot it on another system it would most likely fail.
Way ahead of you, Microsoft. Change The BSoD color If your error crashes my computer, I'm not going to care if it was a "red" level of severity or a "blue" level of severity. I already know it was severe enough to crash my computer.
Or you have malware such as a trojan horse or virus that is crashing your system.
I am curious... Did that same computer also freeze or cause kernel panics when Linux was run on it?
Clearly he's using SPARC, unless he has 100 brand new machines, in which case he probably would have mentioned the amd64 architecture.
Microsoft isn't helping the user out any. It still doesn't mean anything to them. People have asked me what the BSOD means to the average person. Instead of intimidating the user, Microsoft could at least try to give the user a sense of confidence and hope.
How do you not set it up correctly? You hit the install button! Then accept the agreement, giving your firstborn to MS.
//Changed screen color from 0x0000ff to 0xff0000
int screen_color = 0xff0000
It's good to use your head, but not as a battering ram.
Buggy drivers? Windows? Two great tastes that go great together!
So, what, you don't sleep? You're in front of your system 24/7/365?
I've used the Catalyst drivers with every new version since christ.. 03 and not had a single BSOD. More than likely it's the Hyperion drivers
Hmmm.... methinks maybe you should read rage3d.com or alt.comp.periphs.videocards.ati sometime.
Him:
I see Linux crash on our cluster of 100 Sun Opteron boxes daily.
You:
Clearly he's using SPARC
You fail it. YHL. HAND.
I have apps running on my machine that don't start automatically. If the system reboots, they won't be running.
Also, I don't have my machine set to automatically log on, so I would be looking at a logon prompt if it had bounced.
"...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
This also works on windows 3.x
I was saying that it's stupid that *Windows* can't handle being moved across different hardware =P.
"...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
I have been running Linux for over two years now and I didn't remember what a BSOD was.
Then I remembered that if I got to that place in a Linux box I could allways ssh over to it and fix it like that, unlike Windows.
MS Windows is crap.
What an odd question from someone on /. to ask...
kurzweil_freak
5th Kyu Genbukan Ninpo/KJJR student
Be the darkness that allows the light to shine.
I got BSODs daily for months. They started when I tried Win2k and then continued when I got WinXP Pro. I got them so often I considered going back to Win98 SE. Then, I changed my RAM from the cheap stuff (PNY) to the good stuff (Kingston) based on the error message I was receiving. The BSODs stopped immediately. I haven't seen a BSOD in over a year.
Please don't humanize the morons around me. It makes me very uncomfortable.
me thinks a lot of their problems are due to other hardware and illconcieved game code. I know for the longest time until it was patched far cry would lock up after 2 hours of playing and it wasn't the video cards fault
cheese logs keep my wang warm at night.
When Apple offered iMacs in five different color choices way back in 1999, some said that Microsoft, as usual, would copy the Macintosh and offer the Blue Screen of Death in five different shades.
Honestly, no kidding, I thought it was a joke. This arrives years later, and the feature set originally envisioned has been substantially scaled back, so I know this story is true.
When all you have is an axe, everything looks like a grindstone.
Note to the artist, it would have been better to take a real BSOD screenshot, change it to indexed color and edit your palette to replace blue with red. You wouldn't have had to spell anything. :-)
This is not an illusion, a rip-off, or a ninja technique!
Hey,I've got xp sp2 and it goes tits up a LOT more often than Win2k.XP-Twice a week,2K-once in four years.I've even tried running the programs on both machines.2K=great xp=very pretty fall down and go BOOM!If i could find a stupid usb 2.0 driver for my game toater I'd dump xp in a heartbeat,But unfortunatly my MOBO only has the drivers for Win98 and xp.Talk about your lousy choices.
ACs don't waste your time replying, your posts are never seen by me.
goong hay fat choy, or shing nian quia le, or chuc mun nam moi! 365 days a year!
You think MS marketing is tying this in with the xbox 360 launch?
Did anyone else notice that the reason for this Red Screen of Death is "An error occurred transferring exectuion"??
'Exectuion' must be a new feature in Longhorn, hence it's instability.
That's because the low-level graphics libraries that display text blindly "slide" the contents of the framebuffer down to simulate text scrolling.
Probably use the same techniques Sun does... there is no "text mode" like on a PC. The BIOS just simulates a console on top of your framebuffer.
You'll get the same thing on a Sun if you do STOP+A or ctrl-break while X is running... you get the "console" text pushing up the GUI with a ok> prompt...
Bleh I'm babbling... sorry.
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
Actually, it isn't in the registry, it's in system.ini. I haven't been able to verify whether this works, as the computer I'm on hasn't had a BSOD since I got it. I take good care of it.
warning: This post is likely to contain gobs of dripping sarcasm. Consume at your own risk.
Does the the red make it crash faster, as we all no red is the fastest colour
A good effort, but you'll need to change your username to something a bit more subtle (ie not "JW Troll". Change your homepage as well, and you have a bright future of snaring zealots ahead of you.
I was really not liking SLES. Lots of weird problems.
RHEL was much nicer...
(I'm bringing this up because I'm thinking of getting some V4xzs but I wanted to know about people's experiences with them)
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
What you're thinking about is that option under system properties that makes the machine automatically reboot if it blue screens (they only way you can tell it happened is if you check the system log)
Restarting explorer is a seperate thing altogether. This has been possible in all the NTs.
It happens when explorer gets messed up for whatever reason (usually due to some kind of built-in behavior and removable media... unavailable network shares, etc.)
Since explorer drives most of the interface, it is designed to start if no existing copy is running. In Windows 95 and 98, it was also possible, BUT, generally speaking explorer dying was just a side-effect of a larger problem that would ultimately take down the whole system. In 95/98, a user-space issue could easily become a system issue.
But that is not the same thing as a BSOD. In Windows NT, a BSOD is strictly a system-level issue, explorer dying is a just a problem with explorer.
They are almost always not connected.
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
wouldnt that actually be RSOD and not ROSD?
That sounds like a really bad webcam. :-)
If it crashes XP with a BSOD, that's because it use a device driver requesting hardware access on Windows.
"Some of us leave our machines always logged on, or 'locked'. I'd know real fast if it automatically rebooted and I was at a fresh login screen."
Heh.
"Welp, I'm done for the next 30 minutes. I'd better close all my windows and get it back to the 'freshly loaded' state so it's nice and clean when I come back after lunch!"
"Derp de derp."
Nah. I have been through two Radeons (one a made-by-ATI and the other a powered-by-ATI), and although the hardware was excellent, the drivers do indeed suck. Lets not even mention the Linux drivers, alright? The Windows TV Tuner drivers for my made-by-ATI 8500DV and the MMC have been shocking. Finding a working combination is like trying to guess the secret handshake or something. Actually, the first time I installed the drivers from the CD that came with the card, it completely killed my OS requiring a complete reinstall of Windows98SE. Couldn't even boot into Safe mode. Upon the first boot attempt explorer.exe couldn't even load due to .dll issues. Couldn't repair manually by extracting original .dll files from the Windows cab files. Things were truly screwed. A reinstall and installation of newer drivers sorted that.
The current Catalyst release (5.4) is being avoided by many due to numerous introduced bugs. Many are using much older drivers for stability and frame-rates. I upgraded to XP hoping that the driver quality would be better, but it is not. The latest XP drivers actually killed the TV tuner on my card. Had to revert to an earlier driver combo to restore TV function. This is the last time I will buy an ATI card. I never had such problems with NVidia Detonators. My whole ATI experience has left a nasty taste in my mouth.
Last time I saw BSOD on my WinXP, it was an optical mouse driver that works with every version but Service Pack 2. It was quite funny because the driver that crashed WinXP2 was obtained through Windows Update. The generic one that came with WinXP by default was fine, as I found out.
I used to think that SP2 suppose to be more stable and would disable that faulty driver instead of BSOD.
Red state = really bad state? I always knew Alabama sucked.
Also, the driver can be either unsigned (means the driver hasn't been tested by Microsoft) or a customized version (since laptop manufacturers tweak the hardware and driver to fit their laptops' designs).
So if I follow the logic if a BSOD is a 'guarded' error and a RSOD is a 'severe' error then a green SOD is a 'low' error, a yellow SOD is an 'elevated' error, and an orange SOD is a 'high' error.
http://www.epic.org/graphics/threat_levels.gif
Oh hell, I can't remember if we're talking about windows errors or terrorist threats. Though, TBH, there are probably times when they are one and the same.
Personally, I've seen Windows (NT & 9x family) BSOD, Linux kernel panic, Mac OS 9 and X system crash (at a point that the mouse cursor does not even response) on several machines for each. I have, however, yet to see a single Sun UltraSparc that runs Solaris 2 crashes. Even though Sun manufactures UltraSparc themselves, it is still amazing that it has a stability that not even the Apple machines can compare to.
Microsoft cannot use magenta in this product, because the german Telecom (T-online, T-mobile, T-whatever) has trademarket, copyrighted and likely patented the use of magenta in the Information Technology sector.
(This is true in Germany, but I think they pushed this thing world wide)
we need an "-1 Plain wrong" moderation option!
Red screens of death will be what in the *nix world are called "panics". These are the kinds of errors that the system was not expecting and that there is no way of possbily recovering from.
* Bad memory/parity/bus error in a kernel page
* NULL pointer access in file system or security-related code
* Hard disk/controller dies during paging
* Double faults
Blue screens of death are the ones where the system is still "up" but it can't continue safely (either you decided with a setting, a driver made a choice, or the OS decided for you). These are more like "oops" in the linux kernel.
* Audit logs / disks full
* watchdog timers
* Bad memory in user space
* System/boot drive died
* Other faults unhandled by drivers or an application
Blue errors are errors of circumstances that you could probably fix and reboot. Red errors are the ones you can't do much about. Red errors are probably microsoft's job to fix... or due to an unrecoverable hardware error. Maybe a reboot and it goes away...
Or it could be something simple like "Red" means it was an "unhandled exception" (interrupt context/unhandled exception from userspace) and "Blue" means it was called explictly by the kernel itself.
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
http://www.computerhope.com/jargon/a/acpi.htm
I believe the redscreen code is turned off in release builds, meaning you are not likely to see one.
This posting is provided "AS IS" with no warranties, and confers no rights.
Perhaps tampon and maxi pad companies should follow suit with Microsoft. I would expect to see commercials where someone pours red liquid onto a maxi pad now to show severe...discharge.
I'll leave that to the imagination before I vomit.
You're hitting that twice, which caused the speaker to go in then back out again. Best results with LDA, only hits it once.
'Lessin you were trying for some poly-symphonic thing. :)
If you misspell the error messages differently in each possible error source, then grep will find your bug instantly :-)
I was also seeing not BSODs but spontaneous reboots with XP - one moment you're using it and the next you're looking at the POST screen and the memory is counting up... no warning whatsoever!
Admittedly I picked up the PC off some guys who were putting it out for the trash (when I got it home it was BSOD on boot), but since changing to Linux I've not had any instability issues whatsoever (it's my webserver and guest Internet terminal, running a full desktop Ubuntu with Gnome, in fact).
I put the Windows probs down to some minor mainboard fault or a Win32 driver issue (Windows 2000 did the same thing).
In order to be flexible across multiple architectures NT (and thus XP) has what is called a HAL (hardware abstraction layer). It loads a different HAL for different processor types.
So if you swap out the hardware underneath it you will need to do a repair install to get it to load the proper HAL.
you turn red when angry;
you are dead when you turn blue.
is this a fake or are the longhorn kernel developers unable to spell ??? whoaa man. microsoft engineers really are shit... news at 11.
Maybe he skipped the firstborn part.
I've been seeing a lot less BSOD's in general since using 2K and XP.
In Windows 98, I would run the comptuer for a few days, and for no reason it would just start being slow and throwing random BSOD's at me.
Since using 2K and XP, I've seen a few recently, but they're all realated to a piece of faulty hardware that I've been too lazy to replace. Other than that, I can't reacall seeing a single BSOD in years on a computer of my own.
I'm honestly asking people. Have you run into BSOD's that really truely was 2000's/XP's fault instead of being some sort of hardware fuckup?
I'm the guy with the unpopular opinion
So, Win2k destroyed your RAM?
Maybe next Microsoft will introduce the Phlegm SOD for the users who screw up Windows badly.
If you're reading this, stop it.
what bullshit. its more about the Activation failing.. and that is a FEATURE .. remember. so lemme get this right XP keeps about 1.5 gig of system restore crap and cab files for every driver etc.. but you have to DO have to do a reinstall to get it to boot on another mobo.. windows is SHIT. figure it out.
What Ziviyr (95582) is referring to, are errors even worse than the Guru Meditation (software failure).
Certain hardware errors would turn the screen into one single color like red, yellow and green.
Red : ROM Error - Reseat or replace
Green : CHIP RAM error (reset AGNUS and re-test)
Blue : Custom Chip(s) Error
Yellow : 68000 detected error before software trapped it (GURU)
Black : No CPU
Amiga System Startup Colours
Personally, I've seen a lot of red screens on an Amiga 600 that I sent in for replacement. I've seen the yellow screen a couple of times, and I think I might have seen the green one. I've never seen an Amiga blue-screen or black-screen.
I did see the Guru Meditation (later renamed Software Failure) many times, and its less serious brother, the "Recoverable Alert" -- a Guru Meditation with yellow text and frame on black background that you could just click away to let the program continue.
In the new Amiga OS4, the crash handler is called the "Grim Reaper" and comes with several functions for debugging, as well as choices to kill the offending application, contiue running, or rebooting the system.
Irene KHAAAAAAN!
This is your last chance. After this, there is no turning back. You look at the blue screen - the story ends, you wake up in your bed and believe whatever you want to believe. You look at the red screen - you stay in Wonderland and I show you how deep the system-error goes.
"We immediately recognized this as a great opportunity for ourselves, our channel partners, and especially our customers," explained the excited Ballmer to a room full of reporters. Immense video displays were used to show images of the new customizable BSOD screen side-by-side with the older static version. Users can select from a collection of "BSOD Themes," allowing them to instead have a Mauve Screen of Death or even a Paisley Screen of Death. Graphics and multimedia content can now be incorporated into the screen, making the BSOD the perfect conduit for delivering product information and entertainment to Windows users.
The BSOD is by far the most recognized feature of the Windows operating system, and as a result, Microsoft has historically insisted on total control over its look and feel. This recent departure from that policy reflects Microsoft's recognition of the Windows desktop itself as the "ultimate information portal." By default, the new BSOD will be configured to show a random selection of Microsoft product information whenever the system crashes. Microsoft channel partners can negotiate with Microsoft for the right to customize the BSOD on systems they ship. Major computer resellers such as Compaq, Gateway, and Dell are already lining up for premier placement on the new and improved BSOD.
Ballmer concluded by getting a dig in against the Open Source community. "This just goes to show that Microsoft continues to innovate at a much faster pace than open source. I have yet to see any evidence that Linux even has a BSOD, let alone a customizable one."
(Copied from here.
Buggy drivers is a lovely one, cos on windows, that usually means new hardware. I had this for a long time, a Win XP box that was doing NAT at my house used to BSOD on a daily basis because of faulty ADSL modem drivers - and the manufacturer refused to release new ones. In the end, I gave up, and put the machine on FC2, with the drivers made by the great guys over at http://www.eciadsl.flashtux.org/. Since then it has been online for (checks) 142 days.
"Those who cast the votes decide nothing; those who count the votes decide everything." (attrib. Joseph Stalin)
EXECTUION?!?!?
Does anybody need better proof that astronomy does matter in our everyday lives? :-))
Regards,
W.
now i can look forward to staring at a red screen of death on my way to college on the bus (they have adverts playing on screens) about half of all the buses have BSOD on there screens not even 9x ones they run on 2k.
I've heard it said that the original BSOD, in the early days of Windows, was in fact red - however, the marketing people asked that it be toned down so as not to alarm people "unnecessarily". Can anyone substantiate this?
You installed a buggy device driver somewhere along the way. Simple as that.
I run a network of aseveral hundred Windows boxes (a mix of 2k and XP) and I see maybe 2 or 3 bugchecks a year. Every one is failing hardware or device driver related.
They just don't happen daily unless you really have no clue.
I don't know if anyone else used this, but there was a hack that would let you change the colour of the BSOD to any colour you wanted.
Pop Quiz: how many lines of code do you recon M$ took to add the RSOD?
a) upto 5 lines
b) upto 50,000 lines
c) upto 500,000 lines
or
d) one reeeeeaaaaaaaaallllllyyyyyy long line.
In the not too distant future, next Sunday A.D.
If that one's still trademarked, call it Extremely Evil Exception Error.
Yeah, thats /.
"Sure there's porn and piracy on the Web but there's probably a downside too."
SP2 . 2k is rock solid, xp is bolloxed on NTFS, TCPIP stack and HTTP
or even abbreviate? how is a "ROSD" a red screen of death?
yesterday we had a "summery" for god's sake. so much for the us tech industry; i'm glad i live in a civilised and cultured (read: european) country.
Oh, you can actually do that with windows nowadays, leave it always on?
Last time I checked it would gradually slow down to a crawl (can admittedly take a week or two) and eventually behave really funny - like certain folders just won't open anymore or networking stops working.
I think this is a good step for MS. I mean, for ten years I've been wondering why is that the worst error possible is featured in a screen that has the company's colors! Now they simply go red and no harm done.
However, I would've done it brown, since:
1) Doesn't change the BSOD acronym;
2) Brown's a color that reflects so much what I'm thinking about when the error screens happen.
Course, I don't use Windows anymore. But my customers do.
The BSOD color on '9x is just a matter of tweaking a couple of ini entries. Heck, I wrote a program to do it.. years ago!
Windows Longhorn Getting one step closer to offering what they promised us in Windows 95.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Did it take 15 years to get it back!?
What the heck? i thought bill wasnt for gay rights? why is he putting the rainbow symbol in his work then?
I've yet to get a BSOD on XP Pro at work or at home.
I'm surprised that Brand Management (or whatever marketing folks handle that for them) are letting them get rid of such a well-known icon of Windows. ;-)
Maybe you should have tried it since the windows 9x series.
no matter what pretty colour it is a screen of death is exactly that ... it's dead or it's deader ? red is for serious dead ?
Question Authority before IT questions You
Yeah, I guess after his we can expect a pitch black screen with a loud WAV file of a beating heart. Or maybe the "X" mechanical fart sound from the Family Feud.
So, I downloaded the Sysinternals BSOD screen saver (emulates a BSOD). I remember thinking that it didn't work, because I had tried it before and some error I don't remember occurred. I tried it again, and, sure enough. My PC BSOD'ed. I was like, wtf, how can a screensaver BSOD, it's not like it needs access to low-level hardware or anything. I sigh and reset the PC. While it was rebooting, a peculiar thought started forming in my mind. My... BSOD... screen saver... BSOD'ed... I can't believe I didn't think of that earlier. Next time I ran it I just pressed a key and it went back to windows :P
Send email from the afterlife! Write your e-will at Dead Man's Switch.
Windows Longorn will get additional ROSD
What is Red of Screen Death, blood?
Tiller's Rule: Never use a word in written form that you've only heard and never read. You will end up looking foolish.
i wouldn't be discouraged by that if i was you, try another distro that doesn't suck balls. (k)ubuntu is quite a nice distro, just install webmin (apt-get install webmin) and youve got a replacement for mandrakes *drake tools (diskdrake, etc)
Windows "Loghorn"?
C'mon editors, this is just getting ridiculous...
Read my blog.
Either this is a hoax or Microsoft outsources all of its error-message programming to South Asia. Not only is "exectuion" misspelled, but there is an inappropriate comma after the word "please" at the end of the last line. It looks hoaxy.
I refuse to believe that such a malevolent thing as giving a BSOD followed by immediately rebooting to be a feature. Something so maniacal could only be a bug of the worst kind.
S OD->restart->ad infinitum, all without user intervention!
Does this setting really affect the BSOD->reboot problem? Does anybody know where in the registry this is hiding? On the computers I work on, I don't really have a good chance to turn that off before the problem occurs (but I have found an off-line registry editor). There is little worse than getting a machine that boots->BSOD->restart->boot->BSOD-restart->boot->B
I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
I have used XP for 2 years now (job, not at home) and I have only seen a couple BSODs on it. HOWEVER, I don't think that the OS is that much more stable than 2k. I still get lockups, massive slow-downs, and unresponsiveness. In fact, I think I get them more in XP than in 2k. XP does weirder things. Does it matter that there is not a BSOD if I have to reset the machine and lose my work anyway? That happens. In my opinion, XP is not more stable than 2k. Microsoft are a bunch of dopes. Windows 2000 was widely regarded as "pretty darn good" even by the Linux crowd. So instead of improving on it by making it more secure and stable, they come out with XP. I don't get it. It's like putting a new gaudy paint job on a reasonably well-running car, and all of a sudden it starts misfiring and stalling.
My beliefs do not require that you agree with them.
When you are the admin of 1000 servers and 25,000 desktops, how often are you "at the computer"?
i like the "SPACE=CONTINUE" message on the bottom of the screen. What would the point of continuing be at this point? in that screenshoot, it looks like the bootloader failed. So I'm guessing that continue really means reboot, because from that point, there's not really anything else you can do.
talk about cryptic. this must be from the same guy who brought us "keyboard missing. hit f1 to continue." i hate to tell you guys, but it's not the 1980's anymore. you can be a little more descriptive with your error messages.
If I don't put anything here, will anyone recognize me anymore?
The jarring nature of a RSOD means customers will be more upset and more unhappy if one happens.
MS is gambling that there will be fewer such events because of more careful combing through the code.
I have to give them credit for doing something which they almost never do anymore - putting their neck on the block and sticking up for their product's quality in a meaningful way.
Making the developers man the 1-800 lines the first month after release would be another incentive...
"Provided by the management for your protection."
He said motherboard. Not CPU type. Not architecture. Motherboard. It has jack to do with the HAL.
--grendel drago
Laws do not persuade just because they threaten. --Seneca
The BSOD is by far the most recognized feature of the Windows operating system, and as a result, Microsoft has historically insisted on total control over its look and feel. This recent departure from that policy reflects Microsoft's recognition of the Windows desktop itself as the "ultimate information portal." By default, the new BSOD will be configured to show a random selection of Microsoft product information whenever the system crashes. Microsoft channel partners can negotiate with Microsoft for the right to customize the BSOD on systems they ship.
Major computer resellers such as Compaq, Gateway, and Dell are already lining up for premier placement on the new and improved BSOD. Ballmer concluded by getting a dig in against the Open Source community. "This just goes to show that Microsoft continues to innovate at a much faster pace than open source. I have yet to see any evidence that Linux even has a BSOD, let alone a customizable one."
http://teach.fcps.net/tips/March/NetworkDown.htm
There is much cruelty in the universe, John.
Yeah, we seem to have the tour map.
I get a BSOD every week or two on my Win2k box, (that IRQL one mentioned somewhere around here), and I don't know what piece of hardware is causing it. I've run a number of diagnostics off Hiren's bootCD, memtest86 gives the all-okay signal, nothing is running excessively hot. So what's the problem?
--grendel drago
Laws do not persuade just because they threaten. --Seneca
It seemed to manage a bit better, but as the PSU got closer to blowing (Of course, all without me knowing it), it caused Linux to freeze, refuse to boot properly and cause errors too. It also enjoyed reporting my 120GB HDD as being 9 Exabytes, and then 17 Exabytes.
In my younger and less socially-adapted days, I once went into a store that sold Apple ][ computers, and typed this:
:-).
:-()
call -151
300:a5 00 20 ed fd ad 30 c0 4c 00 03
300g
Or for those that don't read 6502 machine code:
LDA $00
JSR $FDED
LDA $C030
JMP $0300
This fills the screen with random garbage and clicks the speaker, repeatedly. I feel kind of bad about it now
(I don't remember whether the second byte was $00 or not; it was a zero page location that was ever-changing. I don't have an Apple ][ reference manual anymore
Linux is 32-bit? Crap, now I have to uninstall it from that Sparc64 server.
--grendel drago
Laws do not persuade just because they threaten. --Seneca
Unless by 'hardware' you mean Alpha, MIPS, PowerPC, S/390, ARM, m68k, Sparc or a variety of other platforms, in which case you get some halfhearted support from NT4 for a few of those other platforms, which was dropped along the way. Or you mean large-scale multiprocessor machines. Or you mean self-reconfiguring ad-hoc supercomputing clusters.
Unless by 'the business world' you mean a preponderance of server equipment, or the core mission-critical systems that are still running on mainframes because no desktop-based operating system will do what they do.
Unless by 'stable' you mean that for mission-critical stability (that five-nines sort of thing), no one in their right mind uses Windows. (I doubt they use Linux, either, but they certainly don't use Windows.)
Unless by 'catch-up ball' you mean that Linux had the ability to turn old hardware into a useful router, small-scale webserver or PBX before Windows. Hell, Windows still doesn't. Or IPv6 support. Or support for so many filesystems. Or genuine random number generation (I *think* this was a Linux innovation) instead of using pseudorandom methods. Or native user-space support for arbitrary binary formats.
And, of course, unless by 'facts' you mean a list of suppositions, unsupported by anything but bluster.
--grendel drago
Laws do not persuade just because they threaten. --Seneca
My apologies if I came off as a zealot. I had one of my biweekly crashes last night, and I'm trying to remember a third of the Firefox tabs I had open at the time.
I'll reply to this again when I get home and can give you the full rundown on my hardware. I only blame the Windows because I have a Linux machine running on slightly older hardware (and I'm nearly certain it's VIA-based) right alongside and it never kernel-panics on me.
Thanks for the help.
--grendel drago
Laws do not persuade just because they threaten. --Seneca
Actually, recently I was having XP SP2 blusecreen, and it didn't show anything, just went right to the loading screen. I was convinced I had a hardware problem till someone told me to turn off the auto reboot.
Sure enough - no more sudden "power loss"/restarts, but a heck of a lot more bluescreens.
It's since stopped doing that - and I really have no idea why. I'm just happy it seems stable again.
Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
Mmmm, I'd be interested in that tutorial if you do happen to stumble upon it. What about repair installs?
Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
I applaud Microsoft for giving equal time to the RSOD. However, they have a long way to go in the fight for equal rights for equal colors. The YSOD still gets no recognition while retaining the stigma that yellow is bad. When we will give our yellow error message brothers the recognition they deserve?
Windows will now have EVEN MORE problems? and it now has a class for each error?
Sorry, I prefer it when linux crashes with a system freeze, at least I know I'm in deep shit when that occasionally or rarely happens.
I've run into quite a number of BSODs on machines that I have been asked to work on. They tend to be hardware/driver related, but not all the time.
Since we see many systems because they are virus infected, I think it has more to do with some virus's playing God with Windows than Microsoft (Microsoft may be indirectly responsible due to of the security flaw that let the infection in). A good sfc or reinstall (repair or full) is often (but not always) a fix. Microsoft is actually halfway decent at giving explanations of their BSOD's try google:
site:microsoft.com xp "stop code: 0x12345678"
(replace the 12345678 with the stop code)
Registry errors can also cause BSOD's.(rare, but happens)
I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
Not necessarily, some software can do it. For a very common example, Azureus 2.2.0.0 was a FREQUENT source of BSODs. Went back to 2.1.0.4 and haven't had an issue since.
As a side note, Although drivers are a common issue, they don't have to be seriously buggy to be a serious problem- The standard Netgear FA311 drivers work very well, except in combination with ANY BitTorrent client, which result in freezes and requiring reboots. The nForce3 250 IDE drivers work well, but cause conflicts (e.g. BSOD when combined with ZoneAlarm).
and put them on flickr
I haven't tried this on XP, but is it always that hard? I've just recently dealt with 98SE, and the only hard thing is getting the 98 CD on the HD (because, for some reason, the IDE drivers in safe mode are good enough to get to the HD, but not to the CD. Stupid MS). If the 98 CD is on the HD (knoppix can be a life saver here), then there is no trouble. Oh yeah, it wasn't a small change, either- Asus A7V to Asus K8N- and no real problems.
Granted, I've since tried A7V266 to K8N on XP, and it went BSOD instantly, no negotiating. That made for an unexpected reinstall.
can be a real RSOL...
Well, I have had XP BSOD on me whenever I tried to disable an unused network connection (IIRC, a 1394 connection). This was completely reproducable. I don't remember why I wanted to disable it, but I think it was interfering with hibernation (I.E. must stop network to hibernate).
# cat
Damn, my RAM is full of llamas.
So...how much do you think Coke had to pay Microsoft to replace some of the "Pepsi Blue" error screens with "Coke Red"?!?
I asked my friend about it and heres the url http://www.users.on.net/~jvizard/myne/XPmoboUG/ its a bunch of screenshots that show you want to do and have some instructions on the pics. You might be able to repair an install with it too, probably depends on how bad the problems are.
Maybe MS will make Screens of Death based on American terrorist threat levels?
"Today the threat of a computer crash is YELLOW..."
[3 days after some new email virus:]
"Today, MicroSoft has upgraded the threat of your system crashing to ORANGE..."
Windows Loghorn will present you less BSOD
Motion to rename the next Windows to Windows Foghorn Leghorn.
Know your pads. One time pad: good for cryptography. Two timing pad: where to take your mistress.