Re: Mass effect games are making my computer restart

I don't get a BSOD, the game seems to want to start. The small launcher window sometimes appears and the icon shows in the task bar, but then the computer restarts. I ran the reliability monitor and the games don't show anywhere in there, it just says that windows shutdown unexpectedly. I have attached one of the instances below.

@Buzzkill83 

There are so many Bluescreen errors in your DxDiag that I assume that you indeed get them in the moment you start the games, but just can see it.

Or have you had Bluescreens on a constant basis lately for other reasons?

I need a dump file from this bluescreens:

Look under "C:\Windows\Minidumps"

Copy the last two (Date) "*.dmp" files to the Desktop > Zip them and load them up to a free file hosting website. (OneDrive, Dropbox for example) and post the link here.

If you can't find "C:\Windows\Minidumps" look under ""C:\Windows" for a "MEMORY.DMP" file.

If there aren't any dump files:

• Press the Windows key > Write: Command Prompt > Right click on "Command Prompt" in the search results > Run as administrator.
• Copy and paste "reg add "HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\devenv.exe" /v DumpType /d 2 /t REG_DWORD" (Without the quotation marks at beginning and end of the line, The quotation marks before HKLM and after devenv.exe need to stay in) into the command prompt Window > Press ENTER.
• Play the game until it crashes.
• After the game crashes, let all Windows crash dialogues finish.
• Press the Windows key and "R" at the same time. > Type "%LOCALAPPDATA%\CrashDumps" (Without the quotation marks) into the new window > Press ENTER.
• Upload the Tdmp files as described above.
  
  If you want to undo the automatic dump creation, use the command below in a elevated command prompt (As in point 1) reg delete "HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps" /f

The games are the only things that i have had a problem with, sometimes Destiny 2 won't start but the computer doesn't shutdown, but that is rare. I have had no other BSOD.

https://www.dropbox.com/s/3a8hvo83cmy8l7o/dmp%20Files.zip?dl=0

@Buzzkill83 

👍

I will return home tomorrow evening. Then I will have a look at your dump files.

@Buzzkill83 

Sorry for the delay in response. 

The culprit for the blue screens in the DxDiag sesame to be "cldflt.sys", that is the "Cloud Files Mini Filter Driver" so it is related to OneDrive.  

To find out if it is responsible for the Game crashes:

• Open the OneDrive App > more > Settings > Settings.
• Uncheck "Start OneDrive automatically when I sign in to windows" > OK.
• Reboot your Computer > Test. 

Doing the same thing, should i try uninstalling Onedrive?

@Buzzkill83 

So you don't use it at all?

If so, you can try.

Here is a MS help article how you can uninstall onedrive. (If you didn't know already.)

But as said, the BSOD have no direct connection to the game crashes in the DxDiag, so it might be unrelated.

That didn't work either

@Buzzkill83 

Are there newer dump files in the "C:\windows\Minidump" folder that have the same date as the recent crashes?

• Hit Windows key and X.
• Choose either “PowerShell (Administrator)” or “Command prompt (Administrator),” whichever option is offered.
• Inside the PowerShell or CMD, enter “DISM.exe /Online /Cleanup-image /Restorehealth” without quotes. > ENTER.
• The system will start validating soon. If it throws an error, please list it here.
• After it reaches 100%, hit Windows key and X again.
• Again, choose “PowerShell (Administrator)” or “Command prompt (Administrator)”
• Inside the PowerShell or CMD, enter “sfc /scannow” without quotes. >ENTER.
• Post the message you receive at the end of the processes here.

I would like to know what is going on in your system on the hardware side. 

• Download hwinfo64 (The green button) > Install and execute the program > Sensors only. 
  
• Click on the sheet with the green cross (logging) > give the file a name and save it to a place of your choice. 
• Wait 5 Minutes > Start a game > wait until it crashes > Stop the hwinfo logging (the sheet again)
• Rename the Log to > ">your name for the file<.CSV.txt"
• Upload the Log file here as you did with the DxDiag.

Performance log Link:

https://www.dropbox.com/s/5udq0fy0wgipwkg/performance%20log.CSV?dl=0

I didn't receive errors when running the /restorehealth scan.

I received this message when running the sfc scan:

Windows Resource Protection found corrupt files and successfully repaired them.

For online repairs, details are included in the CBS log file located at

windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline

repairs, details are included in the log file provided by the /OFFLOGFILE flag.

Here is some of the information that the sfc scan error directed me towards.

https://www.dropbox.com/s/qhpr7w9f1qthhwm/sfc%20info.docx?dl=0

@Buzzkill83 

The AVCC3 (Analog Power Supply voltage) is all over the place, but so much that I think it is a invalid readout.

Everything else looks fine.

Do you have, or could borrow a PSU to test with?

Please use the "MassEffect3Config.exe" under ">drive<:\Program Files (x86)\Origin Games\Mass Effect 3\Binaries"

Disable Audio and set the game to windowed mode.

Also choose the smallest resolution that is offered to you. > Test.

I have an extra psu that I could test but I was doing some reading on the radeon furoms and people were talking about gpu scaling, would that be something to try?

@Buzzkill83 

GPU Scaling normally refers to a AMD technology that let you scale old game who are based on 4:3 aspect ratio to a modern 16:9 or 21:9 aspect ratio. 

All Mass Effect games are capable of modern aspect ratio settings.

Or do you refer to something else?

Did you tried the steps I suggested?

I would check if all power cables are firmly connected and if yes, with another wall outlet. (No multi socked.)

If that don't works, test the PSU.

The windowed and audio thing worked, I also checked the power cables, there didnt seem to be anything wrong. What do you think causes this?

@Buzzkill83 

It is very hard to diagnose something like this over the internet.

My initial reaction was a power problem and I think that is still likely.

The reduced resolution was suggested by me because the game needs way fewer resources in this state.

Look if it works if you turn the audio on, then look if it works in Widowed mode at native resolution.