- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
I'm experiencing persistent errors with Intel Turbo Boost Max Technology 3.0 in the Device Manager. Here are the details:
I recently performed a fresh installation of Windows 11 on December 29, 2023.
Despite attempting to update the driver, the error persists.
The Intel Driver Support Assistant indicates that my drivers are up to date.
Initially, the technology worked, but the problem emerged a few days later.
My BIOS is current.
Intel Turbo Boost Max Technology (ITBM) is enabled in the BIOS.
The processor is overclocked using EVGA OC software, from 3.00 to 4.50.
Despite my efforts, all the information I find is outdated. I've been unable to locate turbo boost software on the Intel website, and Windows support offers generic instructions on driver updates. I have attached screenshots for reference. If anyone can provide assistance, I would greatly appreciate it as I've run out of ideas.
Actual Error
Device List
Window Services
Intel Driver Assist
It did work at some point.
コピーされたリンク
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
rg16, Thank you for posting in the Intel® Communities Support.
We will be more than glad to assist you with this matter.
Please attach the SSU report so we can verify further details about the components in your platform, check all the options in the report including the one that says "3rd party software logs":
https://www.intel.com/content/www/us/en/support/articles/000057926/memory-and-storage.html
Any questions, please let me know.
Regards,
Albert R.
Intel Customer Support Technician
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Here you go...TY for the reply.
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
rg16, You are very welcome. Thank you very much for providing the SSU document.
After checking the SSU report we can confirm, as you mentioned, that Windows* 11 was properly installed, that the drivers and BIOS are up to date, and all the components are properly recognized.
Regarding the Intel® Turbo Boost software and drivers we would like to let you know that Intel
By removing the drivers and applications, you haven’t lost any CPU features of Intel Turbo Boost Max technology, the Windows Operating System has the support natively and the Intel Turbo Boost Max technology is still a feature of our processor. Windows Operating System has the support natively for ITBM. The CPU feature Intel Turbo Boost Max is enabled in hardware and pCode. There is no way to enable or disable ITBM 3.0 feature of a processor as it is enabled in hardware and pCode. You can run a tool like Intel Extreme Utility to monitor the ITBM frequency of a CPU:
You can also get in contact directly with Microsoft Support for further details on this subject:
https://support.microsoft.com/en-us
Regards,
Albert R.
Intel Customer Support Technician
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Sure, I get that.
But the initial issue stands the device manager is saying the driver can't start and I don't have the software installed, never did as you said it has been taken down.
So, Just let it be?
Have that one lonesome driver flagged in the device manager?
Did Microsoft screw up the device manager?
Are we hoping Microsoft picks up on it and magically adds a fix in one of their many many many updates?
I know the machine is running fine, by my OCD can't have that one driver flagged and no one has an explanation.
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
I guess I'm not understanding.
I remove the driver.
I don't have the ITBM program.
The issue now becomes an unknown device under the device manager.
That's intel hardware ID correct?
So, how do I get rid of that device not having the proper drivers?
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
I went ahead and disabled ITBM 3.0 support under the bios. That took care of the pesky unknown driver and ITBM is still running under Windows services, go figure.
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
rg16, Thank you very much for your response.
Perfect, it is great to hear that after disabling the ITBM 3.0 support under the BIOS the unknown driver was removed. Yes, the ITBM will still run under Windows services since the Windows Operating System has the support natively for the feature. Thank you also for taking the time to share the solution, we are sure it will be very useful and helpful for all the peers looking at this thread.
Any other inquiries, do not hesitate to contact us again.
Regards,
Albert R.
Intel Customer Support Technician
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Please allow me to communicate on behalf of our friend and original poster, rg16 as I am also experiencing the same issue on two of my rather expensive work stations.
It should be clear to the reader that nothing here has been accomplished in the way of remedy.
The ITBM issue is still being recognized in Windows device manager whether the driver is installed or not installed. The issue remains unsolved. There is no solution and we need not pretend that there is one.
The issue is this: There is a bang in the device manager that requires appropriate attention. There should be a way to eliminate this bang, either by way of some microcode, a Windows Update, or some type of hardware mitigation. Our friend, rg16, has been offered none of these options and I'm guessing the reason for this is simply because they are not available.
Allow me to be very clear on this as I fully concur that sometimes language barriers exist. The matter is not solved. That bang will return again, and again, and again. Just uninstalling a driver in device manager to leave some vestigial "unknown device" dangling in the tree is not a solution nor is it a resolution. The matter is not resolved and the response to it offered by Albert R. is not nearly of any benefit to those who are seeking a solution to the problem.
The reality:
ITBM 3.0 is broken. It is broken because Intel discovered a problem with it and pulled the software for it for security reasons. Then Intel left us hanging without any way of removing this unsightly blemish from the device manager. They simply swept it under the rug. That is the reality. Very callous, very sloppy, and very unprofessional of them I should think. No remedy or "solution" is being offered here.
Perhaps Intel might consider fixing the problem by offering Windows some microcode as they have in the past for other CPU issues?
Surely Intel could afford to offer us this much relief. As a long time Intel user I would like to see this matter escalated. The device manager should be free of bangs and "unknowns" as this presents yet another security issue.
