Crash Dump File may give himt of Game crashing?

Anonymous
2022-05-30T05:11:44+00:00

Hello, I was told to pot these results here from WinDbg. My game keeps freezing and or closing. 3 other family members with separate logins also play the same game but have no issues.

If anyone has any insight it would be greatly appreciated.
Regards,
Charles

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 827

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 4061

    Key  : Analysis.Init.CPU.mSec
    Value: 250

    Key  : Analysis.Init.Elapsed.mSec
    Value: 50324

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

FILE_IN_CAB:  Airport City.exe.1852.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
eax=00000000 ebx=1b8cda30 ecx=0f840cd8 edx=0000a388 esi=02d47e1d edi=00000000
eip=6753ca70 esp=0488f714 ebp=0488f71c iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
GameAssembly!UnityPalGetTimeZoneDataForID+0x33c00:
6753ca70 890f            mov     dword ptr [edi],ecx  ds:002b:00000000=????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 6753ca70 (GameAssembly!UnityPalGetTimeZoneDataForID+0x00033c00)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 00000000
Attempt to write to address 00000000

PROCESS_NAME:  Airport City.exe

WRITE_ADDRESS:  00000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  00000000

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
0488f71c 68c9f57b     02d47e1d 0488f748 6887a3fb GameAssembly!UnityPalGetTimeZoneDataForID+0x33c00
0488f728 6887a3fb     02d47e1d 00000000 3473c6c8 GameAssembly!SetHeaderUpdateCallback+0x173874b
0488f748 683e7409     389f90c0 1b09d1e8 54032b88 GameAssembly!SetHeaderUpdateCallback+0x13135cb
0488f75c 6879806d     2057d5e8 1b9279f0 3473c6c8 GameAssembly!SetHeaderUpdateCallback+0xe805d9
0488f774 68428669     44892f40 3473c6c8 1b983380 GameAssembly!SetHeaderUpdateCallback+0x123123d
0488f78c 676343bd     3473c6c8 3473c6c8 1b8ce0b4 GameAssembly!SetHeaderUpdateCallback+0xec1839
0488f7c8 6841bacc     3473c6c8 1b694210 1b8cda30 GameAssembly!SetHeaderUpdateCallback+0xcd58d
0488f7e0 68fd6b08     1b6abf90 00000000 0488f830 GameAssembly!SetHeaderUpdateCallback+0xeb4c9c
0488f7f0 676a8aad     3a27d1a0 1b691db0 4012a564 GameAssembly!SetHeaderUpdateCallback+0x1a6fcd8
0488f830 68419330     448a4f40 1b691db0 1b16a2e8 GameAssembly!SetHeaderUpdateCallback+0x141c7d
0488f84c 6841bd62     1b6abf90 448a4f40 1b691db0 GameAssembly!SetHeaderUpdateCallback+0xeb2500
0488f880 683d8d6e     1b6abf90 00000000 00000000 GameAssembly!SetHeaderUpdateCallback+0xeb4f32
0488f898 671d8495     1b6a9380 00000000 16b83d6c GameAssembly!SetHeaderUpdateCallback+0xe71f3e
0488f8ac 6753897f     683d8c70 16b83d6c 1b6a9380 GameAssembly!il2cpp_gc_set_external_wbarrier_tracker+0xf475
0488f8e4 674f16e6     16b83d6c 1b6a9380 0488f9e8 GameAssembly!UnityPalGetTimeZoneDataForID+0x2fb0f
0488f8fc 63152396     16b83d6c 1b6a9380 0488f9e8 GameAssembly!il2cpp_runtime_invoke+0x26
0488f920 63155a1f     16b83d6c 1b6a9380 0488f97c UnityPlayer+0x692396
0488f954 6316a422     0488f978 0488f97c 0488fac4 UnityPlayer+0x695a1f
0488fa74 62ecc33e     198e7590 0000000c 0488fb24 UnityPlayer+0x6aa422
0488fad0 63051653     000001e8 63051653 63ed0630 UnityPlayer+0x40c33e
0488fb1c 63060970     63eb8ce4 00000000 00000000 UnityPlayer+0x591653
0488fb4c 636c5040     0488fbc0 636b35d4 1a3259ac UnityPlayer+0x5a0970
0488fb54 636b35d4     1a3259ac 636b3a10 636b3a10 UnityPlayer+0xc05040
0488fbc0 636b3a1b     0488fbd8 7681fa29 0350f6f0 UnityPlayer+0xbf35d4
0488fbc8 7681fa29     0350f6f0 7681fa10 0488fc34 UnityPlayer+0xbf3a1b
0488fbd8 77547a7e     0350f6f0 30954cd8 00000000 kernel32!BaseThreadInitThunk+0x19
0488fc34 77547a4e     ffffffff 775689eb 00000000 ntdll!__RtlUserThreadStart+0x2f
0488fc44 00000000     636b3a10 0350f6f0 00000000 ntdll!_RtlUserThreadStart+0x1b

SYMBOL_NAME:  GameAssembly+33c00

MODULE_NAME: GameAssembly

IMAGE_NAME:  GameAssembly.dll

STACK_COMMAND:  ~10s; .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_POINTER_WRITE_c0000005_GameAssembly.dll!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x86

OSNAME:  Windows 10

FAILURE_ID_HASH:  {002af295-703b-59e9-f620-dcb6b87f0701}

Followup:     MachineOwn
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 No comments

81 answers

Sort by: Most helpful
  1. Anonymous
    2022-06-02T22:25:04+00:00

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-06-02T20:56:58+00:00

    There were 2 posts that you made and only the second post appeared in the Window.

    The first post was correct where it had displayed 3 customized tests and approximately 20 non-Microsoft drivers.

    The second post was incorrect where it had displayed 3 customized tests and a large number of Microsoft drivers.

    Please return to the first post where there were 3 customized tests and approximately 20 Microsoft drivers.

    Now add these customized tests:

    [ ] 0x00000001 Special pool. 
    
    [ ] 0x00000002 Force IRQL checking. 
    
    [ ] 0x00000008 Pool tracking. 
    
    [ ] 0x00000020 Deadlock detection. 
    
    [ ] 0x00000080 DMA checking. 
    

    There will now be 8 customized tests and approximately 20 non-Microsoft drivers.

    If there is no immediate BSOD then post an new verifier /querysettings share link.

    It there is a BSOD then post a new V2.

    (if there is a BSOD this will be the first BSOD using the tool > you must know how to return to the desktop to turn off the tool and run V2)

    If there is a dump file available and if the debugging displays a misbehaving driver the driver will be uninstalled or uninstalled and reinstalled.

    Then the tool will be restarted to find the next misbehaving driver.

    Report into the thread if there are major performance problems or very slow boot.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-06-02T15:17:29+00:00

    Please refer to the earlier instructions and the links:

    Test all non-Microsoft drivers.

    Test no Microsoft drivers.

    https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

    https://answers.microsoft.com/en-us/windows/forum/all/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

    Make a new restore point:

    https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html

    Please restart the tool making the above changes.

    There will be no reason to boot into safe mode unless there is a BSOD.

    https://www.tenforums.com/tutorials/2304-boot-into-safe-mode-windows-10-a.html

    The purpose of using the tool is for it to create BSOD.

    When there is a BSOD if dump files are created and collected they can be debugged.

    Once there is a BSOD it will be impossible to return to the desktop unless you turn off the tool.

    In order to turn off the tool run the commands in this sequence as needed to be able to turn off the tool: (only move to the next command if the prior command fails to turn off the tool)

    a) verifier /reset

    b) verifier /bootmode resetonbootfail

    c) system restore

    Again the last method to use is system restore as the dump files are often lost.

    The dump files are needed for the BSOD troubleshooting.

    So little progress would be made in the troubleshooting unless there are dump files.

    Please find a flash drive that you can format (> or = 8 GB)

    Create a bootable Media Creation Tool (MCT) (Windows 10 iso).

    https://www.tenforums.com/tutorials/2376-create-bootable-usb-flash-drive-install-windows-10-a.html

    https://www.tenforums.com/tutorials/9230-download-windows-10-iso-file.html

    https://www.microsoft.com/en-us/software-download/windows10

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-06-02T11:49:19+00:00

    All Microsoft Drivers (No BSOD)

    Part 1

    Image

    Part 2

    Image

    Part 3

    Image

    Part 4

    Image

    After this I booted into safe mode and ran command verifier /reset
    I shall check back in the morning Sydney time.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-06-02T11:11:51+00:00

    All Non Microsoft Drivers (No BSOD)

    Image 1

    Image 2

    Was this answer helpful?

    0 comments No comments