Windows 10: usb-usbhub3 win32k and netwtw12 spamming event viewer

hey yalli got an issue with my new rog flow z13so basically win32k usb-usbhub3 and netwtw12 spam event vieweri tried reinstalling and updating the network driverhere are the screenshots and the event viewer logalso i had the same on my surface so i think that intel just has trash driversthe surface also had the same wifi cardhttps://www.mediafire.com/file/xlxnze5rwnyywfs/events_%25281%2529.evtx/file

:)

 

Event viewer: MTConfig Event 1 Errors and Win32K Event 267

I recently clean installed Windows 10 on my Surface Pro 3 because of rampant BSODs and since then things have been somewhat 'funny--,' the strangest thing being my event viewer now being populated by many instances of the following events:

Error: "MTConfig"

Event ID: 1

Description: An attempt to configure the input mode of a multitouch device failed.

and

Information: "Win32K"

Event ID: 267

Description:

The description for Event ID 267 from source Win32k cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:

The specified resource type cannot be found in the image file.

I have no idea where to start troubleshooting these two. These are just two little issues in a number of many that I don't think a clean install of windows ought to be suffering--but these two are the ones that are the most enigmatic to me.

 

Event viewer

I suggest you re-install the video driver.

I'll add a few words of explanation about Event viewer in a moment. They won't affect the need to reinstall that driver as your first step.

Denis

 

Event viewer: MTConfig Event 1 Errors and Win32K Event 267

Surface Pro 4, 128GB i5, issue is happening now in event viewer after installing 14986 build of windows insider.

MTConfig does prevent a Surface from turning on (but I haven't had that issue in a while)

But Manly all of my bluescreens when I was the stable builds and now have been do to:

Win32Kfull.sys And mostly with Microsoft edge flickering out is when event viewer pops the Win32K message. Or like last night when I was Playing Minecraft Windows 10 and it bluescreened due to Windows update wanting to install updates. (cause
the PC restarted, set up updates and installed updates before going back to my login page.