Hmmm... ๐ค
this post was submitted on 28 Oct 2024
518 points (87.6% liked)
memes
16802 readers
3487 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've used Windows since the late 90s and I've had infinite blue screen loops before. probably a hardware issue but it's not like this fear is irrational.
Seemingly once a year my windows machine goes into an infinite loop of bluescreens. It's because of my wireless/bluetooth card everytime.
Windows will update the driver during one of it's bug updates, fail, then I have to go into safe mode and install the correct driver. Then it's business as usual.
Windows doesn't seem to care that I told it to never update my drivers, it'll still do it once a year.
For me, it's not that Windows updates my drivers during a big update. It's simply that Windows broke the driver while installing a big update.
I've had it happen where my Wi-Fi driver broke so it could only connect to an unprotected network. So I'd simply setup my phone as a hotspot and download the Wi-Fi driver from the manufacturer's website and reinstall it. That'd immediately fix the issue. Though, actually, that issue hasn't occured in years. The last time it happened, I think, was in the early years of Windows 10.