Constant Instant Crashes
I followed the Troubleshooting Guide.
All 41632 files are verified. The OS on this Machine is barely 4 Weeks old. And i have no further clue on what i can fix to get the client to work Here the only error message i received Aside from that i have a pleathora of Dump Files and no clue to what is causing the crash. https://drive.google.com/drive/folders/1BAXpHwwqR4r7ST-9T2hoD1Nkhjxfk_0t?usp=sharing Please help? Last bumped on Jul 29, 2024, 6:15:57 PM
|
|
I have uninstalled the Steam Client (worked for 1400h) and now am on the Standalone and it seems that fixed the issue... for now...
Last steam crash then finally generated an event Name der fehlerhaften Anwendung: PathOfExileSteam.exe, Version: 0.0.0.0, Zeitstempel: 0x6699c6a9 Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.22621.3880, Zeitstempel: 0xdb9989e8 Ausnahmecode: 0xe0000001 Fehleroffset: 0x000000000005fabc ID des fehlerhaften Prozesses: 0x0x397C Startzeit der fehlerhaften Anwendung: 0x0x1DADA0B04BA31A9 Pfad der fehlerhaften Anwendung: D:\Steam\steamapps\common\Path of Exile\PathOfExileSteam.exe Pfad des fehlerhaften Moduls: C:\Windows\System32\KERNELBASE.dll Berichtskennung: cff3691c-f055-4954-b779-237710a1b17e Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: |
|
I am getting the exact same Windows Error Event on the standalone client:
Name der fehlerhaften Anwendung: PathOfExile.exe, Version: 0.0.0.0, Zeitstempel: 0x6699c6a9 Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.22621.3880, Zeitstempel: 0xdb9989e8 Ausnahmecode: 0xe0000001 Fehleroffset: 0x000000000005fabc ID des fehlerhaften Prozesses: 0x0x718 Startzeit der fehlerhaften Anwendung: 0x0x1DADC5423EAAABA Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile.exe Pfad des fehlerhaften Moduls: C:\Windows\System32\KERNELBASE.dll Berichtskennung: e333f983-1295-4da9-9f7e-0f111b08eb69 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Last edited by poe2nd on Jul 22, 2024, 2:14:43 PM
| |
same exact issue (stand alone)
Faulting application name: PathOfExile.exe, version: 0.0.0.0, time stamp: 0x66a41da2 Faulting module name: KERNELBASE.dll, version: 10.0.22621.3958, time stamp: 0xfbc3a4f6 Exception code: 0xe0000001 Fault offset: 0x000000000005fabc Faulting process id: 0x0x347C Faulting application start time: 0x0x1DADFBAC93A4860 Faulting application path: C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 8f9348f0-dac5-415a-9532-0e4d3a2f0907 Faulting package full name: Faulting package-relative application ID: thought my pc was corrupted but i think its ggg's fault | |
Same Issue
Name der fehlerhaften Anwendung: PathOfExileSteam.exe, Version: 0.0.0.0, Zeitstempel: 0x66a5d3ba Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.22621.3958, Zeitstempel: 0xfbc3a4f6 Ausnahmecode: 0xe0000001 Fehleroffset: 0x000000000005fabc ID des fehlerhaften Prozesses: 0x0x2904 Startzeit der fehlerhaften Anwendung: 0x0x1DAE18EE24F4A96 Pfad der fehlerhaften Anwendung: c:\Games\Steam\steamapps\common\Path of Exile\PathOfExileSteam.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll Berichtskennung: 4c8fb733-f220-4c83-9c57-8f6c3d3674cf Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: | |
if any of you have 13th or 14th gen cpus, its your cpu, these cpus have a software bug, completely at the fault of intel, where your cpu will over volt.
to fix this turn off windows turbo boost in your bios, or turn down the turbo boost multiplier in your overclock settings. intel said they will patch it mid august but it is a preventative patch, meaning your cpu is permanently damaged. |
|
The Turbo Boost is deactitivated allready and the crash still persists.
You can also limit the voltage and multiplier of the cpu. This on is a Kernel error that is an interaction with the application. |
|
" try running the command "sfc /scannow" in your command prompt while it is running in administrator mode. this was the same error that i got and turning off turbo boost fixed it, however, i also ran the command above after i turned turbo boost off and it reported back that it did fix the integrity of some system files. Last edited by cancelsarge on Jul 29, 2024, 6:16:29 PM
|
|