Associate
I have that error as well [plus others] and it seems ASRock have a problem with keyboards being recognised
RMA'd mine, it was completely dead after working fine for a couple of days.
I also suffered the keyboard problem with my Logitech G510 not being recognised during boot up.
I was going to replace it with another but decided to go for an EVGA Z68 in the end. It's a shame as it's a feature rich board and the PCIe slot layout is one of the best available for keeping dual gfx cards spaced nicely while using a dedicated sound card.
really? thats a shame... was still looking to get it
the features for the price are fantastic
Is there anyone who WOULD recommend this board as reliable?
I can! Running at 5GHZ now with a 6990/6970/6970 also Asus pcie sound card and killer 2100 lan card all running 24/7 no problems, only thing i had a problem with was the psu not cutting it under full load.. Now on a 1250watt psu and flying ..
is the serial number anywhere on the board or just on the label on the box? I've tried looking on the board and can't see any where that matches the serial on the label, or any bit that clearly syas 'serial number' on the board.
don't know if anyone is still reading this thread as been 25 days since last post
have emailed asrock the serial number, now to wait for them to reply with the address + rma number.
I'll keep my fingers crossed for you, hope you get it sorted soon
Nice to hear it is going well for you - not so good for me as I have a pig of a 2600K which wont even do a stable 4.6 without silly volts/heat, and this even under water. Oh well just have to face the fact I have a lousy cpu
What Ram do you have, all i use are the auto OC settings at 4.8 no probs, so was thinking it maybe your ram poss??
Nice to hear it is going well for you - not so good for me as I have a pig of a 2600K which wont even do a stable 4.6 without silly volts/heat, and this even under water. Oh well just have to face the fact I have a lousy cpu
What Ram do you have, all i use are the auto OC settings at 4.8 no probs, so was thinking it maybe your ram poss??
The ram is fine - it is the g skill here
http://www.overclockers.co.uk/showproduct.php?prodid=MY-060-GS&groupid=701&catid=8&subcat=1517
Bought 2 sets ie 16Gb. In any case I left the ram at standard settings and timings to leave it out of the overclocking scenario to see how the chip went first. I deffo just had a very standard 2600K - dont get me wrong the cpu worked fine but just guzzled v core on o clock, which obviously meant I hit unsustainable temps much earlier than I would have hoped.
Mark
neither of the 2 stickers you've circled or the one next to the 24pin atx connector match the serial number it says on the label on the box.
edit: just had a look on the asrock site and it says the serial number is on a yellow sticker on one of the i/o panel 'bit's', I found it on the one with the usb3.0 matches the one on the label on the box.
have emailed asrock the serial number, now to wait for them to reply with the address + rma number.
they've replied with the rma number and address, just need to pack it up and post it to them. anyone know how much royal mail charge to post parcel to holland? looking on parceltogo the cheapest was £18(insured only to £50, to insure the value of the mobo will cost another £10 or so), plus asrock want 25 euro/£15 in cash in an envelope to cover the return cost.
they say its a 5 day turn around from when they recieve the board, so thinking if its worth me getting a temp board as I've already waited a month since I started building and found the issue.
they've replied with the rma number and address, just need to pack it up and post it to them. anyone know how much royal mail charge to post parcel to holland? looking on parceltogo the cheapest was £18(insured only to £50, to insure the value of the mobo will cost another £10 or so), plus asrock want 25 euro/£15 in cash in an envelope to cover the return cost.
they say its a 5 day turn around from when they recieve the board, so thinking if its worth me getting a temp board as I've already waited a month since I started building and found the issue.