109
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Nov 2024
109 points (96.6% liked)
PC Gaming
8668 readers
554 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
Hmmm. I don't really like Windows myself and haven't setup a machine without for me in one a decade. But neither my work "development" laptop (in quotation marks because I'm not a developer) nor a mini PC I installed for my dad ever had bluescreens. They can still happen, of course... but it almost seems to require effort with really bad drivers or broken hardware.
The obvious Windows issues nowadays are a different category from 20 years ago in my opinion.
They still happen even on W10, but we support a lot of customers, that have a lot of users, so I probably encounter them more than a person with one or two PCs ( just statistically)
Often it were would be network or monitor connection.
HP workstations laptops I could blue screen consistently by plugging in my phone set to USB network tether. Immediate NDIS bluescreen. I don't blame windows 100% for that, it just didn't like seeing a new network device in the Kernel