AsRock Extreme4 Gen3 - constant rebooting

Veevoh

Veevoh

Veevoh

Associate
Joined
18 Aug 2011
Posts
41
Location
Newcastle
So I've just built my first machine (specs below) and it randomly powers off or reboots occasionally. Sometimes it boots straight back up, but other times it will not power on until I hit the 'Clear CMOS' button on the motherboard. Sometimes it doesn't even finish booting before it powers off again. I've checked the power connections, both the external one, and the ones connected to the components and they are all fine.

This is what I'm running:
Intel i5 2500k 3.3Ghz (currently at stock speed).
AsRock Extreme4 Gen 3 motherboard.
8GB Corsair Dominator RAM (2x4GB).
Corsair H60 cooler.
Corsair AX750 modular PSU.
Windows 7 Ultimate SP1.
Two SATA3 7200rpm Western Digital Caviar Green 1TB HDDs.
GPU has not arrived yet.

The fact it works when I hit 'Clear CMOS' implies, to me at least, that the problem is something to do with the motherboard. The UEFI (or whatever it is called) has been reset and I am running the board at factory settings, no changes anywhere in the UEFI.

If someone could help me out with this I would be really appreciative.
 
Yup. Every screw point is on a standoff. There may be a fan cable or something under the mobo, I can't remember. Do you think that could affect it? Also, should I try unplugging everything and removing the CPU, cooler, and RAM and then reinstall?
 
Haven't got a reset connector plugged in. It's not constant, I can run the machine for hours between it happening, but then when it happens it seems to happen often at the same time.

I'll try removing all the connectors, and also the CMOS battery to see if it works. It's difficult to test though, as the poweroffs are so far apart.
 
Can you explain a little why I should do this? I am fully willing to learn about things like this, and overclocking in general, but how will this affect my system? Will it run more stable with a fixed voltage than an 'automatic' one. It's currently running at 0.894V.

Also, when I get my graphics card, should I revert this back to auto, or keep it fixed at 1.20?
 
It does seem to be crashing mostly when I have tried to play a couple of games without a dedicated graphics card (World of Warcraft and Minecraft) so I think this might be true. I'm getting my graphics card soon which should hopefully sort this out then. Thanks Chippy for the great explanation. I'm now running with a fixed vcore of 1.2v and I will report back if I have further problems.
 
Wow. That really sucks. I don't know anything about any of the brands to be honest, but it's a shame such a popular board is causing so many problems.

As I said previously, I have upped my vcore to 1.2V and this appears to have solved my problem (after about 6 hours of gameplay it hasn't reboot once). Should I now try and lower that vcore back down a bit? To something like 1.1 or something, or is 1.2 a reasonable number to leave it at?
 
Ok so it's started again. I'm pretty angry about this as I thought I'd fixed it. I still have a fixed vcore of 1.2 and it's occuring still. I'm going to put a GTX260 in until I put the proper card in, I can't live with this problem.

Don't think I will buy AsRock again, thought I was getting good value for money but this is a bit of a joke tbh.
 
I understand it's a new board and stuff but it's really frustrating. I thought I would give one of the none-'A-list' brands a chance but now I feel I should have went with Asus or something.

Hopefully I can resolve this with a graphics card but it's a shame it's happening for people who choose not to have a dedicated card and want onboard graphics.
 
Last edited:
Ok well I received my 560TI today, installed it, removed CMOS battery, rewired the entire machine, and still getting reboots. I get error 67 I think it is on the Dr Debug LED screen which is to do with the CPU. Close to RMA'ing it now :(

I have tried setting fixed vcore at 1.2, setting the LLC to Level 1. Still no luck, rebooting within 15 seconds of hitting the desktop most of the time now.

I have the harddrives in IDE mode, simply because I forgot to swap before installation and cba to swap and reinstall. This couldn't be anything to do with it could it?

Chippy, I'll have to check which profile I am using, but it will most likely be default.
 
Right so even with my new 560TI it's not working, nor with the 1.10 BIOS. I've done everything; offset the Vcore, fix vcore, rewired everything, switched RAM to A2/B2 slots, removed CMOS battery, tried the preset overclocks.

I love this board, and want it to work. :(
 
Last edited:
Davefran said:
That looks like a problem with the CPU then, not the board.
Click to expand...

Maybe, but I am not sure. It only showed that display once; it almost always just reboots and doesn't display an error code, just the normal numbers it hops through as it boots up.

I wish I had another Sandybridge processor to test :(
 
chippy08 said:
Well if you go that route and you have had the cpu more than 28 days be prepared for a 1 month wait to get a replacement cpu if they send it off.
personaly i think you should send both and let them test it to see if they can get it stable.
Click to expand...

I'll speak to OCUK in the morning and see what they think. Full system is about a week old I think.
 
You must log in or register to reply here.
Back
Top Bottom