WWE 2k19 crash in game universe mode (dump files question) - PROBLEMS SOLVED (23/11/2020)

[BlackBen83]

Hi guyz,  I hope you're fine all.

Hi, I was wondering if someone could help me figure out what's wrong.
I don't know anything about it, but I still tried to search the internet and followed the advice of other friends here.

After cleaning my hard drives with chkdsk, updating all the drivers, I still have this problem sometimes.

This file is the last Crash_dump of the 16/11/20 happen in Universe mode analyzed with Windbg. Note that I've Windows 10.

Quote

Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\Program Files (x86)\Steam\steamapps\common\WWE 2K19\CrashDump\2KMiniDump_20201116_131046.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv*
Executable search path is: 
Windows 8 Version 9200 MP (2 procs) Free x64
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Mon Nov 16 13:10:48.000 2020 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:47:08.000
................................................................
................................................................
..
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(19b0.2b34): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ff9`aeffe484 c3              ret
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify checksum for bink2w64.dll
DBGHELP: Timeout to store: C:\ProgramData\dbg\sym*https://msdl.microsoft.com/download/symbols

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.Sec
    Value: 4

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BLACKBEN-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 81

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 154

    Key  : Analysis.System
    Value: CreateObject

    Key  : Timeline.Process.Start.DeltaSec
    Value: 2828

CONTEXT:  (.ecxr)
rax=0000000000000000 rbx=000000000014cd60 rcx=000000000014cd60
rdx=000000001c98e2ac rsi=0000000000000000 rdi=00000000ca5aefdc
rip=0000000140175a63 rsp=000000000014cce0 rbp=000000000014ce20
 r8=0000000000000002  r9=00007ff9a5080000 r10=000000001c98e2ac
r11=000000000014cd80 r12=0000000000000000 r13=000000000000002c
r14=00000000000000c6 r15=000000000014d020
iopl=0         nv up ei ng nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
WWE2K19_x64!AK::Monitor::PostString+0xc49e3:
00000001`40175a63 66397724        cmp     word ptr [rdi+24h],si ds:00000000`ca5af000=????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000140175a63 (WWE2K19_x64!AK::Monitor::PostString+0x00000000000c49e3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000ca5af000
Attempt to read from address 00000000ca5af000

PROCESS_NAME:  WWE2K19_x64.exe

READ_ADDRESS:  00000000ca5af000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - L'instruction   0x%p emploie l'adresse m moire 0x%p. L' tat de la m moire ne peut pas  tre %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000ca5af000

STACK_TEXT:  
00000000`0014cce0 00000001`40179cba : 00000000`ca5aefdc 00000000`00000000 00000000`000000c6 00000000`cde62fd8 : WWE2K19_x64!AK::Monitor::PostString+0xc49e3
00000000`0014cd20 00000001`40166658 : 00000000`638a11e4 00000000`638a11e4 00000000`00000400 00000000`000000b1 : WWE2K19_x64!AK::Monitor::PostString+0xc8c3a
00000000`0014cf90 00000001`40166edc : 00000000`1d12f0f0 00000000`cde61010 00000000`cde61010 00000000`cde61010 : WWE2K19_x64!AK::Monitor::PostString+0xb55d8
00000000`0014f3d0 00000001`40be7948 : 00000000`0000000c 00000000`07dee0d8 00000000`cde61010 00000000`00000006 : WWE2K19_x64!AK::Monitor::PostString+0xb5e5c
00000000`0014f490 00000001`40a473e2 : 00000000`00000000 00000000`00000004 00000000`00000000 00000001`415789c2 : WWE2K19_x64!AK::WriteBytesMem::SetCount+0x526598
00000000`0014f4c0 00000001`401609a3 : 00000000`07de7580 00000001`415c59dd ffffffff`fffffffe 00000000`00000000 : WWE2K19_x64!AK::WriteBytesMem::SetCount+0x386032
00000000`0014f4f0 00000001`40be75b9 : 00000000`9777c620 00000001`40579c50 00000000`00000000 00000000`0014f6e0 : WWE2K19_x64!AK::Monitor::PostString+0xaf923
00000000`0014f550 00000001`41287a55 : 00000000`00000525 00000000`cde61010 00000000`0014f6e0 00000000`07dee0d8 : WWE2K19_x64!AK::WriteBytesMem::SetCount+0x526209
00000000`0014f5e0 00000001`400aaf96 : 00000000`00000000 00000000`00000000 00000000`2b139490 00000001`411aa323 : WWE2K19_x64!AK::WriteBytesMem::SetCount+0xbc66a5
00000000`0014f850 00000001`400a80be : 00000000`00000000 00000000`00000000 00000000`0014f9b0 00000000`2b139490 : WWE2K19_x64!AK::MemoryMgr::SetPoolName+0x19d66
00000000`0014f8b0 00000001`41d195f6 : 00000000`00000001 00000000`00000000 00000001`43651310 00000000`00265000 : WWE2K19_x64!AK::MemoryMgr::SetPoolName+0x16e8e
00000000`0014fef0 00007ff9`ae967c24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WWE2K19_x64!AK::StreamMgr::SetFileLocationResolver+0x15a926
00000000`0014ff30 00007ff9`aefcd4d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000000`0014ff60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

SYMBOL_NAME:  WWE2K19_x64!AK::Monitor::PostString+c49e3

MODULE_NAME: WWE2K19_x64

IMAGE_NAME:  WWE2K19_x64.exe

STACK_COMMAND:  ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_WWE2K19_x64.exe!AK::Monitor::PostString

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8

FAILURE_ID_HASH:  {158667be-e079-1d1c-b952-8e78a483915b}

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

I don't see what I should do eventually even when I search on the net.

Thanks for the help.

Ben

Edited November 16, 2020 by BlackBen83

[BlackBen83]

I've fixed some Redistribuable 2015 to 2019... but since this day, after a lot of crash and try... this message in WinDbg appears. It talk about the VCRUNTIME140.dll.

Quote

PROCESS_NAME:  WWE2K19_x64.exe

READ_ADDRESS:  0000000001e1f000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - L'instruction   0x%p emploie l'adresse m moire 0x%p. L' tat de la m moire ne peut pas  tre %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000001e1f000

STACK_TEXT:  
00000000`097afc08 00000001`4126010c : 00000000`0022f3a0 00007ffe`f11874d2 00000000`66056010 00000000`097afd20 : VCRUNTIME140!memcpy+0x57
00000000`097afc10 00000001`412601d6 : 00000000`097afe90 00000000`00000000 00000000`00000023 00000000`00000023 : WWE2K19_x64!AK::WriteBytesMem::SetCount+0xb9ed5c
00000000`097afcc0 00000001`40c1f91a : 00000000`00000000 00000000`097afd69 00000000`0000002b 00000000`1b88f014 : WWE2K19_x64!AK::WriteBytesMem::SetCount+0xb9ee26
00000000`097afd00 00000001`412683fb : 00000000`00000000 00000000`07326800 00000000`3537e010 00000000`06fbb610 : WWE2K19_x64!AK::WriteBytesMem::SetCount+0x55e56a
00000000`097afdd0 00000001`41270890 : 00000000`5c14b0a2 00000001`412683b0 00000000`00000001 00000000`fffff1f0 : WWE2K19_x64!AK::WriteBytesMem::SetCount+0xba704b
00000000`097afe00 00000001`4127f629 : 00000000`00000000 00000000`00000000 00000000`03ec0700 00000000`06fbb610 : WWE2K19_x64!AK::WriteBytesMem::SetCount+0xbaf4e0
00000000`097afef0 00007ffe`f0967c24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WWE2K19_x64!AK::WriteBytesMem::SetCount+0xbbe279
00000000`097aff30 00007ffe`f11ed4d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000000`097aff60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

FAULTING_SOURCE_LINE:  f:\dd\vctools\crt\vcruntime\src\string\amd64\memcpy.asm

FAULTING_SOURCE_FILE:  f:\dd\vctools\crt\vcruntime\src\string\amd64\memcpy.asm

FAULTING_SOURCE_LINE_NUMBER:  137

SYMBOL_NAME:  VCRUNTIME140!memcpy+57

MODULE_NAME: VCRUNTIME140

IMAGE_NAME:  VCRUNTIME140.dll

STACK_COMMAND:  ~36s ; .ecxr ; kb

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_VCRUNTIME140.dll!memcpy

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8

FAILURE_ID_HASH:  {6cc7063a-c9e9-809b-b45d-40b8348a9d9b}

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

After several research on google and a lot of hours of try, the universe mode crashes again. So, it's not the game, or mods, or others, only the entrance tag team in universe mode and the loading of the universe mode crashed the game, I hope someone can help me to solve this problem  

Thanks.

Ben

[BlackBen83]

Hi,

I'm here to give feedback because I found one of the sources of the problem.

To start again on an almost "clean" game, I removed my Universe mode, which was only crashing the game
I put back the original files in Pac > Universe.

Just to see if it would come from mods (wrestlers, arenas or others mods) or caws (logos) I didn't want to uninstall everything.. All this content works 100%, the problem comes from elsewhere.

The cae_item.30 seems to be corrupted, I don't know how it's possible, but after replacing it with the original file, everything is better. I was able to create a team tag entry without any problem in the game with mods.

Now I have to re-edit I think either cae_item.10 or 20 instead. Because having more than a hundred titantrons, the problem must come from there. I use all the CCT content with mods.

Maybe I need to balance the number of trons present in each cae (25 trons or 30 in each cae_). It seems that the corruption of my cae_30 was done after installing more than sixty trons on it.

I also note that now the titantrons of Shane Thorne or Liv Morgan, for example, no longer appear as well. I will check the cae_item.20 also (Since @squaredcirclefan has modified it well, I'll restart with this one).

I'll let you feedback as soon as I can.

Ben

Edited November 20, 2020 by BlackBen83

[BlackBen83]

Hi all,

I finally found out where the problem was coming from. So I had my CAE_item.20 and 30 corrupted, I don't know how.

I reinstalled the number trons in a fresh CAE10 & 20 these last two days (keeping the original ones just in case). I don't use the CAE30.

Results, the game starts very well, no lag or reboot in the entrance creation for superstar or team (2 or 3 men/women), the universe mode works well too. As he was crashing every time. So for those who have had this problem before, that's where it comes from.

Ben

Edited November 25, 2020 by BlackBen83

[KJ SimsJr]

On 11/23/2020 at 3:52 AM, BlackBen83 said:

Hi all,

I finally found out where the problem was coming from. So I had my CAE_item.20 and 30 corrupted, I don't know how.

I reinstalled the number trons in a fresh CAE10 & 20 these last two days (keeping the original ones just in case). I don't use the CAE30.

Results, the game starts very well, no lag or reboot in the entrance creation for superstar or team (2 or 3 men/women), the universe mode works well too. As he was crashing every time. So for those who have had this problem before, that's where it comes from.

Ben

Thank this is gonna help a lot, but how'd you get a fresh cae_item 20 and 30

[BlackBen83]

13 hours ago, KJ SimsJr said:

Thank this is gonna help a lot, but how'd you get a fresh cae_item 20 and 30

I've the original files, just PM me if you need.

[juskool14]

I'm wondering if this is what is causing my random crashes in universe as well...I never had issues with crashing but within the past couple days it's been consistent.