Persistent OS errors even after clean install dtdll.dll svchost, etc

Thank you, so the Driver verifier is more like a driver stress tester that tries to find faults in drivers right?

I just got back from the Microsoft and had a chat there with one of their managers and a tech, really helpful and guided me through some more troubleshooting. The tech there I believe changed a few things in BIOS and when we were shutting down the computer we noticed it was very slow. He just said we could force shut it down since it was taking like 30 seconds, the screen went off but the fans and lights were still on.
Upon coming home I received my errors.... Attached here, I went and reinstalled the OS...

But now I'm on the fresh install, I've just loaded my drivers (Chipset, MEI, Video, Audio, Lan, RST), and i'm checking the windows store for updates and microsoft for updates (Theyre downloading).

But so far I've got 128 errors and about 300 warnings. Again, I know a lot of these don't mean anything but someone did mention hundreds of event viewer errors upon clean install is not good.

Also answering your question about AV scanner, I paid for Bitdefender 2017 ultimate edition, and none of my bitdefender scans ever come back with anything.
For any addons, I run none in Edge, for Chrome I just have bitdefender wallet and whatever stuff Chrome comes with by default (some readers).

The guys at the Windows store all suspected my Motherboard, they said its either broken or there's some sort of underlying compatibility issue. They said that since I've already swapped the GPU and the CPU before I can pretty much cross those two off. Ram is very unlikely, and the drives they said also looked fine, PSU was also sufficient. So they said the last thing that was left was possibly the Motherboard. Since i'm getting similar issues across hardware changes and system reinstalls, the only thing left over is the Motherboard.

Again going back to how I had just come back from the Microsoft store and booted up my computer to a broken boot file, the tech there had changed some small things in my BIOS of which I have a screenshot of down below.
He turned on XMP and changed like two things or so.

I remember the last time I turned on XMP, Fastboot malfunctioned. I'm unsure if it was coincidence or if XMP caused it, but after enabling XMP whenever I shutdown my computer or hibernated windows would show me an error saying the system was shut down incorrectly and fastboot had failed.

So If changing something in BIOS caused windows to malfunction... again... then I'm really starting to believe a motherboard issue may be likely.

What are you guys thoughts? I know I may seem a bit paranoid with my problems but please bear with me, I definitely believe there is something wrong with this computer and it is not just the Event viewer or reliability history errors.

Caledon Ken said:

Yes to the driver verify, it is a stress test of their abilities.

With XMP on you are applying a simple "Overclock". I would run with over clock on and shut off Hibernation which in turns shuts off Windows Fast Startup. You ability to wake from sleep with your SSD is already good. I want the speed when I'm running. Now depending on how fast your XMP profile is, and your memory appears fast, that will determine the "Overclock". You shouuld be able to see the overclock. Overclocking can cause issues.

As lx07 said you will have errors and your really can't start counting until your machine is updated and stabilized.

I saw again that you install chipset and other drivers. Why? Did Windows get them all wrong and could not recognize the devices?

If you suspect MB by all means RMA it. You want to be able to sleep at night and game when you want to.

Right, XMP simply performs a simple overclock of the ram to the manufacturer specified performance of the ram.
I'll turn off fastboot when I turn on XMP then, I just figured XMP and Fastboot are both something Windows should support, so I shouldn't have to turn off one for the other to function.

I was under the impression that it was best for the motherboard chipset drivers, audio, lan, etc drivers to be installed after a clean install? Everyone I've spoken to has told me that drivers do need to be installed after a fresh install and its better to do it myself than to let Windows do it. (As outdated drivers may be installed, or some drivers may be missed)

I'm suspecting some kind of driver conflict somewhere, Motherboard is that main piece right there haha. I've spoken to a few computer techs, including ones at Microsoft, they're all suspecting the Ram or the motherboard to likely be at fault either being faulty or having some odd compatibility issue.

But I'm going to run more tests, Memtests to rule out ram completely, and then of course im going to run that Driver verification process. That driver verification process, there isn't a chance it'll break anything will it? Or will it just bluescreen and I have to restart?

Correct, the system should be able to function without myself needing to apply drivers.

I did test that a bit. I remember once I installed windows without loading any drivers myself and letting Windows just install its own drivers. Since reliability history takes some time to generate reports I viewed event viewer instead for looking at those events.
The corrupt cache/ licenses error popped up... about 30 minutes or so after the clean install finished. The edge errors and some svchost errors were being logged immediately. The Windows Image Acquisition problem happened immediately as well.

So if it is driver related, then Windows is even loading the faulty drivers.

And the CPU speed shouldn't/ didn't change after XMP is applied, it should just be the ram set to the rated speeds. However I believe you are correct, XMP is an intel thing and it is more motherboard/ ram dependent.
(Although normally I run with this off and I only turn it on during times of troubleshooting)

But DDR4 runs stock at 2133mhz, XMP makes mine run at 3200mhz, my CPU is the i7 6700k and runs at 4.0ghz with turbo boost to 4.2ghz

Interesting, that might be motherboard specific, I was turning on XMP to run memtests on the ram, this time it didn't break fastboot... But I checked the CPU speed and voltage, looked fine at like 1.280V and 4.0 GHZ stock

Hey I just wanted to ask and make sure before I run the driver troubleshooter.

I read through it, so the reason I should be doing a restore, is it could potentially break something in my system, cause a bluescreen and cause windows not to boot/ load right?

It won't do permanent damage to anything will it....? Or at least have a risk of.