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-06T02:23:04+00:00

https://1drv.ms/u/s!AjMy9pTKckn-gYFGAYC8aHvUWF8eqw?e=t7rDWx
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-06T02:06:18+00:00

Memory dumps are overwritten by default.

They disappear when there is another BSOD.

Please look now for C:\windows\memory.dmp

Save the file to the downloads folder.

Zip the file.

Post a share link with only the zipped memory dump.

Please save the file now and upload in the thread using a share link.

Size 2.2 GB > please ZIP

6/06/2022 11:23:42 AM 2254.38 C:\Windows\MEMORY.DMP

One of the two BSOD displayed again misbehaving Intel GPU drivers.

Multiple times these GPU drivers were replaced during the thread.

Each time the same driver was reinstalled.

It is important to test different driver versions.

Please uninstall and reinstall the Intel GPU drivers igdkmd64.sys.

Make sure that the new driver is a different version from: Driver Version 30.0.101.1273

Turn off Windows updates of non-Microsoft drivers: https://www.tenforums.com/tutorials/48277-enable-disable-driver-updates-windows-update-windows-10-a.html

The drivers displayed on the motherboard website are not 30.0.101.1273

Please install one of the drives displayed on the motherboard website.

One of the bugchecks, 116, displayed video TDR.

Different drivers must be tested to determine whether there is or is not a stable driver.

If there is a stable driver then this driver can be used.

If there is no stable driver then the computer will continue to have hangs, freezes and BSOD until the malfunctioning hardware is replaced.

A common stability problem in graphics occurs when the system appears completely frozen or hung

while processing an end-user command or operation.

Usually the GPU is busy processing intensive graphics operations, typically during game-play.

No screen updates occur, and users assume that their system is frozen.

Users usually wait a few seconds and then reboot the system by pressing the power button.

Windows tries to detect these problematic hang situations and dynamically recover a responsive desktop.

This process of detection and recovery is known as Timeout Detection and Recovery (TDR).

The default timeout is 2 seconds.

In the TDR process for video cards, the operating system's GPU scheduler calls the display miniport driver's

DxgkDdiResetFromTimeout function to reinitialize the driver and reset the GPU.

During this process, the operating system tells the driver not to access the hardware or memory and gives

it a short time for currently running threads to complete.

If the threads do not complete within the timeout, then the system bug checks with 0x116 VIDEO_TDR_FAILURE.

For more information, see Thread Synchronization and TDR.

The system can also bug check with VIDEO_TDR_FAILURE if a number of TDR events occur in a short period of time,

by default more than five TDRs in one minute.

If the recovery process is successful, a message will be displayed, indicating that the

"Display driver stopped responding and has recovered."

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x116---video-tdr-failure

Event[221]:

Log Name: System

Source: Display

Date: 2022-05-01T10:58:29.7700000Z

Event ID: 4101

Task: N/A

Level: Warning

Opcode: Info

Keyword: Classic

User: N/A

User Name: N/A

Computer: DESKTOP-N5UBAEP

Description:

Display driver igfx stopped responding and has successfully recovered.

Event[1346]:

Log Name: System

Source: Display

Date: 2022-05-06T11:47:53.7390000Z

Event ID: 4101

Task: N/A

Level: Warning

Opcode: Info

Keyword: Classic

User: N/A

User Name: N/A

Computer: DESKTOP-N5UBAEP

Description:

Display driver igfx stopped responding and has successfully recovered.

Event[7251]:

Log Name: System

Source: Display

Date: 2022-05-30T11:16:06.8070000Z

Event ID: 4101

Task: N/A

Level: Warning

Opcode: Info

Keyword: Classic

User: N/A

User Name: N/A

Computer: DESKTOP-N5UBAEP

Description:

Display driver igfx stopped responding and has successfully recovered.

Event[11332]:

Log Name: System

Source: Display

Date: 2022-06-06T07:29:42.1820000Z

Event ID: 4101

Task: N/A

Level: Warning

Opcode: Info

Keyword: Classic

User: N/A

User Name: N/A

Computer: DESKTOP-N5UBAEP

Description:

Display driver igfx stopped responding and has successfully recovered.

There were many other entries with different dates.

One of the BSOD bugchecks was 116:

The VIDEO_TDR_FAILURE bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed.

These were the live kernel event bugchecks: 141 and 193 that were related to problematic video:

The VIDEO_ENGINE_TIMEOUT_DETECTED live dump has a value of 0x00000141. This indicates that one of the display engines failed to respond in timely fashion.

The VIDEO_DXGKRNL_LIVEDUMP live dump has a value of 0x00000193. This indicates a livedump triggered by dxgkrnl occurred.

Name Intel(R) UHD Graphics 630

PNP Device ID PCI\VEN_8086&DEV_9BC5&SUBSYS_D0001458&REV_05\3&11583659&0&10

Adapter Type Intel(R) UHD Graphics Family, Intel Corporation compatible

Adapter Description Intel(R) UHD Graphics 630

Adapter RAM 1.00 GB (1,073,741,824 bytes)

Installed Drivers C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0797c0ea8580ae89\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0797c0ea8580ae89\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0797c0ea8580ae89\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0797c0ea8580ae89\igd12umd64.dll

Driver Version 30.0.101.1273

INF File oem32.inf (iCML_w10_DS section)

Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_0797C0EA8580AE89\IGDKMD64.SYS (30.0.101.1273, 38.15 MB (40,004,152 bytes), 26/02/2022 8:39 AM)
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-06T01:39:24+00:00

Reset Verifier in order to upload latest Zip file

https://1drv.ms/u/s!AjMy9pTKckn-gYFFalr9HchqAexFXQ?e=iAgFvO
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-06T01:34:37+00:00

Got two more BSOD doing nothing.

Cannot upload zip file to one drive as it keeps crashing - BSOD.
Was this answer helpful?

0 comments No comments
Anonymous

2022-06-06T01:21:05+00:00

Doing nothing got BSOD - https://1drv.ms/u/s!AjMy9pTKckn--SqhNgWen9IJm_Hp?e=y7xEOh https://1drv.ms/u/s!AjMy9pTKckn--Sx7OHHlGV-Ycji4?e=p2eI8G Wil now run V2
Was this answer helpful?

0 comments No comments