Crash Dump File may give himt of Game crashing?

Anonymous

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

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

81 answers

Anonymous

2022-06-05T08:41:24+00:00

I'm heading to bed and can wait briefly for the share links.

(It's 3:41 AM)

Please make a brand new restore point.

Then run WDV with only

[ ] 0x00000004 Randomized low resources simulation.
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-05T08:17:02+00:00

Shall I include all except [ ] 0x00000004 Randomized low resources simulation, same as last time?
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-05T07:49:46+00:00

Please post a new query settings share link and a new V2 share link.

Bugcheck 141 is related to GPU.

Bugcheck 144 is related to USB ports.

The error report above was caused by a device failure to enumerate.

If possible reconnect various devices to the USB ports and identify reports in reliability monitor.

Which one is repetitive or frequent enough to establish a cause and effect relationship?

Also run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/358470d1643456903-batch-files-use-bsod-debugging-gather_additional_dump_files.bat

Post a share link using one drive, drop box, or google drive.
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-05T02:51:48+00:00

I have turned off the tool.
The only issue I have experienced was after 34 hours whilst VLC media player was paused, I made a coffee, came back, and the PC had shut down. I let it run another 4 hours.

The system was a bit sluggish when watching MP4 videos from my SSDs but overall, no issues.
I have yet to reinstall Bitdefender or Airport City Game.

I am aware of the Reliability program and have been watching.
The issue that has propped up 4 times is -
Problem Event Name: LiveKernelEvent

Code: 144

Parameter 1: 3003

Parameter 2: ffff9b02196d75b0

Parameter 3: 40010002

Parameter 4: 0

OS version: 10_0_19044

Service Pack: 0_0

Product: 768_1

OS Version: 10.0.19044.2.0.0.768.101

Locale ID: 2057

From my understanding this often pertains to graphics/drivers.
There are no issues with this unless the game Airport City is playing, and only when I, as admin, played.
Other users when logged in have no issues.
I doubt this is the problem and feel it could relate to USB.
MY fairly new Gigabyte Z490 Vision G board has 2 X 3.0 slots.
When I plug anything in to those slots it constantly beeps the disconnect sound.

However, perhaps nothing to do with the game freezing or crashing.
This again, is the only issue I have with the PC. Everything else (bar USB sound) is fine.
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-03T07:11:47+00:00

It looks good.

Run WDV with the current customized tests for approximately 36 hours.

If there are no BSOD during this time period then that will complete the testing.

The tool can be turned off.

You can continue using Microsoft defender or reinstall Bitdefender.

Also the software that had been uninstalled can be reinstalled once you're comfortable with the computer stability.

Generally several days of computer stability is sufficient.

To follow the computer stability / instability use reliability monitor:

https://www.howtogeek.com/166911/reliability-monitor-is-the-best-windows-troubleshooting-tool-you-arent-using/

It reports many of the events seen in the event viewer and it has a chart to follow trends over time.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments