Crash to desktop on launch

and it seems like now I am seeing more and more people posting with mystery CTD and no solution.

I really wish there was a way to ping a dev or get some sort of feedback
From my log file I am getting these errors

2023/05/14 23:29:58 228890 7bb478d [CRIT Client 5972] [BUNDLE2] Failed to Oodle decompress (corrupted data). [From 11222347 bytes to 262144 bytes.]

[CRIT Client 10488] [BUNDLE2] Failed to Oodle decompress (corrupted data). [From 14637671 bytes to 262144 bytes.]

[CRIT Client 20532] [BUNDLE2] Failed to Oodle decompress (corrupted data). [From 1921420 bytes to 262144 bytes.]

[CRIT Client 20532] [BUNDLE2] Failed to Oodle decompress (corrupted data). [From 14637671 bytes to 262144 bytes.]

[WARN Client 20532] tool_settings.json was not found. Resetting to default settings.
First of all, as a level 3 IT application analyst it pains me greatly to see people suggest deleting the production INI file. Rename it! Same effect without losing precious settings in case you narrow down the cause.

As for not having audio enhancements, that's not going to apply to your problem because the errors read corruption of shader cache and/or files.

Are you copying the same install folder over to the new computer? Has this been fully downloaded from scratch multiple times with the same issue?

Spoiler=How to view event logs & export for sharing
Spoiler

Open Event Viewer, Windows Logs, Application,

From right-hand pane, click "Filter Current Log..."

In "Filter Current Log" window, Change dropdown for "Logged" to 30 days. Check the "Warning" and "Error" check-boxes, hit OK.

The log should be easier to read & pinpoint any APPCRASH related events.


If you want to post it, from right-hand pane in EventViewer, you can "Save Filtered Log As..." and save it as .evtx file. It'll be big, so right click the file & ZIP, then attach with your preferred file sharing service.
Last edited by raz0rh00f on May 17, 2023, 4:01:10 PM
Sorry to hear about your father-in-law.

I missed the part of this conversation regarding HDDs being swapped between computers. This almost guarantees the HDD and/or the data on that HDD is bad. Might have corrupted sectors.

A quick and dirty fix to get PoE working today on your rig is to install a secondary HDD in the computer, uninstall PoE from current location, re-install PoE, changing install location to the secondary HDD. Run the client & download PoE fresh to the new drive. Since your partner's machine has a good copy of the data, you could also drag & drop that install folder onto the secondary HDD.

The HDD likely has issues & either needs to be RMA'ed or possibly repaired via firmware update. You would need to know the model number of the HDD to have this done.
here is what I have tried so far.

poe installed on my main drive in my cpu:crashes

poe installed on my partners drive in her pc:fine

poe installed on my partners drive in my PC:crash

poe installed on my drive in her PC:fine

poe installed on new samsung 980 pro in my cpu:crash

swapping that drive into her pc, fine

I also took my old HDD from before I built this new PC a month or so ago that ran poe fine and I CTD on launch after it updated
Last edited by ImGryssLOL on May 17, 2023, 6:30:42 PM
"
raz0rh00f wrote:


Are you copying the same install folder over to the new computer? Has this been fully downloaded from scratch multiple times with the same issue?



fresh install every time. DL either through steam or stand alone client
"
raz0rh00f wrote:

Spoiler=How to view event logs & export for sharing
Spoiler

Open Event Viewer, Windows Logs, Application,

From right-hand pane, click "Filter Current Log..."

In "Filter Current Log" window, Change dropdown for "Logged" to 30 days. Check the "Warning" and "Error" check-boxes, hit OK.

The log should be easier to read & pinpoint any APPCRASH related events.


If you want to post it, from right-hand pane in EventViewer, you can "Save Filtered Log As..." and save it as .evtx file. It'll be big, so right click the file & ZIP, then attach with your preferred file sharing service.


Faulting application name: PathOfExileSteam.exe, version: 0.0.0.0, time stamp: 0x64545bb0
Faulting module name: KERNELBASE.dll, version: 10.0.22621.1635, time stamp: 0x61869dd2
Exception code: 0xe0000001
Fault offset: 0x000000000006536c
Faulting process id: 0x0x44FC
Faulting application start time: 0x0x1D9890F3A90002E
Faulting application path: D:\SteamLibrary\steamapps\common\Path of Exile\PathOfExileSteam.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: ad8269b4-b82e-4ef5-ad76-f4cf0c3336b8
Faulting package full name:
Faulting package-relative application ID:

I can post the whole file if you think it would help, I can put it on google drive or something
https://drive.google.com/file/d/1kUxkbtdINSzANmanPV89e1vMtaY9KZQK/view?usp=sharing

I think that should be it
Last edited by ImGryssLOL on May 17, 2023, 6:50:03 PM
Whom ever used a vall orb on my oodles can go fly a kite
Faulting application name: PathOfExileSteam.exe, version: 0.0.0.0, time stamp: 0x64545bb0
Faulting module name: KERNELBASE.dll, version: 10.0.22621.1635, time stamp: 0x61869dd2
Exception code: 0xe0000001
Fault offset: 0x000000000006536c
Faulting process id: 0x0x2450
Faulting application start time: 0x0x1D9893E2E119C05
Faulting application path: D:\steam\steamapps\common\Path of Exile\PathOfExileSteam.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 6532ef1a-f6a2-4195-a4d4-3812bea6d818
Faulting package full name:
Faulting package-relative application ID:

do you think it would be worthwhile to try a fresh windows install on D? even though poe is on the new drive windows isn't

Report Forum Post

Report Account:

Report Type

Additional Info