Memory integrity forced off "incompatible driver" STTub30.sys (STmicroelectronics)

I tried all of the suggestions listed above with exception of the deleting the OEM 77.Inf file as on my computer, it was a bluetooth driver from intel and not the SStub30.sys driver. I uninstalled Steeleseries GG and the driver in question was still there and the core isolation still could not be turned on. I found the driver on my C drive and contemplated uninstalling it and deleting it, but decided against it as I am not sure as to what piece of hardware this driver is being used for and do not want to uninstall something that could make my system unstable when it is running beautifully at the moment, but for the core isolation. I have tried using another program that should have "disabled" the driver to see if that would work after restarting windows after doing so, but to no availe. I have been all over STMicroelectonics website and can see where others like myself have had this very problem, yet have yet to find a common solution to the problem like an updated driver. Part of me wants to think that my computer might be seeing a false flag that is preventing core isolation from being able to be applied, but I am not sure and short of redoing my operating system and not installing Steelseries software, provided that is the problem, or antiviruses such as Norton or McAfee that could be sending up false flags as well. Is core isolation crucial to have on? Is it detrimental or can a person be ok in todays computing world without having it enabled? Is it worth all the trouble it is causing me trying to find a solution to this problem? Like others on this post have stated, I am very grateful to those of you who have replied and are trying to help me fix this issue and thank you for your time.

Here is a truly trivial solution from the ST web page Peter BENSCH (ST Employee)

13 days ago

Normally, this problem should not occur on a PC or notebook that was purchased normally and not equipped with ST software for developing microcontroller applications. In this respect, the manufacturer of the PC/notebook would be the right contact person who would have to eliminate this problem.

 

However, if you want to help yourself, you could deactivate this typically unneeded software:

• launch "Device Manager"
• in the View menu, select "Show hidden devices"
• find the device associated with oem77.inf (it might done by selecting "Device by driver" in View menu
• right click on this oem77 - does it offer an option to remove the device? If yes, remove it.
• you'll maybe need to reboot the machine afterwards

 

We would be pleased if you would paste the result here and even more pleased if you would ask the respective manufacturer of the PC/notebook to remove the software from the standard installation.

All due respect, this is neither a good nor safe solution. OEM driver labels vary by machine. One person's OEM77.inf could be another person's OEM32.inf or OEM65.inf. These driver labels are not generalized.

The safest way to identify which .inf file is associated with STTub30.sys, you should follow the instructions in Step 1 here. This will map the STMicroelectronics device to the proper .inf file for your specific machine.

That said, the problem for me is that using command prompt to pull a table of 3rd party drivers did not include a search result including anything from STMicroelectronics. So I think I might try uninstalling SteelSeries GG app from the machine and see if that removes the STTub30.sys file, enable memory integrity, and then reinstall the SteelSeries GG app.

STTub30.sys driver is causing the issue. Not sure what it is for and if it is safe to remove it but if Microsoft is enabling safety features to help protect our computers from malicious viruses and so forth by enabling these new features, why would they not address this issue with a fix?

I myself have tried everything short of disabling the driver and I can not find an updated driver for STTub30.sys anywhere. The one occurrence I read that did have a solution with an updated driver, the company STMicroelectronics took down their post with the update. For what reason, I do not know.

All of us are looking for a solution to this issue so that we can enable the security features that this outdated driver is causing to not be enabled. Can someone please point us in the right direction?

Thank you

Same issue here...

Having the same problem. Might also hold up my Windows 11 22H2 update?