76 replies to this topic

[CoughingCouch]

I'm having an issue where I press the play game button and it'll just sit there and say "please wait" for forever.

[Shae Starfyre]

Candun, on 30 July 2013 - 12:23 PM, said:

im having the same problem with the regular game as i'am with the 12 v 12 i hit play and game freezes get a pop up that says MWO has stopped working, close program Problem Event Name: APPCRASH
Application Name: MWOClient.exe
Application Version: 3.4.1.4418
Application Timestamp: 51f05ada
Fault Module Name: StackHash_ba63
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 77760bd2
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: ba63
Additional Information 2: ba63ca3652d33a4a52b1606e5c006cbe
Additional Information 3: 21a5
Additional Information 4: 21a54a926b0c590057ac6cd2e9a0f287

Typically, the C0000005 errors tend to be resource issues like RAM or even Devices that are not compatible with something.

[wDraco]

my fps dropped from an average 35 to 20, turn everything to low and the result is the same.

[Strongpaw]

Mech of War, on 01 August 2013 - 02:52 AM, said:

The second workaround (disabling hardware-assisted virtualization in Avast's 'troubleshooting' section) actually works, but the game and PC are working slower...

I run 2 Crossfired XFX R7950's. Been having a war trying to get MWO running since the 6th having uninstalled, reinstalled, updated everything that exists (disabling hardware-assisted virtualization in Avast's 'troubleshooting' section) is the thing that finnaly Finally fixed it -.-

[paradym123]

AMD + AVAST user here as well. I too can confirm this fixed my client.

[Searoy]

I'm running AMD all around, MSI board with Althalon II x4 640 and a Sapphire 7950. I'm not running Avast. I tried the fix, nothing. I uninstalled/reinstalled, nothing. It doesn't just sit there though. I get a "sessions was lost" and can't log in.

ONe thing that seems to be going hand in hand with this is recently I started getting "certificate" errors on MWO. "Could not display content," etc never appeared before but is now. I suspect that it's part of the problem.

Edited by Searoy, 11 August 2013 - 12:20 PM.

[Tarl Cabot]

Searoy, on 11 August 2013 - 11:55 AM, said:

I'm running AMD all around, MSI board with Althalon II x4 640 and a Sapphire 7950. I'm not running Avast. I tried the fix, nothing. I uninstalled/reinstalled, nothing. It doesn't just sit there though. I get a "sessions was lost" and can't log in.

ONe thing that seems to be going hand in hand with this is recently I started getting "certificate" errors on MWO. "Could not display content," etc never appeared before but is now. I suspect that it's part of the problem.

If the certificate error the installer is trying to install one or more missing microsoft components but cant.

Two workarounds
Temporarily change system date to May 5 or earlier and run the installer,
or
Install/reinstall directx 9c, C++ and several .Net programs, as listed in the sticky at the top of this sub-forum. Just remember the game itself requires the 86x versions, and if you only install 64bit it will not work. If you post the omnicron logs, it will say what is missing.
Crash at Login? This may help!

[Gremlich Johns]

Tarl Cabot, on 31 July 2013 - 07:57 AM, said:

After reinstalling Avast!, did you allow it to fully update (added) and rebooted your system before playing MWO?

For others, PGI has a sticky in the patch area and they are looking into it.

Amd + Avast! = Stuck On Please Wait

They are NOT looking into it. Find the last time anybody from PGI dev staff said anything about it. Moderators are messengers - they are not responsible.

[Gremlich Johns]

Zatharus Mathew deTora, on 31 July 2013 - 07:11 AM, said:

Why on earth would they release this patch with this kind of problem?

Money

[sinsofzavv]

same here

[Marikc0]

Played the game a good while back with no problems. Installed it again on a clean install of Windows 7 (have wiped since the last time I played this game quite a while back). Patched the game. Hit play in the launcher and the launcher closes as it should and I wait for the game to load... nothing happens. Absolutely nothing. No hung process. No error logs whatsoever. Not a thing.

Over 20 years of experience in diagnosing issues like these and I can tell you: a patch is at fault and it is something that the developers are responsible for and need to fix themselves.

Every possible software is up to date. I run a flawless up to date system. Always.

Edited by Marikc0, 01 October 2013 - 02:28 AM.

[Pyrometheus]

I keep getting 'Failed to find a match' when trying to drop solo.

[Phero77]

Same problem.. Click play and i get an error. I got i7 4770k with Nvidia 780.

[Tanreh]

Same here.....

patched.....
got 4 crashes in a row...
now i only get

Failed to find match error
the message takes between 2 and 30 seconds to appear...;(

[Mech of War]

Since today's patch (October 1st) the Game is working fine with AMD CPU/APU (A10-5800K) and AVAST! Antivirus! No more dancing with a tambourine and AVAST!'s settings (hardware-assisted vitualization)! BTW, the new map is really HUGE...

Edited by Mech of War, 01 October 2013 - 07:47 PM.

[Rose Scented Love Puff]

SantaDiego, on 30 July 2013 - 12:40 PM, said:

Can't play too, but i did not catch appcrash. Just pushing blue "play" button, then she's turn into grey "please wait" button and... Thats all. That starts right after today's patch.

Reinstalling client (2 times), restarting router, using MWORepairTool (4 times) and tambourine didnt helps.

Refer to the Support Workarounds Thread, AMD and Avast topic. If you're running those two, you may find your solution. If you're running Intel, ( like me ) then get used to a dry spell without MWO I've a support ticket lodged and hoping for something more positive soon.

[Rose Scented Love Puff]

Muriea MacRisa, on 30 July 2013 - 08:46 PM, said:

Let's try disconfirmation instead. If anyone has this problem but does NOT run an AMD processor would you please speak up?

I've got the exact problem. Running Intel and currently no antivirus till a solution is found. Occured straight after the first patch in September. Support ticket lodged.