Strange Motherboard POST Behavior

[ApplesOfEpicness]

I recently moved a SSF build into a rajintek metis case and have been having troubles getting it working. When I turned it on for the first time after moving, the bios had reset itself for some reason. I reset my settings and save/exit. Then nothing. No post screen, just fans and lights. If I reset the cmos, it posts, but resetting it in any way triggers the previous behavior. Anyone can help me out on this? Everything was stable before the move.

 

z170i gaming asus

i7-6700k

gtx 1080 mini

corsair sff 600w

samsung ssd

[mr moose]

Have you tried re-seating your ram and disconnecting anything not necessary (like extra drives and peripherals).

 

Also I know it sounds silly but have you double checked the header to ensure the reset switch and power button/LED are in the right place?   Wouldn't be the first time a power LED has been plugged into the reset header.

[ApplesOfEpicness]

9 minutes ago, mr moose said:

Have you tried re-seating your ram and disconnecting anything not necessary (like extra drives and peripherals).

 

Also I know it sounds silly but have you double checked the header to ensure the reset switch and power button/LED are in the right place?   Wouldn't be the first time a power LED has been plugged into the reset header.

Yes, I’ve reseated a few times. It seems to be software/bios related since I can actually enter windows after a cmos reset, but trying to restart the computer in any way bricks it again.

[mr moose]

Hmmm, that's weird. So essentially you have to reset the CMOS in order to get it to boot every time?

[ApplesOfEpicness]

5 minutes ago, mr moose said:

Hmmm, that's weird. So essentially you have to reset the CMOS in order to get it to boot every time?

Pretty much. If I don’t reset the cmos, I just get a blank screen/no signal. My hunch is that it’s ram related. At one point the cpu and dram led’s were alternating between each other. Looked around the web and it seems that that could be a ram issue. I’ll do a bit of tweaking in morning.

 

Really wish I had a speaker. Wonder what post codes it’s putting out.

[mr moose]

O.K, do you have a wireless keyboard plugged in?  Sometimes they can interfere with the boot (don't ask me why I just read about it once), if not you could check the bios battery and if that is O.K you could try re flashing the bios just in case it became corrupted during the move.  If all that doesn't work take the motherboard out of the case and try it on a box or something to rule out the case being the issue ( I doubt it but you never now).   Finally if you get to here and it still does this weird thing then you can try unplugging everything (absolutely everything) , removing the bios battery and setting the CMOS jumper to clear and leave it for 15 minutes to totally drain of all residual power.

 

Failing all that I might be stumped for an answer.

[ApplesOfEpicness]

9 hours ago, mr moose said:

O.K, do you have a wireless keyboard plugged in?  Sometimes they can interfere with the boot (don't ask me why I just read about it once), if not you could check the bios battery and if that is O.K you could try re flashing the bios just in case it became corrupted during the move.  If all that doesn't work take the motherboard out of the case and try it on a box or something to rule out the case being the issue ( I doubt it but you never now).   Finally if you get to here and it still does this weird thing then you can try unplugging everything (absolutely everything) , removing the bios battery and setting the CMOS jumper to clear and leave it for 15 minutes to totally drain of all residual power.

 

Failing all that I might be stumped for an answer.

I’m not sure I want to reflash if the end possibility is that it might brick itself in the process. That said, I did do some bios tweaking and it works now apparently.

 

Changes:

DRAM freq - auto->2400mhz

all fans set to pwm mode.

 

It looks like the board just didn’t know how to properly set RAM timings etc. Forcing it to do the rated spec in my ram fixed it.