Last 2 games I entered, my screen froze after a few seconds of moving, the funny thing is, I could still hear sounds and even hear myself moving when pressing "w".
Is this normal ? because I had alt f4 out in both cases after waiting 30 seconds, just to be dead by the time I managed too reconnect, no really a fun experience :/
I'm using nvidea's own advice on graphical settings for this game and yesterday I crashed once (even in full combat I remain above 40 fps) , but I didn't screen freeze and hear sounds.
Is it me or the game ?


Game Freeze ?
Started by PanzerSmurf, Aug 15 2014 06:38 AM
5 replies to this topic
#1
Posted 15 August 2014 - 06:38 AM
#2
Posted 15 August 2014 - 06:45 AM
It's not normal. Immediately exit out of the game. Reopen the game. Rejoin the match if possible.
What you can do is send email reports to support@mwomercs.com with some information as well as the files Omikron.log, DXDialog.txt, and your Crashdump.dmp file.
DXDialog.txt comes from the windows program DXDiag.exe
Omikron can be found in your Mechwarrior Online folder. Crashdump.dmp can be found in your Mechwarrior Online\User folder.
That'll let them know and from that they can tell you whether it's their end or your end.
Personally I had problems with temperature, and ever since I popped the side open and have a box fan blowing on it. Most of my problems went away.
But that's a pretty redneck way to fix it.
What you can do is send email reports to support@mwomercs.com with some information as well as the files Omikron.log, DXDialog.txt, and your Crashdump.dmp file.
DXDialog.txt comes from the windows program DXDiag.exe
Omikron can be found in your Mechwarrior Online folder. Crashdump.dmp can be found in your Mechwarrior Online\User folder.
That'll let them know and from that they can tell you whether it's their end or your end.
Personally I had problems with temperature, and ever since I popped the side open and have a box fan blowing on it. Most of my problems went away.

#3
Posted 15 August 2014 - 06:52 AM
Sounds like your display driver is crashing, and since you can still hear game sounds the game itself hasn't crashed.(unless you're hearing an audio loop)
My display driver/GPU is pretty flaky and I will get frequent display driver crashes which are not associated with intense combat or effects (they tend to happen when I am out of combat, not in combat) but it's very clearly an issue with my GPU and not MWO.
My display driver/GPU is pretty flaky and I will get frequent display driver crashes which are not associated with intense combat or effects (they tend to happen when I am out of combat, not in combat) but it's very clearly an issue with my GPU and not MWO.
#4
Posted 15 August 2014 - 06:55 AM
I'll see if I can find some updates then for my drivers and collect the crash reports if it happens again.
#5
Posted 15 August 2014 - 08:19 AM
when it happens try looking in your system tray for 'display driver has stopped working and recovered message' i used to get this all the time mostly on alpine or river city.i used to fix it by using older drivers but have since rebuilt my computer.i did upgrade my video card bios (didnt know they had bios) thyere could be risks updating the bios but it may be an option for a fix.also you should post your system specs.they might help peoiple help you troubleshoot.
i can't say exactly what fixed my problems because my MB died and i went from win7 32 to 64, new MB and ram and updated my vid bios all around the same time.
the 2 crashes i used to get were display driver stopped working (black screen but still hear game) or memory allocation error ### bytes failed(game crashes with an error box center of your screen)
i can't say exactly what fixed my problems because my MB died and i went from win7 32 to 64, new MB and ram and updated my vid bios all around the same time.
the 2 crashes i used to get were display driver stopped working (black screen but still hear game) or memory allocation error ### bytes failed(game crashes with an error box center of your screen)
Edited by Gorantir, 15 August 2014 - 08:22 AM.
#6
Posted 15 August 2014 - 08:51 AM
Quote
But that's a pretty redneck way to fix it.
But the redneck way is the best way!

I've had this happen to me a few times, alt tabbing out and back in always fixed it.
Edited by Nurph, 15 August 2014 - 08:52 AM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users