Access Violation crash...
|
As with all the other crashes of this kind reported. game hangs has to be killed.
Event: " WinDbg:
Spoiler
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\puk\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_PathOfExile.exe_e041f0f53d9c34614c0ad55a26b1fc3bcb2384_cab_0ae042ab\WER4251.tmp.mdmp] User Mini Dump File: Only registers, stack and portions of memory are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible Product: WinNt, suite: SingleUserTS Machine Name: Debug session time: Thu Sep 15 14:18:47.000 2016 (UTC + 10:00) System Uptime: 0 days 1:05:49.231 Process Uptime: 0 days 1:03:27.000 ................................................................ ............ Loading unloaded module list ...... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (b30.394): Access violation - code c0000005 (first/second chance not available) eax=00000000 ebx=11fef220 ecx=00000003 edx=00000000 esi=00000002 edi=00000000 eip=77cd0ab5 esp=11fef1d0 ebp=11fef26c iopl=0 nv up ei pl zr na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246 ntdll!NtWaitForMultipleObjects+0x15: 77cd0ab5 83c404 add esp,4 0:026> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for PathOfExile.exe - *** WARNING: Unable to verify checksum for fmod.dll *** ERROR: Symbol file could not be found. Defaulted to export symbols for fmod.dll - *** WARNING: Unable to verify checksum for fmodstudio.dll *** ERROR: Symbol file could not be found. Defaulted to export symbols for fmodstudio.dll - *** ERROR: Symbol file could not be found. Defaulted to export symbols for bink2w32.dll - FAULTING_IP: atiumdag+ac6d5 724dc6d5 0fb644d701 movzx eax,byte ptr [edi+edx*8+1] EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 724dc6d5 (atiumdag+0x000ac6d5) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000001 Attempt to read from address 00000001 CONTEXT: 00000000 -- (.cxr 0x0;r) eax=00000000 ebx=11fef220 ecx=00000003 edx=00000000 esi=00000002 edi=00000000 eip=77cd0ab5 esp=11fef1d0 ebp=11fef26c iopl=0 nv up ei pl zr na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246 ntdll!NtWaitForMultipleObjects+0x15: 77cd0ab5 83c404 add esp,4 DEFAULT_BUCKET_ID: NULL_CLASS_PTR_READ PROCESS_NAME: PathOfExile.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000001 READ_ADDRESS: 00000001 FOLLOWUP_IP: atiumdag+ac6d5 724dc6d5 0fb644d701 movzx eax,byte ptr [edi+edx*8+1] NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 APP: pathofexile.exe ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre FAULTING_THREAD: 00000394 PRIMARY_PROBLEM_CLASS: NULL_CLASS_PTR_READ BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ LAST_CONTROL_TRANSFER: from 724dbc87 to 724dc6d5 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 11fef9f0 724dbc87 7bd14ec4 7bd187dc 7bd14ec4 atiumdag+0xac6d5 11fefa24 724c9b73 7bd14ec4 7bd187dc 446db00c atiumdag+0xabc87 11fefa64 724d842e 7bd14ec4 422cec90 422ce7e0 atiumdag+0x99b73 11fefa90 724acb19 422ce7c4 1bbe3058 00000000 atiumdag+0xa842e 11fefaa8 725485d8 444642ac 65740f08 00000000 atiumdag+0x7cb19 11fefae0 72548700 00000000 11fefaf8 75b3338a atiumdag+0x1185d8 11fefaec 75b3338a 1bbe3058 11fefb38 77cea242 atiumdag+0x118700 11fefaf8 77cea242 1bbe3058 6627f591 00000000 kernel32!BaseThreadInitThunk+0xe 11fefb38 77cea215 72548684 1bbe3058 00000000 ntdll!__RtlUserThreadStart+0x70 11fefb50 00000000 72548684 1bbe3058 00000000 ntdll!_RtlUserThreadStart+0x1b SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atiumdag+ac6d5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atiumdag IMAGE_NAME: atiumdag.dll DEBUG_FLR_IMAGE_TIMESTAMP: 57c5ebed STACK_COMMAND: ~26s; .ecxr ; kb FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_atiumdag.dll!Unknown BUCKET_ID: APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ_atiumdag+ac6d5 ANALYSIS_SOURCE: UM FAILURE_ID_HASH_STRING: um:null_class_ptr_read_c0000005_atiumdag.dll!unknown FAILURE_ID_HASH: {480e4178-3919-7a59-0070-d76b0a93de21} Followup: MachineOwner --------- Last bumped on Oct 15, 2016, 12:10:57 AM
This thread has been automatically archived. Replies are disabled.
| |
|
Another:
" | |
|
Another:
" | |
|
Another:
" | |
|
Another:
" | |
|
did you update your catalyst driver to the latest version?
age and treachery will triumph over youth and skill!
| |
" I've been through numerous crimson drivers including the latest 16.10.1. However, I found the the drivers from 16.8.x onward worse than the older drivers for my card. I'm now using 16.7.1 again. I certainly don't discount the possibility of an issue at my end, however, I'm personally unable to interpret the error presented in the WinDbg: FAULTING_IP: atiumdag+ac6d5 724dc6d5 0fb644d701 movzx eax,byte ptr [edi+edx*8+1] It's obviously amd related but AMD have been less then responsive and I can't find anything related via search. Although there seems to be plenty of atiumdag.dll+game error posts all over the place. I also don't understand why, in some of the event logs, the file atiumdag.dll is referenced in 'C:\Windows\System32': " whereas, it has never existed in that location with any of the drivers I've used. Moreover, In some cases, the file isn't referenced at all: " In this case it's just the PoE executable and whichever module caused the fault remains unknown. I would say that looking around these forums and reddit, you'll see plenty of "PoE has stopped working" error messages and I would guess, if people took the time to check the logs, they'd see it's been caused by the Access Violation bug check. I'll continue researching the issue but I might as well keep reporting these errors as they happen. |
