The game crashes after 5-10 minutes, v.1.7.4

[Kk-Yrxs]

Hi, for me and my friend, the game crashes after 5-10 minutes, without an error, it just throws it to the desktop. I tried changing the graphics settings, deleting the game along with my accounts, but still nothing changed, it was impossible to play. I played before, I never had this problem, after the update this problem appeared, please help

[Robert_Shapiro]

Same exact problem.

[Robert_Shapiro]

I suppose it have something to do with bit versions of the game itself, like, lemme explain:

Launcher is launching 32 bit verison of the game, when at the same time you have 64x version of your OS, operating at the moment

I don't know how to switch it from 32 to 64 though, but there is distinctly a file of PRBF2 without w32_ded prefix to it in the root directory of the game

[Suchar]

Hi, for me and my friend, the game crashes after 5-10 minutes, without an error, it just throws it to the desktop. I tried changing the graphics settings, deleting the game along with my accounts, but still nothing changed, it was impossible to play. I played before, I never had this problem, after the update this problem appeared, please help

https://www.realitymod.com/forum/showth ... p?t=147961

[SemlerPDX]

I suppose it have something to do with bit versions of the game itself, like, lemme explain:

Launcher is launching 32 bit verison of the game, when at the same time you have 64x version of your OS, operating at the moment

I don't know how to switch it from 32 to 64 though, but there is distinctly a file of PRBF2 without w32_ded prefix to it in the root directory of the game

Battlefield 2 (and therefore Project Reality) is a 32-bit application. You can't switch it from 32 to 64, that's not a thing. Windows uses a compatibility layer called Windows-on-Windows 64-bit (WoW64) to allow 32-bit applications to run on 64-bit versions of the Windows operating system. This has been a standard for almost two decades.

Your issue has nothing to do with the bit version of the game itself, or your Windows OS.

Provide a crash dump as directed by Suchar above, and I'm sure the actual culprit can be properly identified.

[saad]

Same exact problem.

Did you find a solution to the problem?