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