Sign in with
Sign up | Sign in
Your question
Closed

AsRock Extreme3 Gen3

Last response: in Motherboards
Share
January 25, 2012 10:01:30 PM

I have a very odd situation, nothing i've found has been similar... When booting there are two scenarios.
1. Boots normal, goes through post fine and windows loads
I shut computer down and then when I turn the computer back on it wont start and stops on post code 2f (Memory Initialization (other))
So half the time my computer works, the other half it does not. I'm also able to get around the computer posting 2f by either unplugging the psu or clearing cmos. I have not Overclocked my system or anything and I'm quite lost as to what is going on.

Core i7 2600k
Asrock z68 extreme3 Gen3
ABS 1100 W psu
EVGA gtx580
Thorv2
Edit: Suppose the type of ram is important? Hah.
Gskill Sniper Low Voltage 2x 4gb ddr3 (Says it's compatible on mobo website)

More about : asrock extreme3 gen3

a c 125 V Motherboard
January 25, 2012 10:04:50 PM

Time to test your memory with memtest86+
Score
0
January 25, 2012 10:10:22 PM

abekl said:
Time to test your memory with memtest86+

I've tried using the mem test that comes with windows, it says nothing is wrong. do I really need to use software from a different company to test it accurately?
Score
0
Related resources
January 25, 2012 10:45:10 PM

I have an ASRock 970 Extreme 4 (AMD however) i got errors like this all the time with the bios the board came with, once updated to their newest bios errors were gone. There is a chance your ram was not supported at the time of the bios release currently on your board.
Score
0
January 25, 2012 10:58:13 PM

omega21xx said:
I have an ASRock 970 Extreme 4 (AMD however) i got errors like this all the time with the bios the board came with, once updated to their newest bios errors were gone. There is a chance your ram was not supported at the time of the bios release currently on your board.

Well, I just tried pulling the cmos battery as well as flashing the bios to newest version (after the battery pull) and neither has changed anything.
Score
0
January 25, 2012 11:22:53 PM

Try getting the ram to run at it's rated speed in BIOS. Low voltage ram can run weird if running at different speeds than they are rated for.
Edit: I should also point out that ASRock boards tend to have a slightly higher DOA rate than other brands. My first board from them wasn't dead but it did throw out errors like crazy. After an RMA, a week of waiting, and putting in the same components back in the new board, everything went smooth. Try to rule out as much as possible first though, if you have a friend with a compatible board/ram try it out on theirs and vice versa.
Score
0
January 25, 2012 11:58:50 PM

omega21xx said:
Try getting the ram to run at it's rated speed in BIOS. Low voltage ram can run weird if running at different speeds than they are rated for.
Edit: I should also point out that ASRock boards tend to have a slightly higher DOA rate than other brands. My first board from them wasn't dead but it did throw out errors like crazy. After an RMA, a week of waiting, and putting in the same components back in the new board, everything went smooth. Try to rule out as much as possible first though, if you have a friend with a compatible board/ram try it out on theirs and vice versa.

Would be taking it up with ASRocks tech department but Chinese new year has hit me right when I need them! Might RMA it to newegg, I've tried pretty much everything but pulling it apart and reseating everything.
Score
0
January 26, 2012 12:06:42 AM

dylarsen12 said:
Would be taking it up with ASRocks tech department but Chinese new year has hit me right when I need them! Might RMA it to newegg, I've tried pretty much everything but pulling it apart and reseating everything.

Well reseating everything is definitely something to try. Especially reseat the ram, boards tend to be picky about which slots they are put in, try one at a time and then try a combination of the slots 1a/1b, 1a/2a, 2a/2b 1b/2a, 1b/2b. There's alot of minor things that could happen. I know I spent a few hours over the course of 3 days trying a few different things just to be sure.
Score
0
January 26, 2012 12:28:24 AM

omega21xx said:
Well reseating everything is definitely something to try. Especially reseat the ram, boards tend to be picky about which slots they are put in, try one at a time and then try a combination of the slots 1a/1b, 1a/2a, 2a/2b 1b/2a, 1b/2b. There's alot of minor things that could happen. I know I spent a few hours over the course of 3 days trying a few different things just to be sure.

Mobo instructions insist you put them in a1 b1 or a2 b2 to get the dual channel. I will try it with none and then one and report back. after that I guess take everything out and put it back in, see if there is a difference if not rma?
Score
0
January 26, 2012 12:38:51 AM

dylarsen12 said:
Mobo instructions insist you put them in a1 b1 or a2 b2 to get the dual channel. I will try it with none and then one and report back. after that I guess take everything out and put it back in, see if there is a difference if not rma?


That's probably what it will come down to, how long did you run memtest? 1 pass is not enough, it sometimes takes a few hours before problems pop up.
Score
0
January 26, 2012 12:46:53 AM

Just the one time, this is my first build, spose I'll run it over and over?
just tried it without ram post stuck at 53 (no compat ram) and with 1 stick in a2 it continued to stall at 2f
Score
0
January 26, 2012 1:00:20 AM

try the other stick in a2, then try the other slot (a1) with each stick, you could have one bad stick or one bad slot (dimm). If one stick works and not the other, bad ram. If one dimm works and not the other bad board.
Score
0
January 26, 2012 1:06:35 AM

Found out that the ASrock website lists my ram compatible while the gskill website does not list my mobo as compatible. Could one or the other be incorrect? If it were incompatible why would it be working half the time and recognized in bios?
Both sticks work during the initial boot up, the issue is if I shut down and try to reboot it posts at 2f. does that show bad board?
Score
0
January 26, 2012 1:17:56 AM

dylarsen12 said:
Found out that the ASrock website lists my ram compatible while the gskill website does not list my mobo as compatible. Could one or the other be incorrect? If it were incompatible why would it be working half the time and recognized in bios?
Both sticks work during the initial boot up, the issue is if I shut down and try to reboot it posts at 2f. does that show bad board?


Sites like corsair g.skill will not usually keep up to date on what their ram is compatible with after their ram is released. It's usually up to the motherboard co. to list these things or release updates to make them compatible. If ASRock lists it compatible then under their test setup they incountered no problems. I'd say you could talk to ASRock about the problem, but they are notorious for just saying "send the board back, we will test it" i've heard many cases where they sent the board back saying they didn't encounter the problem. If they don't ask that they'll usually just say to return for another. I don't think they have enough people who know how to troubleshoot problems on the phone. When you are in windows, bring up cpu-z and look at the ram specs, see if they are running in dual channel ganged/unganged and speed and so on.
Score
0
January 26, 2012 1:43:46 AM

running cpu-z as I type, is it normal for a cpu to cycle from 1596 mhz to 3591?
as far as ram specs what all should I list? running one stick brings up in the SPD tab: single channel
JEDEC#1 622MHz 7.0-7-7-22 29 1.28v
JEDEC#2 711 MHz 8.0-8-8-25 33 1.28v
JEDEC#3 800MHz 9.0-9-9-28 37 1.28v
xmp-1600 800MHz 9-9-9-25 40 command rate of 2t 1.25 v
And in the Memory tab
798.2MHz
1.6 FSB
9.0-9-9-28 Command rate of 1T
Score
0
January 26, 2012 2:30:29 AM

The CPU cycling between the two is just the CPU spinning down when its not under stress, saving power.
Do you have the problem when just having the one stick of RAM? If so try with the other stick. If it doesn't happen with one stick then ones bad, usually memtest will pick up on bad RAM too
Score
0
January 26, 2012 2:40:43 AM

omega21xx said:
The CPU cycling between the two is just the CPU spinning down when its not under stress, saving power.
Do you have the problem when just having the one stick of RAM? If so try with the other stick. If it doesn't happen with one stick then ones bad, usually memtest will pick up on bad RAM too

It happens with one stick or two, it doesn't make a difference.. Just tried unplugging and plugging all power to the mobo.
(Side question)
I have my fans hooked up to be powered by my front panel rather than through the mobo, would this cause the mobo to think there are no fans in the computer?
Score
0
a b V Motherboard
January 26, 2012 2:52:10 AM

I had a similar problem with my ex3 gen3. It worked fine for 2 weeks and then started having random crashes, and boot problems. You need to run memtext86+ for 5-8 hours to be sure that the Ram is OK, the windows checker is not that great.

For my issue it turned out to be both a bad stick of ram, plus bad power management on the mobo when using all 4 sticks of ram (which was a real pain in the ass to troubleshoot by the way). I thankfully have a friend who owns a computer repair business and lent me 10 4GB sticks of ram to play with for troubleshooting, which helped me figure out what was wrong, and no combination of 4 sticks would work in the board after the problem developed. Thankfully I have had my new board and ram for over a month with no problems (though I did notice that the gold plating is missing from the caps on the replacement board.... but I'm not complaining if it works properly!).

Most likely though you have bad ram, but just know that the mobo could be at fault (ASRock is the budget line of ASUS, so some lack of QC is to be expected).


To the fan question, no. All the mobo cares about is temperature, so long as temps are good then the system will love you.
Score
0
January 26, 2012 3:11:38 AM

^+1 yep, its very common with asrock, I had this happen as well like I mentioned. Sadly I built a computer for a friend with asrock and he got unlucky with not 1 but 2 boards, by then we just went and got a gigabyte board. When an asrock board works, they are amazing, but you press your luck sometimes. :) 
Score
0
January 26, 2012 3:16:28 AM

CaedenV said:
I had a similar problem with my ex3 gen3. It worked fine for 2 weeks and then started having random crashes, and boot problems. You need to run memtext86+ for 5-8 hours to be sure that the Ram is OK, the windows checker is not that great.

For my issue it turned out to be both a bad stick of ram, plus bad power management on the mobo when using all 4 sticks of ram (which was a real pain in the ass to troubleshoot by the way). I thankfully have a friend who owns a computer repair business and lent me 10 4GB sticks of ram to play with for troubleshooting, which helped me figure out what was wrong, and no combination of 4 sticks would work in the board after the problem developed. Thankfully I have had my new board and ram for over a month with no problems (though I did notice that the gold plating is missing from the caps on the replacement board.... but I'm not complaining if it works properly!).

Most likely though you have bad ram, but just know that the mobo could be at fault (ASRock is the budget line of ASUS, so some lack of QC is to be expected).


To the fan question, no. All the mobo cares about is temperature, so long as temps are good then the system will love you.

Ok, thanks. answered a lot of questions I hadn't gotten to yet. Right now i'm sitting at 10% on windows memtest and have been there quite awhile. I'm hoping it is just the ram, much easier to replace.
Score
0
January 26, 2012 3:24:53 AM

Wondering if it IS the board, now when I get it into windows it won't show the network adapter. I'll have to work around install memtest. There a reason it would forget its onboard adapter?
Score
0
January 26, 2012 3:25:51 AM

I should point out if the dimm's on the board are bad then the ram will always seem bad. Best way to check is with someone else's system if you can.
Score
0
January 26, 2012 3:27:45 AM

Board seems to be showing its true colors maybe?
Score
0
January 26, 2012 3:43:53 AM

omega21xx said:
I should point out if the dimm's on the board are bad then the ram will always seem bad. Best way to check is with someone else's system if you can.

Unfortunately, not an option for me. It's either it works or it doesn't. Don't know a whole lot of people who have ddr3 systems haha.
Would Memtest86 pick up on bad dimm's?
Score
0
January 26, 2012 3:57:10 AM

I doubt it would be able to differentiate between a bad dimm or bad ram. If you see errors and its not too much trouble you could always rma both to be sure.
Score
0
January 26, 2012 3:59:02 AM

Would be RMA'ing to same place, so why not? If no errors, just the board? or... out of luck.
Score
0
January 26, 2012 4:02:30 AM

Yep, if you get plenty of passes in memtest then its just the board. You get errors I'd return both due to the driver issue you mentioned
Score
0
January 26, 2012 4:06:32 AM

taking about 36 min a pass, how many passes would plenty be? (you mentioned 5-8 hours)
Score
0
January 26, 2012 4:43:58 AM

Yeah, some suggest 20 passes, but if you can get 10 you should be fine. I usually see RAM fail somewhere between the 3rd and 6th pass but some take longer.
Score
0
January 26, 2012 12:18:09 PM

sure enough, pass 3 test 6 brought failure... could it be that both sticks are bad given I've tried to trouble shoot 1 stick at a time, or more likely the board? guess I'll just RMA both today.
Score
0
January 26, 2012 2:04:56 PM

If you bought both sticks together as a kit they'll want both even if one is good. I'd probably rma the RAM and if you don't think you'll run out of time to rma wait for the new sticks to come so you can test and see if all your problems are gone before rma'ing the board (you could do the board too since it seemed to have a weird network quirk)
Score
0
February 1, 2012 10:02:06 PM

the saga continues.... rma'd both the ram and mobo, got both back today put it all together and have the exact same problem.
Score
0
February 1, 2012 10:40:20 PM

Have you tested the new sticks?
If they pass for 6-12 hours then you at least have one problem solved. It will come down to possibly the psu (for the computer not starting) or the board again (for the error code it shows). I had 2 bad ASRock boards in a row when building for a friend. It's rare but these things happen.
Score
0
February 10, 2012 3:44:43 AM

ran mem test for 10 hours and no problems (10 passes) I have replaced the psu as well and i'm still getting the same results... I've even tried different outlets and different surge protectors..
Score
0
February 10, 2012 4:52:09 AM

dylarsen12 said:
ran mem test for 10 hours and no problems (10 passes) I have replaced the psu as well and i'm still getting the same results... I've even tried different outlets and different surge protectors..


So its still showing the f2 error?
I recently got the same board as you, I haven't had any issues, but I wouldn't rule it out that the RAM isn't compatible, it says so on the site but its making me skeptical. Have you talked to asrock? Now that I have the same board maybe I can help you out in BIOS a bit better. Manually type in your RAM specs printed on the sticker that's on the heatsink of it. If that doesn't work try auto instead of xmp.
Score
0
February 10, 2012 4:59:51 AM

I've read of other people having the same ram with the board so I know it is compatible. though in bios for whatever reason it is 9-9-9-28 rather than the listed speed of 9-9-9-24
Score
0
February 10, 2012 1:52:31 PM

i've tried auto and the xmp settings, as well as changing the speed to the listed speed manually.
Score
0
February 10, 2012 4:26:59 PM

Call asrock, they should have the same parts on hand since they say its compatible, they should be able to help more on this, they have glitchy BIOS so they should be familiar with the problem you are having. Just be sure to mention the error code and that your RAM passed memtest multiple times. They should be able to say if its bad BIOS or another bad board
Score
0
February 10, 2012 5:10:31 PM

I've been running through their suggested steps (same as yours) and nothing is working haha. how could it be that i get two of the same board with the exact same issue? seems super off to me.
Score
0
a c 107 V Motherboard
February 10, 2012 5:26:33 PM

I had problems with G.Skill RAM with my board too. Ill change with Corsair and from then everithyng runs smooth.
Score
0
a c 107 V Motherboard
February 10, 2012 5:35:06 PM

Oh and i remembered , the other problem why i had BSOD and had memory errors it was the CPU load line calibration it was set on the lower level and i set mine to level 3 and the BSOD's have gone. I found this explanation after i googled an entire week. I hope i could help you.
Score
0
February 10, 2012 5:39:50 PM

Strange that switching to corsair fixed your problems, I had the opposite, I switched to g.skill because I kept getting either bad RAM or problems with corsair unfortunately.

And getting two bad boards happens... I build pcs for friends and family and one time had two boards back to back with problems, eventually I just went to a local pc shop and dropped my stuff in one of their boards, once working I paid and left with a working one.
Score
0
February 14, 2012 3:50:17 AM

turned out to be a bad reset switch header.. once It was pulled it starts up every time no problem, my question now is... What exactly does that do while it is plugged in and is it necessary? Basically, from my front panel to the mobo the wire is bad and was screwing up my boot, I don't understand what it does and can't seem to find any info on that.
Score
0

Best solution

February 14, 2012 3:59:22 AM

Huh, strange. That shouldn't cause errors on the board to show though, probably just cause strange resets and hang ups. It's not essential to be plugged in though. Just means you can't use the reset button :) 
Share
February 14, 2012 4:08:38 AM

Can't believe that was it, caused the rma of a lot of good parts! :/  now I feel bad haha! Thanks for all your help. Pretty awesome that you can find helpful people on the internet!
Score
0
February 14, 2012 4:09:01 AM

Best answer selected by dylarsen12.
Score
0
February 14, 2012 4:15:36 AM

dylarsen12 said:
Can't believe that was it, caused the rma of a lot of good parts! :/  now I feel bad haha! Thanks for all your help. Pretty awesome that you can find helpful people on the internet!


Yeah, I returned a few things that probably didn't need an rma before, but it can't be helped. Trial and error :) 
Glad we could help you out even if you figured it out yourself :lol: 
Score
0
a c 328 V Motherboard
February 14, 2012 6:41:58 AM

This topic has been closed by Nikorr
Score
0
!