• Wow - M$ Fixes Everything - Blue Screen-of-Death Replaced by BLACK Scre

    From c186282@21:1/5 to All on Fri Jun 27 23:41:27 2025
    https://www.gadgets360.com/laptops/news/microsoft-windows-11-blue-screen-of-death-bsod-black-error-message-8776837?pfrom=home-ndtv_tech

    The new black screen appears to be identical to the green one
    shared by the company in March. It bears an uncanny resemblance
    to the Windows 11 update screen, with centre-aligned text telling
    users that the computer is restarting because of an error and
    the percentage that reveals the progress of the crash log
    collection process.

    Users will also see a stop code with an error that can be
    shared with system administrators, while the black screen
    will also inform them about the process that failed (for
    example, it will tell users that a particular driver file
    failed, such as rdbss.sys).

    It's also worth noting that this isn't the first time that
    Microsoft has announced that the BSOD warning would be
    changed from blue. Back in 2021, the company tested a
    black version of the warning message, but that version
    also included the text emoticon with a colon and a
    bracket (a frown).

    . . .

    Well THAT fixes it ! When in doubt, just change
    the color :-)

    Admittedly Linux boot-failure messages/logs are
    also almost impossible to interpret unless you
    are an ultra-anal hyper-nerd who hasn't moved
    from the PC for ten years .........

    Clue - we need a generally BETTER fail-mode
    solution - much clearer defs of what bombed
    and why and maybe some automated fixes or at
    least really good instructions. In short a
    "system spy" routine that runs even before
    official boot.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From LV-426@21:1/5 to All on Sat Jun 28 05:11:43 2025
    On 2025-06-27 11:41 p.m., c186282 wrote: >https://www.gadgets360.com/laptops/news/microsoft-windows-11-blue-screen-of-death-bsod-black-error-message-8776837?pfrom=home-ndtv_tech

    The new black screen appears to be identical to the green one
    shared by the company in March. It bears an uncanny resemblance
    to the Windows 11 update screen, with centre-aligned text telling
    users that the computer is restarting because of an error and
    the percentage that reveals the progress of the crash log
    collection process.

    Users will also see a stop code with an error that can be
    shared with system administrators, while the black screen
    will also inform them about the process that failed (for
    example, it will tell users that a particular driver file
    failed, such as rdbss.sys).

    It's also worth noting that this isn't the first time that
    Microsoft has announced that the BSOD warning would be
    changed from blue. Back in 2021, the company tested a
    black version of the warning message, but that version
    also included the text emoticon with a colon and a
    bracket (a frown).

    . . .

    Well THAT fixes it ! When in doubt, just change
    the color :-)

    Admittedly Linux boot-failure messages/logs are
    also almost impossible to interpret unless you
    are an ultra-anal hyper-nerd who hasn't moved
    from the PC for ten years .........

    Clue - we need a generally BETTER fail-mode
    solution - much clearer defs of what bombed
    and why and maybe some automated fixes or at
    least really good instructions. In short a
    "system spy" routine that runs even before
    official boot.

    Maybe they finally decided to follow IBM's idea with the black trap screens
    of death on OS/2.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From rbowman@21:1/5 to All on Sat Jun 28 06:18:31 2025
    On Fri, 27 Jun 2025 23:41:27 -0400, c186282 wrote:

    Clue - we need a generally BETTER fail-mode solution - much clearer
    defs of what bombed and why and maybe some automated fixes or at
    least really good instructions. In short a "system spy" routine that
    runs even before official boot.

    https://fedoramagazine.org/%f0%9f%94%a7-deep-dive-into-sosreport- understanding-the-data-pack-layout-in-fedora-rhel/

    https://fedoramagazine.org/unlocking-system-performance-a-practical-guide- to-tuning-pcp/

    I don't know if either of those are useful. sosreport generates a lot of
    crap that might be meaningful to a Red Hat engineer.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Charlie Gibbs@21:1/5 to c186282@nnada.net on Sat Jun 28 14:07:21 2025
    On 2025-06-28, c186282 <c186282@nnada.net> wrote:

    Clue - we need a generally BETTER fail-mode
    solution - much clearer defs of what bombed
    and why and maybe some automated fixes or at
    least really good instructions. In short a
    "system spy" routine that runs even before
    official boot.

    You mean something better than a message that says
    "Something went wrong"? What a concept!

    --
    /~\ Charlie Gibbs | Growth for the sake of
    \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
    X I'm really at ac.dekanfrus | of the cancer cell.
    / \ if you read it the right way. | -- Edward Abbey

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Nuno Silva@21:1/5 to All on Sun Jun 29 10:45:09 2025
    On 2025-06-28, LV-426 wrote:

    On 2025-06-27 11:41 p.m., c186282 wrote:
    https://www.gadgets360.com/laptops/news/microsoft-windows-11-blue-screen-of-death-bsod-black-error-message-8776837?pfrom=home-ndtv_tech

    The new black screen appears to be identical to the green one
    shared by the company in March. It bears an uncanny resemblance
    to the Windows 11 update screen, with centre-aligned text telling
    users that the computer is restarting because of an error and
    the percentage that reveals the progress of the crash log
    collection process.

    A percentage? Will they then finally re-add progress bars?


    Users will also see a stop code with an error that can be
    shared with system administrators, while the black screen
    will also inform them about the process that failed (for
    example, it will tell users that a particular driver file
    failed, such as rdbss.sys).

    It's also worth noting that this isn't the first time that
    Microsoft has announced that the BSOD warning would be
    changed from blue. Back in 2021, the company tested a
    black version of the warning message, but that version
    also included the text emoticon with a colon and a
    bracket (a frown).

    . . .

    Well THAT fixes it ! When in doubt, just change
    the color :-)

    Windows 4 did it better, couldn't you just choose the background color
    of your preference from a set of colors? It was blue by default, but
    could be e.g. green.


    Admittedly Linux boot-failure messages/logs are
    also almost impossible to interpret unless you
    are an ultra-anal hyper-nerd who hasn't moved
    from the PC for ten years .........

    A lot of messages do provide information to try to address the
    problem. This is often much more than certain systems provide.

    No need to insult people who have at least some knowledge to get
    something from these messages.


    Clue - we need a generally BETTER fail-mode
    solution - much clearer defs of what bombed
    and why and maybe some automated fixes or at
    least really good instructions. In short a
    "system spy" routine that runs even before
    official boot.

    Maybe they finally decided to follow IBM's idea with the black trap screens of death on OS/2.

    --
    Nuno Silva

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Ahlstrom@21:1/5 to Nuno Silva on Sun Jun 29 08:19:32 2025
    Nuno Silva wrote this post while blinking in Morse code:

    On 2025-06-28, LV-426 wrote:

    On 2025-06-27 11:41 p.m., c186282 wrote: >>>https://www.gadgets360.com/laptops/news/microsoft-windows-11-blue-screen-of-death-bsod-black-error-message-8776837?pfrom=home-ndtv_tech

    The new black screen appears to be identical to the green one
    shared by the company in March. It bears an uncanny resemblance
    to the Windows 11 update screen, with centre-aligned text telling
    users that the computer is restarting because of an error and
    the percentage that reveals the progress of the crash log
    collection process.

    A percentage? Will they then finally re-add progress bars?

    Users will also see a stop code with an error that can be
    shared with system administrators, while the black screen
    will also inform them about the process that failed (for
    example, it will tell users that a particular driver file
    failed, such as rdbss.sys).

    It's also worth noting that this isn't the first time that
    Microsoft has announced that the BSOD warning would be
    changed from blue. Back in 2021, the company tested a
    black version of the warning message, but that version
    also included the text emoticon with a colon and a
    bracket (a frown).

    . . .

    Well THAT fixes it ! When in doubt, just change
    the color :-)

    Windows 4 did it better, couldn't you just choose the background color
    of your preference from a set of colors? It was blue by default, but
    could be e.g. green.


    Admittedly Linux boot-failure messages/logs are
    also almost impossible to interpret unless you
    are an ultra-anal hyper-nerd who hasn't moved
    from the PC for ten years .........

    A lot of messages do provide information to try to address the
    problem. This is often much more than certain systems provide.

    No need to insult people who have at least some knowledge to get
    something from these messages.


    Clue - we need a generally BETTER fail-mode
    solution - much clearer defs of what bombed
    and why and maybe some automated fixes or at
    least really good instructions. In short a
    "system spy" routine that runs even before
    official boot.

    Maybe they finally decided to follow IBM's idea with the black trap screens >> of death on OS/2.

    I always liked the Atari ST's cherry bombs.

    --
    "You can't get very far in this world without your dossier being there first."
    -- Arthur Miller

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From c186282@21:1/5 to Chris Ahlstrom on Sun Jun 29 19:21:26 2025
    On 6/29/25 8:19 AM, Chris Ahlstrom wrote:
    Nuno Silva wrote this post while blinking in Morse code:

    On 2025-06-28, LV-426 wrote:

    On 2025-06-27 11:41 p.m., c186282 wrote:
    https://www.gadgets360.com/laptops/news/microsoft-windows-11-blue-screen-of-death-bsod-black-error-message-8776837?pfrom=home-ndtv_tech

    The new black screen appears to be identical to the green one
    shared by the company in March. It bears an uncanny resemblance
    to the Windows 11 update screen, with centre-aligned text telling
    users that the computer is restarting because of an error and
    the percentage that reveals the progress of the crash log
    collection process.

    A percentage? Will they then finally re-add progress bars?

    Users will also see a stop code with an error that can be
    shared with system administrators, while the black screen
    will also inform them about the process that failed (for
    example, it will tell users that a particular driver file
    failed, such as rdbss.sys).

    It's also worth noting that this isn't the first time that
    Microsoft has announced that the BSOD warning would be
    changed from blue. Back in 2021, the company tested a
    black version of the warning message, but that version
    also included the text emoticon with a colon and a
    bracket (a frown).

    . . .

    Well THAT fixes it ! When in doubt, just change
    the color :-)

    Windows 4 did it better, couldn't you just choose the background color
    of your preference from a set of colors? It was blue by default, but
    could be e.g. green.


    Admittedly Linux boot-failure messages/logs are
    also almost impossible to interpret unless you
    are an ultra-anal hyper-nerd who hasn't moved
    from the PC for ten years .........

    A lot of messages do provide information to try to address the
    problem. This is often much more than certain systems provide.

    No need to insult people who have at least some knowledge to get
    something from these messages.


    Clue - we need a generally BETTER fail-mode
    solution - much clearer defs of what bombed
    and why and maybe some automated fixes or at
    least really good instructions. In short a
    "system spy" routine that runs even before
    official boot.

    Maybe they finally decided to follow IBM's idea with the black trap screens >>> of death on OS/2.

    I always liked the Atari ST's cherry bombs.


    Amiga "Guru Meditation" messages with the huge
    number following were fun :-)

    Got so many with my A-1000 that I dumped the box.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bobbie Sellers@21:1/5 to All on Sun Jun 29 16:48:50 2025
    On 6/29/25 16:21, c186282 wrote:
    On 6/29/25 8:19 AM, Chris Ahlstrom wrote:
    Nuno Silva wrote this post while blinking in Morse code:

    On 2025-06-28, LV-426 wrote:

    On 2025-06-27 11:41 p.m., c186282 wrote:
    https://www.gadgets360.com/laptops/news/microsoft-windows-11-blue-
    screen-of-death-bsod-black-error-message-8776837?pfrom=home-ndtv_tech >>>>>
    The new black screen appears to be identical to the green one
    shared by the company in March. It bears an uncanny resemblance
    to the Windows 11 update screen, with centre-aligned text telling
    users that the computer is restarting because of an error and
    the percentage that reveals the progress of the crash log
    collection process.

    A percentage? Will they then finally re-add progress bars?

    Users will also see a stop code with an error that can be
    shared with system administrators, while the black screen
    will also inform them about the process that failed (for
    example, it will tell users that a particular driver file
    failed, such as rdbss.sys).

    It's also worth noting that this isn't the first time that
    Microsoft has announced that the BSOD warning would be
    changed from blue. Back in 2021, the company tested a
    black version of the warning message, but that version
    also included the text emoticon with a colon and a
    bracket (a frown).

    . . .

       Well THAT fixes it ! When in doubt, just change
       the color  :-)

    Windows 4 did it better, couldn't you just choose the background color
    of your preference from a set of colors? It was blue by default, but
    could be e.g. green.


       Admittedly Linux boot-failure messages/logs are
       also almost impossible to interpret unless you
       are an ultra-anal hyper-nerd who hasn't moved
       from the PC for ten years .........

    A lot of messages do provide information to try to address the
    problem. This is often much more than certain systems provide.

    No need to insult people who have at least some knowledge to get
    something from these messages.


       Clue - we need a generally BETTER fail-mode
       solution - much clearer defs of what bombed
       and why and maybe some automated fixes or at
       least really good instructions. In short a
       "system spy" routine that runs even before
       official boot.

    Maybe they finally decided to follow IBM's idea with the black trap
    screens
    of death on OS/2.

    I always liked the Atari ST's cherry bombs.


      Amiga "Guru Meditation" messages with the huge
      number following were fun  :-)

      Got so many with my A-1000 that I dumped the box.

    Maybe you should have looked those big numbers up.

    I got tired of the problems but loved the AmigaOS and went with it
    from 1.3 to 3.9. Amiga 1000 to Amiga 2000b But AmigaOS had no memory
    protection due to the costs of including chips to manage the memory.
    So when CBM went down the tubes I moved to GNU/ Linux and am narly
    as happy with it as I was with AmigaOS. I am older now and find memory protection a very valuable matter. I even used XP in the transition from
    Amiga to the Mandriva Linux 2006. But the AmigaOS was a real operating
    system and I learned a lot from using it much more than I learned from
    the Commodore 64 or the 64/128 on which I used native mode, CP/M and
    GEOS. I still have all the bookmarks I gathered on the Amiga and some
    few of them are still active.

    bliss-Dell Precision 7730-PCLOS 2025.06- Linux 6.12.35 pclos1-KDE Plasma 5.27.11

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Not Necessary@21:1/5 to All on Mon Jun 30 10:12:37 2025
    On 28/06/25 9:11 am, c186282 wrote:
    https://www.gadgets360.com/laptops/news/microsoft-windows-11-blue- screen-of-death-bsod-black-error-message-8776837?pfrom=home-ndtv_tech

    The new black screen appears to be identical to the green one
    shared by the company in March. It bears an uncanny resemblance
    to the Windows 11 update screen, with centre-aligned text telling
    users that the computer is restarting because of an error and
    the percentage that reveals the progress of the crash log
    collection process.

    Users will also see a stop code with an error that can be
    shared with system administrators, while the black screen
    will also inform them about the process that failed (for
    example, it will tell users that a particular driver file
    failed, such as rdbss.sys).

    It's also worth noting that this isn't the first time that
    Microsoft has announced that the BSOD warning would be
    changed from blue. Back in 2021, the company tested a
    black version of the warning message, but that version
    also included the text emoticon with a colon and a
    bracket (a frown).

    . . .

      Well THAT fixes it ! When in doubt, just change
      the color  :-)

      Admittedly Linux boot-failure messages/logs are
      also almost impossible to interpret unless you
      are an ultra-anal hyper-nerd who hasn't moved
      from the PC for ten years .........

      Clue - we need a generally BETTER fail-mode
      solution - much clearer defs of what bombed
      and why and maybe some automated fixes or at
      least really good instructions. In short a
      "system spy" routine that runs even before
      official boot.

    So it is still BSOD: Black instead of Blue!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From c186282@21:1/5 to Not Necessary on Mon Jun 30 01:49:57 2025
    On 6/30/25 12:42 AM, Not Necessary wrote:
    On 28/06/25 9:11 am, c186282 wrote:
    https://www.gadgets360.com/laptops/news/microsoft-windows-11-blue-
    screen-of-death-bsod-black-error-message-8776837?pfrom=home-ndtv_tech

    The new black screen appears to be identical to the green one
    shared by the company in March. It bears an uncanny resemblance
    to the Windows 11 update screen, with centre-aligned text telling
    users that the computer is restarting because of an error and
    the percentage that reveals the progress of the crash log
    collection process.

    Users will also see a stop code with an error that can be
    shared with system administrators, while the black screen
    will also inform them about the process that failed (for
    example, it will tell users that a particular driver file
    failed, such as rdbss.sys).

    It's also worth noting that this isn't the first time that
    Microsoft has announced that the BSOD warning would be
    changed from blue. Back in 2021, the company tested a
    black version of the warning message, but that version
    also included the text emoticon with a colon and a
    bracket (a frown).

    . . .

      Well THAT fixes it ! When in doubt, just change
      the color  :-)

      Admittedly Linux boot-failure messages/logs are
      also almost impossible to interpret unless you
      are an ultra-anal hyper-nerd who hasn't moved
      from the PC for ten years .........

      Clue - we need a generally BETTER fail-mode
      solution - much clearer defs of what bombed
      and why and maybe some automated fixes or at
      least really good instructions. In short a
      "system spy" routine that runs even before
      official boot.

    So it is still BSOD: Black instead of Blue!

    Yep ... and M$ will CLAIM it's "done something" :-)

    Umpteen millions/billions will fall for it.

    We SAW what M$ 'fixes' look like in Vista.
    It basically made the OS nearly unusable
    unless YOU personally disabled most of the
    'security' settings. Then it was all YOUR
    fault .......

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fritz Wuehler@21:1/5 to All on Mon Jun 30 17:37:11 2025
    Not Necessary <...@necessary.invalid> [NN]:
    So it is still BSOD: Black instead of Blue!

    Black is the new blue...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to Fritz Wuehler on Tue Jul 1 00:41:29 2025
    On Mon, 30 Jun 2025 17:37:11 +0200, Fritz Wuehler wrote:

    Black is the new blue...

    Copying Linux, yet again!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Charlie Gibbs@21:1/5 to c186282@nnada.net on Tue Jul 1 11:45:21 2025
    On 2025-06-29, c186282 <c186282@nnada.net> wrote:

    Amiga "Guru Meditation" messages with the huge
    number following were fun :-)

    Got so many with my A-1000 that I dumped the box.

    I dumped the poorly-written software that caused them.

    --
    /~\ Charlie Gibbs | Growth for the sake of
    \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
    X I'm really at ac.dekanfrus | of the cancer cell.
    / \ if you read it the right way. | -- Edward Abbey

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From c186282@21:1/5 to Charlie Gibbs on Tue Jul 1 12:37:42 2025
    On 7/1/25 7:45 AM, Charlie Gibbs wrote:
    On 2025-06-29, c186282 <c186282@nnada.net> wrote:

    Amiga "Guru Meditation" messages with the huge
    number following were fun :-)

    Got so many with my A-1000 that I dumped the box.

    I dumped the poorly-written software that caused them.

    Couldn't find replacements soon enough ...

    The underlying OS seems to have been released
    a little before it was ripe.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Charlie Gibbs@21:1/5 to c186282@nnada.net on Wed Jul 2 01:13:08 2025
    On 2025-07-01, c186282 <c186282@nnada.net> wrote:

    On 7/1/25 7:45 AM, Charlie Gibbs wrote:

    On 2025-06-29, c186282 <c186282@nnada.net> wrote:

    Amiga "Guru Meditation" messages with the huge
    number following were fun :-)

    Got so many with my A-1000 that I dumped the box.

    I dumped the poorly-written software that caused them.

    Couldn't find replacements soon enough ...

    The underlying OS seems to have been released
    a little before it was ripe.

    If anything, it's the hardware that wasn't ripe
    (i.e. no memory protection). As for software being
    released prematurely, that's been going on for far
    longer than that. All too many times we've had our
    noses rubbed in the basic marketing fact that it's
    better to be first than best.

    --
    /~\ Charlie Gibbs | Growth for the sake of
    \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
    X I'm really at ac.dekanfrus | of the cancer cell.
    / \ if you read it the right way. | -- Edward Abbey

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to Charlie Gibbs on Wed Jul 2 01:25:43 2025
    On Wed, 02 Jul 2025 01:13:08 GMT, Charlie Gibbs wrote:

    All too many times we've had our noses rubbed in the basic marketing
    fact that it's better to be first than best.

    Actually, for too long it’s been “the mightiest marketing machine wins”. Look at the number of times some company other than Microsoft has
    pioneered some concept (the GUI from Apple/Xerox, PenPoint from Go, PDAs
    from Palm, the original Netbooks running Linux) only to have Microsoft
    come along and grab most if not all of the market by copying the basic
    idea (often badly) and simply drowning out competing voices with its advertising.

    Luckily, I think we’re past “peak Microsoft”.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From c186282@21:1/5 to Charlie Gibbs on Tue Jul 1 21:58:45 2025
    On 7/1/25 9:13 PM, Charlie Gibbs wrote:
    On 2025-07-01, c186282 <c186282@nnada.net> wrote:

    On 7/1/25 7:45 AM, Charlie Gibbs wrote:

    On 2025-06-29, c186282 <c186282@nnada.net> wrote:

    Amiga "Guru Meditation" messages with the huge
    number following were fun :-)

    Got so many with my A-1000 that I dumped the box.

    I dumped the poorly-written software that caused them.

    Couldn't find replacements soon enough ...

    The underlying OS seems to have been released
    a little before it was ripe.

    If anything, it's the hardware that wasn't ripe
    (i.e. no memory protection). As for software being
    released prematurely, that's been going on for far
    longer than that. All too many times we've had our
    noses rubbed in the basic marketing fact that it's
    better to be first than best.

    There IS some truth in that !

    Recently saw a mini-doc about the copier wars.
    Xerox came out with its 914. The thing actually
    CAUGHT FIRE at its public debut. They still got
    about 9000 orders ! Each machine sold came with
    it's own "Scorch Suppressor" - ie FIRE EXTINGUISHER -
    until they had time to re-design the bad bits :-)

    IBM had totally ignored that market and then had to
    play catch-up ... but Xerox was already way ahead
    of the game. It's why 'Xerox' and 'photo-copy' are
    still interchangeable terms.

    The 'modern PC' was born at a Xerox center of
    course ... GUIs, mice, cheap networks. However
    they never got enough funding - and foolishly
    let Steve Jobs check out their stuff when they'd
    done some other deal with him. Jobs only kinda
    sorta maybe 'stole' it all.

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