Hard crashing PC locks up

WARNING: It's not safe to play PoE 2 right now, it's gonna fry your PC in some areas of the game, like in the ACT 2 Caravan, the game is not optimized at all and I'm not willing to risk my PC just to play a game!

"

Waiden#9514 wrote:

Sure, I believe there are users on Win 10, Win 11 22H2 or 23H2 with loading screen freezes, but those might be caused by other reason, maybe faulty hardware, overclock, corrupted or not up-to-date drivers. Anyone who is on 24H2 and experience freezes and would like to play POE 2, should try 23H2, might work and might not.

2 hours it takes to create Win ISO and clean Windows installation is worth the shot.

How do you explain that full lock ups started for me only after December 9 patch? 24 update installed month ago, or even more.

Also, ofc its mostly 24 update, coause MOST users keep theyr OS and drivers up to date.

"

luizdoc#0279 wrote:

WARNING: It's not safe to play PoE 2 right now, it's gonna fry your PC in some areas of the game, like in the ACT 2 Caravan, the game is not optimized at all and I'm not willing to risk my PC just to play a game!

Ok, lets chill. Your PC isn't going to explode.

At most, what's going to happen is that your Windows installation gets corrupted and you might have to reinstall, with a low chance of happening.

My PC is hard-freezing after updating to 24H2 when playing Path of Exile 2. It was fine before the update. The game locks up and the only way to fix it is hard-restarting the PC entirely.

It's happened when loading the game, or fighting enemies, or just walking around, seems completely random.

Game is not playable until either GGG or MS fixes it.

"

Shirofune#6303 wrote:

"

luizdoc#0279 wrote:

WARNING: It's not safe to play PoE 2 right now, it's gonna fry your PC in some areas of the game, like in the ACT 2 Caravan, the game is not optimized at all and I'm not willing to risk my PC just to play a game!

Ok, lets chill. Your PC isn't going to explode.

At most, what's going to happen is that your Windows installation gets corrupted and you might have to reinstall, with a low chance of happening.

Incompleteness of shutdown process interrupts system operations, which can interrupt critical tasks leading to data corruption. Even with modern file systems, an abrupt shutdown may leave temporary files or critical system configurations in an inconsistent state, requiring repairs during the next boot.

In mechanical drives, a forced shutdown could interrupt the normal parking of the read/write head, potentially causing minor wear. While rare, repeated occurrences could increase the risk of a catastrophic "head crash", a severe mechanical failure in a HDDs that occurs when the read/write head, which hovers right above the spinning platters, comes into direct physical contact with the platter surface. Since the platters are coated with a thin magnetic material used to store data, any contact with the head can cause permanent physical damage and data loss.

For SSDs, which lack moving parts, and rely on firmware to manage data, if a forced shutdown interrupts critical internal operations (like garbage collection or wear leveling), it could result in data loss or even firmware corruption.

There is also electrostatic and capacitive effects. The key here is "Charge Imbalance". Capacitors in power circuitry store charge. A sudden shutdown might not allow for controlled discharge, which could affect components over time due to uneven stress cycles.

Another problem you might encounter is with all-in-one (AIO) liquid cooling systems. In these the pump is responsible for circulating coolant through the loop. An abrupt power cut halts the pump's operation instantly, which can leave coolant stagnant in the system. Stagnant coolant may allow air bubbles that were previously suspended in the liquid to collect in the pump or tubing. When the system restarts, these bubbles can disrupt the normal flow of the coolant, causing cavitation (tiny air pockets in the pump), which manifests as unusual sounds like gurgling, grinding, or rattling.

In some other cases where the cooler was already on its last legs, if the liquid cooler contains any sediment or impurities, sudden stops could lead to clogging in the radiator or pump, potentially resulting in noise or reduced performance. I am mentioning this because there is a person in this very thread that was talking about "weird sounds" from his cooler so when I read that I thought about what might have caused it.

There is also how this crash is (supposedly) happening in the first place: 100% CPU utilization. This happens in a spike format. A sudden spike to 100% CPU utilization generates significant heat in a short period. If the system crashes at this point, the CPU may remain hot while cooling mechanisms (fans or pumps) that should have been dissipating heat are not functioning because forcing a shutdown stops cooling systems immediately. The residual heat can cause localized overheating, particularly in the CPU die (and Voltage Regulator Modules on the motherboard). Repeated instances increase the risk of thermal degradation.

The sudden power-off may induce transient voltage fluctuations, which can harm sensitive components like the CPU, GPU, or motherboard power circuitry. These components are especially vulnerable during high load conditions.

There is also the capacitor strain: The power delivery systems on the motherboard and power supply unit (PSU) experience increased strain during peak utilization. Abrupt shutdowns can exacerbate this strain, leading to shortened component lifespan.

For air-cooled systems, fans running at high speeds during 100% CPU utilization experience mechanical stress when stopped abruptly. Over time, this can degrade fan bearings or motors.

For any component that is already on its last legs, an event that would lead to shortened component lifespan might be the finishing blow.

And remember, this is not once in a while event, these crashes happen frequently, with short intervals(if one keeps playing the game after the crash and crashes again and again and again).

Please stop spreading misinformation.

My poe2 client crashes when reaching 6gb ram usage, something is leaking memory hard. Leaks can be very hard to nail, especially on a barebone C++ code. Good thing is, leaks may depend on what you use in game, which is why it crashes more often for different players. Compare notes and you may help devs nail it.

If it were 24h2 why do people have the problem persist on W10 or 23h2? I have no crashes in Helldivers or Hunt showdown. It's just poe 2.

"

Echothesis#7320 wrote:

My poe2 client crashes when reaching 6gb ram usage, something is leaking memory hard. Leaks can be very hard to nail, especially on a barebone C++ code. Good thing is, leaks may depend on what you use in game, which is why it crashes more often for different players. Compare notes and you may help devs nail it.

Only if they are actually trying to fix the issue. They did not even check DxDiag of one person that sent it, I would guess that they have done the same to many others as well.

How do you know that they didn't check any DxDiag?

"

Pyroga#2822 wrote:

How do you know that they didn't check any DxDiag?

I see access history in Google Drive (since there is no way to attach files directly in PMs; at least I didn't find one).