I have the new vbios, 10.8 dell version, and my performance in Bad Company 2 has been great. Only thing is that it crashes about once every 10-30 minutes. I have no idea what is happening, I tried all the solutions posted everywhere, and I can't find an answer. Anybody know why this happens/how to fix it?
-
C:\Users\YOUR_USER_NAME\Documents\BFBC2
- GameSettings.bin
- GameSettings.cfg
- settings.cfg
Known issue apparently - found via googling and checking the BC2 Steam Forum. Worked for me. Also, if you purchased via Steam, verify the integrity of the game files. -
There might be some more information about the crashes in the Windows event logs. Bring up your Event Viewer (under Control Panel > Administrative Tools), and look in the Application logs (under Windows Logs). Look for any entries with a level of Error and a source of Application Error.
Any entries in here for BC2 will give better information about what type of crash you're seeing, and what's causing it. Post back some of the info here and we may be able to help. -
Near (if not ON) the time of the crash, there is an error that reads: Log Name: Application
Source: SideBySide
Date: 9/29/2010 6:16:44 PM
Event ID: 63
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: M17X
Description:
Activation context generation failed for "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="SideBySide" />
<EventID Qualifiers="49409">63</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-09-29T22:16:44.000000000Z" />
<EventRecordID>17892</EventRecordID>
<Channel>Application</Channel>
<Computer>M17X</Computer>
<Security />
</System>
<EventData>
<Data>assemblyIdentity</Data>
<Data>version</Data>
<Data>MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll</Data>
<Data>c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll</Data>
<Data>3</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Although I crashed twice today, there is only one entry, so I don't know. About to try to delete those things, BatBoy, I'll see how it works.
EDIT: In my documents/BFBC2 folder, I found an xml file titled crashreport, and it reads: <?xml version="1.0" encoding="UTF-8" ?>
- <report>
<version>2</version>
<sessionid>38fb22844ca3abe0</sessionid>
<type>crash</type>
<sku>ea.dice.RomePC.Cl</sku>
<createtime>2010-09-29 21:31:12</createtime>
<buildsignature>553292</buildsignature>
<systemconfig />
<categoryid>0x6BECC497</categoryid>
<stack>0x6BECC497 0x6BED7966 0x6BED7929 0x6BEECEB7 0x6BEE7C10 0x6BEECF53 0x74AD3677 0x76F29D42 0x74AF9775 0x74AF9775 0x76F603DD 0x44DB09 0x76F29D15 0x6BEECEDD 0x6BEECEDD</stack>
<threads />
<screenshot />
<memdump />
<contextdata>registers: Edi 13ba7940, Esi 6becbe60, Ebx 76f12210, Edx 6becc480, Ecx 16a03574, Eax 8b501051 Ebp 76f12250, Eip 6becc497, Esp 1700ff30</contextdata>
</report>
That mean anything? -
the Adobe AIR has nothing to do with BC2. The BC2 crash report is greek to me. I imagine only EA Support can pick it apart.
Post back once you try the file delete I suggested. Keep in mind, since you are dumping the settings file you will have to reset your preferences (keyboard commands, etc.) in addition to class loadout. No big deal though - at least that is how I look at it if the crash is resolved.
I've had it come back from time to time but dumping the files seems to resolve it.
If I had to guess, it has something to do with a bad server register. IDK. -
Mine used to crash and I used to get the lag really bad, so everytime I started Throttlestop that seemed to take it away. It's worth a try
-
my M17X crashed all the time too. It froze for no reason in game.
I had 5% overclock in bios and i upped the Vcore to 75Mv and no issues so far. Bad Company 2 uses alot of CPU and i guess it wasnt stable at 5% without some extra juice. I now use throttle-stop and performance is great -
i think uninstalling all of the C++ redistributables and re-installing the one with BFBC2 might do the trick
-
-
-
-
If that didn't help, next step is a complete reinstall of BC2. Its not the hardware.
-
Its BC2's programming and coding causing errors. Its not your machine man. Until EA/Dice release a patch that fixes it, you'll continue to have errors. Lets just hope that MOH: Tier 1 won't have the same issues...
-
But, when I was on the original dell drivers, it never crashed. The minute I switched to the newer ones, it crashed away. But, upon switching to original, no crashes. However, performance is almost doubled with new ones, so I'm not about to give that up.
-
Have you tried Throttlestop? Mine used to lag and crash but with Throttlestop it helped big time
-
Just turning it on with clock mod set to 100% or any other things?
-
-
Dude I think its the drivers - I have the same issues plus a lot of flickering. Im waiting for the 10.9 mobility drivers and if these dont solve the problems I'm going ask ask Dell for GTX 285M Nvidia replacements. Even though these cards are not as good (DirectX 11 etc) they must preform better than these crap ATI cards. This is what I usually see when playing BFBC2;
Considering the price - not good enough in my opinion. -
Ah bugger ey chiefs.
AMD decided to leave us in the lurch this past month unfortunately chiefs. There will be no 10.9 driver. They said there was a bug or something in it so they won't be releasing one this month (well last month) now but you know what I mean. So hopefully 10.10 will make it and actually improve performance and fix game bugs like your one. Also being directX 11 capable is nothing you have to worry about as it is the 1st gen of the DX11 supporting cards and really won't be able to run anything DX11 properly or with playable frames.
I sure hope AMD get their act together soon and smash us up a super driver this month. My Dual 260s are beating the dual 5870s in a few games I'm playing atm and its darn right embarrasing LOL. Just needs proper game and driver performance improvement though and all should be good.
Cheers. -
I do believe that the Throttlestop thing along with a couple other fixes put together have either spread out or even stopped my crashes! Thank you very much for the suggestion!
-
Glad it worked for you V3_Shae! I play as tacokicker btw -
I play as... V3_Shae..... imaginative, huh?
-
Mechanized Menace Lost in the MYST
Dirtybiscuit lets get a game goin.
-
I usually play on the KoF server, as I'm a clan member, and get a VIP slot
On a side note, that is actually about the topic, so it's probably the main note, the crashes ARE less often, but I have isolated the causes. It will only crash if I open the scoreboard right after I die (1/10-11 times) Or whenever I switch kits rapidly (1/4 times). As long as I can avoid opening the scoreboard, I can just switch kits slowly, and it won't crash. Too bad I have developed some kind of unearthly reflex to death which is rapidly pressing the tab button, bringing up the scoreboard -.- I'll just have to work on that I guess... -
BUMP Did this help anyone lessen their crashes?
-
The deleting files in the BFBC2 folder did not for me. I just did a validate files and it found 3 files that needed to be recreated. I will let you know if that fixed it.
-
Deleting the settings files didn't work for me either. It kept stable for about an hour and then started getting flashing black screens and then crash. The new Dell driver has definitely caused some sort of conflict. My system was running BFBC2 awesome before. The only issue was the load time in between games. Now it crashes at least once an hour. Haven't noticed a significant performance increase. Frame rates are still very inconsistent.
I downloaded and installed Throttlestop, but I have never used the software before. I'm not really looking to OC or anything, just want to run the game stable for awhile. Can someone who uses Throttlestop tell me what settings I need to have it on to get the game running stable? Do you open it each time prior to playing the game? Let me know. Thanks -
I've been experiencing crashes after updating my drivers .
It worked fine before . Now it just crashes everytime the map changes . Can't seem to get BC to run past 1 map transition . -
It hasn't crashed on me since validating the files (which recreated the ones in my documents folder and I edited the one to reflect the dx=10. I haven't played over an hour yet though.
-
Played another hour or so this afternoon with no issues...
-
Shae, I haven't tried what you suggested but everything seems to be running good.
Guys, try Throttlestop, I think it really helped with th lag and crashes -
-
Mechanized Menace Lost in the MYST
-
Frozenarcticguy,
How do you have Throttlestop setup? Do you run it all the time or just before you start the game? I have no idea how to setup/use this program.
Can you give me a quick how to? -
any way to validate files w/out Steam purchase?
-
Does anyone get a performance increase in game with the new drivers and vbios installed? I'm at 60 FPS consistently with 30s during smoke/heavy fire. With the last Dell drivers I was in the 90s often. And my game still crashes occasionally. Why do I continue to think new drivers will make in game play better? I should have stuck with the ones I had.
Can anyone help with the Throttlestop setup? -
Mechanized Menace Lost in the MYST
-
Mechanized Menace Lost in the MYST
-
As far as Throttlestop goes, are you saying that if I don't have an XM processor that it won't help? I have an 820QM. -
Mechanized Menace Lost in the MYST
I gained anywhere from 20-30 FPS by OC, and changing my settings, But to make sure it is set to 11 just goto your documents--->BFBC2 folder----> open settings.ini and change it to 11 from auto and make those other changes I told you and you will not regret it.
http://forum.notebookreview.com/alienware-m17x/495203-how-oc-m17x-r2s-920xm-940xm-using-setfsb.html -
It's a AMD problem with BC2. Nothing can be done. It'll crash eventually mind you.
-
Mechanized Menace Lost in the MYST
-
Thanks for the info Mkelliny. I was PM'ing the Throttlestop author to see what he says. But with my 820, there isn't much I can do I guess.
-
I have played 3 hours straight with no crash now. I think I can consider this "fixed" at least in my case.
-
Mechanized Menace Lost in the MYST
-
-
Mechanized Menace Lost in the MYST
-
-
For some strange reason, every time I overclock my 720 with setFSB, even just a little bit, with a voltage increase, it makes BC2..... not work.... no more.
-
I think I'm going to see if I can swap cards for the 285's. I don't care much about benchmarks and I know that some games run better with them plus the driver situation should be better
Bad Company 2 crashes
Discussion in 'Alienware 17 and M17x' started by V3_Shae, Sep 29, 2010.