PC only posts randomly

[thiagohpc]

My PC posts randomly, as far as i can tell. I was using it normally and restarted to solve a bug, but after that it only posts eventually. I've tried to reset CMOS, remove battery and reset CMOS, tried to post w/ no storage, no storage and no GPU, with only one stick of ram (tried both sticks, one at a time). It really seems to be random, got it to post twice. The first sucessful post was after i removed storage, GPU and one of the sticks of RAM. Swapped both sticks to verify if that was the issue, no post. Swapped back to the same stick of RAM that posted earlier and it wouldn't post anymore. The second sucessful post was after i reinstalled all parts, GPU, both sticks of RAM, storage, etc. Everything showed up in BIOS as it should, but with memory running at 2133. Applied XMP and boot order for the drivers and it refused to post again. Checked cables (both HDMI and DP), screen, power, etc, and everything works as it should. It really seems like the CPU or the MB decides to work and post randomly. I don't have access to other compatible hardware to test CPU and MB, anyone has any idea on how to solve this without finding another MB/CPU?

 

 

Specs:

i7 7700K

Asus Z170M-Plus

2x Hyper X 8GB 2400

Galax RTX 2070 Super

1x Samsung 1TB SATA SSD

1x Kingston 128GB SATA SSD

2x WD HDD 1TB

Corsair VS600 (i know, i'm pushing it to the limit)

[SpookyCitrus]

Most likely your motherboard. It's rare for a CPU to just go out.

[Light-Yagami]

If motherboard doesn't spit out codes or light patterns or something that will let you know what's making it not post, then it's most likely the motherboard. If the CPU hasn't been reseated and it worked fine before you started having issues, then it's probably nothing wrong with it.  

 

[Somerandomtechyboi]

First thing id try is dunking some 99% IPA on the socket just to make sure theres no contamination cause its pretty common for sockets to get dirty and start malfunctioning, also wipe the back of the cpu just to make sure thats not contaminated either

 

Youll also wanna have a go at cleaning the golden ram contacts just to make sure rams arent contaminated

[thiagohpc]

32 minutes ago, Light-Yagami said:

If motherboard doesn't spit out codes or light patterns or something that will let you know what's making it not post, then it's most likely the motherboard. If the CPU hasn't been reseated and it worked fine before you started having issues, then it's probably nothing wrong with it.  

 

I managed to scavenge a buzzer and install it. I got 4 longer beeps and one short. I tried to attach a recording of it here, don't know if it worked. I also can't seem to find this exact beep code, can someone point me in the right direction please?

[Light-Yagami]

56 minutes ago, thiagohpc said:

I managed to scavenge a buzzer and install it. I got 4 longer beeps and one short. I tried to attach a recording of it here, don't know if it worked. I also can't seem to find this exact beep code, can someone point me in the right direction please?

Try reseating the CPU, pull all RAM out, plug everything else in. Try to boot without RAM. See what it does. Then, try booting with one RAM stick, testing different slots if the first one doesn't work. If you get it to boot, just try get it to boot into windows.. No BIOS fiddling. This seems like motherboard failure to me.

 

Keep in mind - when you switch components around, PSU switch should ALWAYS be in OFF position. If you're moving components around while the system has power running through it, even if turned on, there's a chance of shorting things out.

[thiagohpc]

So, this is like 3h after i turned the PC off and went to dinner. I was about to start pulling RAM, reseating the CPU, etc, and decided to power it up one last time to get a baseline on the PC behavior... i turned the PSU switch back on (because i forgot to earlier), pressed the power button and the SOB turned on like nothing ever happened. XMP enabled, it booted to the correct drive, RAM, GPU. The only thing wrong was the time.

Since i already had this issue for a few weeks now, i'm willing to bet that if i put it to sleep, it will wake up like it did during those weeks. It seems that this issue only pops up when restarting or turning it back on after a complete shutdown.

Obviously there's something wrong with it, but now at least i have another way to perform tests. Any suggestions?