Nvidia issues running battlefield bad company 2

[pnico]

hi,

do any of you guys that run bfbc2 have any issues with it like screen flickering, game crashing..etc?

 

[gopherkiler9]

I'd like to resurrect this thread because I am having a similar issue yet the internet hasn't been able to solve my problem.

My system used to be
AMD anthlon ii x4 something
AMD radeon 5750hd (i think)
4gb ram

And I was able to run bad company 2 without any issues

Much later down the road (now) I've upgraded to a
AMD phenom ii x4 965 black edition
NVIDIA geforce gtx 750 ti
8gb ram
But now I'm getting the sudden game freeze + Sound loop (EEEEEEEEEEEEEEEEE) until I ctrl alt delete/ task manager/ end process on the game. However, after this happens, if I were to go online and read forums or anything, my graphics are glitchy and it omits letters or sometimes never loads the page texts. This forces me to restart my computer and everything is peachy. Before I restart, if I were to open BFBC2 again, it won't get past the opening video without white screen crashing with a record scratch snap sound.

People say to
- disable onboard audio... did that and it didn't solve it
- verify game cache.... Mine is from origin, not steam, so I'm unsure of this applying
- end process punkbuster B in game... did that, it might work for a bit? but it loads up again and I still crash, so I'm not sure if it has any affect
- load game from C drive, NOT shortcut... didn't help
- make sure punkbuster is fully updated.... did that and it MIGHT have helped. However, midgame I'll get the flashing graphics that makes it seem like its about to crash, but it didn't. However, I'll get graphics dropping where all I see is my crosshairs, map, ammo, etc but NO gun, field, enemy... nothing. Just a black screen with the general player overlay (only no player). The graphics will drop long enough for me to die (about 5 seconds) before they come back. I've lowered graphics from high to medium, and that doesn't solve it, so I'm assuming its not an overheating issue. Especially since my system isn't dusty, has solid air circulation, and everything in there is new except mobo and powersupply.

I've done my research and I just can't seem to find any forum that has any sort of legitimate answer. It seems that the audio disabling solves it for most people, but not me. I ONLY have this problem with BC2. Otherwise I can run anything else I've ever tried.

I'm sorry that this is a 5 year old thread, but the problem still exists and I figured I'd put this problem here instead of creating a new thread with the same issues.

Does anyone have any speculations?

you can get better respond if you make your own thread.

Well if you start your own thread with similar threads in the pool, you usually get yelled at to "read old threads" or "you should post on existing threads of the issue" but if you resurrect an entirely applicable thread, you get told to make your own. And (lord of choice) help you if you post an ambiguous topic in the arguably wrong section. It's just my forum experience that you simply cannot win and someone will ALWAYS want to redirect you. So I made my decision and I stand by it


Anyway, an update!

I've been managing to play for quite a while without any sort of graphic spike or sound glitch/loop. Though it could be coincidence or not, as of now I would feel confident booting up without fear of graphical spike. My solution was to manually update punkbuster from their site. By doing so, you get their little program that allows you to update PB based on what game you have. When I first did this, it decreased frequency of the spikes. Then a couple days later I had to redo the update (not sure why the first time didn't work properly) and since then, I have had no graphical or audio problems. Though I NEVER had this problem back with my radeon 5750 and it only began after upgrading to a 750ti, but some time as well as a HDD->SSD transition had passed since then, so I could believe that PB was just severely out of date. And since the only surviving servers seem to require PB, there is no way to avoid updating it I guess.