Mass Effect 2 - Failure to Launch

Darkfire575​ 

Please add a DxDiag to your next reply.

A DxDiag is an overview of your PCs technical features and recent software errors.
There is no personal info in it expect for the “Machine name” in the second row.
(You might delete the “Machine name” and “Machine Id” line if you wish too.)

How to create a DxDiag:

1. Press the Windows key and "R" at the same time.
2. Copy and past or type "DxDiag" in the new field. (Without the quotes) > ENTER
3. Wait until the green bar is gone > Click on "Save all information"
4. Save the file to your desktop.
5. Here at EA Forum > Click Replay > Click the paper clip icon at the bottom of the replay Window.
6. Navigate to the "DxDiag.txt" on your desktop > select the "DxDiag.txt" > click on "Open".
7. Type you massage > Reply.

Here is my DxDiag??

Darkfire575​ 

Please update your NVIDIA graphics driver. 
Then restart your laptops and test. 
 

If that don't helps:
Unfortunately, the DxDiag cannot access the WER (Windows Error Reporting) data.

Please look at the Reliability Monitor:  
1. Press the Windows key and "R" at the same time.  
2. Copy and paste "perfmon /rel" (without the quotes) in the new Window > hit “ENTER”  
3. Look if it has entries for the game or EA app.  > If yes double click at the last entry for the game executable or EA app, copy the info and save it to a text file.  
  
Then upload the file as you did with the DxDiag. 

holger1405​ 

I updated the driver with no success and I don't have the option to download so here is the copied info:

Description
Faulting application name: MassEffect2.exe, version: 1.2.1604.0, time stamp: 0x50906ae5
Faulting module name: MassEffect2.exe, version: 1.2.1604.0, time stamp: 0x50906ae5
Exception code: 0xc00001a5
Fault offset: 0x00013f39
Faulting process id: 0x1B48
Faulting application start time: 0x1DC448741C8B704
Faulting application path: D:\Mass Effect 2\Binaries\MassEffect2.exe
Faulting module path: D:\Mass Effect 2\Binaries\MassEffect2.exe
Report Id: 74948fc7-8298-445f-b628-94acb895e838
Faulting package full name: 
Faulting package-relative application ID: 

Darkfire575​ 

This exception code, as well as the missing WER information in the DxDiag, indicates an invalid exception handler routine or issues with system-level operations, such as corrupted system files.

1. Hit Windows key and X.
2. Choose either “PowerShell (Administrator)” or “Command prompt (Administrator),” or "Windows Terminal (Administrator)", whichever option is offered.
3. Inside PowerShell, CMD or Terminal enter (copy and paste) “DISM.exe /Online /Cleanup-image /Checkhealth” without quotes. > ENTER.
4. If errors are found, notify us. If no errors were found repeat steps 1 & 2.
5. Inside PowerShell, CMD or Terminal enter “DISM.exe /Online /Cleanup-image /Restorehealth” without quotes. > ENTER.
6. The system will start validating soon. If it throws an error, please list it here.
7. After it reaches 100% repeat steps 1 & 2.
8. Inside PowerShell, CMD or Terminal enter “sfc /scannow” without quotes > ENTER
9.  Post the message you receive at the end of the processes here.

holger1405​ 

So sorry for the wait on this the last message I receive is:

"Windows resource protection could not start the repair service"

after multiple attempts.

Darkfire575​ 

This means there are limited options left, one is the compleat fresh installation of the operating system.

If a fresh installation is a problem for you I would recommend a Windows repair installation, also called a "in-place upgrade", that will allow you to keep your data and your applications. 
However, it cannot be guaranteed that it will solve all OS problems. 

You will find a Microsoft video guide about it here.

Here is the Website to create the Install medium. 

 This is normally a very safe process, but you should make a full backup of all your important data anyway. (And not just before such on operation.) 😉

Make sure that "Keep Personal files and Apps" is marked before you click "install".  
  
If you are unsure about a step, feel free to ask for help! 😉

I got it to work! I manually deleted all of the files and reinstalled. Thank you so much for your patience with me! Not sure how it worked but it did!