This bundle installed without issue (have just rebooted), and it [correctly] didn’t pave over the newer Intel drivers installed by the Intel® Driver & Support Assistant, however I got the following notification from Intel:
Uninstall Legacy User Interfaces
Intel® Graphics Software detected legacy versions of graphics user interfaces are installed on your system. It is highly recommended to uninstall legacy versions of software such as Intel Arc Control and Intel Graphics Command Center from Windows via the add/remove software menu while IGS is installed. Having multiple user interfaces configured at once may cause conflicts.
The Intel Graphics Command Center was installed today, so will remove that. This could be an Intel installer problem (not looking for newer apps), or something you should look at in the Driver Bundle installer.
I uninstalled the Intel Graphics Command Center that was installed today without issue. The “Intel(R) Graphics Software & Drivers” app was also installed today, but Uninstalling it from add/remove would have also uninstalled the current 32.0.101.7085 for 11th-14th Gen Intel® Core™ Processor Graphics driver, so I left that package.
P.S. A Windows Update scan installed “Intel - SoftwareComponent - 1.71.99.0”, but I hadn’t run that scan immediately before running the Framework bundle, so it may have been unrelated and just waiting for a WU scan.
This issue does not appear to be driver-related. We have been actively trying to replicate the 400MHz capping on our 12th Gen systems, but have not been able to reproduce it so far. We are continuing our reproduction and testing efforts to get the necessary logs for further debugging.
As my (not primary) role as a 3rd level support engineer I would get directly in touch with a few users who experience this problem, ask for (specific) logs, ask them to collect information while/before the problem occours (and tell them how to do it), maybe even provide some tools for further analyses you need …
I mean … There are users who are saying they can reproduce it … so … why not just ask them? I’m pretty sure, at least some of the users here are happy to help.
But you did a great job at sitting it out … if you are still trying to reproduce it, you are either really slow, don’t have much time for this problem, just telling it to keep users calm or Framework is waiting for the moment to say “12th Gen. Intel is too old to support it”.
I know it’s not driver related. I’m being facetious.
Keiran confirms Framework have reproduced the issue, but of course he stopped responding.
If you couldn’t reproduce it, how did you supposedly write BIOS updates that fixed it? (they didn’t). As @mahe says, you really must be putting minimal effort in to not notice it. I’d really suggest aligning your story with the rest of the staff because it smacks of dishonesty when the message is different each time the staff is asked.
The attitude of framework regarding this issue seems to be in extremely bad faith. “Contact support” isn’t a remedy, they will tell me to go and buy a new board.
We’re here to remake consumer electronics to respect people and the planet. Unlike most products, ours are open for you to repair, customize, upgrade, and own at the deepest level.
I don’t feel respected, nor do I have the ability to fix a computer that you didn’t build right.
Just because your machine shows a problem doesn’t mean every machine does. You just happen to have a CPU/memory/mainboard/whatever set of chips that happens to show an edge case and doesn’t mean every machine shows the same edge case.
So get off your high horse and provide the information they want and you will have a much better chance of getting a fix.
You’ve quoted Quin_Chou stating that FW has reproduced the issue “under high load in low fail rate”. That “low fail rate” is key, and it means they can confirm the issue internally, which is very useful to escalated support. But it’s not conducive to effective troubleshooting, so it makes sense they’d continue trying to find a reliable reproduction of the issue. Cooperative user feedback helps here.
If they’re being inconsistent about reproducing this issue, what you quoted doesn’t show it.
I applied the updated driver bundle to my FW13 (12th gen, i5-1240p). Everything was smooth and I think it made my fingerprint reader reliable; it’s been hit-and-miss since forever.
I also have some version of the issue with the FW getting stuck at 400 MHz. I think it’s just plain thermal throttling, and cleaning didn’t resolve it. The driver bundle and latest BIOS didn’t seem to affect it. I’ll be applying PTM once I find time.
How many user accounts do you intend on creating until you realise you need to change your approach and stop being - as the numerous notes on the accounts you’ve created say - “combative”?
I just had an unrelated power failure during connected standby (Windows 11) and Event Viewer is showing a bunch of critical errors I hadn’t been seeing in the past.
I installed the Beta BIOS 3.20 a day later but the Event Viewer shows the issue started first but is continuing. I have verified the version of the faulting driver is the one in this driver bundle (but is not new per the notes above), and Device Manager shows the driver installed on 9/15/2025.
I suspect this is a change in Windows that triggered the failures, however as far as I can tell from searching these drivers are customized for the OEM hardware, so thought I should give Framework a heads-up.
Description:
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2e35aaeb-857f-4beb-a418-2e6c0e54d988}" />
<EventID>10120</EventID>
<Version>1</Version>
<Level>1</Level>
<Task>64</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000000</Keywords>
<TimeCreated SystemTime="2026-06-24T10:33:22.0648129Z" />
<EventRecordID>998150</EventRecordID>
<Correlation />
<Execution ProcessID="1408" ThreadID="1560" />
<Channel>System</Channel>
<Computer>redacted</Computer>
<Security UserID="redacted" />
</System>
<UserData>
<UMDFHostProblem2 xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event">
<LifetimeId>{dbc403d2-3b94-4347-9271-0767e088c378}</LifetimeId>
<Problem>8</Problem>
<DetectedBy>2</DetectedBy>
<ActiveOperation>0</ActiveOperation>
<ExitCode>3221226356</ExitCode>
<Message>0</Message>
<Status>4294967295</Status>
<InstanceId>PCI\VEN_8086&DEV_461D&SUBSYS_0002F111&REV_02\3&11583659&1&20</InstanceId>
<HardwareId>PCI\VEN_8086&DEV_461D&SUBSYS_0002F111&REV_02</HardwareId>
<ServiceName>ipf_umdf2</ServiceName>
</UMDFHostProblem2>
</UserData>
</Event>
I would be happy to provide more information if it would help identify the cause of the crash so you could work with Intel and Microsoft to get this fixed. I couldn’t fine a Memory.dmp or minidump but Reliability Monitor but Reliability Monitor (from one of the faults today) says “Report sent” and “Fault Module Name: StackHash_2ddf”.
Source
Windows Driver Foundation - User-mode Driver Framework Host Process
Summary
Stopped working
Date
7/7/2026 1:32 PM
Status
Report sent
Description
Faulting Application Path: C:\Windows\System32\WUDFHost.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: WUDFHost.exe
Application Version: 10.0.26100.8737
Application Timestamp: 1a6e8a15
Fault Module Name: StackHash_2ddf
Fault Module Version: 10.0.26100.8737
Fault Module Timestamp: 7b64c48f
Exception Code: c0000374
Exception Offset: PCH_BF_FROM_ntdll+0x0000000000160BB4
OS Version: 10.0.26200.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 2ddf
Additional Information 2: 2ddf55e72ffbfb88b9730ab9ff0edc22
Additional Information 3: c989
Additional Information 4: c9899205649f9df9395bc05d04255381
Extra information about the problem
Bucket ID: 2ad89a0cc0e677b10305900844c72371 (1370660026792223601)