55 replies to this topic

[Fotracul]

I had hourly fatal error crashes before the hotfix 2 and 2 GPU device lost crashes.
After reducing the overclock on GPU and apppling the hotfix 2 i had 2 fatal error crash and a random crash in about 12 game hours.
Never in my life had so many times a game crash this often, not even the terminator game made by the poles who made the crap rambo game

[Funky Bacon]

I had one crash during a loading screen after finishing a mission but that's it.

If the game is crashing that hard then there is a possibility your hardware is starting to fail. (recently lost my GPU as it started crashing when put under heavy load and had to fall back on my old 570. The card still works under light load, but any heavy load will cause it to blackscreen and force me to reset the PC via the power button.)

[Daggett]

I had no fatal error crashes and two freezes during missions. I guess that's okay for the amount i played so far.

[FRAGTAST1C]

I get that Fatal Error crash if I play for a couple of hours at a stretch. This happens even on games like Fortnite.

[MW Waldorf Statler]

after use the Geforce Control seetings and set MW% by Vertical Synch to adaptive , the Crashes very rare , most only by Tabbing out ,or by end of tnd Mission and not going fast enough from the first Mission Screen after it

[lazorbeamz]

I have like 45 game hours and have finished the game. It has happened to me but only once.

[Appogee]

No crashes.

No overclocking.

[Nesutizale]

I had 2 hickups because of tabbing out while loading the game. It dosn't seam to like it. Other then that, no crashes.

[Fotracul]

FRAGTAST1C, on 16 December 2019 - 03:05 AM, said:

I get that Fatal Error crash if I play for a couple of hours at a stretch. This happens even on games like Fortnite.

Thanks for explaining, seen your other reply on the dedicated thread to fatal error, i kinda missed it when making this thread anyway...

Funky Bacon, on 16 December 2019 - 02:44 AM, said:

I had one crash during a loading screen after finishing a mission but that's it.

If the game is crashing that hard then there is a possibility your hardware is starting to fail. (recently lost my GPU as it started crashing when put under heavy load and had to fall back on my old 570. The card still works under light load, but any heavy load will cause it to blackscreen and force me to reset the PC via the power button.)

Sorry about your GPU, rip.
But in my case it is not this, the 2070 super and 9700KF are 3 months old and under watercooling, the only time i got the device removed error was when playing mech warrior online, and this kind of error shows up as well in unreal engine, it is a generic error when the videocard driver fails, due to overclocking.
I lowered the OC just for that game, since MWO did not liked it, and i spend one day stress testing the GPU and it boggles my mind that no synthetic benchmarks ever crashed, but MWO did. Now the same story happened with MW5, benchmarks ran fine, did not spend a day with them, just a few hours. Anyway that "device removed" crash happened only once and made me spend half a day to check my OC again.
Funny thing is, today i did not had a single crash, i think it is the way the map seeds are generated, it happens random, i just appreciate Russ for delaying the game 1 year to try to polish the random level generator, i cannot imagine the state of the game if it was released last december...

Edited by Fotracul, 16 December 2019 - 05:57 AM.

[RickySpanish]

No crashes whatsoever thus far for me. The game performs very well with graphical settings jacked up and loading times are general in the 10 second range. I noticed that the game begins generating the map as soon as you hit the lance select screen - that's a nice touch. By the time I've decided who's piloting the Locust of Inevitability* the map is often ready.

*I've since sold the Locust, after it failed to murder my least liked pilot. We now have a Javelin of Inevitability instead.

[Vellron2005]

For me, I had trouble even starting the game, and the Beta crashed to black screen often. I later realized it was probably caused by my power supply, as since I replaced with a more powerful one, and after the latest hotfix, I have not experienced a single crash.

I am at this moment more likely to think you have a hardware issue, rather than a software issue.

I suggest you try running some other, equally hardware-intensive game, and see if you still get crashes.

[cszolee79]

OP: just to answer, in 30-40 hours it did not crash for me. Not even once. Zero problems.
CPU and GPU both overclocked (minimally).
Never had a crash in any UE4 games. Or with MWO for that matter.

[arcana75]

It's easy to blame MW5 when you already have alot of hate for PGI and anything it does. Somewhere else not here I read someone blamed MW5 and EGS for crashing his Windows mid-MW5 install and failing to boot up upon restart. Several rage posts later turns out his hardware is 7 years old and more likely a failed/failing drive or power supply or motherboard.

I've had MWO & HBS BattleTech hard-freeze repeatedly on me, lobby, mech lab, combat, crashed often. I blamed it on everything from game bugs to drivers to Windows 10 updates to power supply, GPU, RAM, CPU. Ran furmark burntests, mem86s, cpu-z burntests, underclocked CPU/GPU/RAM, ran DDU, installed various "stable" driver versions, sent parts to RMA (even though all came back negative on problems). Could not make the freezes disappear for months. All the burntests made the PC freeze, so it had to be that part being burn-tested right?

In the end it was one thing I didn't consider. Failing motherboard. Bought a used mb to replace, refitted everything back, and it's been stable for weeks. All my hardware is dated mid 2016, and despite being only 3+ years old the one thing that was dying was the 1 thing I refused to acknowledge because it was the most annoying to troubleshoot, until I decided to bite the bullet.

I started playing MW5 after changing the motherboard. According to EGS I've played MW5 for 15 hours. Not 1 crash or freeze.

Edited by arcana75, 16 December 2019 - 06:43 AM.

[Fotracul]

Well i'm sorry i mentioned before that the benchmarks and other games except for terminator resistance that crashed once because of a game bug, never crashed, even MWO runs fine once i lowered my video card OC, I spent 2500 euros on the pc and in my country we do not have euro, so i will not spent more because of a possible hardware issue affecting one game. It is still playable for me the autosaves are a blessing, i never bashed PGI directly, i just wanted to know if this problem occurs for more people and it seems that it does. thanks for the replies

[cszolee79]

Fotracul, on 16 December 2019 - 06:58 AM, said:

i just wanted to know if this problem occurs for more people and it seems that it does

UE4 is very quirky with OC. I have some UE4 games and all their forums are full with UE4 crash problems with overclocked hardware or whatever super-duper-overclocker-registryfixer cr.p installed.
Generally, if you have a basic fresh Windows installation, a new GPU driver and nothing else, you won't have any problems.

Edited by cszolee79, 16 December 2019 - 07:06 AM.

[RickySpanish]

Fotracul, on 16 December 2019 - 06:58 AM, said:

Well i'm sorry i mentioned before that the benchmarks and other games except for terminator resistance that crashed once because of a game bug, never crashed, even MWO runs fine once i lowered my video card OC, I spent 2500 euros on the pc and in my country we do not have euro, so i will not spent more because of a possible hardware issue affecting one game. It is still playable for me the autosaves are a blessing, i never bashed PGI directly, i just wanted to know if this problem occurs for more people and it seems that it does. thanks for the replies

People have been having issues, so maybe it's your hardware configuration and nothing bad. But in my personal experience with a single game locking up my PC, it has been a hardware issue unfortunately. Often, that one game was the most demanding application I had run up to that point, so it was the first to demonstrate the hardware failure. A month or so later though and windows would be blue screening while idle. The last time that happened it was a damaged stick of RAM, and before that a failing HDD.

Edited by RickySpanish, 16 December 2019 - 01:11 PM.

[Button man]

i do not think it has crashed for me yet

[Mumuharra]

No crash here.
MW5 is extremely stable and runs smoothe on an old Intel i5 750 with 16 GB and AMD 290 4 GB.
Did not try Coop, just solo vs engine.
From this side the game is great.

[Vorpal Puppy]

No crashes. No problems whatsoever.

[WhineyThePoo]

Nada, running just fine on my ancient setup on nearly max settings.