Soldato
I worked in a desktop support team for 2500 developers and some of the builds we would have to put together could take 4 days of software installs before being dropped of with one if the devs for 'tuning' before taking the image so I understand what the OP is saying.
But, if you want to test if hardware is working try a fresh build and install the latest drivers etc and see how things go. If it works ok after that then you know its an image problem and can create a fresh image.
If you do have to recreate your build, I would recommend you test your build now & then to ensure everything is still working and take the odd mid-build creating image just incase theres a problem.
OP: Your tone is really bad and you don't make yourself an easy person to help. Years of suffering/ working in support has taught me to ALWAYS be nice when asking for help/ support, people are much more likely to want to help.
You should see the PC refresh we had. Took about 3 months to get the builds right, which is what I was eluding to in my reply about being machine specific installations. What it all comes down to is that it can be more than JUST the drivers. It might be the lack of windows updates, patches, fixes (from MS), dot net installation, an old directory hanging around and many other things.
He still hasn't answered critical questions like, do those drivers work fine for games on a fresh install with nothing else on the machine? Also, since he was having issue's with slots on the board, it could EASILY be BIOS problems, or a crap motherboard for example.
I had an Asrock board, and whilst it was good for the money I had to alter many BIOS settings to get gfx cards stable. Blaming the drivers isn't always the way.
Even if it is the drivers, that is why I asked for specific problems he was having and with WHICH SET, so he could compare to other people. We simply have not had those answers yet.

