Computer needs restarts to POST and boot correctly.

WThieves

Commendable
Jun 19, 2016
4
0
1,510
Hey all,
I really need some help with this problem.

Ever since my SSD died on me (4 months old) my computer has been having a lot of problems.
When it died I was not sure what was going on so I re-seated the RAM multiple times, and flashed te BIOS to a newer version.
After I found out my SSD died, I ordered a new one and plugged it in.

My computer did work again, but not for long, after a couple of starts it stopped POSTing on regular occasions.
Every time this happened it needed a restart (Hold the button, then press it again).
It's like it needs to warm up or something.
From then on it usually needs a restart every time, there have been days where it started on the first try, and lately there have been days where it started on 5 to 8 tries.

I've tried re-seating the RAM, trying every RAM stick on its own and doing a memtest which turned up fine.
The problems persisted.
I've tried starting without peripherals and the likes but the problems persisted.
I've tried starting with only 1 drive but the problems persisted.

The strangest thing is when it finally does start, it runs like nothing ever happened and it seems perfectly fine.

The pc is now 5 months old, so I still have warranty on it, but the company I ordered it from has a horrific warranty policy which seems to be carefully written to make sure people would rather let a 3rd party solve their problems.
The biggest problem is that it could easily take 6 weeks for the computer to be fixed, and as a Software Engineer I cannot wait that long.

Do any of you know what might be going on or what can be done to find what is actually going on?

Best regards.

Specs:
GA-Z170X-Gaming 3-EU
Intel Core i7 6700
32GB DDR4 2133
NVIDIA GTX970 4GB
 

WThieves

Commendable
Jun 19, 2016
4
0
1,510
I've disconnected the drives, it seems to POST consistently then.
I've tried with every drive separate in every port separate, the problems keep happening no matter what cable, port or drive.
 

c0ck7aiL

Reputable
May 9, 2014
22
0
4,510
Hi, I have the exact same problem and it started happening after I reseated my SSD. I think the problem is in the drives... Shame there is nobody who knows more than me to answer
 

WThieves

Commendable
Jun 19, 2016
4
0
1,510
Yes, I came to this forum for help but apparently nobody has ever encountered this problem before, I'm still waiting for an answer.

I have had some luck though.
I ran my windows 10 installation in dual boot mode, because after my SSD died I really still needed to acces the files on the HDD's I still had in there so I installed Windows 10 onto a HDD.
When my new SSD arrived I plugged it in and installed Windows 10 on that without uninstalling the old Windows 10 first.

I thought dual boot was fine, but it really isn't.
Since the first installation installs the windows boot manager, any other installs seem to not create the much needed EFI partition for this.
I think the guys at Microsoft consider this to be obvious but to me it isn't.

This means that if I were to format the drive with the old windows on, there wouldn't be an EFI partition and there would be no way for me to boot into Windows 10 on the SSD anymore.
But that was not the problem, the problem was that the pc didn't start 3 out of 4 times.

My theory was that because the EFI partition was on the HDD, the SSD was just too fast.
Somehow the SSD needs to read that EFI off of the HDD and since the HDD takes a little while to spin the HDD was not "alive" yet.
After I repaired (I can't quite remember how I did it, something with an installation USB, command prompt and fixboot) the missing EFI partition so my computer could boot with only the SSD it seemed to have stopped.
Or at least appear a lot less frequent.