Windows 10: CPU and Audio related driver issues on cloned Windows 10 SSD

Gooday ladies and gents, so the story is that we had quite a lot cloned clean Win10 SSDs from an external partner who basically ****ed it up.
The thing is all the cloned ones have driver issues, in device manager it marks the CPU (something I haven't seen before) and the Audio Controller with the scary yellow sign, telling me "A driver(service) for this device has been deactivated. Possibly a different driver is able to take over its functionality. (Code 32)" (Translated from german, so you are not confused if its slightly different from the messages you know).

So, my theory was (well, still is) that because of the CPU and Audio controller issues the pc is unable to properly recognize and/or install the integrated soundcard, leading to the problem that the audio devices are not listed (btw USB connected devices work, if that helps you).

Basically what I'm trying to find is a way to force it to freshly install those drivers or if there is a repair tool or something similar for these cases, its no option to reroll the whole cloned batch. (Well, to be fair, it actually is the last option)

Is there somebody having the same experience with a solution or is the only option to reroll?

:)

 

Windows 10 won't sleep after update from Version 1607 to 1703

It's a clone based on a Gigabyte GA-EP45T-USB3P motherboard with an Intel Core 2 Quad Q9550 CPU and 8 GB of memory. All drivers, with the exception of a couple audio drivers, are up to date.

 

Windows 10 Pro - SSD is causing PAGE_FAULT_IN_NON_PAGED_AREA blue screen of death....

An update - I cloned the SSD in question to a "normal" HDD, and tried the HDD in the laptop, it still BSODs so let's assume it is software or driver related.

I also cloned the working fresh install of Windows 10 on a 1TB HDD to the "problem" 500GB SSD after using diskpart to clean it out completely. The SSD has now been in the laptop for 4 hours, and NO BSODs. Doubly confirming my suspicion it is not the SSD
at fault, but something in Windows 10 update or, something else specifically software related.

Now I know I have basically solved my own problem by doing a fresh install, but is there another way? I still have a complete copy of the faulty windows installation which includes all of the data, and all of the programs already installed and activated.
If there was a way to fix that rather than have to re-install EVERYTHING, that would be much appreciated.

 

Hi and Welcome!

Did you/they clone the same PC to an exact same computer with the same hardware?

If not, that is the problem and the drivers for that PC will need to be installed to fix the triangles.

 

Yes of course they all have the same hardware, I checked that multiple times to be sure.

 

Clone is a hit or miss. Works great for some and not for others.

Making a disc "image" (backup of entire drive all partitions) to a separate drive then restoring that image to the new drive is another option.

The free version of Macrium Reflect will do the disc image.

Macrium Software | Macrium Reflect Free

 

That's the sort of thing I would like to avoid because that would mean dozens of SSDs need to go through that process, though if nothing else works we just reroll them with adjusted, proper new clones which would probably be more safe.

Still thank you for your idea.

 

We had a very long discussion, on the Win 7 forum, with the "guru's" about cloning. After many tests, the consensus was image was a sure way, cloning as noted was a hit or miss.

I used to be a regional LAN/WAN Network and Hardware Help Desk Manager (until retirement). We had disc images that we used for our workstations and servers. But it was not a "clone" type. The workstations (all 55,000 of them) were one brand and had the same hardware and software configurations, just the local addresses were manually set up after the install. The same with the client servers, all 1800 were the same brand and hardware configuration. The local setups were done by the LAN Administrator, but the basic disc image was the same. (we did nightly backups of the servers and that was a full backup every night. We tried incremental and turned out to be a mess).

 

I don't doubt that, it's not about whether cloning is they way to go or not.
Actually what I'm looking for is a way to fix those issues, worst case is that we reroll per image if cloning really doesn't work but we don't want to set all this up again, actually we want to simply fix the driver issues and, most important, the missing audio.

I appreciate your intel to the topic but as I'm relatively new in this company I can't just force everything to go "my" way (that means avoid cloning in the first place) but actually it was the external partner who just couldn't do it better to support us.

At this point we invested enough time to justify rerolling but every day we find a new particular update package, driver or similar which should work, but doesn't in the end.
I'm assuming it's actually something totally stupid like the serial nr. of a particular part or similar that just didn't change with cloning and can't recognize the new one because of that.
Maybe I'm totally wrong though...

 

In case somebody runs into the same issue I've solved it - I used the manual way to install drivers and used "Processor" instead of "Intel Processor" which solved the CPU issue, then I could install the Audio Controller in the same way and from there the audio driver was able to be installed, a reboot and boom - the speakers boomed my song.