Strangest problem with new pc

[kinkladze10]

Hi I'm really hoping someone from the community can help me here, please I bought a new PC recently.
Custom build with a great specification

Windows 10
Intel Core i7 6700K Processor (overclocked to up to 4.6GHz)
Cooler Master Nepton 240M Water Cooler
Asus Z170 PRO GAMING Motherboard
NVIDIA EV3A GeForce GTX 980Ti 8GB Graphics Card
32GB 3000MHz DDR4 Memory
512GB Samsung SM951 M2 PCIe Solid State Drive
2000GB Seagate SSHD Hybrid Drive
Cooler Master V750 750W Gold Rated PSU

Bascially when I got the PC right out of the box it would start to boot up but then switch itself off after 10-15 seconds, the 2nd boot however would always be fine.
This issue would only occur on the first ever boot, the 2nd time it would always go through to windows without an issue. Also if I ever restarted the pc that too would be fine.

I spoke to the supplier and they took me through the usual, unplug all external devices, check all connetions are seated properly, reset CMOS, reseat the RAM, revert to Stock profile in Bios etc.
All of which I did and none of which changed anything.

The supplier suggested an RMA which I did and they found they couldn't replicate the problem their end but they tweaked the overclock settings and replaced both the MOBO and the PSU.
Again when I recieved it, the same issue was present with it restarting on the first boot.

The supplier then said they would build a brand new pc from the same spec and send me that, and I would return the old one.
The new pc booted correctly and there didn't seem to be a problem, that was for the first 48 hours, however to my horror I've just come to switch the PC on and the very same issue is back!!!

Again I've been through the main issues but I'm just at a total loss as to whats going on.
I'm new to Windows 10 but I don't believe that's causing the issue and I really don't know where I stand on this, I don't want an expensive PC that won't boot the first time I switch it on but equally I just don't know what to suggest as it was working perfectly before.

Is there something I'm missing here? I just don't know what to do or suggest, I really would appreciate any help.

Thanks in advance

[kinkladze10]

Hi I'm really hoping someone from the community can help me here, please I bought a new PC recently.
Custom build with a great specification

Windows 10
Intel Core i7 6700K Processor (overclocked to up to 4.6GHz)
Cooler Master Nepton 240M Water Cooler
Asus Z170 PRO GAMING Motherboard
NVIDIA EV3A GeForce GTX 980Ti 8GB Graphics Card
32GB 3000MHz DDR4 Memory
512GB Samsung SM951 M2 PCIe Solid State Drive
2000GB Seagate SSHD Hybrid Drive
Cooler Master V750 750W Gold Rated PSU

Bascially when I got the PC right out of the box it would start to boot up but then switch itself off after 10-15 seconds, the 2nd boot however would always be fine.
This issue would only occur on the first ever boot, the 2nd time it would always go through to windows without an issue. Also if I ever restarted the pc that too would be fine.

I spoke to the supplier and they took me through the usual, unplug all external devices, check all connetions are seated properly, reset CMOS, reseat the RAM, revert to Stock profile in Bios etc.
All of which I did and none of which changed anything.

The supplier suggested an RMA which I did and they found they couldn't replicate the problem their end but they tweaked the overclock settings and replaced both the MOBO and the PSU.
Again when I recieved it, the same issue was present with it restarting on the first boot.

The supplier then said they would build a brand new pc from the same spec and send me that, and I would return the old one.
The new pc booted correctly and there didn't seem to be a problem, that was for the first 48 hours, however to my horror I've just come to switch the PC on and the very same issue is back!!!

Again I've been through the main issues but I'm just at a total loss as to whats going on.
I'm new to Windows 10 but I don't believe that's causing the issue and I really don't know where I stand on this, I don't want an expensive PC that won't boot the first time I switch it on but equally I just don't know what to suggest as it was working perfectly before.

Is there something I'm missing here? I just don't know what to do or suggest, I really would appreciate any help.

Thanks in advance

Just a quick update to the above, if I reset the PC it will always boot up fine and if I go into the Bios settings by pressing F2 on the first boot, if I select the Windows Boot Menu and click on my HDD it will also boot up fine.

It's only when the pc boots for the first time and is left on it's own that it will shut itself down.
Really hope there is a solution to this as I just want to cry

[DannyM]

Tried just one stick of RAM?

I've been having a bit of a torrid time with Windows 10, however after manually updating all my drivers most of my issues have gone.

Another solution might be to try running a Live USB/CD of ubuntu or something similar and see what happens then just to eliminate the OS.

[GoNz0]

Sounds like memory training, That came in with DDR4. Technically it is doing it as it deems it unstable.

[kinkladze10]

I can try 1 stick of Ram, which one should I leave in to test?

What I don't get is why it won't work on my side yet the supplier said it was fine their end?
Also why does it boot ok on a restart and if I manually select the HDD through the Bios?

Could it be a local voltage issue but then surely it's wouldn't boot the first time round?

[smargh]

I know this is an unlikely long shot: if you didn't send them your power cable for their tests, perhaps it's not grounded properly? Try a different cable. Or maybe the desk where you're putting the PC is grounded differently than where they tested it? i.e. you have a metal desk, or they did their tests on a workbench with an ESD matt.

Or perhaps it's just coincidence and it's an intermittent problem where the shipping process jiggled cables in just the wrong/right way. Perhaps try without anything plugged in at all - no monitor even, no USB kbd/mouse, no ethernet etc. Just power.

[DannyM]

Leave the stick that's in slot one, refer to your manual about which slot this is. Gonzo and smargh both make a good points too.

[kinkladze10]

Thanks so much for all the replies.

I did try a lot of that the first time it happened. I will identify slot one and test with 1 stick of RAM.

The PC is on a wooden floor where my previous pc was placed which never had a problem but I will move it to an entirely new location in the house and try it there.
I've tried with every component removed on the previous pc, so no monitor, ethernet sound etc and still no difference.
I'd tried a different plug slot and even a different power cable and that made no difference either same with both the stock and oc profiles.

I think it would be a massive coincedence for the shipping to have changed something and for this 2 happen 3 times is hugely improbably.
I can only think that it could be a voltage issue, i.e. the voltage at my property is lower than at the suppliers factory, however this wouldn't explain why it boots the 2nd time or why it works if I go through the BIOS and/or Windows 10 has downloaded an update perhaps that is causing a conflict maybe (I'm on Windows 10 Home so the updates are automatically downloaded) but again this wouldn't explain why it didn't work at the supplier.

It has to be a local issue with me, is it worth trying to increase the voltage settings slightly in my bios or is this a bad idea as when it comes to technical stuff like that I don't know what I'm doing.

[MrRockliffe]

I have that some times when I've killed power to the power supply (switched it off at the plug for example). It could be the extension lead if you're using one? Have you tried a different plug socket?

[GoNz0]

Sounds like memory training, That came in with DDR4. Technically it is doing it as it deems it unstable.

I looked into this and got a reply from Asus who said it is memory training causing the reboot as it fails from cold boot when it runs the more complex memory check. Post reboot it has relaxed the timings meaning your overclock is unstable.

This was on my Asus R5E DDR4 board, people who are thinking along the lines of DDR3 should exit the thread on the left as things got shook up with DDR4

try upping the system agent voltage, if you used the 125 strap for overclocking then go back to 100 strap

FYI my system for all intents was 100% stable and behaved fine on the later BIOS updates. The reboot was very random in my case so the overclock was afaik 99% stable apart from the weird memory training at cold boot.

[kinkladze10]

Thanks for this guys.
I have tried the pc in a different plug socket with a new power lead with nothing else plugged in and the same issue occured.

Which leads me to it being a RAM issue, however even if I bring the PC to stock settings in the bios the same issue prevails?
Also it doesn't make sense why it would work ok at the suppliers premesis? It's been clocked by experts and stress tested and they wouldn't ship it in this state so why is happening?
I can understand it happening on the first pc but surely not the 2nd?

I will go down to 1 stick of RAM on the stock profile and see what happens

[ceejays88]

I had something similar when I first got a M2 SSD - it was due to the PSU when I changed that it worked fine.

It was something along the lines of the SSD not having enough power to it on cold boot. Do you have a spare PSU you could try ?

[kinkladze10]

Hi all
the supplier suggest this fix, to remove the fast start up option from Windows.

http://www.tenforums.com/tutorials/4...dows-10-a.html

I did as suggested and have cycled the PC through the shut down/start up function, each time it has booted correctly and first time.

Could it be something as simple as this? I'm certainly not complaining if this is the fix!!!

[GoNz0]

It is not a fix it is a workaround, you didn't pay the premium for a workaround did you?

Also did you note the serial numbers of the parts they changed as this sounds very dubious.

[kinkladze10]

Well they built me a brand new pc with the exact same specification so all the components are correct and inline with the specification.
It seems as if for some reason that function was putting the computer into a sleep/hibernate state so it would boot quicker as opposed to a full shutdown, somehow this has caused an issue.

Since I've made the change all seems to be ok as I've tried several restarts from a cold boot so I'm hoping this is it, I'm no suffering any lack of performance and the boot time to windows is fine, it's still miles quicker than my old pc.

[GoNz0]

I had issues (well a lot of people on the asus forums) where fast boot would cause a lock up, but the BIOS fast boot option that skips initializing sata devices, if it was set to boot drive only it would lock up, once set to all it worked fine.

Just a thought.