Often Windows blue screens would be associated with hardware changes or driver updates. This one happened a couple times this morning on a previously stable machine that hasn't had any hardware changes in some time, so we're presuming this one will down to a Windows update.
This is a Hewlett Packard machine running Windows 10 Pro 64-bit - it's a couple of years old with a reasonable spec (Intel Core i5 with 12GB RAM) and has been problem-free so far.
We're on first release for Office 365 updates and the semi-annual release for Windows 10. The HP Support Assistant runs in the background and is configured to install updates automatically.
So far this combination has worked pretty flawlessly.
Other than the odd reboot when Chrome or Edge exhausts memory with too many tabs open this machine hasn't had much in the way of problems.
Those who have worked around PCs for a while will know that current hardware and Windows 10 (in spite of well-publicised recent issues with updates) is much more reliable than even a few years ago.
So much so, in fact, that getting a Blue Screen of Death (BSOD) is something of a novelty these days.
That's not to say that it's not a real pain, but at least we get a bit more of an error message these days... Some of us can still remember having to use a flip camera to video the flash screen with an error on a machine with a terminal BSOD loop then freezing the frame to get the HEX error code to look up!
It would be difficult to get definitive stats on this, but my impression is certainly that much less time is devoted to poking around the registry, updating drivers and especially installing and configuring printers.
There are, of course, still plenty of user issues, security problems and malware/trojan/ransomware issues to deal with, but broken hardware and broken Windows is much less frequent than it used to be.
No comments:
Post a Comment