Constant Crashing

[Olm]

I have fixed my problem with BF3, so decided to let you know, since your forum and this post pointed me to the solution.

I had failure in atkdx11disp.dll and this particular DLL has nothing to do with DX11. This is the ASUS driver, which comes with Gamer OSD. So I just uninstalled this crappy software (which I was not using anyway) and it stopped crashing.

Thought may be useful for you guys

[BadHabitz]

There was an update to Origin when I logged in this morning. Maybe there's something in there that will help?

[Apache Warrior]

I have fixed my problem with BF3, so decided to let you know, since your forum and this post pointed me to the solution.

I had failure in atkdx11disp.dll and this particular DLL has nothing to do with DX11. This is the ASUS driver, which comes with Gamer OSD. So I just uninstalled this crappy software (which I was not using anyway) and it stopped crashing.

Thought may be useful for you guys

Thank you for the information. And
Apache

[Dutchguy000]

I feel like a good majority of purchasers are having issues of some sort, but no official word on it?! What gives?

I've fiddled with all of the settings, still working through disabling all of the options for the CPU. I can't set affinity for the bf3.exe process, but I went into msconfig and set it so only 1 core is seen at startup, I figure that does the same. Didn't work, either way.

I'll be going into event viewer tonight...back into the fray....

AND THE GAME IS SO GREAT WHEN IT RUNS. CURSES

[Apache Warrior]

AND THE GAME IS SO GREAT WHEN IT RUNS. CURSES

Apache

[Cain]

AND THE GAME IS SO GREAT WHEN IT RUNS. CURSES

Very true, and Welcome to Cain's !!!

[Dutchguy000]

FINALLY got mine to work for longer than 1 round. I actually managed to play mine for ~4 rounds, then it DID freeze again. But this was the first time I actually played back to back rounds start to end, so I believe it made a large difference:

1) Prepare the operating system to be able to use beyone 2GB address space with a userva of 2.5GB (only 32 bit OS's need to do this): I am purposely using only 2500 for userva for specific reasons and any more will likely not be needed, as a result the kernel will have plenty of space to play in.

All 64 bit OS's
Nothing to do on the OS. Proceed to step 2 on setting the executable. 64 bit OS's running 32 bit binaries are also limited to 2GB application space.

XP 32
* Find your Boot.ini located usually on the C:.
If you cannot see it, you probably have system files hidden, then follow these instructions at microsoft (also uncheck "hide protected operating system files")
* Right click on the boot.ini and choose properties. Uncheck "read only"
* Open the boot.ini by double clicking it.
* Under the section called find the line that says "multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=" Wind ows XP Professional...". Yours may look a bit different. We are going to make a duplicate, so that if you make a mistake you will not harm yourself from booting into your computer. Drag you're mouse across the entire line, right click and choose copy. Then right below the line you just copied right click your mouse and choose paste. You should now have two lines one after another that are exact duplicates.
* Change the bottom line that you just copied with the following addition on the end. Add a space at the end of the line and then this without the quotes "/3GB /USERVA=2500"
* In that lower boot entry you just made, find the name of the operating system in quotes and change it to something like "Windows XP 3GB", so you can differentiate at boot up.
* Close and save the boot.ini.
* Right click on the boot.ini, hit properties, check read only.

Windows 7/Windows Vista
* In Windows 7/Vista go to Start menu. Go to Accessories. Locate the command prompt shortcut and hover mouse over it. Right Click on the shortcut then select Run as Administrator.
* In the command prompt type this exactly: bcdedit /set increaseuserva 2500. Then hit enter.
* Make sure you get a message back confirming the change was made. To verify the entry is there you can type just bcdedit, hit enter, and you should see the entry now listed.
* Then close the command prompt. You just told Vista to increase user virtual address (userva) space to 2500MB.
* Changes take effect on reboot but don't reboot yet.

SUMMARY
We extended the user virtual address space in XP, Vista and 7 to 2500MB, so now applications can utilize up to that much if they are set to be Large Address Aware. While some 32 bit games/applications are set, Empire is not.

2) Now reboot the PC because Windows needs to set the userva at 2500 which only happens after startup.

If you skip any step it will not work. When you have rebooted you should be good to go. Run the game as normal with the original game shortcut.

TO UNDO THE CHANGES
For the XP 32 bit just delete the line from your boot.ini.
For Vista 32 Open command prompt as administrator and type: bcdedit /deletevalue increaseuserva. That deletes the entry.
Reboot and you are back to normal.


Going to fool around with this some more tonight, but I feel like for 32-bit systems this will make a difference!

[{CLR} Cobalt]

Isnt the game run in 32bit process/mode. It would make sense if it runs in 32bit mode. I'm assuming this is a 32 bit mode game and doesnt utilize the 64 bit Virtual Address Space.

See reference here:http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

[slice]

Isnt the game run in 32bit process/mode. It would make sense if it runs in 32bit mode. I'm assuming this is a 32 bit mode game and doesnt utilize the 64 bit Virtual Address Space.

See reference here:http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

Yeah... 99% sure it is a 32 bit app

[Quamin]

Yeah... 99% sure it is a 32 bit app

As I have this thing crash in a weird way, forcing me to use the task manager to kill the process, I always see it's running in 32-bit mode. Tis a shame...

[{CLR} Cobalt]

So if it's running in 32 bit mode then this fix above does work for 64bit systems right.

[paceman]

I've been BSOD about every third game. Last night I tried changing my video settings from High to Medium. I then played 3 straight games without a crash. I'll try some more today and report back on if I BSOD again.

[Nauticas]

We extended the user virtual address space in XP, Vista and 7 to 2500MB, so now applications can utilize up to that much if they are set to be Large Address Aware. While some 32 bit games/applications are set, Empire is not.

This has worked for me. I played last night for a good 2.5 hours straight without crashing.

I was getting 2 types of crashes:

1) Black screen on map load. I have a Geforce 560 Ti. I was using the 285.62 drivers when I was getting the black screens. I backed up one driver version to the Beta driver released just before BF3 Beta came out, which was 285.38 I believe. The 285.38 drivers have not given me the black screen on map load for a good 4 hours of gameplay now.

2) Game freezes mid game. ALT-TAB to find a BF3.exe needs to be closed crash. The large address aware fix stated above seemed to fix this issue.

My system specs are below:
Dell XPS 630i
Windows Vista 32 bit Home Premium
Intel E8500 Dual Core 3.16 GHz (overclocked to 3.8 GHz)
4 MB DDR3 RAM
PNY Geforce 560 Ti
nVidia motherboard

P.S. Dutch is my new best friend.

[Pumpkin_Jack]

I laugh because i should be having problems given my driver is version 160 sometin and it tells me to update to at least 250 somtin but hell, if it aint broke dont fix it

[Nauticas]

PJ, The 285 version has significant performance increase from the 280 and below versions.

I have actually tested this and the 285 drivers increased fps a good 20%.