Been getting BSOD freezes out of the blue. Can an auto high VCCIO damage components

[Jacob-gtr]

Hi.
I have been getting BSOD random freezes on desktop all kind's of codes through the dump files.
It can range from using the PC for hour's on end no problem to anytime. Gaming for 6+ hour's no worries'.
From DPC_WATCHDOG violation's to HARD_PAGEFAULT error's etc.
Other times I don't get a blue screen it just freezes.
At one stage I couldn't even boot into window's it was just throwing BSOD at me.
So I had to do a clean install.

I have run Memtest64+ multiple time's no error's chkdsk /R on all 3 of my ssd drives. Ran multiple drive health program's no problem's found.
Updated all drivers. Monitored the PSU voltage's etc.
The : ntoskrnl.exe like's to crash with " The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. "
Or " Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. "

I have noticed when it hard lock's the ssd activity led completely disappears.
Spent the last 4 odd week's troubleshooting and just now noticed in the bios CPU VCCIO I left on auto with XMP profile enabled was running at 1.248v. When I set it to manual it set's 1.2v and show's yellow.
I set it to 1.25v manually out of curiosity and it went purple.
So has the board been over volting this?. Does this have a connection with the IMC on the CPU?. I'm worried I have fried the IMC.
It's one setting I don't bother with when overclocking. I just set it to 1.1v to get it off the yellow warning But worried it's little too late.
HWinfo is showing IMC voltage at 1.136v atm if I open graph it's in red.
I cant find any info on Kaby Lake and what this should be.

Windows 10 is completely up to date.
Ill list my spec's so anyone might have an idea and some advice would be awesome.

Windows 10 pro 64.
Asus maximus viii hero bios 3201.
7700k
32GB corsair dominator DDR4 2400mhz 14-16-16-31
SLI 1080's
3 Intel SSD's
Corsair ax1200 PSU

Thank's.

Edit.

Just to add Intel diagnostic test passes.

[NemesisChild]

Have you tried clearing the CMOS? Can you boot into safe mode without BSOD's?

[Jacob-gtr]

NemesisChild wrote:
Have you tried clearing the CMOS? Can you boot into safe mode without BSOD's?

Thanks for helping me.

I haven't reset the CMOS for a while.

When I couldn't boot without BSOD I didn't try safe mode system restore didn't work so I thought I will just do a fresh install because it's been 6month's and I figured it couldn't hurt to start from there.
So that went well no BSOD I updated to anniversary update straight away and all updates fully updated.

Like prior to the reinstall it would just be idling on desktop I'm not using it and it would reboot.
Once I even had a q=code of 50 I think it was and wouldn't boot. I just took the ram out reseated it and it was fine. Then I had my boot drive not detected pretty much the same time. It's like something happened in one hit.
Other symptom's copying files over to external hard drives the other day using usb3 towards the end the drive would just disappear.
Never done this before.

This is my second AM8 hero MB the first one I bent the usb 3 pin's for the case I have no idea how that happened but this is the second board I never have luck with them I have like 6 Rog boards from the V that most crapped themselves in some way or another PCI-E stopped being detected back Lan port stops working.
My PSU I checked the voltages when under load they are fine. I know that doesn't rule that out I do have another one that's the same but to me it could be anything I just cant get an idea. This VCCIO voltage has me worried it must have been running at 1.248v for the last 2 months.
So since then the fresh windows install is done I have updated all driver's sata lan usb everything. So what happens now is I can be using it fine for hours play games and get no problems. Then other times it will just freeze doing a non demanding thing like opening up a program or BSOD.
I can leave it on overnight downloading now problems.

I thought well at least games are not effected then the other night I was playing sints row 4 and it just stopped responding with the sound still going.
I could alt tab out of it.
But no popup saying NVidia driver has recovered etc. Which my old system done I would game like 5 minutes an hour 2 hour's then hard lock with the buzzing sound and that always happened it was just a matter of when and only ever happened playing a game.
This one does it on the desktop. Rarely in a game.

I thought it was Microsoft and Nvidia forcing windows to install this specific driver because they found a vulnerability in the kernel.
I kept using DDU reinstalling 376.33 then come back an hour later and it installed 376.52 I think it was.
Now they launched 378.78 I was hoping this was the root of the problem but no.

I have used driver verifier but I get a BSOD before I get into window's saying driver violation found so I cant even work out which driver it's referring to.

Sorry for the rant I'm just trying to give as much info as possible.

Thanks again.