XPost: alt.comp.os.windows-11, alt.comp.windows.blue-screen-of-death, sac.politics
XPost: talk.politics.guns

The dreaded �blue screen of death� that has tormented millions of Windows
users for decades is being put to rest.

Microsoft is ditching the notorious feature that appears on Windows
computers in the coming months, �streamlining the unexpected restart experience� with a new black-colored screen, the company announced in a
blog post.

The �simplified� screen that appears during �unexpected restarts� will
roll out later this summer on all Windows 11 devices that use 24H2
operating software. It will also reduce reboots to �about two seconds for
most users,� the company said.

Variations of the �blue screen of death� have been in use since the early 1990s. It started with the �blue screen of unhappiness� in Windows 3.1
when the control-alt-delete shortcut was added to exit an unresponsive
program, along with dialogue written by former Microsoft CEO Steve
Ballmer.

But according to Microsoft employee Raymond Chen, the actual �blue screen
of death� launched in 1993 on Windows NT when the �system is unrecoverably
dead at this point.�

Also, a version of the black screen was introduced in 2021 to Windows 11
users. This new iteration has updated dialogue.

The blue screen haunted millions of people last July when a massive outage caused by CrowdStrike brought most of the world�s technology to its knees
and Windows-operated machines displayed the infamous blue.

https://www.cnn.com/2025/06/27/tech/microsoft-blue-screen-of-death-changes

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.os.windows-11, alt.comp.windows.blue-screen-of-death

On 20/07/2025 6:58 pm, Shitty Indian Programmers wrote:

The dreaded “blue screen of death” that has tormented millions of Windows users for decades is being put to rest.

Microsoft is ditching the notorious feature that appears on Windows
computers in the coming months, “streamlining the unexpected restart experience” with a new black-colored screen, the company announced in a blog post.

So the BSOD will remain the BSOD, just changing Blue to Black!!

How useful. ;-P
--
Daniel70

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 20 Jul 2025 21:15:44 +1000, Daniel70
<[email protected]> wrote:

On 20/07/2025 6:58 pm, Shitty Indian Programmers wrote:

The dreaded “blue screen of death” that has tormented millions of Windows
users for decades is being put to rest.

Microsoft is ditching the notorious feature that appears on Windows
computers in the coming months, “streamlining the unexpected restart
experience” with a new black-colored screen, the company announced in a
blog post.

So the BSOD will remain the BSOD, just changing Blue to Black!!

Hmmmm ...

How useful. ;-P

Would it be a little better, and more useful, to have it changed to
Brown SOD? On the principle that when we get one we should be ever so
slightly not very calm?

In WinXP, or maybe WinME, I once changed the BSOD default colour to
something nice and cool such as a dark yellow but I'm not entirely
sure how I managed it.

It was probably XP as I remember ME never crashing on me. XP,
however, fell over a lot. It was probably a hex-hack inside a system
file, something which was far easier to do in those days.

Perhaps Microsoft could give us a "HAL" type eye-light and a nice,
friendly "I am sorry but I can not do that, <<User>>" vocalisation
instead of the garish, horrible, far-too-bright and terminally boring
Blue screen?

I really dislike the idea of a black screen. If we got one of those
and the textual error message didn't pop-up that would be quite
worrying.

J.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.os.windows-11, alt.comp.windows.blue-screen-of-death, sac.politics
XPost: talk.politics.guns

On 2025-07-20 09:58, Shitty Indian Programmers wrote:

Microsoft is ditching the notorious feature that appears on Windows
computers in the coming months, “streamlining the unexpected restart experience” with a new black-colored screen, the company announced in a blog post.

That a PC automatically reboots after a BSOD, whatever the background
colour, is one of the stupidest default Windows settings, which I always change, because it means that if the fault that has developed prevents
the computer rebooting successfully and so causes another BSOD, the
machine reboots indefinitely, making it very difficult to get to read
the message, and so discover what is actually wrong. The only way I've
found is to video the process with a phone and then step through the
resulting video until the BSOD is displayed, but things would be so much simpler if the default setting was to display the screen indefinitely
until a user intervenes.

--

Fake news kills!

I may be contacted via the contact address given on my website:
www.macfh.co.uk

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 20 Jul 2025 10:58:48 +0200 (CEST), Shitty Indian Programmers
wrote:

Newsgroups: alt.comp.os.windows-10, alt.comp.os.windows-11,
alt.comp.windows.blue-screen-of-death, sac.politics, talk.politics.guns

Meh.

--
s|b

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.os.windows-11, alt.comp.windows.blue-screen-of-death, sac.politics
XPost: talk.politics.guns

On Sun, 7/20/2025 9:11 AM, Java Jive wrote:

On 2025-07-20 09:58, Shitty Indian Programmers wrote:

Microsoft is ditching the notorious feature that appears on Windows
computers in the coming months, “streamlining the unexpected restart
experience” with a new black-colored screen, the company announced in a
blog post.

That a PC automatically reboots after a BSOD, whatever the background colour, is one of the stupidest default Windows settings, which I always change, because it means that if the fault that has developed prevents the computer rebooting successfully

and so causes another BSOD, the machine reboots indefinitely, making it very difficult to get to read the message, and so discover what is actually wrong.  The only way I've found is to video the process with a phone and then step through the resulting
video until the BSOD is displayed, but things would be so much simpler if the default setting was to display the screen indefinitely until a user intervenes.


Imagine if the STOP code was in 108 point font, so you could read it.

Oh, well. Same old, same old.

[Picture]

https://i.postimg.cc/63N82L5r/New-BSOD-via-My-Fault-push-button.gif

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2025/7/20 12:58:33, John wrote:

On Sun, 20 Jul 2025 21:15:44 +1000, Daniel70
<[email protected]> wrote:

[]

So the BSOD will remain the BSOD, just changing Blue to Black!!

Hmmmm ...

How useful. ;-P

Would it be a little better, and more useful, to have it changed to
Brown SOD? On the principle that when we get one we should be ever so slightly not very calm?

In WinXP, or maybe WinME, I once changed the BSOD default colour to something nice and cool such as a dark yellow but I'm not entirely
sure how I managed it.

I remember that hack (but not what it was) - someone posted (or it might
even have been in a magazine!) how to change the foreground and
background colours of the BSOD; I think it was under '9x or XP.>

It was probably XP as I remember ME never crashing on me. XP,
however, fell over a lot. It was probably a hex-hack inside a system
file, something which was far easier to do in those days.

I have a feeling it was! I _think_ it told us how to change a few other
colours too, but it was a Long Time Ago. I went for an orange background
- can't remember what text (black maybe?).>

Perhaps Microsoft could give us a "HAL" type eye-light and a nice,
friendly "I am sorry but I can not do that, <<User>>" vocalisation
instead of the garish, horrible, far-too-bright and terminally boring
Blue screen?

I really dislike the idea of a black screen. If we got one of those
and the textual error message didn't pop-up that would be quite
worrying.

J.

The switch to other than an 80 by 24 (25?) character mode (fixed font)
screen - not sure when, 7 or 10 I think - also unsettled me. (To be
fair, it was very rare - I think I may not have _seen_ a BSOD from 7 on. Certainly I don't think I've had one in the two months or so I've been
using 10 [apparently "Build 19041.vb_release 191206-1406" according to
the bottom right of my screen, "22H2" and "19045.6093" according to
Control Panel | System].)>


--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Q. Why did the chicken cross the Mobius strip?
A. To get to the same side.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 20 Jul 2025 17:08:13 +0200, s|b wrote:

On Sun, 20 Jul 2025 10:58:48 +0200 (CEST), a troll
wrote:
[crap]

Meh.

Spammers will spam, and trolls will troll, and there's nothing we can
do about it. What I don't understand is why otherwise intelligent
people reward their spamming and trolling by reposting it and
responding, encouraging them to persist in their antisocial behavior.

--
After using my real address in 37 years of Usenet articles,
I am now reluctantly posting a fake address because of the
large number of sites scraping Usenet articles without
permission and putting them on their own pretend forum sites.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.os.windows-11

On 20/07/2025 09:58, Shitty Indian Programmers wrote:


Sneha Ramachandran, Software Engineer, Microsoft has created "Visual
Studio's Remote File Explorer". You'll learn a thing or two if you pay attention to what she has to say about it to educate obese Americans!.

<https://youtu.be/_8plZbYaV40?si=KDFLb4pgD-g4gDBB>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.os.windows-11, alt.comp.windows.blue-screen-of-death

On 20/07/2025 12:15, Daniel70 wrote:

So the BSOD will remain the BSOD, just changing Blue to Black!!

How useful.

Yes so that you can still use the acronym BSOD to mean "Black Screen of
Death". Black tie and black jacket is not obligatory for the funeral!

<https://bsodmaker.net/>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 20 Jul 2025 17:26:54 +0100, J. P. Gilliver wrote:

[snip]

In WinXP, or maybe WinME, I once changed the BSOD default colour to
something nice and cool such as a dark yellow but I'm not entirely sure
how I managed it.

I remember that hack (but not what it was) - someone posted (or it might
even have been in a magazine!) how to change the foreground and
background colours of the BSOD; I think it was under '9x or XP.>

I remember having a way to change it in 9x. I made it RED, which seemed
more appropriate to something messing up (although brown could be good
too).

BTW, the new Ubuntu seems to have a MSOD (Magenta Screen Of Death).

[snip]

--
Mark Lloyd
http://notstupid.us/

"When people learn no tools of judgment and merely follow their hopes,
the seeds of political manipulation are sown." [Stephen Jay Gould]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.os.windows-11, sac.politics, talk.politics.guns

On 20/07/2025 09:58, Shitty Indian Programmers wrote:

The dreaded “blue screen of death” that has tormented millions of Windows users for decades is being put to rest.

snip <

https://www.cnn.com/2025/06/27/tech/microsoft-blue-screen-of-death-changes

Not exactly 'News'. I read about this months ago.

--
Regards
wasbit

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.os.windows-11, alt.comp.windows.blue-screen-of-death

On 21/07/2025 3:44 am, BSOD Maker wrote:

On 20/07/2025 12:15, Daniel70 wrote:

So the BSOD will remain the BSOD, just changing Blue to Black!!

How useful.

Yes so that you can still use the acronym BSOD to mean "Black Screen of Death". Black tie and black jacket is not obligatory for the funeral!

<https://bsodmaker.net/>

Hmm! Is my clicking that link going to CAUSE a BSOD?? ;=P
--
Daniel70

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 20/07/2025 9:58 pm, John wrote:

On Sun, 20 Jul 2025 21:15:44 +1000, Daniel70
<[email protected]> wrote:

On 20/07/2025 6:58 pm, Shitty Indian Programmers wrote:

The dreaded “blue screen of death” that has tormented millions of Windows
users for decades is being put to rest.

Microsoft is ditching the notorious feature that appears on Windows
computers in the coming months, “streamlining the unexpected restart
experience” with a new black-colored screen, the company announced in a >>> blog post.

So the BSOD will remain the BSOD, just changing Blue to Black!!

Hmmmm ...

How useful. ;-P

Would it be a little better, and more useful, to have it changed to
Brown SOD? On the principle that when we get one we should be ever so slightly not very calm?

It would be a little better if the BSOD included a BUTTON which would
allow me to send MS the relevant data that caused the FAILURE .... so, hopefully, MS could do something about fixing it .... maybe even fixing
the most popular BSOD of the month cause!!
--
Daniel70

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 7/21/2025 7:24 AM, Daniel70 wrote:

On 20/07/2025 9:58 pm, John wrote:

On Sun, 20 Jul 2025 21:15:44 +1000, Daniel70
<[email protected]> wrote:

On 20/07/2025 6:58 pm, Shitty Indian Programmers wrote:

The dreaded “blue screen of death” that has tormented millions of Windows
users for decades is being put to rest.

Microsoft is ditching the notorious feature that appears on Windows
computers in the coming months, “streamlining the unexpected restart >>>> experience” with a new black-colored screen, the company announced in a >>>> blog post.

So the BSOD will remain the BSOD, just changing Blue to Black!!

  Hmmmm ...

How useful. ;-P

  Would it be a little better, and more useful, to have it changed to
Brown SOD? On the principle that when we get one we should be ever so
slightly not very calm?

It would be a little better if the BSOD included a BUTTON which would allow me
to send MS the relevant data that caused the FAILURE .... so, hopefully, MS could
do something about fixing it .... maybe even fixing the most popular BSOD of the month cause!!

You can trigger that behavior, by reporting a bug on the Feedback Hub.

Depending on the nature of the bug, you will see an upload run for
around an hour, as some reporting subsystem collects Event Viewer info
and so on, to attach to the bug automatically.

Feedback Hub reports are unidirectional. You don't know the status or disposition of your bug, once you've sent it.

The one in this picture (from TheVerge), the staff know what this one is.

[Picture]

https://i.postimg.cc/63N82L5r/New-BSOD-via-My-Fault-push-button.gif

Russinovich has a piece of software (not a part of Sysinternals as such),
and there is an option in MyFault, to crash the system. Hobbyists use this,
if they have modified the crash response of Windows, and they need to check that the right things happen on a kernel panic. The text at the bottom
of the picture, indicates that's a synthetic crash done purely so the
operator of the computer, could take a picture of the "new" BSOD screen.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.os.windows-11

On Mon, 7/21/2025 5:18 AM, wasbit wrote:

On 20/07/2025 09:58, Shitty Indian Programmers wrote:

The dreaded “blue screen of death” that has tormented millions of Windows
users for decades is being put to rest.

snip <

https://www.cnn.com/2025/06/27/tech/microsoft-blue-screen-of-death-changes >>

Not exactly 'News'. I read about this months ago.

They have been pissing around with this, for quite a while.
Even when it was News, it was Non-News.

There is still a STOP code and a faulting module, but they
still haven't made the font big enough. Maybe if we wait a
hundred years, they'll fix the font.

The older the OS, the easier it would be to write the
code, to write on the screen. It's not as easy today to do that.
The video card module is in a container, on an Inverted Hypervisor.
And the system has just crashed (whatever does that mean, to an
Inverted Hypervisor system?). So this is more complicated than
you might expect.

One thing we don't know, is whether the memory writer got fixed.
If you dump the entire memory, the older OSes were glacially slow
at writing out the memory to disk. On machines with plenty of RAM,
if you actually configured them for a "big memory dump", half the
day could be wasted generating the trace. Normally the dumps
on your machine would be minidumps of some sort, and not
quite as taxing to write out.

The BSOD itself isn't the torment, it's fixing the root cause
that is the torment.

The example used in the picture, you should recognize the source of that
one. That's a program, where one of the features is crashing the system
so you can check whether the BSOD works properly. If you have just
configured Windows to do a Big Crash Dump, then you can use
MyFault (Russinovich) to test it.

[Picture]

https://i.postimg.cc/63N82L5r/New-BSOD-via-My-Fault-push-button.gif

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)