Ir al contenido

Foto

Multiplayer: Collector's Wave 2 crash


  • Por favor identifícate para responder
44 respuestas en este tema

#1
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes
Hey there,

I was wondering if anyone else had this crash on any mission with Collectors. Wave 1 is fine but then Wave 2 starts and the game craps out.

Takers? At first I thought it was the fact that I was injecting Cinema Mod into it. But then I disabled it and then played again. Apparently not with Collectors since it worked fine. Had it off and a Collectors mission started. Wave 2 : CRASh. :blink: 

#2
Xeonzs

Xeonzs
  • Members
  • 211 mensajes
Hmm I haven't seen this happen to anyone yet.

#3
Athanis

Athanis
  • Members
  • 118 mensajes
Just had a crash on the re-modelled Firebase White versus Cerberus- Wave 6 or 7. Previously, only endured the Rio/Melee crash bug- otherwise, game doesn't crash. Odd sound effects since the DLC popped up though, muffled weapon or power noises and distortion.

#4
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes
I've already emailed EAs tech support last night - no reply yet but maybe a smart person can decipher this:

Source
Mass Effect™ 3

Summary
Stopped working

Date
‎10/‎9/‎2012 8:29 PM

Status
Not reported

Description
Faulting Application Path: C:\\Program Files (x86)\\Mass Effect 3\\Mass Effect 3\\Binaries\\Win32\\MassEffect3.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: MassEffect3.exe
Application Version: 1.4.5427.111
Application Timestamp: 504fa5f7
Fault Module Name: MassEffect3.exe
Fault Module Version: 1.4.5427.111
Fault Module Timestamp: 504fa5f7
Exception Code: c0000005
Exception Offset: 0090be25
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: d7df
Additional Information 2: d7df6762e2195a0183d3ea64a93fc6ac
Additional Information 3: d342
Additional Information 4: d3427e3da56225f01269bfd13c540d81


I think this crash is also associated with Geth even at the beginning since I haven't been able to play a match with Geth yet. And I wouldn't know since they are always random. 

Editado por MACharlie1, 10 octubre 2012 - 04:17 .


#5
Eixle

Eixle
  • Members
  • 30 mensajes
I've had the exact same problem with crashing on the second collector wave, MACharlie. So far, I've gone as far as rebooting, uninstalling and re-installing ME3, and no luck. I can't even start or join a match with collectors now, as soon as a wave begins it crashes.

I also have an odd "black floor" that I didn't have before the Retaliation DLC - extends in a perfect circle on some surfaces for a few meters, regardless of any environment variables.

EDIT: I've attempted to screencap the aforementioned phenomenon but the picture shows up as just a black, screen res size box :\\

Editado por Eixle, 10 octubre 2012 - 07:29 .


#6
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes
Reinstalled everything from scratch without any difference. : /

I'm going to rollback my Nvidia driver to 285 from last year. 

EDIT:

And unsupringsingly, no change. ****ing annoying. 

Editado por MACharlie1, 10 octubre 2012 - 09:35 .


#7
nanotm

nanotm
  • Members
  • 967 mensajes
something else got updated perhaps and it messed wiht the settings

did you try re-installing physx ?

Editado por nanotm, 11 octubre 2012 - 12:32 .


#8
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes

nanotm wrote...

something else got updated perhaps and it messed wiht the settings

did you try re-installing physx ?

Yes. Just attempted this and fail. 

#9
nanotm

nanotm
  • Members
  • 967 mensajes
what os are you useing ?

#10
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes

nanotm wrote...

what os are you useing ?

Windows 7 

#11
nanotm

nanotm
  • Members
  • 967 mensajes
ok its possible that something in your system is causing the problem, do you have acess to any test software?

specifically i'm thiking about ram cpu graphics card and hdd
the problem seems rather odd but its possible that its related to free space, the collectors take up quite a lot of resources and in wave 2 they go up a notch in terms of the graphics draw especially withe the swarms.

the other possibilitiy in terms of hardware faults would be the psu is under powered/performing and the new higherload graphics load is trying ot pull more power than it can offer (although thats less likely to only affect collector games in me3)

if i was you i'd start by running the memory test tool in windows, then if your gfx card has a test utility run that perhpas try the windows revovery console (press f8 a lot during the boot sequence)

#12
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes

nanotm wrote...

ok its possible that something in your system is causing the problem, do you have acess to any test software?

specifically i'm thiking about ram cpu graphics card and hdd
the problem seems rather odd but its possible that its related to free space, the collectors take up quite a lot of resources and in wave 2 they go up a notch in terms of the graphics draw especially withe the swarms.

the other possibilitiy in terms of hardware faults would be the psu is under powered/performing and the new higherload graphics load is trying ot pull more power than it can offer (although thats less likely to only affect collector games in me3)

if i was you i'd start by running the memory test tool in windows, then if your gfx card has a test utility run that perhpas try the windows revovery console (press f8 a lot during the boot sequence)

Well.....I did just run a stress test and realized that one of my graphic cards is missing. I have two cards set up via SLI...that might be contributing to the problem. I really hope that something is just loose and I don't have to replace one of them. :unsure:

EDIT: It appears that my motherboard might need to be replaced entirely. FUUUUUUUCCCCKkk.

Editado por MACharlie1, 11 octubre 2012 - 05:19 .


#13
nanotm

nanotm
  • Members
  • 967 mensajes
let me guess its between 3 and 6 years old and has two or three blue/brown caps near the southbridge heatsink that have poped (them being the voltage regulators for the pci buss) and although low intensity stuff is fine anything wich needs a bit of oomph is crashing

oh and its made by asus or foxconn

based on the fact those two comapnies bought up the majority of the dodgy capacitors in 06 and didnt stop using them in pc parts untill 2010.

#14
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes

nanotm wrote...

let me guess its between 3 and 6 years old and has two or three blue/brown caps near the southbridge heatsink that have poped (them being the voltage regulators for the pci buss) and although low intensity stuff is fine anything wich needs a bit of oomph is crashing

oh and its made by asus or foxconn

based on the fact those two comapnies bought up the majority of the dodgy capacitors in 06 and didnt stop using them in pc parts untill 2010.

Ah, nope. It's a Gigabyte and is about a year old. :?

The only issue is that one slot that refuses to work. I can't even remember it working in the first place. I always assumed it was. Thankfully, Gigabyte has that 3 year warranty on all boards. 

Editado por MACharlie1, 11 octubre 2012 - 11:39 .


#15
saltisgood

saltisgood
  • Members
  • 237 mensajes
Okay I'm getting the same issue. It crashes on wave 1 if you're playing silver or higher and wave 2 if you're playing on bronze. This leads me to believe that it's a particular enemy that's spawning on those waves that's causing the problems.

EDIT: And I was also getting those black floor issues Eixle is getting after the last patch but before Retaliation. So maybe the fault lies with the patch...

Editado por saltisgood, 12 octubre 2012 - 05:57 .


#16
nanotm

nanotm
  • Members
  • 967 mensajes
if the problem was with the patch then it would affect a lot more people,

unless its only happening ot users of a particular piece of hardware (and then it would need ot be happening to all of them)

@MACharlie1

well i'm glad ot hear its stull under warrrenty, i had an asus mobo go belly up last year for a pci problem and had to argue with the vendor about it being there fault due to supplying faulty ram modules with it before getting the whole lot replaced (it had been doing odd things for a while)


but then thats what you get if you buy bundles sometimes they shove in dodgy patriot dimms then lie about them, lucky me i still had the original packaging though so i was able ot win before taking them to court, even gave me extra store credit as well perfect in the run up to xmass last year since the kids all wanted new tech :)

#17
saltisgood

saltisgood
  • Members
  • 237 mensajes
Thank god. A clean install and then all the DLC copied across has fixed my problem. No idea what the problem was though.

#18
Eixle

Eixle
  • Members
  • 30 mensajes

saltisgood wrote...

Thank god. A clean install and then all the DLC copied across has fixed my problem. No idea what the problem was though.


I tried that, but it just auto-installed all the DLC's I have, which leaves me with the same problem. I've been back and forth with tech support on it, they're crunching a gamelog and a system diagnostic right now. :\\ Here's to hoping.

Anyone know a way to manually reinstall the DLC without wiping the core game install?

EDIT: Btw Salt, thanks for the batch file for running Texmod in ME3 (Not that I am right now, trying to get this problem sorted :s)

Editado por Eixle, 12 octubre 2012 - 09:16 .


#19
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes
Dammit. The solutions Gigabyte provided were not lucrative and now I probably have to wait until Monday to know if I should ship it back.-___-

#20
Eixle

Eixle
  • Members
  • 30 mensajes

MACharlie1 wrote...

Dammit. The solutions Gigabyte provided were not lucrative and now I probably have to wait until Monday to know if I should ship it back.-___-


Ouch. Hopefully they'll hotswap you a working one?

Seeing as multiplayer is pretty much borked I figured I would finish one of my Shepards - only to discover that as I approach them, any set of doors turn black (much like my black floor glitch). This also appears to be causing a some sort of feedback loop or memory leak, as the memory usage of ME3 continuously rises, and then the game crashes due to having no memory to access (or so it would appear). Which has never, ever happened to me before the Retaliation DLC.

Man, this bites.

#21
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes

Eixle wrote...

MACharlie1 wrote...

Dammit. The solutions Gigabyte provided were not lucrative and now I probably have to wait until Monday to know if I should ship it back.-___-


Ouch. Hopefully they'll hotswap you a working one?

Seeing as multiplayer is pretty much borked I figured I would finish one of my Shepards - only to discover that as I approach them, any set of doors turn black (much like my black floor glitch). This also appears to be causing a some sort of feedback loop or memory leak, as the memory usage of ME3 continuously rises, and then the game crashes due to having no memory to access (or so it would appear). Which has never, ever happened to me before the Retaliation DLC.

Man, this bites.

I just want them to fix it. I have a waterblock screwed into my motherboard and I really don't want to have to redo all that. As much as I love putting a computer together - it's not as fun if the pieces are sparkling new and I've never played with them.

I was getting the black textures before Retaliation. But that was mainly because I bumped up my textures in the coalesced and I guess it wasn't agreeing with each other. But yeah - I also had black textures in maps after Retaliation. Hopefully - this is simply the fact that my card isn't producing enough memory (about 600mb) and that other card not being there is taking it's toll. I don't have the money to upgrade cards. NOT AT ALL. 

(And as I wrote this, I get an email telling me that I have to disassemble everything and just send the motherboard...:()

Editado por MACharlie1, 13 octubre 2012 - 12:02 .


#22
Eixle

Eixle
  • Members
  • 30 mensajes
Double ouch. :(

Why were you bumping up the textures via coalesced? No Texmod or ME3explorer?

Your card not producing enough memory could make sense, but I have 3GB dedicated VRAM on my card, 8GB on the board, and I'm still getting black surfaces right from the get go (all my stuff is quite new, less than a year old). My best guess is that something regarding lighting around the position we're in got adjusted and didn't play nicely with something else down the line.

#23
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes

Eixle wrote...

Double ouch. :(

Why were you bumping up the textures via coalesced? No Texmod or ME3explorer?

Your card not producing enough memory could make sense, but I have 3GB dedicated VRAM on my card, 8GB on the board, and I'm still getting black surfaces right from the get go (all my stuff is quite new, less than a year old). My best guess is that something regarding lighting around the position we're in got adjusted and didn't play nicely with something else down the line.

Well, it was before ME3explorer had updated so you didn't need to edit the coalesced. When adding the bigger image, you had to update a field to 4096 in order for the game to produce the larger textures rather then the 1024. Unfortunately, for me, that wasn't working out since I was getting the black textures and had to undo it. And then I decided it was pointless to edit the textures since norm maps couldn't be updated yet - now I know how. 

If you're running 3GB on your card, then fixing my second card might not fix it since you're having the exact same problems. Unless something isn't running correctly with yours...maybe reset your graphic settings or reseat the card itself. What card are you using? I'm sure I'm not using the same since my cards will be 3 years old in January I believe? (Geforce 8800 GTS) But I'm also running with 16GB on the board. It might be a memory leak. 

I'm not sure but I discovered I also can't run games on Firebase Condor and possibly London. 

*sigh* Did driver verifications and the only thing it did was make me realize that my audio and mouse drivers were out of date. Not that it did anything to help. Turned off the Blackmagic drivers. Nothing. <_<

Editado por MACharlie1, 15 octubre 2012 - 02:42 .


#24
Eixle

Eixle
  • Members
  • 30 mensajes
Gotcha, gotcha. I just tried doing a clean install of ME3 and all the DLC and no joy. Still haven't heard back from EA either yet.

I messed with ME3explorer for a little bit but the majority of textures that I would run with Texmod haven't been found with it, so I'd stick with that. Except for the rise of the black surface bug, so now I don't use it at all.

My video card is a GeForce 670GT M on the latest driver set. When ME3 was working, it could eat it with fully loaded texture mods for breakfast, lunch, and dinner and still have room for dessert.

I can run both Condor and London, though not against the Collectors. Running on London actually worked somewhat better than any other maps - the black surface bug appeared to be more of a circular shadow on the ground instead of outright eliminating textures, which has convinced me further that something code-wise isn't playing nice.
Also, big fan of the work you and smarteck have done for ME3. Just FYI.:wizard:

EDIT: Discovered that right-clicking the "installed" label of DLC under game details provides options for updating/repairing DLC - and the option for Retaliation seems to be working, as it's redownloading. *Fingers crossed*:blink:


EDIT: So I checked all the muliplayer DLC, and both Retaliation and Rebellion were apparently borked somehow. Unfortunately, still crashing on the Collectors. Maybe you guys should give it a shot and see if it fixes yours.

Editado por Eixle, 15 octubre 2012 - 07:10 .


#25
MACharlie1

MACharlie1
  • Members
  • 3.437 mensajes
Nah - tried that the first day.

I really haven't put any real work into textures - my EDI is just a new specmap using JeanLuc's texture - therefore it's just a texture modification. And the hair piece is just smarteck.

I can't even claim the new norm maps since I just generated them via CrazyBump. XD

I did get ANOTHER reply from EA this morning asking for another dxdiag file. Terrible service really. I'll be shipping my motherboard for repair tomorrow so I'm just taking care of a few things and then taking her apart.