Live data from Hacker News

New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

bleepingcomputer.com

141–150 of 150 posts

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#141

Earlier quoted context omitted.

well that's just like your opinion man

aluminum chassis master race.

Which to me makes very little sense in a "laptop". It's pretty good at helping the device stay cool, but you will regret wearing shorts should your processor or GPU really need to get work done, should you actually have it on your lap.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#142

Earlier quoted context omitted.

> And again, where did you got your install media for Windows? Directly from https://www.microsoft.com/software-download/windows10 ? Somewhere else? Somewhere else: https://www.microsoft.com/fr-fr/software-download/windows11 This was Windows 11, downloaded in June 2023 or something like that. I always create a new USB drive when I reinstall. > your media is older than the drivers No it's not, see below. > Because Int…

(see the addendum) > Somewhere else Heh. > Then how come windows magically knows to install all those drivers, Wi-Fi and touchpad, if I plug in a USB network adapter, and it only connects to Windows update Because it asks WU about all PCI\VEN&DEV&SUBSYS&REV found in the system and WU responds with the specific drivers it has for these devices . Remember, there is no 'generic' drivers in Windows, like in Linux. > So n…

> Do you just download an .ISO or do you use the 'Installation Assistant'? There are some shenanigans with that tool.

I'm pretty sure Linux doesn't have "generic" wifi cards. See all the issues people have getting to work brand-new models. I had already seen the AX201 in a separate machine for some time before buying this laptop, so it wasn't brand-new when I first tried installing Windows. Didn't check the PCI IDs to confirm it was precisely the same, though.

I don't have that specific PC on hand to check the IDs right now.

For installing, I create the USB drive with the "media creation tool" I download right before from that site. I only use the direct ISO download to install on VMs, since my usual approach of writing it with dd from linux doesn't work for some reason.

I've noticed the driver reinstall issue because at one point, there was some kind of issue with my external monitor which worked with the Intel drivers but not with the Windows Update ones, and every so often the display output would break again until I manually reinstalled the ones from the Intel site. The Windows Update drivers have been fine for a few months now. Wi-Fi never had any issue once it got going after the first reboot and Windows update run.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#143

Earlier quoted context omitted.

That's really not an option for some industries. Mine, for example. When you're in a sufficiently niche market, you can't just "yay open source" your way out of the issue.

What industry? And not everything on Linux is open source. My 3D printer is proprietary stuff.

Emergency services.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#144

Earlier quoted context omitted.

The vendor? Ha! Let me laugh. Would this have tripped on some obscure device specific to Dell laptops, sure, I would understand. (like their blimey fingerprint reader). But this is the standard NVMe controller on this generation of intel CPUs. The drivers are common for _most intel platforms_: the Intel Rapid Storage Technology. As somebody else pointed out, Linux fares much better in this space. All devices are prop…

> Intel Rapid Storage Technology. This is a SATA AHCI/RAID controller. It has nothing to do with NVMe. Also iRST was (and looks like still is ) the most troublesome driver for Windows since it's introduction: there are bazillion of variants and vendor sub-variants with different VEN/DEV IDs, so it's CAN'T be identified by some generic driver! And yes, it was (and from your description - is) the one stupid driver whic…

>> Intel Rapid Storage Technology. > This is a SATA AHCI/RAID controller. It has nothing to do with NVMe.

Yet it was somehow required to use the NVMe drive in this machine. This is braindead.

> This is not (and were not) a problem with any other SATA and SAS controller I ever encountered, from cheap-ass Silicon Image ones to $2000 LSI/HPE ones. Only Intel, only ICH/R.

Learnt this the hard way on a previous motherboard I had with two sata controller, the native Intel one, and an additional Marvell one. Sanity would encourage to use the intel one, except for all those friggin issues.

As for Linux, I know why it works :) But it always amazes me that this FOSS project can ship all those IDs, quirks and all, but not one of the largest company on the planet. What a time to live where Linux has less driver issues than Windows.

Thank you for all the details, I did not know iRST was such a hot mess. It's not that new, one would have guessed shit would have been figured out since. But no. Oh well...

Btw sorry for the tone, I thought by "vendor" you meant Dell and not Intel. They produce some of the worst driver I ever had to work with. Don't get me started on their drivers for the E810 line of datacenter network adapters.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#145

Earlier quoted context omitted.

Windows runs the largest of enterprises. Very few go without at least Active Directory.

Fortunately the enterprise IT seems to be slowly waking up to the realization that AD is just LDAP wrapped in a thick layer of (very expensive) Microsoft epoxy and glue. OSS is alive and well in the enterprise!

[deleted]

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#146

Earlier quoted context omitted.

Windows runs the largest of enterprises. Very few go without at least Active Directory.

Fortunately the enterprise IT seems to be slowly waking up to the realization that AD is just LDAP wrapped in a thick layer of (very expensive) Microsoft epoxy and glue. OSS is alive and well in the enterprise!

First off, it's primarily kerberos with LDAP frosting. Kerberos is what makes the AD world go round and for much of what happens in windows its purely resting on tickets and the PAC, not LDAP queries. Second, there's a lot of special bits that others do not replicate.

For instance shadow rights / MIM / PAM does not to my knowledge have an OSS equivalent.

Windows Hello for Business is the only moderately secure take on biometric auth into kerberos that I have heard of.

LAPS is the only secure, native LDAP take I have heard for managing root passwords, which fills a big compliance need for a lot of orgs.

And there is quite a lot about GPO that works wonderfully when paired with sssd, e.g. access control.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#147

Earlier quoted context omitted.

Battery aside apple laptops are rather lame.

Battery's a pretty big fucking deal on a laptop tho.

Good news, the laptops with the longest battery life aren't Macs.

Better news, installing Windows on Intel Macs improves battery life under common use cases.

Best news, Linux on that same Mac is even longer.

Hilariously, as much as Chromebooks suck, there are many Chromebooks that have half the Wh of M1/M2 99Wh Macbooks, cost half as much, and meet or exceed battery life under common tasks (implying they're both twice as efficient per watt, and twice as efficient per dollar). These Chromebooks can run Linux, and aren't stuck with ChromeOS.... so if you're really into ultra-thin laptops with excessive battery life, well, they're an option.

I also semi-recently saw a review for the LG Gram 17, an Intel laptop that has 3/4th the Wh of Macbooks, yet has the same battery life in common tasks, and a 17 inch (!) screen; costs about the same as a Macbook. So, even with the Intel CPU holding it back, its keeping up with those Macs.

So yeah, Apple hasn't kept up with the battery life game at all, another myth cranked out by the FUD+FOMO Apple PR machine.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#148
post #133

Earlier quoted context omitted.

After several (three, I think?) boot failures, Windows will automatically restart to recovery mode and use system restore to undo the last update. This fixes the BSODs until you install the updates again.

> This fixes the BSODs until you install the updates again. But _you_ don't install updates. The thing autoupdates itself.

That depends on your setup, but updates that have been rolled back usually don't get auto-installed for a while exactly for this reason.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#149

Earlier quoted context omitted.

Ah, yes, Gates personally banned the drivers for this 2020 WiFi cards. Or maybe it was Intel who did a bazillion of cards with a minor diffs and/or didn't ask MS to add this flavour to the default driver set, shipped with Windows install media?

I haven't used a device that Windows didn't ship drivers for In twenty years !

Firewire...

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#150

Earlier quoted context omitted.

(see the addendum) > Somewhere else Heh. > Then how come windows magically knows to install all those drivers, Wi-Fi and touchpad, if I plug in a USB network adapter, and it only connects to Windows update Because it asks WU about all PCI\VEN&DEV&SUBSYS&REV found in the system and WU responds with the specific drivers it has for these devices . Remember, there is no 'generic' drivers in Windows, like in Linux. > So n…

> Do you just download an .ISO or do you use the 'Installation Assistant'? There are some shenanigans with that tool. I'm pretty sure Linux doesn't have "generic" wifi cards. See all the issues people have getting to work brand-new models. I had already seen the AX201 in a separate machine for some time before buying this laptop, so it wasn't brand-new when I first tried installing Windows. Didn't check the PCI IDs t…

Got my hands on the PC in question. The full string of the ID is PCI\VEN_8086&DEV_A0F0&SUBSYS_00748086&REV_20

Fun fact: if I look for drivers, in the "recommended drivers" list there are two drivers by Intel and one by Microsoft. https://i.imgur.com/jpghrgd.png

Post reply on HN