misk@sopuli.xyz to Linux@lemmy.worldEnglish · rok temusystemd 255 Released With A "Blue Screen of Death" For Linux Systemswww.phoronix.comexternal-linkmessage-square7fedilinkarrow-up147arrow-down10
arrow-up147arrow-down1external-linksystemd 255 Released With A "Blue Screen of Death" For Linux Systemswww.phoronix.commisk@sopuli.xyz to Linux@lemmy.worldEnglish · rok temumessage-square7fedilink
minus-squareGrass@sh.itjust.workslinkfedilinkEnglisharrow-up2·rok temuLol imagine if windows bsod had any meaningful information (specifically non EoL versions)
minus-squarenoodlejetski@lemm.eelinkfedilinkEnglisharrow-up5·rok temuit doesn’t matter, regardless of the error code the only solution you find will be “run sfc /scannow and if it doesn’t work, reinstall Windows”
minus-squareKepabar@startrek.websitelinkfedilinkEnglisharrow-up2·rok temuThe actual information you want for troubleshooting is in the mini dump and it’s actually super useful. Tracking down the cause of a Windows BSOD is pretty easy.
Lol imagine if windows bsod had any meaningful information (specifically non EoL versions)
it doesn’t matter, regardless of the error code the only solution you find will be “run
sfc /scannowand if it doesn’t work, reinstall Windows”The actual information you want for troubleshooting is in the mini dump and it’s actually super useful.
Tracking down the cause of a Windows BSOD is pretty easy.