New build will boot and is rock solid stable, but can't *reboot*.

slugg

Diamond Member
Feb 17, 2002
4,723
80
91
I've never seen this problem before. I just built a computer and everything is fine, except 9 times out of 10, it fails to reboot. I've stripped it down to the minimal hardware in order to minimize variables. The hardware is:

Asrock Q1900B-ITX Motherboard (built in CPU)
Crucial 4 gb DDR3 x2 (8 gb total)
FortronSource 300 watt PSU (forgot exact model, but it's 80+ gold)

How to recreate:
If you get the machine to reboot in any way via software, the machine will shutdown for a split second like many other computers, then turn back on. I've seen this behavior a lot, so I say it's normal. But the weird thing is when it turns back on, USB does not get any power, nothing gets displayed, the OS does not boot, but the fans are spinning.

This happens with any operating system, and even the board's own UEFI setup utility. So for example, if I change some BIOS settings and choose "save and exit," the settings will save, then the display will shut off, USB will lose power, and the fans keep on spinning. If I then manually shut off the computer and start it up again, everything is fine.

I'm at a loss here. I have no idea what's causing this. I've used all sorts of combinations of bios settings and I'm running the minimal hardware required to POST and this still happens. Any ideas?
 
Last edited:

MagnusTheBrewer

IN MEMORIAM
Jun 19, 2004
24,122
1,594
126
It seems like a Bios problem to me. It's unusual but, you might try replacing the battery even though it's a new build.
 

TerryMathews

Lifer
Oct 9, 1999
11,464
2
0
I've never seen this problem before. I just built a computer and everything is fine, except 9 times out of 10, it fails to reboot. I've stripped it down to the minimal hardware in order to minimize variables. The hardware is:

Asrock Q1900B-ITX Motherboard (built in CPU)
Crucial 4 gb DDR3 x2 (8 gb total)
FortronSource 300 watt PSU (forgot exact model, but it's 80+ gold)

How to recreate:
If you get the machine to reboot in any way via software, the machine will shutdown for a split second like many other computers, then turn back on. I've seen this behavior a lot, so I say it's normal. But the weird thing is when it turns back on, USB does not get any power, nothing gets displayed, the OS does not boot, but the fans are spinning.

This happens with any operating system, and even the board's own UEFI setup utility. So for example, if I change some BIOS settings and choose "save and exit," the settings will save, then the display will shut off, USB will lose power, and the fans keep on spinning. If I then manually shut off the computer and start it up again, everything is fine.

I'm at a loss here. I have no idea what's causing this. I've used all sorts of combinations of bios settings and I'm running the minimal hardware required to POST and this still happens. Any ideas?

Is the machine sitting fully outside a case? I'm suspecting front panel wiring.
 

slugg

Diamond Member
Feb 17, 2002
4,723
80
91
Is the machine sitting fully outside a case? I'm suspecting front panel wiring.

It's inside this case: Antec ISK600

What can I check with regard to the front panel wiring? I'm not sure how that can cause this... I even tried unplugging all of the front panel except for the power button; still no go.
 

Steltek

Diamond Member
Mar 29, 2001
3,292
1,038
136
Have you tried flashing the BIOS with the most recent version? If you have the most recent version, you might try re-flashing the BIOS with that version or reverting to the next most recent version to see if there is a bug.

Also, does this happen if you run with just one memory module? I'd also recommend pulling the board and trying it on a non-conductive surface outside the case to see if you might have a ground fault somewhere between the board and the case.
 

slugg

Diamond Member
Feb 17, 2002
4,723
80
91
It came with the latest version of the bios from Newegg. I did try reflashing, but it won't flash because I already have the latest. I haven't tried it with one stick of memory, but I'll give it a shot tomorrow. Memtest passed just fine, however.

I sent in a ticket to Asrock and is think I'm going to push to get this board replaced. Do you guys think that's reasonable at this point?
 

TerryMathews

Lifer
Oct 9, 1999
11,464
2
0
It's inside this case: Antec ISK600

What can I check with regard to the front panel wiring? I'm not sure how that can cause this... I even tried unplugging all of the front panel except for the power button; still no go.

Pull it out of the case, plug the PSU in, and use a screwdriver to short the power switch pins to turn on.

I suspect your power switch may be plugged into the right pins.
 

slugg

Diamond Member
Feb 17, 2002
4,723
80
91
Revisiting this.

I got my second board from an RMA. This is still happening. I've confirmed with Asrock that the two motherboards are from the same batch. Other people aren't reporting any problems.

Any other ideas?
 

boomerang

Lifer
Jun 19, 2000
18,883
641
126
Just looked through the manual for your board. Based on your earlier posts, it sounds like you have installed at least some of the add-on software that came with the board. If so, I would uninstall all of it as a trouble shooting step.

Other than that, you have received all the advice I would give but I don't like it when advice is given and no answers are received. For example it was suggested you remove the board from the case and you did not reply. Did you do this? It is helpful for us to know the answers.

I would do these steps in this order if removing all add-on software does not cure the problem.

Reset the CMOS following the procedure in the manual.

Reflash the BIOS to newer version if available. Now, you say you're on the latest so I would flash to the previous version which looks to be 1.30. 1.40 has a release date only a little over a week ago. Are you on 1.30 or 1.40? Flash accordingly.

Take the board out of the case. Connect only the PS, the CPU fan, your monitor and the HD.

Then you're down to compatibility problems. Is your RAM truly compatible? It's Crucial so you should be able to check at their site. I have even called Crucial to find that the chips on the RAM I have have been giving them problems with such and such a board. They then supplied me with memory that worked.

Is the CPU you have compatible with the board at the BIOS level you're at?

Lastly, substitute a different HD. Are you running an SSD? You make no mention of what HD you are using. These last steps are sort of grasping at straws, but at this point you're down to something obscure and you have to eliminate them as a variable.

The chances of two boards having the same problem is miniscule IMO. It's something common between the two and that is attached hardware or installed software.

I suspect the add-on software you installed from ASRock is putting your computer into a sleep state. In reading through your manual briefly, there are some utilities that IMO are questionable as to their usefullness. One piece of software puts the computer into a state where it will get your email and your social networking info while it is in a state of suspension. This sounds like a potential source of trouble to me which is why I suggest uninstalling all of it. Drivers only. Additional software, nyet.

A quick story. I have a laptop running 8.1 (came with 8) that from time to time the cursor would respond to a tap from the touchpad by jumping up to the upper right corner of the screen. The only way to correct it was to reboot. I have tried many things over the course of many months but I eventually fixed it by turning off the slide show of my desktop background. A feature built right into the operating system. It seemed like a hardware issue but it was a software issue.
 

slugg

Diamond Member
Feb 17, 2002
4,723
80
91
Just looked through the manual for your board. Based on your earlier posts, it sounds like you have installed at least some of the add-on software that came with the board. If so, I would uninstall all of it as a trouble shooting step.

Other than that, you have received all the advice I would give but I don't like it when advice is given and no answers are received. For example it was suggested you remove the board from the case and you did not reply. Did you do this? It is helpful for us to know the answers.

I would do these steps in this order if removing all add-on software does not cure the problem.

Reset the CMOS following the procedure in the manual.

Reflash the BIOS to newer version if available. Now, you say you're on the latest so I would flash to the previous version which looks to be 1.30. 1.40 has a release date only a little over a week ago. Are you on 1.30 or 1.40? Flash accordingly.

Take the board out of the case. Connect only the PS, the CPU fan, your monitor and the HD.

Then you're down to compatibility problems. Is your RAM truly compatible? It's Crucial so you should be able to check at their site. I have even called Crucial to find that the chips on the RAM I have have been giving them problems with such and such a board. They then supplied me with memory that worked.

Is the CPU you have compatible with the board at the BIOS level you're at?

Lastly, substitute a different HD. Are you running an SSD? You make no mention of what HD you are using. These last steps are sort of grasping at straws, but at this point you're down to something obscure and you have to eliminate them as a variable.

The chances of two boards having the same problem is miniscule IMO. It's something common between the two and that is attached hardware or installed software.

I suspect the add-on software you installed from ASRock is putting your computer into a sleep state. In reading through your manual briefly, there are some utilities that IMO are questionable as to their usefullness. One piece of software puts the computer into a state where it will get your email and your social networking info while it is in a state of suspension. This sounds like a potential source of trouble to me which is why I suggest uninstalling all of it. Drivers only. Additional software, nyet.

A quick story. I have a laptop running 8.1 (came with 8) that from time to time the cursor would respond to a tap from the touchpad by jumping up to the upper right corner of the screen. The only way to correct it was to reboot. I have tried many things over the course of many months but I eventually fixed it by turning off the slide show of my desktop background. A feature built right into the operating system. It seemed like a hardware issue but it was a software issue.

Yes, I have tried removing it from the case.

No, I don't have any addon software from Asrock. In fact, even if I only run the minimum required hardware to POST (i.e. Memory and PSU, since the CPU is embedded), it still can't reboot, like from CMOS/BIOS, for example. I know the CPU is compatible because it's embedded on the motherboard.

The one thing I'm not sure about is the bios version. At the time of writing this thread, 1.30 was the latest. When I swapped the boards, I did not check, but I would assume it's running 1.30, as it's from the same batch. I didn't know a version was released. I'll give that a shot.
 

slugg

Diamond Member
Feb 17, 2002
4,723
80
91
Have you tried flashing the BIOS with the most recent version? If you have the most recent version, you might try re-flashing the BIOS with that version or reverting to the next most recent version to see if there is a bug.

Also, does this happen if you run with just one memory module? I'd also recommend pulling the board and trying it on a non-conductive surface outside the case to see if you might have a ground fault somewhere between the board and the case.

Still happens with one stick. I tried both slots witch each stick.
 

boomerang

Lifer
Jun 19, 2000
18,883
641
126
Yes, I have tried removing it from the case.

No, I don't have any addon software from Asrock. In fact, even if I only run the minimum required hardware to POST (i.e. Memory and PSU, since the CPU is embedded), it still can't reboot, like from CMOS/BIOS, for example. I know the CPU is compatible because it's embedded on the motherboard.

The one thing I'm not sure about is the bios version. At the time of writing this thread, 1.30 was the latest. When I swapped the boards, I did not check, but I would assume it's running 1.30, as it's from the same batch. I didn't know a version was released. I'll give that a shot.
Sorry for my confusion. You'd think if I looked at your manual I would have realized the CPU was embedded. I'm a little embarrassed actually...
 

chusteczka

Diamond Member
Apr 12, 2006
3,399
3
71
I built an ASRock with a similar reboot malfunction. I update this computer remotely from another state and am unable to test it. The computer rebooted fine when I rebuilt it, then I gave it to my brother. He either did something to it or it broke on its own but now it will not reboot. When remotely installing updates and I need to reboot the computer, I remotely shut it down and ask him to manually start it. I have not yet figured out the problem but am unable to troubleshoot due to geographic separation.

Just letting you know that your system is not the only one and that it is not something new with ASRock.

ASRock A785GXH/128M AM3/AM2+/AM2 AMD 785G HDMI ATX AMD Motherboard
http://www.newegg.com/Product/Produc...82E16813157180
 

slugg

Diamond Member
Feb 17, 2002
4,723
80
91
I built an ASRock with a similar reboot malfunction. I update this computer remotely from another state and am unable to test it. The computer rebooted fine when I rebuilt it, then I gave it to my brother. He either did something to it or it broke on its own but now it will not reboot. When remotely installing updates and I need to reboot the computer, I remotely shut it down and ask him to manually start it. I have not yet figured out the problem but am unable to troubleshoot due to geographic separation.

Just letting you know that your system is not the only one and that it is not something new with ASRock.

ASRock A785GXH/128M AM3/AM2+/AM2 AMD 785G HDMI ATX AMD Motherboard
http://www.newegg.com/Product/Produc...82E16813157180

Man, this is good to know.

I won't have a chance to test the new bios until tomorrow. Hopefully that does the trick.