Widescreen Gaming Forum

I've been struggling with this for 8 or 9 months now. Whenever I play this game using some sort of 3 screen display, I eventually get Crash to Desktops. If I play the game on just a single monitor, it never crashes.

I used to play the game using 2 5870s in Crossfire. After trying every possible suggestion and everything I can could think of to keep this game running, I decided to try nVidia Surround to see if that was any better.

So I switched to GTX480s in SLI. The same issue was present. Again, I kept trying things, but nothing has worked.

I'm now using a pair of GTX580s in SLI and still the issue is there.

The only constant in all of this is that using a single screen lets me play the game and using 3 screens eventually leads to crash to desktop.

I wish I could remember all the things I've tried to fix the issue. But over the span of time and the vast number of things I've done, I can't remember them all.

I run the game as 6050x1080 (bezel corrected). I use a FOV setting of 47 to equal 135 degree FOV.

Has anyone else had a similar issue with this game? Did you find out how to keep the game running?

Try uninstalling the Microsoft virtual c++ then reinstalling it from the Bad Company disk, its in the Redist folder.

this might help
If you are overclocking your CPU or system memory then revert back to the default frequencies for those devices through these tests. IT IS VERY IMPORTANT NOT TO OVERCLOCK ANY COMPONENTS DURING THIS TEST. If you are using 1066MHz or 1333 MHz 1.5V memory than try increasing the memory voltage to 1.6V and leaving the memory at stock speeds. AMD CPUs and Intel Core i3, i5, i7, and i9 CPUs are all rated for a maximum of 1333MHz memory. If you are using memory rated for higher than this then return the memory frequency to 1333MHz at 1.6V. You could be overtaxing the memory controller in the CPU, not actually running at a frequency where the memory is unstable. Some DDR2 memory will require 2.1V or higher to run stable but may auto-configure to 1.8-1.9V by default. Make sure that your memory is configured properly. This is a common cause of instability that can cause this problem. Make sure that you have updated your motherboard BIOS to the latest version from your motherboard manufacturer. BIOS updates can resolve small issues like slight memory instability that may cause this type of an issue. Check your motherboard manufacturer’s website for the latest BIOS update and instructions on updating your motherboard. Make sure that you are up to date on your motherboard chipset drivers. AMD chipset drivers are available from http://sites.amd.com/us/game/downloads/Pages/downloads.aspx . Intel chipset drivers are available from http://downloadmirror.intel.com/18494/a08/infinst911autol.exe. NVIDIA chipset drivers are available from http://www.nvidia.com/Download/Find.aspx. Download the latest driver from http://game.amd.com/us-en/drivers_catalyst.aspx. Remove your previous display driver from Programs and Features. Remove any utilities capable of controlling clock frequencies like Rivatuner or Afterburner. Completely remove them from the system, not just disable. You want to run the card at our rated frequencies through these tests. Test again with the new driver if you are still seeing the same issue. Open your Windows Control Panel. Go to Programs and Features. Uninstall NVIDIA PhysX if you have it installed. Retest again. If you must have PhysX on your system for a game that you are playing than make sure that it is the latest from http://www.nvidia.com/object/physx_system_software.html but first try without PhysX installed. Download memtest86 from http://memtest.org/#downiso. Download the Prebuilt ISO (.zip) Burn the image to a CD. Windows does not know how to burn an ISO file. You will need a third party program like Nero Burning ROM or PowerISO. Restart the system with the disc in. Run memtest through 2 or more passes, overnight if you can. Any errors will show up in red with the faulting memory address.

I've had the same issues from day 1 with this game as well.
I just gave up and play it on one screen now.

I have stability tested the living hell out of this system and it passes everything I've thrown at it. (Intel Burn test, Y-Cruncher, Prime95, Looped Heaven Benchmarks you name it)

Sometimes the crashes would happen in 10 minutes, sometimes 2 hours, the only thing that seems consistent is that the crashes happen when there's some UI being drawn like the scoreboard or class/squad selection screens.

Same here, I have a new rig (apart from PSU and I tested with another) and it still does it. Normally it is not often enough to annoy me, but when it starts it happens 2 to 5 times quickly in a row. I restart seems to sort it... til the next time.

However a mate with a similar rig has no problems so who knows.

_________________
Dipping bags at Mach1.9

this might help
If you are overclocking your CPU or system memory then revert back to the default frequencies for those devices through these tests. IT IS VERY IMPORTANT NOT TO OVERCLOCK ANY COMPONENTS DURING THIS TEST. If you are using 1066MHz or 1333 MHz 1.5V memory than try increasing the memory voltage to 1.6V and leaving the memory at stock speeds. AMD CPUs and Intel Core i3, i5, i7, and i9 CPUs are all rated for a maximum of 1333MHz memory. If you are using memory rated for higher than this then return the memory frequency to 1333MHz at 1.6V. You could be overtaxing the memory controller in the CPU, not actually running at a frequency where the memory is unstable. Some DDR2 memory will require 2.1V or higher to run stable but may auto-configure to 1.8-1.9V by default. Make sure that your memory is configured properly. This is a common cause of instability that can cause this problem. Make sure that you have updated your motherboard BIOS to the latest version from your motherboard manufacturer. BIOS updates can resolve small issues like slight memory instability that may cause this type of an issue. Check your motherboard manufacturer’s website for the latest BIOS update and instructions on updating your motherboard. Make sure that you are up to date on your motherboard chipset drivers. AMD chipset drivers are available from http://sites.amd.com/us/game/downloads/Pages/downloads.aspx . Intel chipset drivers are available from http://downloadmirror.intel.com/18494/a08/infinst911autol.exe. NVIDIA chipset drivers are available from http://www.nvidia.com/Download/Find.aspx. Download the latest driver from http://game.amd.com/us-en/drivers_catalyst.aspx. Remove your previous display driver from Programs and Features. Remove any utilities capable of controlling clock frequencies like Rivatuner or Afterburner. Completely remove them from the system, not just disable. You want to run the card at our rated frequencies through these tests. Test again with the new driver if you are still seeing the same issue. Open your Windows Control Panel. Go to Programs and Features. Uninstall NVIDIA PhysX if you have it installed. Retest again. If you must have PhysX on your system for a game that you are playing than make sure that it is the latest from http://www.nvidia.com/object/physx_system_software.html but first try without PhysX installed. Download memtest86 from http://memtest.org/#downiso. Download the Prebuilt ISO (.zip) Burn the image to a CD. Windows does not know how to burn an ISO file. You will need a third party program like Nero Burning ROM or PowerISO. Restart the system with the disc in. Run memtest through 2 or more passes, overnight if you can. Any errors will show up in red with the faulting memory address.

Thanks very much for all the suggestions. But believe it or not, I've tried all that at one point or another in some form or fashion.

I wonder why some of us seem to be unable to run this in surround and others not.

This is confounding. I'm about to start raising voltages in my bios for the hell of it.. even though everything has passed stability tests.

Too bad this crashreport that gets generated means nothing to me :-?


-
2
38fb22844cfffd8a
crash
ea.dice.RomePC.Cl
2010-12-08 22:04:17
602574

0x5A3DB6
0x5A3DB6 0xAC8537 0x2FFFF 0xACF12D 0xAE284E 0xAE2EC8 0xAC8D40 0xBBFD5F 0xACD870 0x144F2B8 0x8E6B1E 0x5B2022 0x74FF166B 0x90AE5F 0x15475D0 0x723C5320 0x7DC7BF 0x7E388E 0x1429700 0x508F87 0xAC6EA9 0x93EDCF 0x74FF166B 0x74FF166B 0x571292 0x74FF166B 0x5B25D9 0xB4094B 0x74FF1126 0xB40B59 0x104938E 0x104938E 0x104938E 0x75100849 0x104938E 0xB3C58E 0xB3C58E 0x1975A68 0xB648A6 0x1975A8C 0xED7198 0x14D8C08 0x723B29BB 0x1975A68 0x723B8CED 0x723B2A47 0x74FF3677 0x76F79D42 0x75019775 0x75019775



registers: Edi 05f22220, Esi 00000000, Ebx 00000000, Edx 00000000, Ecx 0afdb530, Eax 1bf104a8 Ebp 0ba7fa50, Eip 005a3db6, Esp 0ba7fa40

Well, here's some hope. DICE is working on the issue, they want to fix it once they figure it out.

http://forums.electronicarts.co.uk/battlefield-bad-company-2-pc/1376576-eyefinity-surround-ctds-2.html#post18861294

Cool, DICE have PM'd me on the EA forums and asked if I could help them gather some info on the problem by running a debug executable and providing some info on the crashes and my hardware.

Wow, Mikael Kalms from DICE just phoned me to talk about the crashes a bit. He think's they've identified the issue causing them and wants me to try out a new build.
He's very nice guy and really wants to get this fixed for us.

DICE ftw! :rockout