[SOLVED] ASUS ProArt B550-CREATOR, working okay - But Unkown Device "on AMD I2C Controller" remains in Device Manager after all drivers have been installed...?

Hi,
I’m currently looking at an ASUS ProArt B550-CREATOR motherboard in my quest for checking out nice APU-only system configurations.

Everything is seemingly working fine, except you have to disable Windows 10’s automatic driver installation via Windows Update in gpedit.msc since you cannot prevent it from forcing a GPU driver from May 2020 onto the system that leads to BSoDs. :frowning:

But even after letting Windows do its drivers rampage without intervention it doesn’t change a thing about an unkown device remaining in Device Manager even after seemingly all drivers have been properly installed:

(Note: Some GUI language mix-ups, I changed the system language to English for the screenshots, doesn’t have anything to to with this issue)

Hardware configuration:

  • UEFI version 2401

  • 4750G

  • 2 x 32 GB Micron ECC UDIMM DDR4-3200

  • AHCI SSD

  • Standard USB mouse and keyboard

  • Nothing else (yet)

  • Windows installed in UEFI mode without CSM

  • Secure Boot enabled

Installed drivers:

Notes:

  • Reinstalling Windows 10 21H1 without any effect
  • CMOS Reset and reflashing of BIOS without any effect
  • Let Windows search through AMD’s decompressed driver folders on C:\AMD\ doesn’t find a suitable driver

Does anybody have an idea what this thing’s about?

Was hoping to avoid ASUS’ own motherboard bloat-malware :frowning:

Did you disable the armory crate thing?

Yes, “ASUS Armoury Crate” as well as “MyASUS” is disabled in the UEFI.

I have already been aquainted with the ASUS Armoury Crate curse but “MyASUS” was new to me.

My gut is grumbling when motherboard manufacturers want to force shitty add-on software upon me so I hope there is a way around that.

2 Likes

Yeah, it seems the “ASUS Armoury Crate” UEFI switch is broken meaning it cannot be turned off.

Tried the inverse to “Have you tried turning it off and on again”, meaning unplugged the ethernet cable and turned ASUS Armoury Crate as well as MyASUS on.

This results in two unkown devices, disabling MyASUS lets one disappear and disabling ASUS Armoury Crate doesn’t do anything at all.

Do you have a contact at ASUS to properly report this to to not have to go through the ever soul-grinding experience of Level 0 end customer support?

3 Likes

Also, please relay & criticize this atrocity:

2 Likes

That’s in my review! Lol

2 Likes

Here you go: Microsoft Update Catalog.
Enable insecure downloads in your browser, download, extract, the use the manual driver update option in Device Manager.

2 Likes

Thanks for that tip!

Do you know what exactly this device is about? Will test it later today.

It’s a USB controller.

1 Like

Yay, was too curious - success!

Sorry to have pointed my middle finger at quality features like ASUS Armoury Crate /s

But I am a bit confused, had thought that ever since Windows 8.1 USB controllers do no longer need third-party drivers…?

any idea what was up with the bsod though? I had it too.

Wait, are you also currently looking at this motherboard model with a 4750G?

1 Like

If you are doing the same testing as me, for me the source of the BSoD was pretty obvious:

Installed Windows 10 21H1 with an USB stick (via Rufus) with an ISO itself created with Microsoft’s public Media Creation Tool and used the command line parameters to create one for Enterprise (Enterprise and Education are the only Windows 10 editions I touch due to GDPR concerns).

Ethernet ports are not connected to not be forced to create a stupid Microsoft online account. I install all available Windows Updates offline, then all drivers with their most-recent release.

So the OS is fully installed and all hardware drivers present, then I connect an ethernet port and Windows automatically downloads and installs an ancient AMD GPU driver (as initially mentioned dated May 2020) while the most recent AMD GPU driver from May 2021 is already installed.

In my case this leads to BSoDs, the only way to avoid it is to disable Windows’ automatic driver installation via gpedit.msc, the option that is available in the GUI has no effect, Windows keeps downloading and installing that old driver.

Just click limited setup twice to avoid Microsoft account, that has been my experience on pro versions

You’re ancient GPU driver problem has been off and on plague of windows update, I’ve had them do boot loops before, as far as I’m concerned is only slightly more Microsoft’s fault forcing the bad drivers than AMD’s for making them that bad in the first place

I’m dumbfounded by why Windows Update doesn’t just check the drivers’ dates and ignores the old one incoming from Microsoft’s update servers.

Sometimes I think Microsoft’s version control is something like “list alphabetically by file name” :upside_down_face:

1 Like

There are “rumors” that even with Pro editions that will sometime soon no longer be possible so I just disconnect all network interfaces to be on the safe side.

It’s not a rumour. Unless you are offline you no longer have the option to do a limited or non-MS account with a new Win 10 setup. It gets so much better each and every update too; your user will be prompted to change their account to an MS linked one - fortunately that can be cancelled out, for now

IIRC it has been this way since after 1908

I always forget and have to redo the setup with no LAN connection to bypass this as well. I have experienced this on both Pro and Home editions.

1 Like

This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.