Given that we haven't had this problem reported by anyone else as yet, it likely means the bug is provoked by particular device driver settings or particular hardware.
FAULTING_IP:
atiumd64+1f0b3
00007ff9`9a0cf0b3 83be2002000001 cmp dword ptr [rsi+220h],1
ExceptionAddress: 00007ff99a0cf0b3 (atiumd64+0x000000000001f0b3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000220
Attempt to read from address 0000000000000220
BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POIN TER_READ
Leave a comment: