Re: Mass Effect 3 No Longer Stable

4 Replies

Anonymous

My video card is not overclocked in any way.

I took a slightly different approach to the video driver this time. I was somewhat concerned (especially after my last post's error messages) that the clean install was not removing all traces of the previous video driver. Therefore I have reformatted and reinstalled the partition I am using to bug chase this.

This partition now:

has a new clean install of Win7 Ultimate
has been patched up to date
I stopped the automatic installation of the video driver
I performed a manual install of the NVidia driver 353.06
I only installed the graphics/sound/PhysX drivers in a custom install (meaning that the undesired components have never been installed on this system)
I installed a password safe, Origin for PC and downloaded a fresh install of ME3
when all was installed I ran ME3

Unfortunately it still doesn't work. On one trial run I got a bit further into the Defence Committee meeting and on a second ME3 collapsed when James comes into Shepherd's room. These are hard crashes where the machine is pole axed and caught by the watchdog timer into a reboot.

There is much less in the event logs.

Event 6008

The previous system shutdown at 21:46:23 on ‎05/‎06/‎2015 was unexpected.


Event 41

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Event 1001

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0xfffffa800dae4010, 0xfffff88005057ad4, 0xffffffffc000009a, 0x0000000000000004). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060515-21559-01.

I have now handed the mini dump to WinDbg and enclose some output.

Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [Z:\ME3 Dumps\20150606a G2\060615-20982-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`02e00000 PsLoadedModuleList = 0xfffff800`03047730
Debug session time: Sat Jun  6 19:42:15.400 2015 (UTC + 1:00)
System Uptime: 0 days 0:05:45.290
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800d1b0010, fffff8800510ead4, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+82fad4 )

Followup: MachineOwner
---------

7: kd> kpn 200
 # Child-SP          RetAddr           Call Site
00 fffff880`04371a48 fffff880`03f5a134 nt!KeBugCheckEx
01 fffff880`04371a50 fffff880`03f2d867 dxgkrnl!TdrBugcheckOnTimeout+0xec
02 fffff880`04371a90 fffff880`03f59f43 dxgkrnl!DXGADAPTER::Reset+0x2a3
03 fffff880`04371b40 fffff880`03e3803d dxgkrnl!TdrResetFromTimeout+0x23
04 fffff880`04371bc0 fffff800`0310e456 dxgmms1!VidSchiWorkerThread+0x101
05 fffff880`04371c00 fffff800`02e662c6 nt!PspSystemThreadStartup+0x5a
06 fffff880`04371c40 00000000`00000000 nt!KxStartSystemThread+0x16
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800d1b0010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800510ead4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+82fad4
fffff880`0510ead4 48ff25e5f1ebff  jmp     qword ptr [nvlddmkm+0x6eecc0 (fffff880`04fcdcc0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre

STACK_TEXT:  
fffff880`04371a48 fffff880`03f5a134 : 00000000`00000116 fffffa80`0d1b0010 fffff880`0510ead4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`04371a50 fffff880`03f2d867 : fffff880`0510ead4 fffffa80`0dde0000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04371a90 fffff880`03f59f43 : 00000000`ffffd846 00000000`0000000f fffffa80`0d1b0010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`04371b40 fffff880`03e3803d : fffffa80`0e67a9b0 00000000`00000080 00000000`00000000 fffffa80`0ddbb010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`04371bc0 fffff800`0310e456 : 00000000`045eb273 fffffa80`0f678060 fffffa80`0c76f040 fffffa80`0f678060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`04371c00 fffff800`02e662c6 : fffff800`02ff3e80 fffffa80`0f678060 fffff800`03001cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`04371c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+82fad4
fffff880`0510ead4 48ff25e5f1ebff  jmp     qword ptr [nvlddmkm+0x6eecc0 (fffff880`04fcdcc0)]

SYMBOL_NAME:  nvlddmkm+82fad4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5566824f

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

Followup: MachineOwner
---------

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`048df000 fffff880`053a2000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu May 28 03:49:51 2015 (5566824F)
    CheckSum:         00A7E4BD
    ImageSize:        00AC3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

EA_Barry
Community Manager
11 years ago
@CChrisA

Thank you for the detailed info. I think at this point we need to consider the possibility that this is a hardware issue. You should maybe look into initiating a warranty replacement of your video card. Not great news but at least we have made some progress here.
Anonymous
11 years ago
@EA_Barry
I have done some more thinking and digging and feel I now have a solution.
I recalled your comment about over clocking and I dug out the old invoice. I found the part was labelled 'super clocked'. I had never given much thought to this as it is otherwise a stock part from mainstream vendor (EVGA). Further digging showed that my part is clocked a bit faster than the same hardware that was sold without the 'super clocked' label.
I downloaded EVGA's Precision X16 application and used it to slow my card down slightly. (You get a 'Wrong Way' achievement. 😕mileyvery-happy🙂
For the record I have:
installed EVGA Precision X16
reduced 69MHz of GPU Clock Offset
reduced 99MHz of Mem Clock Offset
This has rendered ME3 stable enough to play. Its not perfect, but decent length sessions are possible.
With thanks,
Chris
EA_Barry
Community Manager
11 years ago
@CChrisA

Excellent! More experimentation with lowering your clocks may allow you to get to a place where you can have a fully stable play session. Thanks for posting your positive reults. +XP for you.

Forum Discussion

Re: Mass Effect 3 No Longer Stable

4 Replies

About Mass Effect Franchise Discussion

Recent Discussions

ME3 multiplayer randomly crashes

"You are not allowed to access the online features of this game."

New Game Mass Effect

Suggestion:New Mass Effect

Suggestion: EA collaborate with Discord on a Mass Effect Profile Collection