Forgotten Hope Public Forum
Forgotten Hope 2 => FH2 Help / Support => Topic started by: tippy on 16-07-2012, 02:07:19
-
I got FH2 2.45 installed and everything it will run fine for about 45 minutes then randomly CTD no error or anything. My screen goes black for a second and then I am back on the desktop.
-
Same problem. Operation Cobra, in a M4A1 76, loading AP shells, bam randomly crashes.
-
Same problem! I will load the map up and 10 secs later it CTD....
-
Could you guys run FH2 in windowed mode for me. Would be nice to know what error pops up just before the game ctds.
-
I ran it in windowed mode...I still don't get an error when I ctd.
-
Anyone got anything else I could do?
-
Ok, how much RAM are you running, what's your OS and where is FH2/BF2 installed?
-
Also getting random CTDs, several times a day, regardless of map.
Specs are a GTX460, an i5 2500k and 4GBs of RAM. GPU doesn't overheat.
Had the same random CTDs on my previous builds as well, on all versions of FH2.
Oh, and running Win7 64. Admin mode on etc.
-
Im running 8 gigs of ram. Windows 7 64 bit with a AMD Phenom II 1045T six core processor. With a Radeon 5570.
-
Aside from maps known to crash from time to time (in 2.4 atleast; Gazala, El Alamein, Cobra and a few more) it could be anything from drivers to faulty hardware like memory etc. If other games crash then check memory with memtest and cpu/gpu temp. always update drivers for soundcard, chipset gfx, network adapter.
-
Aside from maps known to crash from time to time (in 2.4 atleast; Gazala, El Alamein, Cobra and a few more) it could be anything from drivers to faulty hardware like memory etc. If other games crash then check memory with memtest and cpu/gpu temp. always update drivers for soundcard, chipset gfx, network adapter.
Never had this issue with other games, including BF2. This is a FH2-only thing for me and it is the number one reason why I don't play more than 2-3 games a day, when I really want to play more of the awesome .45 stuff. As said in an earlier post, the temps are normal. And I doubt that it would be hardware related seeing as how I got the same random CTDs on three different PC builds.
-
Unfortunately the CTDs is something we all have to live with. Some suffer from this more than others and although devs have tried many times to find a solution, nobody knows exactly what causes it. From my experience it' s most likely RAM/sound card related as it happens when a lot of things start to blow up / show on screen (diving with a plane, artillery shelling nearby). It's a persistent problem haunting FH2 from day 1.
-
it' s most likely RAM/sound card related as it happens when a lot of things start to blow up / show on screen (diving with a plane, artillery shelling nearby).
Nope. It happens to me even on Pointe du Hoc when nothing happens. Happened twice in a row yesterday, and didn't CTD throughout Bastogne later even in the thick of the fight. Again, it happened to me through 3 different PC builds (the latest one having no trouble running ArmA2 on high settings), and regardless of audio source. Be it integrated chip or my Creative SC, bug still happens.
Since this happens only on FH2 and since the beginning, it means that the devs were the ones who introduced the bug early. Can't they track it back, going through the first versions until they reach the one that started all that?
-
Well there have been numerous tries iirc, but they all boiled down to how BF2 uses it's networkable objects and how the engine uses the RAM on a PC.
The devs have done a lot of things to improve the performance (better shaders, better resource loading, etc...) while pushing the engine to it's limits, but here's the crux. FH2 looks on par with games from 2010 on an engine that was made in 2005 and thus has mutated to the best hardware benchmark program you can wish for. If there is one single error in your RAM, then it will CTD once it touches that on bit in your RAM address. ^^
A solution would be to reduce the number of vehicles, statics and kits on a map, but that would really be a pitty imho.
Just load back up once you CTD! With modern hardware that takes less than 2min.
I seem to belong to the lucky few who can play 3h without a CTD, but that's how I'd do it if I'd ctd.
-
You should try a clean boot of the PC and play some rounds. See if it makes a difference.
http://support.microsoft.com/kb/331796
-
Just load back up once you CTD! With modern hardware that takes less than 2min.
How long it takes is not the problem, but the fact that the server will often put you in the opposing team upon connecting again, if the server isn't already full by the time you come back (it's a battle of fast clickers to get in that one server that has 64 players).
Also, may I ask about how much RAM you have? I have another 4GB bar somewhere that I could patch up with the first, but I'm too lazy to try that if it won't fix anything. If having 8GBs is what allows you to resist the memory bug, then I'll have fixed mine as well.
-
I have 8 GB with 2 4GB RAM sticks. Both produced last year.
-
I have 8 GB with 2 4GB RAM sticks. Both produced last year.
I'll try that then.
-
Played two hours without crash. I guess having only 4GBs wasn't enough. Can't believe the fix was so simple.
Now to bump my topic on the sound in tanks problem.
-
I have 8 gigs and it still crashes. Hope someone can find the source of it and fix it. Never had this problem in any of the previous updates.
-
It's not the amount of RAM in my experience, its the quality that matters.
-
Instead of trying to justify the problem with "get better hardware", how about we solve this problem so people with less fortunate budgets can actually enjoy the game?
-
I'm not saying get better hardware, I'm just listing things that are imho affected by the 'problem' and where it might stem from. And try to provide help from my vantage point as your 'friendly' support guy. Everything else is up to the devs.
-
Happens to me too sometimes... Since practically... Always. I have just learned how to live with it.
-
Getting real tired of these CTD's.
better hardware is not the answer. EVERYONE is having these random CTD's, not just the several dozen who've decided to post here about it.
I have a brand new rig, that can run any game out there on high settings, it is certainly not my ram or hardware. And this started before the last release, but is MUCH worse since.
-
I have a lower end PC and the CTD's only hit me with this patch.
I average at least 1 per session.
-
I get the same random CTD's since patch 2.45.
Played BF2 for 5 years without having these problems, and never had the issue on the previous FH2 patches.
After the CTD there's not much I can find about any errors. There's nothing being registered in the Event Viewer for example.
Specs:
Intel i5 3570K @ 4Ghz
MSI Z77A-GD55 S1155 Z77
Corsair Dominator 8GB(2x4GB) DDR3 1600MHZ
MSI Nvidia GTX580 Twin Frozr
Crucial M4 128GB SSD
-
Similar Problem. But only if I play COOP.
If I play any map in COOP mode alone, everything works fine.
But no matter which map or how many AIs - whenever a friend of mine joins me, we are able to play the map for between 20 and 40 minutes. Then CTD. Always.
There are also other bugs appearing only in coop when I play with someone that dont appear when I play alone (also coop mode), like flags that can't be captured although the bar is already full blue. But this is a known bug I think.
Nevertheless, those ctds are really annoying because you can't finish a single round together without being cut off at some place.
And no, hardware really cant be the problem.
-
Darman I have the same problem except it crashes when I play coop alone too. I played on 762 conquest server with no crashes or anything for 3 hours then quit. Something is really wrong with coop which makes me sad since its fun to kill time by killing bots :(
-
I have random crashes too.
i5 2500k, GTX 570, 2x4gb 1600mhz g.skill RAM, P8Z68-V LX, Win 7 64-bit.
Last time I tried playing in windowed mode no crash occurred. Sometimes I can play just fine the whole day but sometimes I get crashes every 30 mins or so.
-
for me game tends to crash after the end of round, when the server is about to change map... it was happening like every other time yesterday while playing on the 96p test server, but it happens on regular servers as well.
I have Phenom II X6 1075T @ 3.2 GHz, HD6950 DDR5 1 GB (slightly OCed), Kingston 16GB (two 2x4 kits) 1333/1600 MHz RAM and 970A-G46 MB with a 600W PSU... other games are running fine, nothing should be overheating (it just has to be a software issue with the mod, this is at least my third setup I've been running FH2 on since 2009 and CTDs were always present, to various extent)
-
it's weird becuase with mine it seems that some servers last MUCH longer then others. I load up 762, 10 minutes later I CTD. I rejoin and 20 minutes later I CTD. I play on hslan and it's much more stable. I can go 1 to 2 hours on there without it crashing. On the 96/128 player server I almost never CTD, ever. Once every 3 or 4 hours if i even play for that long. I don't know if this is random luck, or if the servers are the problem. I do seem to get them less then other people, (At least on hslan), so I should just be thankful for that...
-
I know I've always had CTD's with FH2, but not this many as with 2.45. This evening I had 3 of them.
I'll try updating drivers etc...
-
I've got 64gb of ram, and 2gb on the video card, crashes, but im going to try it with the desktop parameter thingie.
-
Me too... never noticed so much CTD before 2.45
I CTD 1-2 times per gaming session (~3-4 hours), mainly on map changes but also in game (mostly when shooting tank or arty guns).