Battlefield 3 Blue Screen of Death?

[yangwangbrock]

Just updated to 12.3 not sure if that is going to fix this problem...

 

[mudkip]

So it happened again, but not in BF3, instead it happened when I was playing ME3. Here is the error message:

Stop:0x00000124 (0x 00000000000000, 0xFFFFFA800DE93028, 0x00000000BE200000, 0x 000000000005110A)

now WTF does that mean?

...... sorry but I hate it when standard questions like these come up.
There is a nice search engine called Google. Also if you go to the overclock section theres a sticky thread with some bsod codes explained.

 

[SK-1]

This program will tell you if and what driver is responsible.
http://download.cnet.com/WhoCrashed/3000-2094_4-75205821.html

 

[Wrigleyvillain]

0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is

Have you actually done/tried anything suggested in this thread yet? I think you probably haven't as all you apparently have to say it "is happened again". My money is still on memory voltage(either vdimm or vtt or both) needing to be raised a bit and the latest code substantiates that. Also still couldn't hurt to get rid of Catalyst 12.1 if you're still on them as some has issues as has been said. But I don't know if 12.2 is any better offhand. May have to go older.

Told you it wasn't inherent to BF3.

 

[erocker]

I'll say it again.. It's most likely a Realtek onboard sound issue. Refer to my other post. You're just beating around the preverbial bush here...

 

[yangwangbrock]

I'll say it again.. It's most likely a Realtek onboard sound issue. Refer to my other post. You're just beating around the preverbial bush here...

Thanks. Getting a Asus Xonar Essence STX ordered and it should be in transit now. When it gets here I will get rid of the on board Realtek shit altogether. Will update how it goes.

 

[Wrigleyvillain]

Well that's good cause kind of hard to rule that out without a sound card to install.

 

[OneMoar]

on-board sound DOES NOT MAKE Battlefield Bad company/Battlefield 3 CRASH its a rumor with NO hard Data backing it I repeat there is NO HARD DATA to backup that claim other then a people that HAPPEN to have realtek audio where getting crashes
I used to play bad compony and I also got the 0.124 stop code do you know what the problem was NOT ENOUGH core voltage

 

[Wrigleyvillain]

Well let's put it this way...erocker generally knows wtf he is talking about. Though if this hadn't been him claiming that I would have probably been said that's really stabbing in the dark.

I still don't see why OP seems so adverse to raising his voltage(s) a little, at the very least in the interest of ruling that out. If it still BSODs then you are only getting closer to the actual solution. A lot better use of his time that just posting here about it again.

 

[erocker]

on-board sound DOES NOT MAKE Battlefield Bad company/Battlefield 3 CRASH its a rumor with NO hard Data backing it I repeat there is NO HARD DATA to backup that claim other then a people that HAPPEN to have realtek audio where getting crashes
I used to play bad compony and I also got the 0.124 stop code do you know what the problem was NOT ENOUGH core voltage

No, you're wrong and I've done testing to prove it. With Realtek sound enabled I would get BSOD's in BF3 consistently. Using the AMD sound through HDMI, no BSOD. Using a X-Fi Titanium, no BSOD. Using an Auzentech X-Raider, no BSOD. In my case it was definitely the Realtek hardware. This has been an issue with BF2 and BFBC2 as well. It is documented in patch notes for BF2. Also, that code could mean a variety of things:http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html, but for this particular situation I'm pretty sure I'm right. I would't give someone some out of the air response. I have nothing to gain or lose by doing so. So RELAX Mr. Caps.

 

[OneMoar]

No, you're wrong and I've done testing to prove it. With Realtek sound enabled I would get BSOD's in BF3 consistently. Using the AMD sound through HDMI, no BSOD. Using a X-Fi Titanium, no BSOD. Using an Auzentech X-Raider, no BSOD. In my case it was definitely the Realtek hardware. This has been an issue with BF2 and BFBC2 as well. It is documented in patch notes for BF2. Also, that code could mean a variety of things:http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html, but for this particular situation I'm pretty sure I'm right. I would't give someone some out of the air response. I have nothing to gain or lose by doing so. So RELAX Mr. Caps.

none of the dumps I have ever seen have had ANYTHING todo with realtek and I have seen 10 or 12 relating to this 'issue' on a few different machines with realtek chips
my conclusion is that disabling stuff such as on-board audio or on-board networking takes load off the cpu/northbridge resulting in improved stability ... Bc2 was/is a strange beast your system could be prime stable and you would still need retarded levels of voltage to make it behave ... hell I have seen stock systems go 0x124 running Bc2 adding voltage ALWAYS fixes the problem
disabling X component and getting a result != mean component-X is faulty ...

 

[erocker]

none of the dumps I have ever seen have had ANYTHING todo with realtek and I have seen 10 or 12 relating to this 'issue' on a few different machines with realtek chips
my conclusion is that disabling stuff such as on-board audio or on-board networking takes load off the cpu/northbridge resulting in improved stability ... Bc2 was/is a strange beast your system could be prime stable and you would still need retarded levels of voltage to make it behave ... hell I have seen stock systems go 0x124 running Bc2 adding voltage ALWAYS fixes the problem
disabling X component and getting a result != mean component-X is faulty ...

Just with BF3 and with two different motherboards? I'll stick with what I said.

 

[yangwangbrock]

Well let's put it this way...erocker generally knows wtf he is talking about. Though if this hadn't been him claiming that I would have probably been said that's really stabbing in the dark.

I still don't see why OP seems so adverse to raising his voltage(s) a little, at the very least in the interest of ruling that out. If it still BSODs then you are only getting closer to the actual solution. A lot better use of his time that just posting here about it again.

I'm embarrassed to admit that I do not know to raise voltage to either ram or CPU...I know I am quite a noob and let the lynch begin...How much voltage should I raise it to and how should I do it?

 

[yangwangbrock]

No, you're wrong and I've done testing to prove it. With Realtek sound enabled I would get BSOD's in BF3 consistently. Using the AMD sound through HDMI, no BSOD. Using a X-Fi Titanium, no BSOD. Using an Auzentech X-Raider, no BSOD. In my case it was definitely the Realtek hardware. This has been an issue with BF2 and BFBC2 as well. It is documented in patch notes for BF2. Also, that code could mean a variety of things:http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html, but for this particular situation I'm pretty sure I'm right. I would't give someone some out of the air response. I have nothing to gain or lose by doing so. So RELAX Mr. Caps.

Thanks Erocker. Soon as the new sound card gets here I will scrap the on board real tech sound card.

 

[Wrigleyvillain]

I'm embarrassed to admit that I do not know to raise voltage to either ram or CPU...I know I am quite a noob and let the lynch begin...How much voltage should I raise it to and how should I do it?

Ah, I see. You should have PM'ed me or someone then. That's what I do when I don't wanna look like noob in public. Nobody's gonna hold it against you here or be a dick about it, btw. It's not that kind of forum.

So you are using some sort of auto-oc feature via Asus software or something? I just assumed otherwise I guess. I hope it's still possible to use that and manually tweak the voltages but if not you may wanna just go BIOS. But that's getting ahead of us.

Can someone pipe in here who knows the board? Even if this is not the cause of his issue he should know how to manually tune his overclock and can't hurt to try before his soundcard shows up.

 

[erocker]

Run it stock until the problem is resolved. Then get into overclocking. There are various threads relating to the sandy bridge platform.

 

[yangwangbrock]

Ah, I see. You should have PM'ed me or someone then. That's what I do when I don't wanna look like noob in public. Nobody's gonna hold it against you here or be a dick about it, btw. It's not that kind of forum.

So you are using some sort of auto-oc feature via Asus software or something? I just assumed otherwise I guess. I hope it's still possible to use that and manually tweak the voltages but if not you may wanna just go BIOS. But that's getting ahead of us.

Can someone pipe in here who knows the board? Even if this is not the cause of his issue he should know how to manually tune his overclock and can't hurt to try before his soundcard shows up.

Thanks Wrigleyvillain. Yes I just used this OC tool comes with the MB (Asus Maximus Extreme Z). It has 2 options of overclocking your CPU to either 4.0 ghz or 4.6 ghz. I just clicked 4.6 ghz and call it a day. Since I have a pretty good CPU cooler the temperature and everything is in check. But I didn't try to tweak the voltage whatsoever.

I will do some research on how to tweak the voltage with my MB. As you said even if the voltage is not the problem it is still nice to know how to do it.

Thanks gain now I feel less ashamed

 

[cadaveca]

If you were in Edmonton, I could help ya out in person. Too bad.


Your BSOD, to me, is the OC. x124 on SB for me has always been low CPU volts....get it a bit closer, and it turns into a x101 error, and a bit more is needed for real stability.


You could try loading up LinX or IntelBurnTest to do a quick stability check; either of those should be very quick to cause BSOD if it really is the OC.

 

[yangwangbrock]

If you were in Edmonton, I could help ya out in person. Too bad.


Your BSOD, to me, is the OC. x124 on SB for me has always been low CPU volts....get it a bit closer, and it turns into a x101 error, and a bit more is needed for real stability.


You could try loading up LinX or IntelBurnTest to do a quick stability check; either of those should be very quick to cause BSOD if it really is the OC.

You from Edmonton Cadaveca? You don't say! Hello from Cow town! Has snow melted up there? It has been really warm these days down here!

 

[cadaveca]

You from Edmonton Cadaveca? You don't say! Hello from Cow town! Has snow melted up there? It has been really warm these days down here!

Yes, currently located in Edmonton. And yeah, has been warm, 12c or so on Friday, if I remember corerctly, and yes, we stil lahve some snow, but mostly melted at this point. We got a fair bit of snow last weekend, so it's mostly that that has melted.

 

[TheMailMan78]

yangwangbrock are you gonna do ANY of the suggestions people have given you or are you just gonna post half errors and hope someone guesses? I'm done trying to help.

 

[Wrigleyvillain]

So Dave is helping you now? If anyone knows how to tweak a newer mobo around here it's him.

So, yang, as you can see this auto-oc software is cool and great for those without a lot of knowledge and experience but really not a good idea as the voltages need to be more properly tuned for true stability under extended heavy loads. Another reason that method is best avoided if possible is because using such automatic overclocking (as well as leaving AUTO settings on in BIOS in some cases) can actually result in much higher voltages than is actually needed to attempt to ensure stability. Obviously, such is likely not the case here but important to note. Not so much extra that anything would get damaged-the engineers know what they are doing of course-but just more heat and power than you need to be producing and using for a given clock speed.

 

[yangwangbrock]

So I finally get to install the soundcard and that totally fixed the problem - no more BSOD, not even one. So I could confirm that Realtek is the problem, at least in my case.

Thanks for all of your advise guys.

 

[TheMailMan78]

So I finally get to install the soundcard and that totally fixed the problem - no more BSOD, not even one. So I could confirm that Realtek is the problem, at least in my case.

Thanks for all of your advise guys.

Thank Erocker. He called it. However we could have told you what it was if you had posted the damn BSOD list as requested to begin with and saved you tons of time.

 

[yangwangbrock]

Thank Erocker. He called it. However we could have told you what it was if you had posted the damn BSOD list as requested to begin with and saved you tons of time.

I did actually posted the error list, only to have another guy laughed at my face for being a noob and not doing my research Not you mailman you've been cool.