Hardware problem after installing Win10?

Hello,
after installing Win10 my mainboard ( Asus Maximus Hero VII ) has been showing me an error on the LED screen.
The error number is 4 which basically says PCH initialization before microcode loading... now I have no idea what that means, and googling it has made me no smarter.

Now, my computer boots up normal and everything is actually fine. Im getting no black screens or anything, can play games etc etc.... Maybe my old hdd is a bit slower than it usually is but yeah, everything seems to be in order.
It just shows me that error on the LED thing and I think it started after I finished installing Win10 two days ago.

Specs:
i7 4790k
16gb ram ( gskill 1600 )
gtx 1070
revolution x't 630w
and 2 HDD's

PCH is the peripheral controller hub (the chipset). Make sure your drivers for the integrated graphics on your CPU are up to date, as well as the 1070. I'd also consider (after doing this) booting the system without the graphics card and see if that still happens.

So, none of that really helped with my problem. This is what I did:
I installed the windows 10 graphics drivers for my card, restarted the computer and didn't get the error shown anymore.
I then turned my pc off a few hours later, turned it back on but got the errorcode 4 again ( PCH initialization before microcode loading ).
There is something really weird going on, though. I restarted my pc then, and got the code yet again.
After another restart, the PC booted up reaaaally slow but I was not getting the error again.
After yet another restart, I was getting the error again but my computer booted up way faster.

For me, this doesn't make sense at all. Is there anything else I could try? I searched through various forums now but theres like nobody with this problem it seems.

1 Like

Honestly I'm not sure. I'd suggest checking your RAM and making sure its slotted firmly. Check to see no power cables are loose in your system either.

Well, just checked again and everything is definitely slotted firmly. I'm still getting the error sometimes when I start the computer. Maybe I'll just have to go back to Win7 again, I don't know. Cant find any solutions in the net at all, but I do know that I didnt get this error with Win7.