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

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.

FYI, I had this issue and uninstalling the Steelseries GG program from my computer also removed the STTub30.sys driver. I was then able to enable memory integrity.

I will be sure to let you know the outcome and thank you for your time and helping me. Thank you very much.

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.

In future updates Microsoft will concentrate to protect computers from viruses and other online impact through providing various security tools which will be integrated in to Windows os and in respective motherboards.

So driver development team must and should release new drivers which is suitable for windows.

According to me , you must update new driver.

All device drivers must be signed with code signing certificate and should comply with WHQL rules.