Windows 11 Retires Blue in Favor of the Black Screen of Death

[_roman_]

My windows 11 pro crashed a few hours ago with a bluescreen and Win32kfull.sys
It was not a smart move to update windows with the build in windows update tool. It was not smart to use the amd graphic card update tool.
So sad to see a bluescreen on a gaming only windows 11 pro installation.

Still bluescreen and not green or black what i read for a long time.


I do run more strict DRAM settings. I highly doubt it is DRAM related or the new mainboard related. I would have seen issues much faster while compiling. No issue at all with the improved DRAM settings with heavy DRAM / CPU stress with the gnu userspace and the linux kernel.

--

On the other hand my gentoo linux lost it's graphical user interface recently after an update and a reboot. Because of a very bad untested binary blob linux-firmware the X-server could not load any binary firmware for the graphics. That issue was in the official tree for several days.
I had to downgrade two versions to find a firmware package which worked. Without firmware I had no option to use the cpu graphics from the ryzen 7600X.

--

I wish microsoft would at least provide bare minimum drivers for MEDIATEK WIFI which is on so many mainboards. No wifi driver with the windows iso.
Microsoft should also fix their updates. Several reboots for a upgrade is stupid. there is technically no need to have several reboots.

 

[harm9963]

GSOD

 

[Alyux]

We already knew Microsoft's priorities were full of shit, but this is just embarrassing on their part.

 

[Tsukiyomi91]

not gonna update my OS. MS can go eat a dick.

 

[maxli86]

My windows 11 pro crashed a few hours ago with a bluescreen and Win32kfull.sys
It was not a smart move to update windows with the build in windows update tool. It was not smart to use the amd graphic card update tool.
So sad to see a bluescreen on a gaming only windows 11 pro installation.

Still bluescreen and not green or black what i read for a long time.


I do run more strict DRAM settings. I highly doubt it is DRAM related or the new mainboard related. I would have seen issues much faster while compiling. No issue at all with the improved DRAM settings with heavy DRAM / CPU stress with the gnu userspace and the linux kernel.

--

On the other hand my gentoo linux lost it's graphical user interface recently after an update and a reboot. Because of a very bad untested binary blob linux-firmware the X-server could not load any binary firmware for the graphics. That issue was in the official tree for several days.
I had to downgrade two versions to find a firmware package which worked. Without firmware I had no option to use the cpu graphics from the ryzen 7600X.

--

I wish microsoft would at least provide bare minimum drivers for MEDIATEK WIFI which is on so many mainboards. No wifi driver with the windows iso.
Microsoft should also fix their updates. Several reboots for a upgrade is stupid. there is technically no need to have several reboots.

Why is why if Microsoft remove OOBE by pass in the future.
User have to manually prepare and load the drivers.
As Windows ISO does not have mediatek WiFi and BT by default.
For myself when I do a clean install of Windows, I will install all the drivers from manufacturer website.
MS update may not have all the drivers for that PC especially newer hardware.
I just hope OOBE bypass isn't remove since MS does not update the driver package in the default ISO.

 

[LabRat 891]

A little more detail, would be appreciated but, I guess there is still the memdump...

 

[R-T-B]

I have no idea how the color of screen became the headline.

It's the headline everywhere. The only explanation honestly is Microsoft wants it to be, for some odd reason.

 

[lexluthermiester]

Indeed, I was debugging my kernel driver last week and was so happy that Windows Vista gave me an error address, took me only 5 minutes to fix the code once I had that

Exactly. If you want evidence that microsoft has lost it's way, this is a good example. Instead of being useful, the crash screen is now useless.

View attachment 405697
A little more detail, would be appreciated but, I guess there is still the memdump...

Maybe. But one would have to dig through the dump and the logs. Anyone who's ever done that knows how much of a pain it is, even if the mini-dump option is selected. Having the exact address/location and data would be and has been FAR faster and vastly more useful.

 

[_roman_]

Why is why if Microsoft remove OOBE by pass in the future.

Just for information. W8 key did not activate anymore a few days ago a w11 pro. This annoys me quite more
I gave up in the middle of the w11 pro install. Too much stuff to change and no feature at all to move all settings over. My 18.5 year (i checked again) gentoo install still has 80% of the settings i set weeks, months, years ago. No WLAN driver .... What's the point to download a fresh iso when it lacks the usual, cheap, MEDIATEK wifi driver? So many people gave up their gnu linux first time install because of no network support. Fact.

they want to bring everyone to their email address login account. The existing drive with w11 pro from the asus mainboard when i used it with the other msi mainboard lost its w11 pro key. I had some issues with hwinfo. Quite a challenge to reset the settings as the user interface is a mess. Wrong displayed ethernet interface with text from the previous ax210 wlan module.

-- that oobe bypass worked on my refurbished notebook with w11 pro a few months ago. You will need several reboots to activate it. In the past I did not need any reboot.

So when you want to keep your windows key you better have that microsoft login email in use. the option for a pin is also stupid. I tested the email account on the aborted w11pro installation. I do not want a pint for login. I just want no password. To remove the email address as a login you need to move around a bit. too complicated and too stupid made.

 

[Vayra86]

Honestly they should make a BSOD just say PEBKAC in font size 112 or something.

Looks like they've already passed the blame to the device after all, saying 'Your device ran into a problem'. No its not Windows, no no. Its your device. The OS is fine.

Still I'm going to be blessed with not seeing this for the next 8 odd years or so, most likely.

not gonna update my OS. MS can go eat a dick.

This

 

[AusWolf]

To be fair, there's too many factors including user induced that could provoke a BSOD. The price to pay for the freedom of having a wide range of hardware combination. You had bad luck with the silicon lottery and can't run ram with timings so tight and a speed so high ? BSOD. Dammaged Riser ? BSOD. Undervolt too aggressive ? BSOD. RTX 5000? BSOD. Raptor Lake ? BSOD. RX 5700? BSOD. First gen Ryzen? BSOD.

Still, I don't see these kinds of announcements regarding Linux.

 

[dyonoctis]

The verge just decided to make a headline about that topic, but as it's been said in another message, It's just one of many adjustments that Microsoft is making. It's buried in a windows insiders blog spot focused on windows for organizations.

Windows is also still more mainstream than Linux. Linux just go into full kernel panic verbose mode with ton of text if something does happen. Modern Windows is trying to hold your hand when a fatal error happens, because non tech-savvy people are probably going to be involved with windows at work. Linux knows that you will be able to deal with it if you made the choice to use Linux in the first place.

But truth to be told, for the full year that I've been in a workplace that mostly use windows, I never had a fatal error. And that's whith computers running all day long beside the week-end. Most of the BSOD that I've had were because I was F***** around, or had damaged hardware. I feel like Windows never totally got over the Windows 98 era, where BSOD were apparently easy to trigger. If you get tons of BSOD on a modern Windows, it's more likely that something is wrong with your hardware, or there's a bad driver

 

[Darmok N Jalad]

The verge just decided to make a headline about that topic, but as it's been said in another message, It's just one of many adjustments that Microsoft is making. It's buried in a windows insiders blog spot focused on windows for organizations.

Windows is also still more mainstream than Linux. Linux just go into full kernel panic verbose mode with ton of text if something does happen. Modern Windows is trying to hold your hand when a fatal error happens, because non tech-savvy people are probably going to be involved with windows at work. Linux knows that you will be able to deal with it if you made the choice to use Linux in the first place.

But truth to be told, for the full year that I've been in a workplace that mostly use windows, I never had a fatal error. And that's whith computers running all day long beside the week-end. Most of the BSOD that I've had were because I was F***** around, or had damaged hardware. I feel like Windows never totally got over the Windows 98 era, where BSOD were apparently easy to trigger. If you get tons of BSOD on a modern Windows, it's more likely that something is wrong with your hardware, or there's a bad driver


View attachment 405722

I can't think of the last time I had a BSOD in Windows, but it was probably from too much undervolt or too much overclock or something user induced. My problem with Windows these days is not stability, but fit and finish, quality, and speed. I experience many random visual issues in everyday use of Windows at work (dialog boxes, start menu, or settings opening with no content in them), the unusability of a centered task bar (every time a task tray item refreshes and then rehides, all the docked icons shift over and then back in a distracting fashion), and just the ridiculously slow Windows Explorer. It's really alarming how bad Windows has gotten in these areas. This was the sort of stuff Linux GUIs used to be like, and now we've swapped roles.

 

[R-T-B]

This was the sort of stuff Linux GUIs used to be like, and now we've swapped roles.

No, linux GUI styling consistency is still a mess honestly. Windows just is too.

 

[sudothelinuxwizard]

i thought the emoticon added a bit of character. Shame to see it go.

 

[mechtech]

Ya still a BSOD, and just black........
Where's the imagination there?!?!

I mean they could have used
Burgundy
Burnt Orange
Burnt Sienna
or the classic Beige!!

mmmmmmm Beige Screen Of Death

come on MS you can do better

 

[Waldorf]

@Shihab
ignoring the rest of the "changes" that come with the switch, i prefer it to be dark, as im running low screen and also low room light brightness,
so the blue sod is always way brighter, even making me turn on the ceiling light before i try to read the screen.

 

[freeagent]

Still, I don't see these kinds of announcements regarding Linux.

Because it is not even remotely mainstream, and it is not pointed at a herd of sheople.

 

[ARF]

I have never heard about Android having this type of issues. Maybe Microsoft should retire its business and focus elsewhere?

 

[jesdals]

Well Ill gues we are going to save energy on BSOD in the future...

 

[lexluthermiester]

I have never heard about Android having this type of issues.

That's because it doesn't. Android crashes gracefully, usually by soft-rebooting the Kernel and UI but sometimes by restarting the device. Even Kernel panics result in a reboot/restart. This was deliberately engineered into the Google version of the Kernel.

Maybe Microsoft should retire its business and focus elsewhere?

Oh yeah, THAT'LL happen...

 

[Ruru]

That looks way better than the light blue BSOD which we've had in several Windows versions for now.

 

[ARF]

That's because it doesn't. Android crashes gracefully, usually by soft-rebooting the Kernel and UI but sometimes by restarting the device. Even Kernel panics result in a reboot/restart. This was deliberately engineered into the Google version of the Kernel.

I have never seen any of my Android devices for a decade to crash. They never crash, maybe an app or two do it, but the whole system to reboot, never.

 

[lexluthermiester]

I have never seen any of my Android devices for a decade to crash. They never crash, maybe an app or two do it, but the whole system to reboot, never.

Good for you. It does happen however.

 

[ARF]

Good for you. It does happen however.

Not as often as Windows, though. Maybe 1 time for Android to 100,000 times on Windows.
Which just reaffirms that Windows is a broken garbage of an OS that needs to be rebuild from the ground up.