BSoD CLOCK_WATCHDOG_TIMEOUT error after OC

[nathanmichem]

So i OC'd my i7 6700K with intel xtu to 4.5Ghz, this made my pc crash after i aplied it and after start up.
I reset everything in my bios, this didn't work so i did a full windows repair and reinstall.
This helped a lot, my pc now didn't crash on start up but just at random moments when browsing the web, when i would play games i was fine tho.
I then oc'd my cpu to 4.5ghz again but this time in my bios, and upoped the voltage.
This now worked.
When i run Aida64 or games everything is fine, my pc only crashes when i'm browsing, i let the pc run for multiple hours without touching it, it ran fine, nothing happened but about 10 min after starting to use it it crashed while browsing?
Also i can hear my PSU click in a rithm.

Specs:
I7 6700K cooled by a corsair H45
MSI GTX1060 6GB gaming X
Asus TUF sabertooth Z170
Cooler master G750M 80 plus bronze
HyperX 2666ghz 16gig ram
Sound blaster Z audio card

Update: i just noticed when it crashed that my drives said 999gb used 999gb free in nzxt cam, could it be an ssd/hdd issue?

Update: i found the issue, was a bent pin on my mobo, fixed it and no problems so far

 

[asoroka]

are you monitoring your CPU temperatures?

Is this a new build, if so have you done a full memory test?

 

[nathanmichem]

are you monitoring your CPU temperatures?

Is this a new build, if so have you done a full memory test?

i've been monitoring cpu temps since the beginning of the crashes, nothing weird there, and no it's not a new build, it's 1 year old but i did just switch my old i5 to an i7 and then tried to oc the i7 like i oc'd my i5 and then the issues started, but now it onlmy crashes when i'm in idle, it runs fine while i'm under load like in games or with aida64

 

[asoroka]

have you restored it to default (non OC) settings

 

[nathanmichem]

have you restored it to default (non OC) settings

jep i have, didn't solve anything

 

[asoroka]

and does it work if you revert back to the i5

 

[nathanmichem]

and does it work if you revert back to the i5

yes it did, wich is weird cause i found the issue, it was a bent socket pin

 

[nathanmichem]

Update: i found the issue, was a bent pin on my mobo, fixed it and no problems so far

 

[asoroka]

excellent news.