BSOD when playing BF3

blair

New member
hi,

dunno if these BSOD relate to the cpu but i get:

0x0000001e

0x0000000e

0x00000050

When playing battlefield but i can play MW2 and any other game for hours and never had a BSOD but BF3 in 10 mins i get a BSOD why?

ran furmark and prime 95 at the same time for 2 hours not one problem and gpu is 40C and cpu got to 52c

HD5870

Phenom x6

Thanks
 
ive got a mate that is having BSOD of BF3, but other games run fine as well and there seems to be others that are having the same prob. Sorry i cant be of any help but it seems you are not alone in this. he is running a i7 950 at stock with a GTX 570 (i have the same card) but "touch wood" im ok
 
starting to get really annoyed with this the bsod even if i do manage to get on the game with this loading loading bug aswell,

never had BSOD before the patch,

8bit if it was my memory surly other games or stress testing would also cause BSOD.

Ok now i get BSOD in MW2 as well.

this bsod gave a quick bluescreen then just a collage of colours and never made a .dmp file. why is that?
 
I noticed you posted a thread about the 12.1 preview drivers, are you using those? If you are that might be why, they are Beta drivers and not fully stable. Try rolling back to 11.11b
 
8Bit was right i ran memtest86 on both stick of ram one passed the other had 3,000,000 errors and counting when i ended it one stick is as far as this program tells me is faulty will try BF3 now with the non faulty one.

as far as the drivers go they are beta but AMD recommends you use them.

Thanks for your help
 
this bsod gave a quick bluescreen then just a collage of colours and never made a .dmp file. why is that?

Check you have autorestart deselected to hold the BSOD and write system log event selected.

s_restart.jpg
 
yea i did scratch my last post the ram is definatly faulty i managed to play BF3 for 2 hours then i got a BSOD with error 0x00000124.

all these BSOD only started this week never happened before.

Please help getting very fed up with this pc had to return 4 parts now got to return a stick of ram and it still BSOD.
 
will do just a little strange cause this clock and vcore has been the same for 7 months and it was tested for 24 hours on prime could it have been a odd one BSOD?
 
Could be but 0x00000124 usually means you need to up the volts a little. I was getting them myself a while back when F@H but I upped my CPU voltage a little and I haven't had one since, touch wood.
 
ok played another hour of BF3 then got 0x00000050 this time seriously pissed now why all the BSOD suddenly everything worked last week.
 
I don't know what causes 0x00000050 you will have to Google to see if you can find out. Why Microsoft doesn't have a list of what all the blue screen errors mean easily available on a website i'll never know, Sometimes finding out what they actually mean is a mission.
 
got another BSOD 0x0000000a

Here is a list of all BSOD

http://imageshack.us/photo/my-images/822/bsodu.jpg/

getting very fed up now.

just uninstalled amd graphics drivers ran driver sweep and reinstalled 11.12 got a message saying installation success but there was warning view log for details, viewed the log but that says no errors strange.

Edit after i reinstalled 11.2 driver i appear to not get BSOD so far (touch wood) played 4 games no BSOD however on big maps like caspian border every 30 sec i get a freeze for about 2 secs then it carries on. any ideas?

ANOTHER bloody BSOD 0x00000124 again and i up'd by vcore 0.02v aswell from the last one what else could be faulty?
 
Getting a BSOD ever hour or so not as much as i used to get but any ideas fast running out of things to try here.
 
Get all your shizzle down to stock performance. Don't set timings for anything in the bios, let the load-optimized basic settings pick it up from spd etc. Install the release drivers, not beta. Test all your games that have been out longer than BF3 and be sure you're not bsod'ing.

Once you're happy there, try BF3, if it plays ok - no problem. If you're playing ok, but there's a "niggle" in something, but still no bsod, try the beta drivers.

From this point, once you're certain everyone is happy - then try some oc goodness.

BSODs are infrequently red-herrings with their numbers. Especially memory related ones, they'll lead you all over the place, with all kinds of component errors, telling you your cd-rom is knackered when it isn't (it's the cd-rom writing to memory FFS!, been there).
 
Back
Top