@[email protected] to Software [email protected] • 6 months agoYellow screen of death in the wildprogramming.devimagemessage-square14fedilinkarrow-up1129arrow-down11
arrow-up1128arrow-down1imageYellow screen of death in the wildprogramming.dev@[email protected] to Software [email protected] • 6 months agomessage-square14fedilink
minus-square@[email protected]linkfedilink37•edit-26 months agoIt’s an Orange Screen of Death, which is usually caused by driver conflicts (especially GPU driver issues). Yellow Screen of Death used to refer to the ASP .NET one (eg see the screenshot here: https://stackoverflow.com/questions/5443334/asp-net-hacking-the-yellow-screen-of-death) but it’s not really a thing any more since it was only in legacy .NET Framework versions.
minus-squareViklinkEnglish7•6 months agoHuh, I didn’t realise the *SOD colour was dependant on the bugcheck context. I always thought it was the OS, like retail windows, insider, Xbox OS etc. Good to know
It’s an Orange Screen of Death, which is usually caused by driver conflicts (especially GPU driver issues).
Yellow Screen of Death used to refer to the ASP .NET one (eg see the screenshot here: https://stackoverflow.com/questions/5443334/asp-net-hacking-the-yellow-screen-of-death) but it’s not really a thing any more since it was only in legacy .NET Framework versions.
Huh, I didn’t realise the *SOD colour was dependant on the bugcheck context. I always thought it was the OS, like retail windows, insider, Xbox OS etc.
Good to know