11 replies to this topic

[That Guy]

MWO is causing my machine to get into a hard lock when left alone and the screen saver goes up. previously the game overrode the screen saver, and it did not pop up.

I assume it is something to do with the screen saver, since when i come back the screen is black and does not respond to any key presses, be it ALT-Tab, AltF4, C A D, and only a hard reset via the power button frees it up.

it has happened three times today. i frequently leave my computer alone while in the mechlab. be it bio break, getting food, taking a break and what not, so this is very game breaking.

as an additional change from last patch, when ALT-tabing from MWO to a web-browser or other program or window, that window is set to the resolution that MWO is set to, rather than remaining at full screen as it did before.

has anybody else experienced a computer lock after time AFK? this is really something i dont want to test out too much, as i am afraid that constant hard resets could break something...


i have windows7 64bit

[Alexander Garden]

Can you bring up your 'Change power-saving settings' window through a Start Menu search and let me know what your current power plan is?

[That Guy]

my machine is a laptop, FYI.

power setting is "gaming". all power settings are all set to 'never' (Dim, turn off monitor, sleep) when plugged in.

[Durandal]

Have you done any Windows/driver updates recently? I was having a similar problem where MWO would lock up my PC (or blue screen it) that I thought was an issue with MWO...but it turned out it was a problem with something that windows had updated automatically. Reverted the windows update, and everything fixed. Worth checking it out to see if it's causing your problem too.

[ShinVector]

That Guy, on 18 February 2015 - 05:56 PM, said:

MWO is causing my machine to get into a hard lock when left alone and the screen saver goes up. previously the game overrode the screen saver, and it did not pop up.

I assume it is something to do with the screen saver, since when i come back the screen is black and does not respond to any key presses, be it ALT-Tab, AltF4, C A D, and only a hard reset via the power button frees it up.

it has happened three times today. i frequently leave my computer alone while in the mechlab. be it bio break, getting food, taking a break and what not, so this is very game breaking.

as an additional change from last patch, when ALT-tabing from MWO to a web-browser or other program or window, that window is set to the resolution that MWO is set to, rather than remaining at full screen as it did before.

has anybody else experienced a computer lock after time AFK? this is really something i dont want to test out too much, as i am afraid that constant hard resets could break something...


i have windows7 64bit

This sound like the crappy bug that causes video freeze for Nividia card owners.
It only happens to me on 64bit for some reason.

Only way to get out of it is to enable 'Always on Top' for Task Manager.
When it happens you can see Task Manager with ALT+CTRL+DEL and End Task MWO client that has hung.

[Willard Phule]

ShinVector, on 19 February 2015 - 01:33 AM, said:

This sound like the crappy bug that causes video freeze for Nividia card owners.
It only happens to me on 64bit for some reason.

Only way to get out of it is to enable 'Always on Top' for Task Manager.
When it happens you can see Task Manager with ALT+CTRL+DEL and End Task MWO client that has hung.

And here I thought it was just a free "Crash to Desktop" Module that PGI was giving us access to.

[ShinVector]

Willard Phule, on 19 February 2015 - 03:18 AM, said:

And here I thought it was just a free "Crash to Desktop" Module that PGI was giving us access to.

Technically video freeze is worst than CTD. You completely lose focus on your PC and being forced to a hard reboot when it happens. Unless you do the work around I just mentioned.

[That Guy]

ok so i watched the crime in progress and yes, it certainly seems to be the screen saver kicking in. screen goes black and then flickers from black to the desktop then just stays black. the background music during this time skips and pauses.

unfortunately setting my task manager to always on top still did not allow me to access it, and it only a hard reset un does the lock.
but yes i do have a Nvidia card with the 344.65 drivers. unless windows did a sneaky update tuesady or wednesday i have not changed any of my drivers lately.

this MWO hard lock only appeared after this patch. even this last weekend i left the game open for about an hour wile afk and it was fine

[ShinVector]

Sad to hear... But be a different bug in your case.
However Town Hall says the found the cause of the Nvidia Video Feeze bug.. 'Cryengine Instancing' issue. ? Thats good to hear.

[PauloBR]

I don't think it's related to the screensaver.

Sometimes my Nvidia driver crash while playing MWO and the screen turns black.
If I can press CTRL+ALT+DEL fast enough (before windows reboot itself after freezing), MWO closes and a Nvidia crash error popup shows, then I can open MWO again.

It happens more often with DX11. Almost never with DX9.

I think it's something related to my factory overclock without enough power input (voltage), but I can be wrong.


I hope you can understand what I typed.

[That Guy]

when my Nvidia drivers crash some very specific things happen to my machine. these are inconsistent with what happens in this case. the computer locks up when the screen saver activates (in my case around 4-5 min). however, i did look into the DX11. i tried switching it back to DX9 and the problem stopped happening. when the 5 min timer passed the computer did not try to turn on the screen saver, and the did not lock up.

so something wonky with DX11. thanks for reminding me that DX11 was a thing paulo. for the time being just going to switch back to DX9.

[Kelbor]

I have also been experiencing a hard crash (power off/ reboot) issue from this weeks patch but it was likely from my own tinkering. I have been changing the sound bit depth and frequency, along with messing with the exclusive mode in the speaker properties lately. Restored the defaults and it fixed itself. Just for FYI i'm running a AMD 7850 GPU.

Edited by Kelbor, 20 February 2015 - 03:11 PM.