7 replies to this topic

[Ph30nix]

i just updated to latest nvidia driver (GTX 760)
ive played one game successfully (it hung up first time and i had to reconnect but it got in after that)
second game it crashed 3 times in a row and i finaly gave up.

comp spec
I7
win 7
GTX 760
4gig ram (yea yea need to upgrade but hasnt been an issue any other time)
1 tb hard drive

oh the map was
SULFUROUS RIFT

first map was
BOREAL VAULT

it ran okay after the initial hang up and rejoin

Edited by Ph30nix, 11 December 2014 - 07:10 PM.

[Aresye]

I crashed 3 times on Sulfurous Rift in the same match. Thanks to that, I did 4 out of 6 kills, and 1060 out of 1360 damage...in a Mist Lynx o.O

I thought it was just my computer, so I've been updating drivers, defragging, etc. Good to know it isn't just me.

[Ph30nix]

yea when games screen has frozen occasionally (like mining map) ive found that hitting ctrl alt del and brining up task manager then just going back into game will get it to wake up and run properly again.
tried it this time right before crash and it didnt work but i did see the mem alocation for MWO to be 3gig at one point and about 3.5 at another (might have been a spike) but 2.7-2.9 seemed the norm for the CW maps.

[Ninthshadow]

I pointed it out elsewhere but just to chip in my two cents: I'm also suffering from these again.

They typically occur when trying to deploy in a new mech, so I'm thinking it's related to either the drop-off sequence or the process of switching mechs.

I noticed the memory numbers themselves were absolutely tiny. I can only assume that this is a pretty good sign that not much would need to be changed for some people to cross Memory Allocation off of their list.

End of Match crashes and other weirdness not withstanding.

[nitra]

core i5 at this location amd r260 x and only 4 gigs of ram

always had memory allocation crashes.


the core i7 nvida gtx 760 with and 16gb of system ram rarely ever gets the memory allocation crash less im playing for hours.


most likely a memory leak that needs to be tracked down.

[Levi Porphyrogenitus]

I started getting the error on my second time through the sulfur map. I tried a reboot and ran the repair tool and rejoined the match, and the error recurred immediately upon loading in.

Edited by Levi Porphyrogenitus, 11 December 2014 - 07:34 PM.

[Rhaythe]

I've dropped in two CW matches tonight. The game has hardlocked and crashed my machine both times. Oddly enough, when I rejoin, everything seems fine. It's always within that first minute of a match that things go POOF.

[scruffy416]

Had one occurrence on Sulfurous as well.

on a core i7, hd7850, 16gb - not running much else concurrently.