this post was submitted on 07 Dec 2023
47 points (100.0% liked)

Linux

8314 readers
53 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Grass@sh.itjust.works 2 points 1 year ago (2 children)

Lol imagine if windows bsod had any meaningful information (specifically non EoL versions)

[–] noodlejetski@lemm.ee 5 points 1 year ago

it 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"

[–] Kepabar@startrek.website 2 points 1 year ago

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.