Re: ME1 (Legendary Edition) PC crashes

@GerardKooij  It's worth disabling the optimizations within the Radeon control software, just to see whether it makes a difference.  If you've overclocked your CPU or RAM, please undo that too, at least long enough to test.

@puzzleaddict  I fully agree. The point is there are umpty options in Radeon settings, I must admit I am lost a bit. So far I have disabled  'sports'  settings back to 'normal' as a general. which also disables Radeon Boost. I wonder however if I should not focus on VSYNC like- Freesync related frequency capping options......Maybe I have time tomorrow to try some settings.

Note that with the same settings and hardware- I have fully played through the non-legendary versions of ME,ME2 and ME3 without any major problem ;-) There is something in ME Legendary Edtion that keeps pushing for framerates, and my 43 inch monitor can only handle 60hz with 3840*2160.

Thanks for your reacttons, will in the next few days try to figure out if  any of the Radeon settings is relevant. 

Any takers on this one ? 

+++ WER2 +++:
Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: MassEffect1.exe
P2: 2.0.0.47902
P3: 6089185a
P4: StackHash_ac46
P5: 0.0.0.0
P6: 00000000
P7: PCH_AF_FROM_ntdll+0x000000000009D974
P8: c0000005
P9: 0000000000000008
P10:

@spootie17  Are you using some sort of screenshot software while playing?  If so, try disabling it while you play.

If that doesn't help, and you play through Origin, try clearing Origin's cache:

https://help.ea.com/en/help/faq/clear-cache-to-fix-problems-with-your-games/

and repairing the game: open your Origin game library, right-click on the MELE icon, and select Repair.

If you play through Steam, click on the MELE in your game library, click the gear icon, select Manage > Properties > Local Files, and click the button to verify the integrity of local files.

ABBYY it is now off, but still crashes. did both repair, plus clear origin cache. 

Play through Origin

It always happens in the fight, and usually when an enemy gets close. Tantau one of the pirates, Noveria in Qins office, Feros when the geth shoot at the very start. 

Thanks for the help. Really so bloody annoying. I had been looking forward to this game and submitted my thesis in time to be able to play it.

@spootie17  Try enabling vertical sync within the game's graphics settings.  It's also worth turning down the in-game resolution (temporarily) just to see whether it makes any difference.

Your new dxdiag does list one error with Radeon software, so although there's no other evidence of an issue with your graphics driver, it might help to clean uninstall and reinstall the driver.  Download Display Driver Uninstaller from here:

https://www.wagnardsoft.com/forums/viewtopic.php?f=5&t=3480

Download the newest recommended (WHQL) driver from AMD, not the newer optional driver.

https://www.amd.com/en/support/graphics/radeon-400-series/radeon-rx-400-series/radeon-rx-470

Next, take your computer completely offline—disable wifi and/or pull the ethernet cord—and double-click the DDU.exe.  Take note of where the file will land, and click Extract.  If it's easier, you can copy the path and then paste it into the address bar in a File Explorer window.  Open the folder and then launch Display Driver Uninstaller.exe, and you'll get a message that you're not in Safe Mode.  Click OK, then go to Options and enable Safe Mode dialog.  Here's a screenshot of what your options should look like; make sure the box in red is checked:

Close options, and the DDU, and then open the DDU.exe again.  For launch options, choose "Safe Mode (Recommended)," and then click Reboot to Safe Mode (you'll need your password, so find it before rebooting).  Once you login, you'll see this:

In the blue box, choose GPU, then AMD if it's not already showing.  Then click Clean and Restart (red box).

Once your computer has rebooted, now back in normal mode, run the driver install .exe as an admin: right-click on the download and select "Run as administrator."  Restart again when you're done, and go back online.

Followed all the steps on reinstalling the driver, still same mistake at the same point. 

And it usually happens when one of the enemy combatants gets close, and I could start engaging Melee.

+++ WER0 +++:
Fault bucket 1318009176226100293, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: MassEffect1.exe
P2: 2.0.0.47902
P3: 6089185a
P4: StackHash_ac46
P5: 0.0.0.0
P6: 00000000
P7: PCH_92_FROM_ntdll+0x000000000009D974
P8: c0000005
P9: 0000000000000008
P10:

@spootie17  Did enabling vertical sync not make any difference?  It does help with some types of crashes, although nowhere near all of them.

Is there any pattern to what kind of enemy causes the crashes, as in, do the enemies have abilities/weapons/race/etc. in common?

Nope, tried it off and on.

In Tantau there are no biotics, it is all Turians and Pirates, and it happens when they are getting close. 

Really weird.

Part of me is wondering whether there is any point in just waiting a month and letting Bioware have a look at it. Submitted the error report too. 

I am not sure whether the Forum or normal people should be doing bug hunting on this level for them.

@spootie17  If you'd like to wait for a patch, that's understandable.  I don't know what the issue is here, so I can't even begin to guess whether it'll be fixed, although I'd hope so.

One thing you might try, if you can find one, is downloading a different save from around the same point as your crashes started.  That way, you can see whether it's the game or your save, and you don't have to start from the beginning.

As for whether players should be doing bug-hunting, that's a matter of debate.  Given that the devs' time is limited (it always is), I'd personally rather they get as much information as possible from players so they can focus on fixing bugs rather than spending part of their resources finding those bugs in the first place.  But that certainly doesn't mean anyone has an obligation to be part of that process.

@puzzlezaddictWell, he's not alone, i have tested any of these Points multiple times, but i just cannot play the game. My game crashes when a shotgun is fired, when any tech or biotic skill hits an enemy (when the sprite/animation should start). out of combat i can use the abilitys, i can see floating beacons, as soon, as an enemy run in those odr gets hit, crash. My dxdiag can be found on the first page.

edit:

this happend after the patch, before i could play just fine

I also had about 6 hours of reasonably clean gaming before the first patch. 

After some ten hours of relentless testing experienced and found the following:

1- enabled the Radeon overlay to display frame rates realtime, and found the game stalled when framerates were down to 40ties iso higher than 60

2- had tried a totally cleaned up game options session and and tried umpty vsync related settings in Radeon settings, the game kept stalling 95% of the times in last scene very intense battle situations

3- had totally disabled Sophos malware suppression, still the same

4- by accident stumbled along a display driver on hardware level admmddmg that was not functioning, with a malfunction code at startup of the drivers which kept repeating. service amdmddmg not starting status 0xC00000E5

5- googled this and found I must repair my system files (sfc /scannow see ps below )which I did, then deinstalled the Radeon software and fresh installed the tested 21.4.1 version to be on the safe side

6- rebooted and now was able to adjust screen resolution at system level contrary to before, from 3840*2160 to 3200*1800. Before due to the broken driver system software, this was impossible. Now tested three times and ran through the whole scene of Therum Ruins smoothly, also with all in game options enabled again (VSYNC, antialiasing, ambient occlusion, etc, and offensive use of powers by whole team, ) and the Radeon Settings on Esports (very optimised). 

7- so , in the past found many settings that seemed to influence the game experience, but flawed reasoning since the outcome of a run at the scene was 95% crashed and no repeatable results. This resulted from a overwhelmed graphics card with 8192mb of main memory, this refuses to run at 3840*2160 with many screen objects: had had the same trouble in old style ME1, then adjusted the screen resolution just like that because my drivers were ok then.

8- only when decreasing resolution in system and in-game, the RX 5700XT pulls the weight again and you can play the game with any settings, save one, Sophos option on Sandboxing that must be checked or else the whole LE won't start. Pffffff, happy now, thanks for all support

PS the part to repair the system files is as follows

The message “the application was unable to start correctly” could appear due to the installation of incompatible drivers, resulting in the failure of system files. To find out and immediately correct the situation automatically, scan your computer with SFC. To do this, open the Run window (Windows + R) and enter “cmd”; press Shift + Ctrl + Enter to grant administrator rights. Enter the following command in the command line and press Enter to execute it: sfc /scannow

After scanning the system files, the utility will automatically replace them with working ones and fix your problem.

settings and screen saves

@alexsavat  Have you seen any LiveKernelEvent 141 errors from after you clean uninstalled and reinstalled the graphics driver?  Those typically only happen when there's a system or hardware issue; a game crash shouldn't cause one.  You can check the Reliability Monitor (Windows key-R, enter perfmon /rel) for any new errors.

If you find any from after the GPU driver reinstall, please post them in a reply here.  You should be able to c/p the info.

nope, never had any of those

only Applicationerror of MassEffect1.exe

@alexsavat  Could you please post the entire error?  Right-click on the entry and select "View technical details," then copy and paste the info you see.

Please also look for an MELE crash dump.  Click Windows key-R and copy and paste this:

%LocalAppData%\CrashDumps

When you enter, you'll see a list of .dmp files.  If one of them is from the MELE, please upload it to a third-party filehosting site (Google Drive, Dropbox, etc.) and link it here.

Here's the Error:

@EA_David @EA_Mako 

Just to alert you on this thread - puzzle addict has been really busy in trying to help people here, but the current conclusion is that the errors are (likely) caused within the last patch, so at least I am now waiting for a new patch to resolve them back. 

Essentially in certain situation, mostly when a shotgun or a power is used in close combat, the game freezes (ME1) and then shuts out completely. As this happens both on Feros at the start and Noveria, the game ME1 is currently unplayable for me and several others. 

+++ WER2 +++:
Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: MassEffect1.exe
P2: 2.0.0.47902
P3: 6089185a
P4: StackHash_ac46
P5: 0.0.0.0
P6: 00000000
P7: PCH_AF_FROM_ntdll+0x000000000009D974
P8: c0000005
P9: 0000000000000008
P10:

Here is the .dmp from the last crash on Noveria (battle in the office with four AI) - crash was repeatable and regardless of resolution or other graphics settings.

https://www.dropbox.com/s/fn796gargmco8yy/MassEffect1.exe.3300.dmp?dl=1

The gist of it from WinDBG is as follows:

*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** WARNING: Unable to verify timestamp for nvwgf2umx.dll
*** WARNING: Unable to verify checksum for PhysXCore64.dll

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Execute

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on CONCORDE

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 104

Key : Analysis.Memory.CommitPeak.Mb
Value: 146

Key : Analysis.System
Value: CreateObject

Key : Timeline.Process.Start.DeltaSec
Value: 229

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000000000dfcf70 rcx=00000000f342df60
rdx=0000000000dfcf70 rsi=0000000000dfccf0 rdi=0000000000dfcd20
rip=0000000000000000 rsp=0000000000dfc7b8 rbp=0000000000dfc7e0
r8=0000000000dfccf0 r9=0000000000dfcf70 r10=0000000000dfcce8
r11=0000000000dfcce8 r12=0000000000dfce50 r13=000000001786bc10
r14=0000000000dfcf70 r15=00000000f342df60
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
00000000`00000000 ?? ???
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000

PROCESS_NAME: MassEffect1.exe

EXECUTE_ADDRESS: 0

FAILED_INSTRUCTION_ADDRESS:
+0
00000000`00000000 ?? ???

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000008

EXCEPTION_PARAMETER2: 0000000000000000

STACK_TEXT:
00000000`00dfc7b8 00000001`4012ab01 : 00000000`00000000 00000001`4012ae89 00000000`1760b060 00000000`418fd708 : 0x0
00000000`00dfc7c0 00000001`401176a7 : 00000000`00dfcf70 00000000`550fde90 00000000`00dfd460 00000001`41822c70 : MassEffect1+0x12ab01
00000000`00dfccb0 00000001`40117890 : 00000000`00dfcf70 00000000`4324ebd9 00000000`00000000 00000001`41822c70 : MassEffect1+0x1176a7
00000000`00dfcce0 00000001`40124a54 : 00000000`00dfcf70 00000000`00000001 00000000`00000000 00000000`00000000 : MassEffect1+0x117890
00000000`00dfcd10 00000001`4012ddc0 : 00000000`00dfcf70 00000000`00000000 00000000`f342df60 00000000`00000000 : MassEffect1+0x124a54
00000000`00dfcd40 00000001`4012ae30 : 00000000`17b35f80 00000000`64cbe2a0 00000000`00dfceb0 00000001`4012ac23 : MassEffect1+0x12ddc0
00000000`00dfcdf0 00000001`4012ddc0 : 00000000`00dfd590 00000000`00000000 00000000`00dfdad0 00000000`00000000 : MassEffect1+0x12ae30
00000000`00dfd430 00000001`4012ae30 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : MassEffect1+0x12ddc0
00000000`00dfd4e0 00000001`401252bc : 00000001`41822c70 00000000`00dfdad0 00000000`00dfe0f0 00000001`40124a54 : MassEffect1+0x12ae30
00000000`00dfda50 00000001`4012ddc0 : 00000000`00dfdc00 00000000`f342df60 00000000`00dfe0f0 00000000`00000000 : MassEffect1+0x1252bc
00000000`00dfdaa0 00000001`4012ae30 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : MassEffect1+0x12ddc0
00000000`00dfdb50 00000001`4012ddc0 : 00000000`00dfe210 00000001`00000000 00000000`00dfe190 00000000`00000000 : MassEffect1+0x12ae30
00000000`00dfe0c0 00000001`4012dbdb : 00000000`4341bd83 00000000`00000000 00000000`40000000 00000000`00000000 : MassEffect1+0x12ddc0
00000000`00dfe170 00000001`402ba729 : 00000001`1ecd5d80 00000000`00dfe3b0 00000000`00000000 00000000`00000000 : MassEffect1+0x12dbdb
00000000`00dfe2a0 00000001`40c5ee70 : 00000001`402ba6d0 00000000`00dfe3d0 00000001`1ecd5d80 00000000`00000000 : MassEffect1+0x2ba729
00000000`00dfe2d0 00000001`40c58509 : 00000000`176dc750 00000000`da619770 00000000`00000000 00000000`5d29a630 : MassEffect1+0xc5ee70
00000000`00dfe520 00000001`40c61a17 : 00000000`000e52db 00000000`00000000 00000001`402ba6d0 00000000`5f7910e0 : MassEffect1+0xc58509
00000000`00dfe630 00000001`40c610f8 : 00000000`0006975c 00000000`176dc750 00000000`00000002 00000000`00000001 : MassEffect1+0xc61a17
00000000`00dfe6d0 00000001`4040f60d : 00000000`5b9de680 00000000`176dc750 00000000`00000000 00000000`00000001 : MassEffect1+0xc610f8
00000000`00dfe780 00000001`4041cced : 00000000`18f08120 00000000`e2043043 00000000`00000002 00000001`418c7b90 : MassEffect1+0x40f60d
00000000`00dfe890 00000001`403cbc0d : 00000001`41ce1528 00000000`00dfea90 00000000`3c8874ae 00000001`41ce1528 : MassEffect1+0x41cced
00000000`00dfe990 00000001`409bbc07 : 00000002`70ad6072 00000002`70ad6072 00000001`41ce1528 00000000`00000000 : MassEffect1+0x3cbc0d
00000000`00dfecb0 00000001`409b8720 : 00000000`0fe36cc0 00000002`70ad5e83 00000002`70ab7a26 00000000`00000000 : MassEffect1+0x9bbc07
00000000`00dfed50 00000000`0fe36cc0 : 00000002`70ad5e83 00000002`70ab7a26 00000000`00000000 00000000`00000000 : MassEffect1+0x9b8720
00000000`00dfed58 00000002`70ad5e83 : 00000002`70ab7a26 00000000`00000000 00000000`00000000 00000002`70ad6063 : 0xfe36cc0
00000000`00dfed60 00000002`70ab7a26 : 00000000`00000000 00000000`00000000 00000002`70ad6063 ffffffff`fffffffe : 0x00000002`70ad5e83
00000000`00dfed68 00000000`00000000 : 00000000`00000000 00000002`70ad6063 ffffffff`fffffffe 00000000`00000000 : 0x00000002`70ab7a26

SYMBOL_NAME: masseffect1+12ab01

MODULE_NAME: MassEffect1

IMAGE_NAME: MassEffect1.exe

STACK_COMMAND: ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_c0000005_MassEffect1.exe!Unknown

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5c018013-d4a7-42bd-9c54-a285db08c61c}

Followup: MachineOwner

Had constant ME1 crashes when trying to play though Therum.
Enabling V-SYNC seemed to solve the problem. The reason V-SYNC was disabled was that before the most recent patch FPS wouldn't go above 60 without disabling it. Perhaps this is due to rare config of 4K 144Hz monitor.

After the patch with V-sync enabled I could get ~144hz and 4k and no crashes.