Forum Discussion
Description
Faulting Application Path: D:\Program Files (x86)\Origin Games\Mass Effect 2\Binaries\MassEffect2.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: MassEffect2.exe
Application Version: 1.2.1604.0
Application Timestamp: 50906ae5
Fault Module Name: MassEffect2.exe
Fault Module Version: 1.2.1604.0
Fault Module Timestamp: 50906ae5
Exception Code: c0000005
Exception Offset: 000132ed
OS Version: 10.0.22631.2.0.0.768.101
Locale ID: 1033
Additional Information 1: cf3c
Additional Information 2: cf3cdae334d54dde465a9fc321e38ef0
Additional Information 3: d10a
Additional Information 4: d10a4540410258e73f34f2ebd69f29c4
Extra information about the problem
Bucket ID: a90e4b3ba963f3ed6e052b8555b9950e (-1023992515)
- EA_Shepard8 months ago
Community Manager
- 8 months ago
THERE YOU ARE. sorry about caps.
- EA_Shepard8 months ago
Community Manager
Thanks. Below is the info from your DxDiag and the steps to take to resolve these.
I did notice that the GPU is an Intel chipset and not a physical GPU. Unfortunately, these start to wear down over time, and since it is a chipset, there's little you can do with this one.EDIT: My bad, I saw a physical one in there. Just run the GPU updater on this one and make sure there are no updates. I would still update the Intel one anyway if there is one available.
1. APPCRASH with
MassEffect2.exe
:
- The exception codesc0000005
andc00001a5
indicate access violations, which are typically caused by invalid memory access.The exception code c0000005 is an Access Violation error in Windows. This is one of the most common and critical errors in the Windows operating system. It indicates that a program has attempted to access a memory location it is not authorized to access. This could be due to several reasons, such as trying to read from or write to a protected memory area.
- Possible Fixes:
- Ensure you are not running the application in debug mode if not required.
- Check for any known issues with the specific version ofMassEffect2.exe
you are running.2. Unhandled Exceptions:
- These indicate crashes that cause the tool to shut down unexpectedly. Ensure the telemetry data is monitored to identify and address the top crashes.
- Possible Fixes:
- Use telemetry to identify the root causes of these crashes and monitor session crash rates and average time to crash. - You can Google videos on YouTube about this one.3. RADAR_PRE_LEAK_64 Events:
- These events are indicative of potential memory leaks.
- Possible Fixes:
- Use diagnostic tools to identify and fix memory leaks.Steps to take next
- Run the System File Checker tool
- Check for Windows Updates
- Check for GPU updates
- Windows troubleshooting tools
- Guide for Troubleshooting Graphics issues
- Install/Repair your VC++ files for the game (Microsoft VC++ Link)
About Mass Effect Franchise Discussion
Recent Discussions
- 16 hours ago
- 18 hours ago
- 19 hours ago
- 2 days ago