So I would be interested in what you are doing, and especially what you are doing. You will practically never see this on compatible HW (i.e. certified for the given OS) and functional (preferably LTS version, i.e. for graphic studio version) drivers (if there is no HW problem such as bad cooling, blown capacitor, etc.), respectively very minimal. In general, IMHO, the stability of today’s OS is at a relatively very good level (for what users do with them and to what state they are able to get them thanks to various CCleaners and other “tuning” utilities :D)Note If, of course, you work on machines where users (often with admin rights) install and uninstall almost anything for many years or run various modified Win to run on the given (unsupported) HW at all or use, for example, old drivers from previous versions of Windows for old printers/plotters/ scanners, etc., then of course there is nothing to be surprised about – but that is no longer the fault of the OS, but of the article between the keyboard and the chair 😀Personally, I always read the log and dare to say that in 99% of cases it is wrongly chosen HW (memories with incompatible timing, etc.), badly installed HW (insufficient cooling) or ill-advised installation of something – usually a clean installation will solve it without problems and the advice to they “didn’t do it and didn’t install it” which almost never falls on fertile ground anyway :D.
Sometimes someone releases problem drivers (that’s why I strongly recommend LTS, the effects on performance even in games are not particularly important and IMHO it pays off 100x in the form of a stable system) but somehow that’s not MS’s fault anymore. Cases when MS breaks the OS to blue death with its own update, not that they don’t happen, but they are really very exceptional.
The opinion was modified 6 times, the last time on 04/21/2023 11:46
