Send News. Want a reply? Read this. More in the FAQ.   News Forum - All Forums - Mobile - PDA - RSS Headlines  RSS Headlines   Twitter  Twitter
Customize
User Settings
Styles:
LAN Parties
Upcoming one-time events:

Regularly scheduled events

Report this Comment
Use this form to report the selected comment to the moderators. Reporting should generally be used only if the comment breaks forum rules.

50. Re: Battlefield 3 Improvements Nov 11, 2011, 05:20 Mordecai Walfish
 
CJ_Parker wrote on Nov 4, 2011, 05:32:
I would like to thank BF3 for helping me remember what a BSOD looks like. This is the first BSOD I have seen on my system in ages so it's quite an accomplishment by DICE to make otherwise 100% rock stable systems crash when playing their fucked up game. Gratz on that one, guys. Keep rockin'...


DICE has a history with these kinds of issues. I experienced something very similar with Bad Company 2, recently.

I would experience CTD's with BC2 on a system I built and tested in every way possible myself to ensure 100% stability in *EVERYTHING* I could run on it. Never a BSOD or system crash since I built and tuned the PC (Dec'10).
When BC2 would crash, it didnt just CTD... it would take the entire fucking ship down with it. Network card would start failing, programs would refuse to open and exhibit other weird behaviour. All sorts of weird shit would start happening. Turned out to be that the ram was overclocked (and 100% stable in literally everything else 24+ hours memtest, prime64 24+ hours, Windows7 memory diagnostic extended tests 10x over..). Everything was completely happy with the settings, but BC2 would not cooperate with the change in the Command Rate from 2t to 1t. This ended up being what caused it, and I only found out because another person had figured this out when he was having similar issues and looking for help in the G-Skill forums.

Hell BC2 still crashes and burns with infinite sound loops and BSOD's for people who are playing on certain motherboards with *very common* onboard audio solutions (realtek) released over the last couple years. (And this issue has been first reported when BC2 game was BETA, and still to this day you will find lengthy threads about this frequent issue)

Not really surprising BF3 is having similar issues reported across the board, but the worst thing is that given DICE's history its unlikely many of these bugs will get the time and attention they deserve.

BC2 is, what, 2 years old now? Still no fixes for many bugs that have affected large portions of the gaming community since beta. Shame.
 
 
Subject
  
Optional
Message
 
Login Email   Password Remember Me
If you don't already have a Blue's News user account, you can sign up here.
Forgotten your password? Click here.
 




footer

.. .. ..

Blue's News logo