BSOD's After installing windows & now in installer

[ExeCuteUK]

Hey Guys,

Hope you can help, im now getting BSOD's on boot up of my newly built computer.

Upon first building the PC I installed windows 10, installed mobo & gfx drivers, rebooted and then installed team viewer. After this I received a BSOD without any .sys links, along the lines of system kernel something (apologies I cannot remember).

After rebooting, it loaded back into windows and BSOD almost instantly and then repeated a cycle.

I decided to do the usual checks of removing devices etc with no luck, until it eventually BSOD's on boot up before it even reaches Windows. Stating a different reason each time (System Service Exception , System Thread Exception Not Handled, A Kernel Error which I cannot remember and WHEA Uncorrectable).

I then decided to try a fresh install but have found the installer also BSOD's when it loads into the windows installer part.

I have tried both USB & DVD media downloaded via Mediacreation.

I have removed the SSD drive leaving just the DVD plugged in, removed the GFX card and using onboard, and tried replacing both sticks of ram. I have unplugged USB ports.

I have today replaced the motherboard expecting that to be faulty, and found the installer is still creating a BSOD with a new mobo (Asus Z170P, old mobo was a MSI Z170).

I have also flashed the new mobo bios to its latest version.

PC Setup :-

i7 4700k
AS Z170P Mobo
2 x 4gb Hyper X Savage 2400 (running at 2133)
1 x Crucial SSD
1 x DVD-R
Gigabyte R480 Gfx
Evo 212 Cooler
Corsaid CX750M PSU

I dont understand why windows installed and ran for 2 hours fine, then suddenly entered a BSOD cycle along with now the installer which does not work on DVD or USB installers causing BSOD's also.

Any help would be great as I thought replacing the motherboard would fix it

Thanks

 

[Colif]

WHEA (Windows Hardware Error Architecture) errors are CPU errors, (I assume you have a I7 6700K, not what you typed), since you on 2nd motherboard its unlikely to be bent pins, it could be you have a bad CPU. Its hard to check it without windows I think

rest could be driver related

 

[reedo_43]

Loose the overclock if doing so...

 

[ExeCuteUK]

Hey guys. Found the solution finally.

It was a faulty core on the i7 cpu. Disabled multi core in bios and run just 2 cores and worked perfectly. So will rma the cpu.

Thanks.