7 replies to this topic

[Dershan]

Hi, first I have to apologize, if there is an existing thread for this. I looked over several threads, but didnt found something similar.

Cliffs:
1.) It happens most time during the first game, sometimes in the second or even third game of the day
2.) The screen gets black for 10 to 15 seconds, then the game goes on.
3.) After the game went on, there is heavy lagging with a very low framerate, which makes it impossible for serious playing and helping the team. Could even leave the match, would be no difference.
4.) In the next games of the day, there are no probs anymore
5.) Tomorrow = new day, SOS (same old sh*t)

I thought, its maybe a driver problem. Nvidia here. Feels, as the driver has to restore after a crash in the game or somewhat. Just a idea. No problems with any other game or stuff.

Some ideas? Any input is appreciated. Thanks.

[Shamous13]

have you tried running the MWO repair tool?

[Tarl Cabot]

1. System details, such as the first part of the dxdiag, from the beginning to the first section or so that also includes the video and sound card.

[Dershan]

Problem solved. Thanks@ Shamous13. Didn't know this nice tool.

[Nucleux]

I keep getting a black screen when i try to play and when i alt+tab out it stays black screen and wont let me reconnect

[RiSE]

Confirmed, I have the exact same issues and it makes the game unplayable.

I'm going to try the repair tool as mentioned, but I'm pritty sure it's a nasty bug, I'm actually hoping it is a video-card driver bug/issue so the devs can focus on other stuff

Please PGI look into this!

Some Specs;
HP Workstation 3.07GHZ XeoN CPU (QuadCore)
6GB RAM / 2 x 128GB SSD HDD
NVIDIA MSI GTX660 VideoCard (+MSI AfterBurner)
24" LCD (Playing at full screen)
150/15 MBIT Internet Connection Behind FortiGate Router

Thanks!

Edited by RiSE, 13 July 2013 - 04:49 AM.

[20k]

This (in my experience) is a classic driver crash, followed by the card running at half clocks - the situation is (normally) unsolvable except with a full system restart. I've run into this issue multiple times while programming (by causing driver crashes), and I wrote quick a tool that defaults clocks back to normal. It even works midgame in mwo

If this occurs regularly, you may want to downclock your card. Some 660tis came clocked at a level that ran acceptably under the first set of drivers released for them, however subsequent drivers actually *lowered* the card's maximum clock stability thing (words) so some of them crash under extreme load (as is my case, i have a shortcut to downclock by ~20 mhz)

I'm not sure if the devs are ok with distributing executables (I'll remove it if they aren't), but here's the source and exe (with mingw dlls). It simply runs an opencl kernel that causes the graphics driver to time out in, which resets the clocks back to default. The source isn't pretty looking, but it works. I'm 100% sure that there can be no damage to your hardware, as it simply uses a feature of windows which is the display driver timeout recovery feature

https://dl.dropboxus...ock%20fixer.rar

I would recommend trying the mwo fixer tool first and seeing if that works

Edited by 20k, 15 July 2013 - 09:33 AM.

[Dershan]

thanks for this, 20k.

Update:
How I said: It worked for me since using the mwotool, but just for 2 or 3 days, then it happened again regularly. After some research, I found following:

http://support.micro...m/kb/2665946/en

seems to be a very old and very known prob, which is widely ignored, even in many other games. I patched it using this tool. Now it worked since then without any further problems and seems stable.

PS: Reclocking to the standard didnt helped me. I run the card with default values again now but this wasnt the solution. The tool above helped.

Dershan

Edited by Dershan, 19 July 2013 - 04:00 AM.