Jump to content

Amd, Windows 10 Rtm, Crash To Desktop


9 replies to this topic

#1 RonanFrost

    Member

  • PipPip
  • Bad Company
  • Bad Company
  • 34 posts

Posted 29 July 2015 - 10:25 PM

Not sure what Microsoft is doing, but my client crashes like a drunk celebrity in an Italian sportscar.
... well and fully, and before getting out of the parking garage.

In a more serious description, starting off, I load the client and can play the game, but only solo queue, or training grounds. Should I attempt to run with a group, it will make it into the loading screen for the map, then CTD.

I can attempt to reconnect, and occasionally get into the client, "rejoin" match, and it will make it to the same spot before CTD.

After this occurs, I load the client, and it will make it through the login, gameplay tip screen, and CTD amid the loading of the mech bay.

On a hunch from another thread I had my unit-mate check, and I was still showing online. Had him PM me to make the server check to see if I was online, it refreshed to show me offline, and I was able to log back in passed the mechbay loading screen. This workaround works consistently, and can be necessary hours later.

Again, at this point I'm back to either dropping in solo queue, or crashing, and repeating the process. I'm at a loss. It seems like it's something between authentication and possibly just the group-queue servers, but the Crashrpt and Omicron contents suggest something related to graphics.

Things I've tried -
- Fresh install
- Repair tool (which comes up with nothing to repair)
- Compatibility Modes for Win7 and Win8
- It is running in Administrator Mode
- UAC is off, and login has Administrator
- Malware / Virus protection is off
- Have gone into Windows Defender, and added exclusions for all executables in the MWO folders
- Have tried turning Windows Defender off entirely
- Drivers:
Catalyst Control Center 15.6, 15.7, 15.7.1
Driver package 15.20.1062.1002-150715a-187327c (and whatever came with CCC 15.6 and 15.7)

For those so inclined/adept, here's the section of the crashrpt.xml:
Spoiler

... and the error-laden portion of the Omicron, cut down with a sub-spoiler so it doesn't fill the entire screen:
Spoiler


#2 Imperius

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • The God
  • The God
  • 5,747 posts
  • LocationOn Reddit and Twitter

Posted 30 July 2015 - 03:42 AM

Did you update your AMD chipset drivers?

#3 Chafe

    Member

  • PipPip
  • Colonel II
  • Colonel II
  • 32 posts

Posted 30 July 2015 - 06:19 AM

Massive error spam in the log concerning flash. Do you have the most recent flash player installed?

#4 nehebkau

    Member

  • PipPipPipPipPipPipPipPipPip
  • 3,386 posts
  • LocationIn a water-rights dispute with a Beaver

Posted 30 July 2015 - 07:28 AM

reinstall DirectX runtime installers and the 64-bit Visual C Runtime and make sure your .NET is up to date

#5 Win Ott

    Member

  • PipPipPipPipPip
  • The Serpent
  • The Serpent
  • 153 posts
  • LocationSomewhere in the Southern Reach

Posted 30 July 2015 - 01:25 PM

Yeah, I'm crashing to desktop too. I upgraded to Win 10 and new AMD drivers. It seems to be the graphic card drivers that are causing all the crashes

#6 Erasus Magnus

    Member

  • PipPipPipPipPipPip
  • Veteran Founder
  • Veteran Founder
  • 383 posts
  • LocationUnited States Of Mind

Posted 30 July 2015 - 03:48 PM

Same here, though i haven`t upgraded to Win 10 yet (still waiting for the message).
Came back to MWO after a good year to check out if the game has become somewhat decent now (ran like arse back then). Bummer , as soon as I try to change to fullscreen or windowed fullscreen, the game crahses and I have to use the repair tool to even get the game to run again.

For me it is DEFINITELY the change from windowed to fullscreen or full window that breaks the game for me.

15.7 catalyst, 15.20.1046-150622a-186188C driver package.
Still on Win 7. All other games run perfectly fine, including Crysis 3, which has the same engine, right?
Driver/Catalyst uninstalled/reinstalled several times.

System: Thuban 1055T@ 3,5ghz, 8gb RAM@1666 CL8, Gigabyte 7870 OCed to 1250mhz core and 1550mhz VRAM
System and game running off a Samsung 840Evo 400GB with newest firmware.
Tried without overclocks, didn`t change a thing.

Sent bug report, hope that it gets fixed soon.

Cheers

Edited by Erasus Magnus, 30 July 2015 - 03:50 PM.


#7 Dragoon20005

    Member

  • PipPipPipPipPipPipPip
  • 512 posts
  • Facebook: Link
  • LocationSingapore

Posted 30 July 2015 - 04:44 PM

View PostErasus Magnus, on 30 July 2015 - 03:48 PM, said:

Same here, though i haven`t upgraded to Win 10 yet (still waiting for the message). Came back to MWO after a good year to check out if the game has become somewhat decent now (ran like arse back then). Bummer , as soon as I try to change to fullscreen or windowed fullscreen, the game crahses and I have to use the repair tool to even get the game to run again. For me it is DEFINITELY the change from windowed to fullscreen or full window that breaks the game for me. 15.7 catalyst, 15.20.1046-150622a-186188C driver package. Still on Win 7. All other games run perfectly fine, including Crysis 3, which has the same engine, right? Driver/Catalyst uninstalled/reinstalled several times. System: Thuban 1055T@ 3,5ghz, 8gb RAM@1666 CL8, Gigabyte 7870 OCed to 1250mhz core and 1550mhz VRAM System and game running off a Samsung 840Evo 400GB with newest firmware. Tried without overclocks, didn`t change a thing. Sent bug report, hope that it gets fixed soon. Cheers



I would suggest reinstalling your game completely

yes it a pain to download all over again

but that what i did and i am running all good here

#8 Erasus Magnus

    Member

  • PipPipPipPipPipPip
  • Veteran Founder
  • Veteran Founder
  • 383 posts
  • LocationUnited States Of Mind

Posted 30 July 2015 - 07:56 PM

uninstalled it, let ccleaner run over it, did a restart, followed up by another ccleaner , then reinstalled it. same result.
did it, just for good measure, a third time, still the same. as soon as i try to apply full screen or full windowed mode, the game instacrashes.

#9 RonanFrost

    Member

  • PipPip
  • Bad Company
  • Bad Company
  • 34 posts

Posted 01 August 2015 - 12:47 PM

Spoiler

Flash was current, chipset drivers were current, DirectX was up to date.
Reinstalled .net and VisC runtimes, NIC drivers, still no notable change.
AMD released a new driver for Windows 10, so with that and turning off all virus/malware/firewall protections I was able to get it to load in with a group without crashing, but the play was terrible ... as in teleporting half way across the map, unplayable, terrible. Loading into a match made TS3 disconnect repeatedly, and coms would be delayed by upwards of 10-15seconds. I had a match where people watched me, both post-mortem and from their own mechs, shooting and hitting enemy targets the entire match; net result 1 damage. Setting the process to "realtime" helped marginally, and I went a step further to removing all extra desktops and processes before launching the game.
After tracking down the old User.cfg thread, I was able to get the game to function somewhat normally, but It's still painful, and seems like my hit reg is horrendous. (I'm bad, but I'm not This bad.) Damage reporting on my end is occasionally failing to get the indicators, though I watch the paperdoll update. TS3 no longer disconnects on load in, but it's still suffering occasional delays.

It really feels like network issues at this point (despite our 30down/6up cable), but it's hard to say, as the whole machine feels somewhat sluggish.

#10 Ano

    Member

  • PipPipPipPipPipPipPip
  • Bridesmaid
  • Bridesmaid
  • 637 posts
  • LocationLondon

Posted 09 August 2015 - 03:55 PM

Obviously there could be a whole bunch of reasons why things aren't working for you, but I'd be pointed at the Windows 10 install to start with.

My guess is that PGI haven't really done any testing with Win10 yet, and as a brand-new version of the OS there's BOUND to be more than a couple of tricksy little bugs in there and the odd issue with drivers. Do you *need* to be on Win10? Can you easily revert back to whatever stable OS you had before?

I know that's not necessarily the most helpful thing to say, but for myself I decided to wait a few months to give Microsoft and friends a chance to fix the initial problems (and developers like PGI a chance to update and test their apps).





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users