Associate
- Joined
- 25 Jun 2013
- Posts
- 9
A while back i built a backup server based around a ASRock J4205-ITX, as i was excited by the new (at the time) Apollo Lake processor. It's left running 24-7 and records cctv footage etc. It uses Windows 10 as it's OS.
At random it will suddenly power itself off every few days and I cant get to the bottom of why. There doesnt seem to be any logic to it. When I try and reboot, the first time it powers up but outputs nothing to the display, a 2nd restart brings up the bios screen and a save of those settings always triggers a 3rd reboot which gets all the way to the windows login splash screen, which appears for a split second before powering off again. A 4th reboot finally brings it back online.
I've tried updating the m'board firmware, first of all i tried the latest offical version which i believe was 1.4, then after some googling I found version 1.5 which had been removed form the official listed versions. There was also a version 1.6 listed unofficially but comments suggested this could cause bricking so I've avoided that.
Any suggestions on how i could go about diagnosing both the powering off, and the wierd sequence of reboots needed to get it powered back up?
Thanks!
At random it will suddenly power itself off every few days and I cant get to the bottom of why. There doesnt seem to be any logic to it. When I try and reboot, the first time it powers up but outputs nothing to the display, a 2nd restart brings up the bios screen and a save of those settings always triggers a 3rd reboot which gets all the way to the windows login splash screen, which appears for a split second before powering off again. A 4th reboot finally brings it back online.
I've tried updating the m'board firmware, first of all i tried the latest offical version which i believe was 1.4, then after some googling I found version 1.5 which had been removed form the official listed versions. There was also a version 1.6 listed unofficially but comments suggested this could cause bricking so I've avoided that.
Any suggestions on how i could go about diagnosing both the powering off, and the wierd sequence of reboots needed to get it powered back up?
Thanks!