Thread 105729458

BREAKING NEWS. MICROSOFT IS KILLING OFF THE BLUE SCREEN OF DEATH.

Replacing it with a more, clean, big BLACK screen of death.

>oh no i won't get flashbanged anymore when my pc crashes
ok? i haven't had a single crash since w8.1

I can't remember the last time i've had an actual crash on my linux machine

The soul is officially gone

>>105729472
The only crash I have had recently was my AMDGPU driver hard locking my system because of a vkd3d issue that blew up my driver.

>>105729458 (OP)
No Guru Meditation no care

>>105729505
Needless to say, it has been fixed and no more vkd3d crashing AMDGPU driver.

>Apple steals aero
>Microsoft steals this boring kernel panic pop up
Not a fair trade, steal something cool from them.

Even less info? great!

Why didn't they name it NSOD?

>>105729458 (OP)
MICROSOFT GOT BLACKED HAHAHAHAHHAHAHAHAHAHAHAHAHAHHAHAHAHAHAHAHAHAHAHHAHAHAHAHA

blue screen is better because it immediately tells you it's a windows error and not something worse

Does blue light hurt Indian eyes or something?

They're trying to catch up with Linux.

>>105729657
obsessed

>>105729507
1980s sovl

The only time I've ever had "random bsods" was because my hardware was just fucked up. I won't be getting bbsod either. I also won't be upgrading, ever. Hopefully Linux figures out what init, DE, toolkit and display servers are by the time I don't upgrade to the next Windows.

>>105729458 (OP)
>breaking news
>three months ago

>>105729472
I can't remember either. Because it never happened, I actually don't know what a kernel panic looks like.

f

i haven't seen a blue screen in almost a decade. last time i had a severe gpu crash was a few months ago but the system didnt even reboot and the game didnt even crash either. it just paused for a few seconds and kept playing but with the amd timeout box in the middle of the screen.

>>105729458 (OP)
classic Microshit, have to make everything worse
>>105729472
linuxfags are like women/trannies, can't go 5 min without attention

>>105729507
No problem, just reboot within seconds

>>105729458 (OP)
>making people associate black with negativity
based, I guess

>>105729472
>A stop job is running

>>105729472
I sometimes get UI crashes after I updated to Ubuntu 24.04LTS. They were triggered by clicking on the Steam store page while the window had been open for a while in the background while lurking on Chrome. The crash would force me to logout and be fixed upon login. Hasn't happened for a couple weeks now at least.

>>105729633
>>105731058
>>105729578
It actually tells what driver/system program crashed to cause the bsod now. The loss of blue is regrettable but it has more information now, kek.

I won't be updating from my Win10 ltsc but this is literally the only functionality upgrade microsoft has done in years.

>>105733333 (Wasted)
No it doesn't, and never has.
The "crashed in driver X" has always been a guess: it's simply where the faulting instruction or memory access occurred. While it's possible for there to be a correlation, I could trivially write a driver that pokes the memory space being used by your driver - and boom, "BSOD in 10573333.SYS".
This is actually much of the reason Microsoft removed the name of the driver from BSODs: they got sick of OEMs bitching them out for some random unrelated driver partying on their kernel memory, then Window crashing with "fault in BIG_OEM_NAME.SYS".

>>105729458 (OP)
>posts a screenshot of a tweet
>doesn't post a link to said tweet
>doesn't post shown link

>>105729472
Doesn't work on my machine.
Had a crash just yesterday.
Have crashes once or twice a month on average.

>>105729739
those have always been fucking worthless unless you have fucking serial wired in your PC permamently

>>105729472
crashes all the time with image/video gen
works fine on windows
cope

>>105729472
i just moved to debian from windows
been using it for 6 months
never had a full system crash but the two times i ran out of memory the computer got really slow
the first time i fucked up my code and accidentally tried to load a 50gb file to ram
the second time was a random memory leak while using wine
first time i just rebooted
second time i just tried to end the process and after like 10 minutes it closed and everything went back to normal

>>105733517
>The "crashed in driver X" has always been a guess:
It's not correct all of the time, but it's correct often enough to be useful. They shouldn't have removed it.

>>105736517
Good thing all PCs ever came with a COM port.