fairly new pc boot cycling with minimum hardware connected

ph1lph1l

Commendable
Feb 25, 2016
17
0
1,510
cpu: i5-6600k
mobo: Gigabyte GA-Z170XP-SLI
ram: G.SKILL 2x8 GB DDR4 2133
psu: EVGA SuperNOVA 650 P2 (not the issue, using it in diff pc)
win10

bought this in 2016. occasionally had hard freeze problems but thought it was just game freeze problems, but the past several months my pc would just hard restart, no error or bsod or crash report. perfectly low temps (30c cpu, 70c max gpu). bios is up to date, drivers are up to date, windows up to date. PSU is not the issue as i'm using it in an old pc just fine. tried running memtests with a single stick of ram in every slot with only the mobo, cpu, and ram connected and system would still power cycle shortly into the memtest. i can still actually use the pc but after a certain amount of time,hours or a day or 2, it'll restart then potentially restart again once it gets to windows.

first of all i'll probably RMA the motherboard but should i RMA the ram and CPU as well just in case?
 
PC rebooting at random is often power-based problem. For example 24-pin cable not firmly plugged can cause such behavior. So first thing would double check all your power connections. Then try different PSU (I know, read that, but still). Actually what's your GPU? Maybe the other PC needs less power so PSU runs fine with it and still can fail with this one.
 

ph1lph1l

Commendable
Feb 25, 2016
17
0
1,510


running both PCs on integrated graphics. was using a gtx 970 but took it out to troubleshoot. i'll try picking up a new 24-pin cable as i really don't want to get 3 different things RMAed, thanks for the reply.
 


Ok thanks for clarification. That indeed puts PSU and GPU out of the picture.
As for RAM, if you did memtest and it worked, I think it's ok. Faulty ram would more likely cause BSODs, not reboots. Unless it failed memtest? Not sure I got you right here, please clarify.
Hard freeze can be caused by failing motherboard battery, but since it's almost new, it's unlikely. And failing battery would not cause reboot.
 

ph1lph1l

Commendable
Feb 25, 2016
17
0
1,510


none of the memtests could actually go through. the pc would restart after several minutes of memtesting. is it the cmos battery i should try swapping?
 
So memtest would not complete.
Was that pre-built PC, or did you built it yourself? I'm suspecting wrong BIOS RAM settings .

As for battery, like I posted before, it's very unlikely. But if you have one nearby (tip: some regular home electronic devices often use the same battery type as mobo, for example I have kitchen scale with them), it won't hurt to test it.
 

ph1lph1l

Commendable
Feb 25, 2016
17
0
1,510

built it myself, didn't do anything to the ram timings or settings it's all default. what would you suggest i try? and thanks for repeatedly taking time out of your day to help me.
 
Default values should work well, on a good mobo like this. Still, we cannot rule out it could not work properly for some reason.
I guess you don't have a different RAM stick for a test purpose? If you do, use it and run memtest since that seems to fastest method to cause the problem to manifest itself.
Also check out if your RAM is XMP capable.
 

ph1lph1l

Commendable
Feb 25, 2016
17
0
1,510


it's the lowest speed ram so i don't have an xmp option, and i can't run a memtest because after a certain amount of time doing anything the pc will just go into a boot loop be it just idle in the bios settings or at desktop. i also just got done re-seating everything to no avail.
 


If it goes to boot loop after being idle in BIOS, it's definitely hardware problem. Did you overclocked CPU or RAM at any time?
 

ph1lph1l

Commendable
Feb 25, 2016
17
0
1,510


i cannot overclock the ram.
 

ph1lph1l

Commendable
Feb 25, 2016
17
0
1,510


will do man, thanks for all your help.
 
Copied from PM: "i just got my brand new cpu, booted up to the bios settings and let it sit there for a few minutes but it still will eventually hard reset into a boot loop. do you think i should RMA the mobo next?"

Did you by any chance made a check for bent pins on CPU socket when you installed new CPU?
Also, had you any chance to test your RAM with memtest on some other comp? It would really help to know that RAM is good.
One more thing - after comp does this hard reset, and goes to boot cycle, does it give any beep error codes or BIOS error messages?
 

ph1lph1l

Commendable
Feb 25, 2016
17
0
1,510
all pins in the CPU socket seem good. can't test the ram in another board but the pc does the same thing no matter what slot a single stick of ram is in. don't have a pc speaker so can't get a beep code and no bios error messages. there are a few reviews about boot loops with this mobo and gigabyte customer service is terrible i've read, they still haven't responded to me. i've also read a few reviews of boot loops with this mobo and they have a pretty sizeable $40 MIR for it right now.
 
Honestly, right now it's like 50/50 - either ram or mobo. I'm afraid can't give you a better advice. It is your call now. If you have an option of buying mobo just for a test and returning it later without costs - sure you can try it, why not.
 

ph1lph1l

Commendable
Feb 25, 2016
17
0
1,510
mobo came back from RMA with no problems found
new CPU from RMA
new PSU from RMA
had tested with a brand new set of ram and got same problems when testing months ago

still getting a hard restart whenever i even begin to run a benchmark

should i RMA this ram still to try and cross out any chance of multiple simultaneous hardware failures? even if i try yet another memtest there is a chance the pc will still reboot during it like last time.
 

ph1lph1l

Commendable
Feb 25, 2016
17
0
1,510
right now i was running benchmarks with my gpu in because the system seemed stable with everything but the gpu in but i didn't really benchmark the cpu or anything. as soon as i click the preset to benchmark with the gpu in i instantly crash ( http://i.imgur.com/wkrw8oB.png ) so now it might be a ram AND gpu problem i really have no idea.
 
I meant other things: drives, usb devices, WiFi card, whatever else. All new equipment should not give the same problem as old, so maybe we should start looking elsewhere. Normally faulty device should not cause such symptoms, but this situation is far from normal.