9 replies to this topic

[Sorero]

Hi,

I get random black screens in MWO. Sometimes I can play for more than an hour. Sometimes it crashes after 2 minutes in game, for several games in a row.

I've a Radeon R9 380.

I can switch to the desktop but only see my taskbar (not the desktop) and I cannot close MWO. I have to logout and login again.

Does anyone have an idea, what I can do? Best without logging out and in again.

Thanks,
Sorero

[chucklesMuch]

Hello,

I also have Radeon R9 380 and was having this issue a month back...

Resolved the the issue by uninstalling the current drivers and reinstalling Dec 2015 drivers (from AMD archived versions)... no more black screens...

[Podex]

it's the driver. It just did it to me...again.

[Helene de Montfort]

I have a R9 380 and also have troubles with MWO, but only when i use directx 11. Personally, it's not black screen but complete loss of video signal. I can hear the game and other programs still running, but the monitor doesn't receive any signal anymore.

This is an issue i have only with MWO, and i solved it by using directx 9 in settings. It did it with the three last driver versions.

[Digital_Angel]

I get the same with my Radeon HD 7800 sometimes. Give it a minute, hit Ctrl+Alt+Del, then escape back into MWO makes it come up 95% of the time at the Ready screen before match start. Occasionally have to wait a minute and repeat a 2nd time. Have never had the work around fail after 2nd attempt.

[Javenri]

Happened to me a few times with a Radeon 7870. If the client crashes once, then it keeps crashing. Better restart PC to save time.

[Mawai]

I have the same issue with an R9 380X ... Crimson 16.3.2 driver set. The game causes a black screen periodically and unpredictably.Sometimes I can play a half dozen matches other times it might happen after one or two. I have not seen it happen in any other app.

Alt tabbing out of the application brings up the bottom bar but the rest of the screen is still black. Trying to close MWO does nothing and I can't get task manager or any app onto the screen in order to force a quit on MWO. I can use the cntrl-alt-del screen to select the power options and reboot and that is about it.

I have noticed that the most recent driver install also automatically starts plays.tv ... I don't know if the screen capture software might be part of the problem.

[The Robot Jox]

i can confirm this on my 780ti, is like if someone turned off my monitor so a quick second. dx11

[Mawai]

For AMD owners ... I have an R9 380X and upgrading to the crimson 16.7.2 beta driver appears to have fixed the issue. I may have just been lucky but I have played a dozen or so games without a crash so far.

P.S. I was also reading that the problem may be related to dx11 and switching to dx9 might bypass the issue.

Edited by Mawai, 22 July 2016 - 02:01 PM.

[Tier5 Kerensky]

AMD R9 270 &Win 10 64-bit preview. Using DX11, I think it's better for weak machine.

My graphics drivers occasionally crash and thus crash the game, right when the battle should start, when the 3D world has loaded. Never after that, or elsewhere. Sometimes I can return to the game, and sometimes it just keeps crashing on that particular map. Once I tried to join back into faction play Invasion about 6 times, always crashed. Happens with some other games too while playing them, but not all. Same as in Windows, crashes while browsing, sometimes even several times a minute. And sometimes the computer freezes completely for a while, if it doesnt' crash, it will resume eventually.

This started happening after installing one new build months ago.(those Windows insider preview builds).

Now recently I did cleanup with DDU. Display Driver unintaller from guru3d. Then I installed the latest hotfix drivers. But before I could see it's effect alone, a new build pops up again and is installed.

So far I've had no crashes in Fallout 4 or MWO, but I still get quite a lot of those freezes in Fallout 4. Sometimes in Windows too. Previously they sometimes resulted into crash, which is nasty as I'm playing in hardcore mode where there is no quick save.

Soooo, maybe give DDU a go. In my case it's possible, as each build is installed, it seems to reinstall/transfer the drivers into it, so it's possible the've become corrupted during that one build where these crashes started to happen. But, like above, these are now crimson 16.7.2 beta drivers so maybe the previous drivers were to blame.

Edited by Teer5, 23 July 2016 - 06:25 AM.