Wikipedia:Featured article candidates/Blue Screen of Death/archive1

Blue screen of death

This is a good and instructive article about a common mysterious computer phenomenon. The is furthermore long and contains some references and sources, so this should be one of the greatest software articles on Wikipedia. --Off! 20:31, 3 March 2006 (UTC)[reply]

Support. Rob 20:40, 3 March 2006 (UTC)[reply]

Object should have gone to peer review, only one reference, no inline citation, and no fair use rationale to start, and the article is rather confusing to some readers --Jaranda ^{wat's sup} 20:56, 3 March 2006 (UTC)[reply]

Object Needs references and the BIG blue images should all be the same size. Suggest Peer Review.

--PopUpPirate 00:54, 4 March 2006 (UTC)[reply]

Object
- Needs references.
- Images needs fair use rationale where appropriate.
- BSoD appears far too often.
- Way too much of the article is composed of pictures or representations of the blue screen.
- There are two Windows error screens that are both referred to as the blue screen of death, with one being significantly more serious than the other. - This is a little silly.
- a blue screen of death occurs when the kernel, or a driver running in kernel mode, encounters an error from which it cannot recover. This is usually caused by a driver that throws an unhandled exception or performs an illegal operation. - This is meaningless to a reader who does not know much about computers. In fact, most of this article is not accessible to non-technical users.

Pagra shtak 16:03, 4 March 2006 (UTC)[reply]

Object Are we OK with full-resolution screenshots of copyrighted software being used? Which of the Wikipedia fair use catagories would these fall under? Our Templat:Windows-software-screenshot would seem to apply - but it does not permit full resolution images. Scaling them down makes them unreadable. Tricky. SteveBaker 02:14, 5 March 2006 (UTC)[reply]
Object. Language needs a lot of debugging. Examples:
- a blue screen of death occurs when the kernel, or a driver running in kernel mode, encounters an error from which it cannot recover. This is usually caused by a driver that throws an unhandled exception or performs an illegal operation - totally incomprehensible techspeak
- They are referred to as "bug checks" in the Windows SDK, DDK, and WDK documentation - what's a SDK? what's a DDK? what's a WDK?
- The "Stop" message contains the error code and its symbolic name (e.g. 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED) along with four error-dependent values in parentheses - more incomprehensible techspeak
- A debugger is necessary to obtain a stack trace - what's a stack trace?
- Windows XP also allows for local kernel debugging - what is local kernel debugging?
- The underlying problem seems to be that the authors of the article assume a level of technical understanding that most readers simply don't have. An article should be written for readers of average intelligence and no expert knowledge. Kosebamse 18:19, 6 March 2006 (UTC)[reply]
  - Fixed the aboveFreedom to share 20:31, 7 March 2006 (UTC)[reply]
  - Technical articles shouldn't use technical language? Evil saltine 00:38, 10 March 2006 (UTC)[reply]
    - You need to use langage that someone who is likely to need to read the article will understand. Someone with enough technical understanding to grok this article will already be all too familiar with the BSOD. However, someone who just heard someone use the term and is curious as to what it means is perhaps unlikely to understand this article. SteveBaker 01:01, 10 March 2006 (UTC)[reply]

Currently object
- One of the categories for featured article is that it is currently stable. We need to wait until Vista is released so we can judge the RSoD better.
- The language needs rewriting, by an English language expert.
- We need to add at least one written "Further reference" material like a book.
- Images have to be cited and bigger.

Freedom to share 09:45, 7 March 2006 (UTC)[reply]