Game crashes seconds after starting the .exe, tried with both steam and origin
Version:
1. Origin digital download, version 1.2.1604.0, also attempted with Steam digital download as well
2. System Details
Configuration Utility | Summary Tab
*Processor: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz (4 CPUs), ~3.4GHz || Memory: 8192MB RAM
*Card name: NVIDIA GeForce GTX 780 || Dedicated Memory: 3039 MB ||Driver Version 382.33
* Sound Adapter CREATIVE Sound Blaster Z
* WIndows 10 Home 64-Bit (Build 15063) - Creators Update
* DirectX 12
3. Nature of the problem: Game suffers an APPCRASH event seconds after launch from any source whether it be the .exe directly or through steam/origin/the launcher.
Problem started occurring as of attempting to start the game a day ago. Game worked fine nearly a year ago when I played it last with the same specs and Windows 10.
4. Problem can be replicated by attempting to open the .exe in any way.
5. The game is unmodded.
6.Additional information: I've attempted a clean reboot, changing the .exe names, running as administrator, running in compatibility mode and changing physX version, none of which have worked.
Reliability monitor report:
Source
Mass Effect 2
Summary
Stopped working
Date
29-May-17 11:22
Status
Report sent
Description
Faulting Application Path: I:\Program Files (x86)\Origin Games\Mass Effect 2\Binaries\ME2Game.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: ME2Game.exe
Application Version: 1.2.1604.0
Application Timestamp: 4bd611db
Fault Module Name: nvcuda.dll
Fault Module Version: 6.14.13.8233
Fault Module Timestamp: 591d2a47
Exception Code: c0000005
Exception Offset: 002a9ffb
OS Version: 10.0.15063.2.0.0.768.101
Locale ID: 1033
Additional Information 1: 2beb
Additional Information 2: 2beba6fb4680d73a8c78ca7c24ccdb46
Additional Information 3: ff01
Additional Information 4: ff013431b2f4a453b29f35e2462cacef
Extra information about the problem
Bucket ID: 30637fb13b87f0d305ce79bb4435e36f (108943321589)
- Anonymous8 years ago
Nevermind I resolved it, changes I made to my driver's tdrlevel were causing the issue.
If anyone else suffers this problem make sure you haven't changed your tdrdelay or level and if you have then delete the registry entries.