Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

bleepingcomputer.com

Post reply on HN
Print view View original

131–140 of 150 posts

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#131

Post by hulitu »

Tijdreiziger wrote: post #30
whalesalad wrote: post #11

My experience with Windows 11 has been roughly bug free - but it’s not a pleasant place to be. Installing is a nightmare too with the online account requirement. You can circumvent with a shell but still annoying. I’ve been much happier with Debian 12 and KDE for my primary workstation. I can’t think of a compelling to use windows outside of gaming.

> I can’t think of a compelling to use windows outside of gaming. - Office - Adobe - Ableton - Visual Studio

> - Ableton

- Visual Studio

Why would someone use both in a corporate env ?

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#132

Post by Already__Taken »

tw04 wrote: post #17

I think people might need to put the pitchforks down. It's a preview release, and we have 0 information on the systems in question. You can easily avoid the issue by not participating in the early release program. Finding issues like this is literally why the preview program exists. Should they have caught this with internal testing? Maybe, we don't have enough information to know.

I think if you manually hit widows update, you get the preview updates. no extra opt in

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#133

Post by hulitu »

jeroenhd wrote: post #16
nerdponx wrote: post #3

> The company also urged users encountering these BSOD errors to file a report using the Feedback Hub. > To do that, you will have to go through the following steps: > Launch Feedback Hub by opening the Start menu and typing "Feedback hub", or pressing the Windows key + F Something seems off here.

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.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#134

Post by hulitu »

WhereIsTheTruth wrote: post #9

Most popular OS on planet earth and they can't afford testing their software on popular CPUs These execs and managers should be criminally charged

> Most popular OS on planet earth and they can't afford testing their software on popular CPUs

Testing is expensive. That's what users are for.

Just look at the SW made by MS and Google. It looks that they work only based on change requests. If the bugs are not rewritten, they are fixed only when there is a change request.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#135

Post by hospitalJail »

at_a_remove wrote: post #110
hospitalJail wrote: post #89

Earlier quoted context omitted.

>- Office >- Adobe >- Ableton >- Visual Studio Find alternative software. If those companies aren't compatible on Linux, use one that is. Make sure you send them an email explaining why you are canceling your subscription.

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.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#136

Post by hulitu »

bitwize wrote: post #2

When Microsoft says "your CPU needs to be this high in order to run Windows 11", perhaps listen to them eh?

> "your CPU needs to be this high in order to run Windows 11"

We besides the user, even the CPU has to be on drugs to run Windows 11, something is teribly wrong with this world. /s

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#137

Post by justsomehnguy »

tuetuopay wrote: post #111
justsomehnguy wrote: post #107

Earlier quoted context omitted.

Yep, just as I said in the previous comment: everyone is at fault but for sure it wasn't the vendor of the device! How the vendor could be the culprit in doing something what would cripple the boot/install of the OS? Nonsense!

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 which couldn't be loaded at the running install, because for somegodfuckingreason it did shenanigans when loaded 'online' and Windows couldn't use it as the install destination.

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.

There is no such thing as generic driver for a hundreds and thousands of variants of some vendor specific device if the vendor did not provided such driver.

Your loved Linux works there only because the kernel module which supports Intel ICH\R chipset (which provides iRST) has those bazillion of PCI VEN/DEV IDs assigned to it and this is why it works 'out of the box' on Linux kernel. Intel NEVER provided such driver for Windows and never would.

Eg: there is a thing called `HPE Smart Array SR Gen10`. It's a series of RAID controllers made by HPE.

Except `HPE Smart Array S100i SR Gen10 SW RAID`, aka S-class. Notice `SW` there? That's just a regular Intel ICH/R. You can manually install Intel ICH/iRST driver on that `HPE controller` and it would work, because it's just a regular Intel ICH/R. You know what wouldn't happen? Windows wouldn't install `the default` Intel ICH driver on it, because:

there is no such thing as `the default SATA` driver

there is no such thing as `the default Intel SATA` driver

all `Intel SATA` drivers built-in in Windows install media do have the PCI VEN/DEV IDs listed for INTEL (VEN8086), not HP/E, DELL, Lenovo or whoever.[0]

You can shit on Microsoft and Windows all you want, but the problem here is strictly with the vendor, Intel.

As soon as Intel would provide MS with the `default Intel SATA` driver what would have all VEN/DEV combos for all their licensed and white-labeled controllers - you would be able to install Windows client SKUs on all these controllers without slipstreaming the drivers in the install media.

Source: I know things, I lost too many hours of my life wrestlning with Intel ICH/R

[0] ffs, just open the .inf you slipstreamed and look for IDs there.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#138

Post by justsomehnguy »

callalex wrote: post #122
justsomehnguy wrote: post #109

Earlier quoted context omitted.

> Those are pretty standard Intel cards installed on laptops with Intel CPUs. ax201 or something If they were 'pretty standard' then they would be in the default list of drivers shipped with install media. If they weren't in the install media then: your media is older than the drivers your device isn't 'standard' device vendor doesn't give a shit if you can reinstall Windows and get the working WiFi out of the box >…

Your combative behavior here is entirely unwarranted. The only person blaming random chief executives here is you. If the drivers work fine in a standard Linux install, it is obviously not some obscure hardware setup.

Repeat after me: Linux has a different driver model than Windows.

If you don't know why Linux-way doesn't work in Windows and you want to know - you can look at my sibling comment.

> Your combative behavior here is entirely unwarranted

What is really unwarranted is 'but it works in Linux1111' without thinking.

> If the drivers work fine in a standard Linux install

Ah, yes, work so good you need to disable RST completely to install Linux: https://askubuntu.com/questions/1233623/workaround-to-instal...

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#139

Post by vladvasiliu »

justsomehnguy wrote: post #109
vladvasiliu wrote: post #67

Earlier quoted context omitted.

Those are pretty standard Intel cards installed on laptops with Intel CPUs. ax201 or something. If "nothing-ever-works-without-fiddling" Linux is able to ship drivers for that card and work out of the box, I don't see why windows couldn't ship with drivers for that, especially since they seem to get updates via Windows update, so ms has them. Plus, if you're going to force people to use an internet account, maybe mak…

> Those are pretty standard Intel cards installed on laptops with Intel CPUs. ax201 or something If they were 'pretty standard' then they would be in the default list of drivers shipped with install media. If they weren't in the install media then: your media is older than the drivers your device isn't 'standard' device vendor doesn't give a shit if you can reinstall Windows and get the working WiFi out of the box >…

> 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 Intel does not give a fuck.

Fair enough. 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? This has worked ever since I bought the PC three years ago. So no, the devices "aren't brand new", intel didn't "just send them to MS yesterday" or "not at all". And if I manually install the drivers out of band by downloading them from intel's website, windows will still install its own over them, even when they are older.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#140

Post by justsomehnguy »

vladvasiliu wrote: post #139
justsomehnguy wrote: post #109

Earlier quoted context omitted.

> Those are pretty standard Intel cards installed on laptops with Intel CPUs. ax201 or something If they were 'pretty standard' then they would be in the default list of drivers shipped with install media. If they weren't in the install media then: your media is older than the drivers your device isn't 'standard' device vendor doesn't give a shit if you can reinstall Windows and get the working WiFi out of the box >…

> 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 no, the devices "aren't brand new", intel didn't "just send them to MS yesterday" or "not at all".

Well, yes.

Now the question why these aren't included in the OS. Don't have Win11 at hand (and probably wouldn't at least for some time, lol).

Back in the day MS gathered info about the most common devices at the market, to include them in the OS distro. So with a wireless chipset made in '19 the question is who to blame, vendor or OS mfg. Considering how hostile Intel to the customers I wouldn't be surprised it's them. BTW you can open Device Manager pretend to replace the driver, select 'I would select manually' and see all the drivers OS has. On your running system you would see those you installed too, but on a clean system you would see only bundled ones.

On my notebook I have a Realtek NIC, so the Intel drivers are the ones what was bundled with Win10 install media (and maaaybe some updates?) and I have there:

    Intel(R) Wi-Fi 6 AX101
    Intel(R) Wi-Fi 6 AX200 160MHz
    Intel(R) Wi-Fi 6 AX201 160MHz
So... can you post the PCI ID of your card? It wouldn't do a shit for you but maybe there is something there. It can be found in Device Manager, open the properties of the NIC, Details tab, Hardware Ids.

> I always create a new USB drive when I reinstall

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

> And if I manually install the drivers out of band by downloading them from intel's website, windows will still install its own over them, even when they are older

Or something had rotten in Seattle or somehow Windows bundled drivers are more specific ones than the ones from the vendor site.

I heard about that but I don't remember ever witnessing this myself. If anything, I needed to that manually, because Intel drivers for 'Intel(R) Wireless-N 7260' are so shitty what the ones bundled with Windows (with Intel copyright from 2011) are way more stable (but not stable enough, sigh) than ANY later revisions from the Intel site.

ADD:

Okay, for the sake of it: I've got my hands on Win11 and it DOES have some drivers for AX201: https://imgur.com/a/ozob6kM

So the question about the PCI ID of your card.

Post reply on HN