PathOfExile_64. exe Crash
This is the 5th time I have had this problem in the last 3 days (1 time it lead to a HC death). Please help!
https://imgur.com/a/HEUqe ------------------ System Information ------------------ Time of this report: 9/25/2017, 15:34:47 Machine name: DESKTOP-FEO97LR Machine Id: {51545959-26BE-4850-B0F3-188D88F9C149} Operating System: Windows 10 Home 64-bit (10.0, Build 15063) (15063.rs2_release.170317-1834) Language: English (Regional Setting: English) System Manufacturer: System manufacturer System Model: System Product Name BIOS: 1201 Processor: AMD Ryzen 5 1600 Six-Core Processor (12 CPUs), ~3.2GHz Memory: 16384MB RAM Available OS Memory: 16304MB RAM Page File: 3787MB used, 14948MB available Windows Dir: C:\Windows DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DxDiag Version: 10.00.15063.0000 64bit Unicode --------------- Display Devices --------------- Card name: NVIDIA GeForce GTX 1060 3GB Manufacturer: NVIDIA Chip type: GeForce GTX 1060 3GB DAC type: Integrated RAMDAC Device Type: Full Device [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 11134 MB Dedicated Memory: 2982 MB Shared Memory: 8152 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) Monitor Name: Generic PnP Monitor Monitor Model: HP 27wm Monitor Id: HWP3355 Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: HDMI Last bumped on Nov 29, 2017, 5:04:01 PM
| |
bump
| |
Same for me, and others too it seems: https://www.pathofexile.com/forum/view-thread/2008424
I have ever more occuring crashes with 64bit Client. DxDiag:
Spoiler
------------------ System Information ------------------ Time of this report: 9/26/2017, 12:09:50 Machine name: PROPPER-PC Machine Id: {9C6FB8EA-9B54-4834-8E82-CC728CF39D9C} Operating System: Windows 10 Pro 64-bit (10.0, Build 15063) (15063.rs2_release.170317-1834) Language: German (Regional Setting: German) System Manufacturer: System manufacturer System Model: System Product Name BIOS: 0609 Processor: AMD Ryzen 5 1600X Six-Core Processor (12 CPUs), ~3.6GHz Memory: 16384MB RAM Available OS Memory: 16320MB RAM Page File: 8635MB used, 10117MB available Windows Dir: C:\Windows DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DxDiag Version: 10.00.15063.0000 64bit Unicode --------------- Display Devices --------------- Card name: NVIDIA GeForce GTX 1070 Manufacturer: NVIDIA Chip type: GeForce GTX 1070 DAC type: Integrated RAMDAC Device Type: Full Device Device Key: Enum\PCI\VEN_10DE&DEV_1B81&SUBSYS_33031462&REV_A1 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 16241 MB Dedicated Memory: 8081 MB Shared Memory: 8160 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) Monitor Name: Generic PnP Monitor Monitor Model: BenQ RL2450H Monitor Id: BNQ7F0E Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: DVI Driver Name: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_63f40b686fe9309f\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_63f40b686fe9309f\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_63f40b686fe9309f\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_63f40b686fe9309f\nvldumdx.dll Driver File Version: 22.21.0013.8569 (English) Driver Version: 22.21.13.8569 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.2 Graphics Preemption: Pixel Compute Preemption: Dispatch Miracast: Not Supported Hybrid Graphics GPU: Not Supported Power P-states: Not Supported Driver Attributes: Final Retail Driver Date/Size: 16.09.2017 02:00:00, 893456 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B71E3E-58C1-11CF-AB56-0E131BC2DB35} Vendor ID: 0x10DE Device ID: 0x1B81 SubSys ID: 0x33031462 Revision ID: 0x00A1 Driver Strong Name: oem5.inf:0f066de361866ac3:Section112:22.21.13.8569:pci\ven_10de&dev_1b81 Rank Of Driver: 00D12001 Video Accel: DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported Could it be, that there is an issue with Ryzen CPUs? As we both do have one, maybe there is an issue. Last edited by Propper on Sep 26, 2017, 6:15:03 AM
| |
FYI, they'll need more than the generic application has stopped working message you posted OP, older versions of windows had a show more button so you could get the error code, you should check the event viewer for it and post it.
Ancestral Bond. It's a thing that does stuff. -Vipermagi
He who controls the pants controls the galaxy. - Rick & Morty S3E1 |
|
Well, these are some examples from my eventlog from the last few days. Sadly they're in german as its my OS' language, but I will translate the most important things:
All logs look like the following, just with (sometimes) different exception codes, offsets and process IDs. Full Log:
Spoiler
Name der fehlerhaften Anwendung: PathOfExile_x64Steam.exe, Version: 0.0.0.0, Zeitstempel: 0x59c07020
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000 Ausnahmecode: 0xc0000005 Fehleroffset: 0xfffffffffffffffe ID des fehlerhaften Prozesses: 0xdec Startzeit der fehlerhaften Anwendung: 0x01d3369e6b5ae6f7 Pfad der fehlerhaften Anwendung: F:\Games\Steam\steamapps\common\Path of Exile\PathOfExile_x64Steam.exe Pfad des fehlerhaften Moduls: unknown Berichtskennung: a3f0bf4b-74d6-43b3-9718-1446be58d84f Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Exception Code: 0xc0000005 (8 times) With offsets: 0xfffffffffffffffe 0x000000000002ff7d (2 times) 0x000000000002ff8f (3 times) 0x0000000000006c81 0x000000000002ae20 Exception Code: 0x80000003 (3 times) all with offset: 0x0000000000475274 Exception Code: 0xc0000409 with offset: 0x000000000008e483 | |
Here are a few of them.
9/25/17 3:29:55 pm Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x59c06db2 Faulting module name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x59c06db2 Exception code: 0xc0000005 Fault offset: 0x00000000007d6d6a Faulting process id: 0x191c Faulting application start time: 0x01d3362fdde777ff Faulting application path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile_x64.exe Faulting module path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile_x64.exe Report Id: 80d5fe4e-8baa-4772-b008-e2922b610cfd Faulting package full name: Faulting package-relative application ID: 9/25/17 2:23:58 pm Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x59c06db2 Faulting module name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x59c06db2 Exception code: 0xc0000005 Fault offset: 0x00000000007d6d6a Faulting process id: 0x4c8 Faulting application start time: 0x01d3362aabe9ae8d Faulting application path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile_x64.exe Faulting module path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile_x64.exe Report Id: 35e5c640-89b4-48f1-adac-ca30deef6e41 Faulting package full name: Faulting package-relative application ID: 9/21/17 11:33:21 pm Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x59c06db2 Faulting module name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x59c06db2 Exception code: 0xc0000005 Fault offset: 0x00000000007d6d6a Faulting process id: 0x4d8 Faulting application start time: 0x01d33350b55f8331 Faulting application path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile_x64.exe Faulting module path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile_x64.exe Report Id: 585eedb9-ff67-4c02-bc9b-b60d8dc1b71a Faulting package full name: | |
bump. Just had another crash. 9/26/17 6:12:54
Faulting application name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x59c06db2 Faulting module name: PathOfExile_x64.exe, version: 0.0.0.0, time stamp: 0x59c06db2 Exception code: 0xc0000005 Fault offset: 0x00000000007d6d6a Faulting process id: 0xab8 Faulting application start time: 0x01d33706e6dd3d09 Faulting application path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile_x64.exe Faulting module path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile_x64.exe Report Id: 83851d00-3124-4b67-9ecb-a61396e0b6f3 Faulting package full name: Faulting package-relative application ID: Last edited by Jawsome1 on Sep 26, 2017, 6:14:38 PM
| |
anyone got a solution on this, happens to me too. Ryzen user as well
thanks | |
Crash Too ... Impossible for me to play ... playing 1 min and crash ... since the last update
Last edited by Sir_Arowana on Nov 29, 2017, 7:27:39 AM
|
|
" You have real problems with your system. 0xc0000005 is an invalid memory access; most of the cases are through a null pointer. That could be a GGG bug, or something triggering in a driver or something else running code in-process in PoE. The root cause is unknowable, and you can't do anything better than report it. (Unless it happens a lot, across a wide range of applications, in which case you might want to investigate the possibility of a memory chip failing, or if you overclock, in which case, stop doing that.) However, 0x80000003 is "the breakpoint opcode was hit", which means that something tried to drop into a debugger. Unless you somehow have a development build of PoE, this is highly unlikely to occur without some sort of corruption, or on the "OMG, things are really broken" error handling path of some code. 0xc0000409 is also a critical windows error, basically saying "hi, some internal OS data structures are really messed up", often associated with registry corruption and things like that. (This is not so much "some registry key has the wrong value" as "the data files on disk are corrupted and broken".) Add all those together and I'd be suspecting either memory or disk failure in a normal machine, or hardware damage if you overclock anything. Anyway, do the usual hardware diagnostic things: run tests, swap as many components as you can, check for overheating, clean fans, etc. Good luck. :( |
|