I just reinstalled Win 10, so it's fresh. I had noted this issue was present before reinstall. I am having some crashes as well, but I am unsure if it's related so didn't bring it up as didn't want to throw out a red herring.
Motherboard drivers - the few that there are - have been downloaded and installed (apart from 'AsRock Polychrome') - but that said all of the drivers are fairly standard and very likely to get picked up by Windows Update (Aquantia NIC, Intel Wireless/Bluetooh, Realtek Audio etc) so I can't see how they would be creating so many instances of the same thing in Device Manager.
I have installed a lot of systems, but never seen anything like this. I should mention that this exact system was previously installed in another motherboard, the motherboard was swapped out due to a non-boot issue. There is a niggling part of my brain telling me something is up with the CPU, but I can't reconcile the suspicion with any tests or outcomes.
Anything that shows up with an error or missing drivers you will need to look up the hardware ID numbers online to see what needs to be installed. After a clean setup the vendor drivers should take care of everything but sometimes the driver pack needed may be hard to track down exactly.
So I think I resolved this. I decided to deal with my intermittent crashes first - went down a rabbit hole of attempting to fix a 'distributed COM' error that appeared to be happening just before a system freeze.
I eventually read this shouldn't be a problem and is a normal part of system operations.
The intermittent nature of the crashes, with no way to 'trigger' them regularly gave me reason to suspect the SSD. I migrated my install over to another Nvme I had lying around and it seems to have solved all of my problems. Including the problem from my OP.
I'm glad it seemed to be a dodgy SSD as opposed to a dodgy CPU! (Although that always made less sense)