[VL92]

Hi guys, as you can tell from title I'm getting the infamous bootloop. I can leave my pc on for over 10 minutes trying to turn itself on but it just keeps rebooting. From the Debug screen it stops just after number 96. When I can boot up it says there was a hardware configuarion failure, so I unplugged my video card, hard drive etc and used the onboad video but still nothing. Using latest bios, any help would be nice thanks

EDIT: I've also reset the cmod and removed the battery, it is also cold in England apperently there is some safety feature on the bios if it gets to cold, possibly this is it? Who knows.

 

[VL92]

Now my computer won't boot up at all after switching it off and on at the back a few times,

EDIT: Now it's back but still rebooting itself

 

[PureBlackFire]

see if updating to the latest bios helps.

 

[VL92]

I'm unable to get any mage, my computer just reboots with no image and no bios option

 

[Anth0789]

Are all the fans spinning up?

 

[VL92]

Yep, now it seems to stay on debug number 72 longer then when it hit 96 it reboots. I'll do some googling to find out what this might indicate but any advice would be great

Okay from google I found out 96 indicates assign PCI device resources, so since it stops the second it hits that my guess would be it isn't able to due to hardware reasons?

 

[Sin0822]

those codes are for BCLK change, like for instance if you want to change your BCLk from 100 to 105mhz the board will reboot goto 96 and then shutdown and if it works it will goto POST if not then it hangs at 72. Why your board is doing that IDK, something is not right though. You should clear the CMOS and take the battery out and clear it again.

 

[deepor]

You can force the second BIOS chip to take over by keeping the power button pressed when turning the PC on.

Before you do that, do not turn off the PC through the PSU. Keep everything connected to a power outlet. Force the PC to turn off with the normal power switch of the case. You might have to keep it pressed for four seconds until the PC shuts down. After it's off, do it like I described it: press the power button and do not let go.

The second BIOS will take over and you will get a short menu on screen, asking you how to proceed. It will have an entry for copying the second chip's content onto the first chip that has that boot loop problem. Use that option, and wait until the PC reboots a few times to set everything up.

It will work again at that point, but this will be the ancient BIOS version that's on the second chip from the time the board was built. You will have to flash something current afterwards.

 

[Sin0822]

or he can just flick the dual BIOS switch

 

[VL92]

Alright thanks I'll try that, theres also a switch I've noticed that changes it, not sure how to work it however

EDIT: Yeah ^^ How do I use it? I saw it earlier and switched it but nothing seemed to happen apart from the light changing positions

 

[Sin0822]

that light is the BIOS selector. IMO this happened to a UP5 of mine i had to use my other UP5 and trash the first one. IMO i would RMA and tell them it does this if you can't fix it.

If yu clear the CMOS and it still does this then its bad.

BTW try one more thing for me and tell me what happens, what if you take out the memory and replace the memory with another pair of memory? Does it still do this or boot right up?

So you do have trouble after clearing the CMOS, right?

 

[VL92]

Sadly I have no other RAM, but if I remove one stick into a different slot or take one out it still happen. Perhaps I can't clear the cmos, it was fine until I turned my pc off for hours and came home when it was raining, maybe the weather is effecting it or something? Do you think I should leave it cycling or turn it off for hours and try to turn it on and update the bios to a beta etc?

 

[Tartar]

I have this board and all that I do when it occasionally hangs is to remove the power cable completely from the power supply, wait a sec and plug it back in and fire it up. I realize that resetting the CMOS and pulling the battery should do the trick, but for the sake of trying something new, it might be worth a minute to play with it.

FYI, just thougt I would point out that I am using 4 4gb sticks of corsair vengeance w/ X.M.P setting at 1600.

 

[VL92]

Same type of ram as me, Vengeance and speed I believe 2x4 GB

 

[Sin0822]

Quote:

Originally Posted by VL92

Sadly I have no other RAM, but if I remove one stick into a different slot or take one out it still happen. Perhaps I can't clear the cmos, it was fine until I turned my pc off for hours and came home when it was raining, maybe the weather is effecting it or something? Do you think I should leave it cycling or turn it off for hours and try to turn it on and update the bios to a beta etc?

Was there perhaps a lighting strike or something? The behavior you are describing requires an RMA.

 

[VL92]

Quote:

Originally Posted by Sin0822

Was there perhaps a lighting strike or something? The behavior you are describing requires an RMA.

Nope

And yeah same speed, took out the cmos battery unplugged it and now it's gone back to cycling, it d

 

[VL92]

Quote:

Originally Posted by Sin0822

Was there perhaps a lighting strike or something? The behavior you are describing requires an RMA.

Nope

And yeah same speed, took out the cmos battery unplugged it and now it's gone back to cycling, it did this before but never like this, maybe it was after I flashed it. Also sorry for the multiple posts, laptop froze -.-

EDIT: Okay if I remove all the ram, it stops at code 53 and reboots. Indicating it is reconizing there is no ram avaible, a glimmer of hope at least

 

[Sin0822]

the board really shouldn't act like that. If you aren't able to get a POST then the board is most likely done for. Do try to do the backup BIOS thing, but if it isn't even posting then that wont help. IMO i would pull the system apart and put it back together. Pull out the CPU and remount it and so on, take it out of the case.

 

[VL92]

Quote:

Originally Posted by Sin0822

the board really shouldn't act like that. If you aren't able to get a POST then the board is most likely done for. Do try to do the backup BIOS thing, but if it isn't even posting then that wont help. IMO i would pull the system apart and put it back together. Pull out the CPU and remount it and so on, take it out of the case.

Good idea, going to make a make shift workbench using my motherboards case, make it easier. Hopefully it'll boot up and I'll be able to update the bios.

 

[deepor]

I mentioned that stuff about the second BIOS chip because I had a problem that I'd describe exactly as in the OP with my D3H. The board was in a boot loop and you could hear the tiniest beep from the speaker. It was more like a click as it was so short. This continued indefinitely in a loop. The D3H doesn't have that display for what it's doing like the UD3H, so there's no way to compare if it's really the same boot loop behavior.

I don't quite remember what I did exactly to get the board to that point. I think one of the two times was caused when trying to overclock memory (a lot). The other case was trying a recent beta UEFI, playing around with Windows 8 and Secure Boot and Fast Boot. Both times, clearing CMOS didn't work. Nothing could revive the first BIOS chip. It didn't make sense at all. I'm also pretty sure one of the times I could actually boot Windows and do experiments, but after rebooting the board started with its boot loop shenanigans. I think that happened when I was doing things to the memory settings.