Share via

Game crashing like hell...

Anonymous
2021-06-01T02:07:03+00:00

Hi all,

My pc game keep crashing a lot. 1st crash at 10 min of playing, then restart pc (mostly times it just close the game) and 2nd crash at 3 min, then 3rd crash at 15 secs, until it freeze totaly..
Tryed EVERYTHING in 3 languages... Don't know what to do.

Please help me Obi Micro Soft, you are my only hope!

Here is the Windbg Diag

Thank you!

Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\user\Documents\STAR WARS Battlefront II\CrashDumps\CrashDump_2021.05.31_22.44.15.119.mdmp]

Comment: 'Frostbite MiniDump. Address: 00007FFDF5DA63FC (In Windbg type: .ecxr)

[EOF]'

User Mini Dump File: Only registers, stack and portions of memory are available

************* Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Version 17134 MP (8 procs) Free x64

Product: WinNt, suite: SingleUserTS

Edition build lab: 17134.1.amd64fre.rs4_release.180410-1804

Machine Name:

Debug session time: Mon May 31 22:44:15.000 2021 (UTC - 3:00)

System Uptime: not available

Process Uptime: 0 days 0:02:05.000

................................................................

..........................................................

This dump file has an exception of interest stored in it.

The stored exception information can be accessed via .ecxr.

(2af0.734): Access violation - code c0000005 (first/second chance not available)

For analysis of this file, run !analyze -v

ntdll!ZwGetContextThread+0x14:

00007ffd`fcccc6f4 c3              ret

0:020> !analyze -v

*******************************************************************************

*                                                                             *

*                        Exception Analysis                                   *

*                                                                             *

*******************************************************************************

*************************************************************************

***                                                                   ***

***                                                                   ***

***    Either you specified an unqualified symbol, or your debugger   ***

***    doesn't have full symbol information.  Unqualified symbol      ***

***    resolution is turned off by default. Please either specify a   ***

***    fully qualified symbol module!symbolname, or enable resolution ***

***    of unqualified symbols by typing ".symopt- 100". Note that     ***

***    enabling unqualified symbol resolution with network symbol     ***

***    server shares in the symbol path may cause the debugger to     ***

***    appear to hang for long periods of time when an incorrect      ***

***    symbol name is typed or the network symbol server is down.     ***

***                                                                   ***

***    For some commands to work properly, your symbol path           ***

***    must point to .pdb files that have full type information.      ***

***                                                                   ***

***    Certain .pdb files (such as the public OS symbols) do not      ***

***    contain the required information.  Contact the group that      ***

***    provided you with these symbols if you need this command to    ***

***    work.                                                          ***

***                                                                   ***

***    Type referenced: nt!IMAGE_NT_HEADERS32                         ***

***                                                                   ***

*************************************************************************

*************************************************************************

***                                                                   ***

***                                                                   ***

***    Either you specified an unqualified symbol, or your debugger   ***

***    doesn't have full symbol information.  Unqualified symbol      ***

***    resolution is turned off by default. Please either specify a   ***

***    fully qualified symbol module!symbolname, or enable resolution ***

***    of unqualified symbols by typing ".symopt- 100". Note that     ***

***    enabling unqualified symbol resolution with network symbol     ***

***    server shares in the symbol path may cause the debugger to     ***

***    appear to hang for long periods of time when an incorrect      ***

***    symbol name is typed or the network symbol server is down.     ***

***                                                                   ***

***    For some commands to work properly, your symbol path           ***

***    must point to .pdb files that have full type information.      ***

***                                                                   ***

***    Certain .pdb files (such as the public OS symbols) do not      ***

***    contain the required information.  Contact the group that      ***

***    provided you with these symbols if you need this command to    ***

***    work.                                                          ***

***                                                                   ***

***    Type referenced: $ntdllsym!_CONTEXT                            ***

***                                                                   ***

*************************************************************************

***** OS symbols are WRONG. Please fix symbols to do analysis.

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec

    Value: 1625

    Key  : Analysis.DebugAnalysisManager

    Value: Create

    Key  : Analysis.Elapsed.mSec

    Value: 19539

    Key  : Analysis.Init.CPU.mSec

    Value: 218

    Key  : Analysis.Init.Elapsed.mSec

    Value: 23738

    Key  : Analysis.Memory.CommitPeak.Mb

    Value: 185

    Key  : Timeline.Process.Start.DeltaSec

    Value: 125

    Key  : WER.OS.Branch

    Value: rs4_release

    Key  : WER.OS.Timestamp

    Value: 2018-04-10T18:04:00Z

    Key  : WER.OS.Version

    Value: 10.0.17134.1

COMMENT:  Frostbite MiniDump. Address: 00007FFDF5DA63FC (In Windbg type: .ecxr)

[EOF]

CONTEXT:  (.ecxr)

rax=00000000578c7450 rbx=a843d9afd9baab27 rcx=00000000578c7448

rdx=a843d9afd9baab27 rsi=0000000000000000 rdi=00000000578c7400

rip=00007ffdf5da63fc rsp=0000000044eff0b0 rbp=0000000044eff1a9

 r8=0000000000000000  r9=0000000000000000 r10=00000000578c7370

r11=a843d9afd9baab27 r12=0000000044eff1b0 r13=000000004a1d2980

r14=00000000578c7448 r15=000000001c0e3f60

iopl=0         nv up ei ng nz na po nc

cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286

d3d11!CContext::TID3D11DeviceContext_SetShader_<1,0>+0x2c:

00007ffdf5da63fc 39b2a8000000    cmp     dword ptr [rdx+0A8h],esi ds:a843d9afd9baabcf=????????

Resetting default scope

EXCEPTION_RECORD:  (.exr -1)

ExceptionAddress: 00007ffdf5da63fc (d3d11!CContext::TID3D11DeviceContext_SetShader_<1,0>+0x000000000000002c)

   ExceptionCode: c0000005 (Access violation)

  ExceptionFlags: 00000000

NumberParameters: 2

   Parameter[0]: 0000000000000000

   Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

PROCESS_NAME:  ntdll.wrong.symbols.dll

WRONG_SYMBOLS_TIMESTAMP: aed1b9eb

WRONG_SYMBOLS_SIZE: 1e1000

FAULTING_MODULE: 00007ffdfcc30000 ntdll

ADDITIONAL_DEBUG_TEXT: 

You can run '.symfix; .reload' to try to fix the symbol path and load symbols. ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

FAULTING_THREAD:  ffffffff

STACK_TEXT: 

0000000000000000 0000000000000000 WRONG_SYMBOLS!WRONG_SYMBOLS+0x0

STACK_COMMAND:  ** Pseudo Context ** ManagedPseudo ** Value: ffffffff ** ; kb

BUGCHECK_CODE:  aed1b9eb

EXCEPTION_CODE_STR:  AED1B9EB

EXCEPTION_STR:  WRONG_SYMBOLS

IMAGE_NAME:  ntdll.wrong.symbols.dll

MODULE_NAME: ntdll_wrong_symbols

SYMBOL_NAME:  ntdll_wrong_symbols!AED1B9EB1E1000

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_17134.1.amd64fre.rs4_release.180410-1804_TIMESTAMP_621210-124323_AED1B9EB_ntdll.wrong.symbols.dll!AED1B9EB1E1000

OS_VERSION:  10.0.17134.1

BUILDLAB_STR:  rs4_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {889a82dc-9a11-9123-602d-ffef664b3286}

Followup:     MachineOwner

Windows for home | Windows 10 | Gaming

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-06-02T04:54:41+00:00

    Thank you for the replay!

    1 - I'm running Win 10 pro , version 1803 , compilation 17134.1304

    2 - No, nothing atypical. This problem started some years ago but with low frequency... and since 1 year to now, it got impossible to play.

    Also, all other programs run perfectly... no crashes, no lags... nothing.

    I'll try this clean boot but it seems the problem is "ntdll.wrong.symbols.dll". Have you had a look on windbg diagnosis above?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-06-01T08:38:18+00:00

    Hi,

    Thank you for writing to Microsoft Community Forums.

    I understand that you’re facing issues when playing games on your PC. I will certainly try my best to assist you with the issue.

    For further clarity on the issue, please respond to the questions below:

    1. Which build version of Windows 10 are you using currently?
    2. Are you aware of any changes made to the PC prior to which you weren’t facing this issue?

    Refer the article Which version of Windows operating system am I running?

    Meanwhile, I would suggest you to try booting the PC in Clean Boot and see if you’re able to play the games normally. Refer the article How to perform a clean boot in Windows

    Performing a clean boot will start the computer with minimal set of drivers and programs, to determine whether a background program is causing the issue. Some of the Startup programs will not load after performing a clean boot on the computer. However, that functionality will return when you reset the computer to start normally after finishing the troubleshooting.

    If you’re able to play the games fine after performing Clean Boot, then please refer the section How to determine what is causing the problem after you do a clean bootto identify the root cause of the issue.

    Note: Please refer the sectionReset the computer to start normally after clean boot troubleshootingto boot the computer in to normal mode after troubleshooting

    Let us know if you need any further assistance, we will be glad to assist you.

    Regards,

    Prakhar Khare

    Microsoft Community – Moderator

    Was this answer helpful?

    0 comments