Hard crashing PC locks up

CPU: Intel i9-13900k
GPU: Nvidia RTX 4090 MSI Suprim
GPU Drivers: 565.77
GPU CUDA Version: 12.7
RAM: 64GB DDR5 @ 5600Mhz
Drive: Samsung 2TB 990 NVME
OS: Arch Linux, Hyprland

1. Game runs natively on Linux without having to use proton experimental or wine.
2. Game consistently freezes after 2+ hours of playtime
3. New bug with 0.1.0f where FPS now degrades after 1 hour of playtime rendering the game to be unplayable until I restart the game
4. CPU spikes between loading areas/map. Game freezes/crashes/fails to load during cogwheel (loading maps/areas)

These are the consistent issues I've had within the last 2 weeks.

1. 0.1.0f introduced a new FPS issue
2. CPU issues across the board need to be fixed asap

"

Sasha_Fast#9104 wrote:

"

Cainrith#2807 wrote:

Standard industry information. Ask any knowledgeable person about this issue and you'll receive an answer between 5 to 20 percent, some will underestimate and say 1% some will overestimate and say "if it happens a couple times in a row it is toast".

Also these numbers are only predicting the bricking event.

Shortened component lifespan? That happens no matter what.

Give me source for this standard industry information.

The source is being in the industry and gaining empirical know-how. Since no sane department would allow you to try and brick thousands of computers for this when the alternative is simply not going through incomplete shutdowns.

You can technically calculate it for yourself using information about components from their manuals, and ECE principles. But this will be long and arduous process so a better way would be to go to your local university's ECE department and ask about it.

Another possibility is to find a PSE and ask them about it but your answers will vary between overestimation and underestimation in this case because PSEs come in two kinds: Those who are awed by electricity and those who joke with electricity.

Furthermore, I ask anyone who sees this message to please give a negative review for Path of Exile 2 on Steam.

"

xqflint#0181 wrote:

Ok so if the problem is with the system and not the game, why am I getting the same errors on XBOX? I´m not a PC player.. look at the Xbox forum and you´ll understand.
We´re not running Windows 24whatever... we don´t even follow the same update schedule.

So you have a game that is freezing and crashing on multiple OS versions and systems, but you´re trying to convince us that the game is not the problem...

Gina.. go back to your desk and answer those customer complaints.. you´re not fooling anyone here.

PS: Before you say "oh, it´s microsoft"... here´s a link to the same complaints from PS5 players: https://www.pathofexile.com/forum/view-thread/3622972

1. XBOX OS is based on NT kernel and shares its low level architecture.

2. I already told, even if it happens on Linux, if the game runs through Proton / WINE (WINE as we know Is Not Emulator) which calls Win32 API.

3. Also, already told, the scope of the problem is around the layer between user and kernel mode driver modules dictated by the driver acrhitecture. This is the reason why it happens on multiple platforms because it shares the platform independent code.

4. It happens in some specific configruations, probably related to UEFI / ACPI but sure not limited by that. This is the reason why people with completely same configs have different result. Their configs differ but not from the average user point of view. Highly likely PoE 2 is only one of the few contributing factors.

5. If the entire environment crashes, the problem affects the whole system, because one of the purpose of the system (hardware + OS + all kernel stuff) is to protect itself from the crashes caused by the isolated limited user-space applications.

6. As for PS5 can you be more specific, because the topic starter complains on the different things.

I'd start to analyze the dumps (some users managed to saved them) and kd the stuff, but it takes A LOT OF EFFORTS knowing it's not something easily catchable. Debugging the kms is a masochism especially if you don't have source code.

"

blacksheepcosmo#0142 wrote:

2. Game consistently freezes after 2+ hours of playtime

Just the game or the system? Are you able to kill the process? Did it ever lead to Kernel Panic?

"

Nyek#6508 wrote:

Remind me again what is GGG's number 1 priority? Sorry you dont work for them but because they arent posting it about every second of the day to appease you they arent taking it seriously? Nobody as of yet has reported hardware bricking that I can see outside of a single post where the dude came back and said they were taking the mick. IF something is causing your system harm as a responsible consumer you stop doing it, if its getting to the point of destroying peoples equipment the fault lies with GGG but also the customer for being an idiot.

They aren't posting about it at all. What every second of the day are you talking about? And let us be honest here: This type of problem is the kind where you do daily updates.

Let me explain it so that there is no misunderstandings:
1) Even a single crash is enough to cause damage. Since the customer cannot know in advance whether they will crash or not before playing GGG should warn people that the game comes with this type of risk.

2) Customers are not responsible for knowing how damaging the hard crashes are, most do not. In the early pages of these threads people argued with me a lot when I presented this possibility and only after we reached week 2 people started to show up to threads and report parts they have lost. I don't understand how you cannot see the posts about the hardware damage on here, on steam, and on the other hard crash thread.

"

Nyek#6508 wrote:

They've communicated with us with pretty much every patch with the patch notes, do you want Johnathan to message you specifically? Like dont know exactly what is causing the issues and their best guess is something to do with multithreading and windows 24hz update which you can see from their latest and the previous patch notes and updates.

The patch notes do not contain any information about this particular crash.

The known issues post is a declaration not a communication. And it is a blatant attempt at blame shifting. We knew that it was not a Windows 11 24H2 problem when that post was posted. There were 100 pages of discussion(s) right here on the early access bug reports.

So seeing it up there still saying "mostly 24H2 issue" is vexing and shows their real priorities: Shift the blame. And it works if you let them. On steam, on here, we have people coming in daily to berate us to downgrade to 23H2. Thankfully they disappear when you ask them how to downgrade from Windows 10/Linux to Windows 11 23H2.

"

Nyek#6508 wrote:

The game is an EA access title, by its very description that means expect the game to not be complete IE bugs galore, software issues etc etc etc. The very tag itself is implied that things may go wrong the fact your going into every single post to post about negative reviews is just pathetic, we bought early access to a game to test it and push its limits both on our end and on their end, the devs have hit stumbling blocks that are impacting peoples abilities to play the game and they have fixed multiple crashing instances since this bug was brought to light. Stop being a child, it gets fixed when it gets fixed, in the mean time go touch grass their are more important things in life than spam whining on a games forums to post negative reviews, I paid for early access and that is exactly the experience I have received.

This is not an early access level bug. This is literally a malware tier. IF this was an indie game Steam would have forced refunds.

Just from you not getting banned, warned, or not getting this post have parts that are "[removed by support]"ed shows on whose orders you have come up here.

You keep saying "multiple crashing instances" to equate this crash to others. They are not equal.

Those crashes are crashes to desktop, harmless.

This crash is a hard crash requiring manual shutdown, harmful.

Again fixing a dozen harmless crashes cannot compare fixing one harmful crash.

And to repeat again: This is not an EA tier bug.

"

Nyek#6508 wrote:

You can see from any of the threads that people are posting multi difference crashes and clumping them all into single threads despite being different issues for alot of people but yea sure, show me a company in the history of ever that has dropped a game into early access and its been perfect from the get go

Once again: This is not "crashes general". This is for a specific type of crash, "hard crashing that cause PC lock up". The crash happens the exact same way for everyone, this is not a set of different crashes, when it happens you know it is this crash from the way it happens.

You keep saying "multiple crashing instances" to equate this crash to others. They are not equal.

Those crashes are crashes to desktop, harmless.

This crash is a hard crash requiring manual shutdown, harmful.

I can show you only one company in history of ever that has dropped a game into early access and it has been bricking PCs of their customers and they have decided to mokusatsu it: GGG.

You talk like we are facing basic inconveniences... This is not my x skill does not work bug, this is literally the game harms my PC "bug".

Furthermore, I ask anyone who sees this message to please give a negative review for Path of Exile 2 on Steam.

I changed to Windows 10 and everything is ok. 24h2 is a problem for many games
Does anyone have problems with Windows 10?

"

cursorTarget#1174 wrote:

"

xqflint#0181 wrote:

Ok so if the problem is with the system and not the game, why am I getting the same errors on XBOX? I´m not a PC player.. look at the Xbox forum and you´ll understand.
We´re not running Windows 24whatever... we don´t even follow the same update schedule.

So you have a game that is freezing and crashing on multiple OS versions and systems, but you´re trying to convince us that the game is not the problem...

Gina.. go back to your desk and answer those customer complaints.. you´re not fooling anyone here.

PS: Before you say "oh, it´s microsoft"... here´s a link to the same complaints from PS5 players: https://www.pathofexile.com/forum/view-thread/3622972

1. XBOX OS is based on NT kernel and shares its low level architecture.

2. I already told, even if it happens on Linux, if the game runs through Proton / WINE (WINE as we know Is Not Emulator) which calls Win32 API.

3. Also, already told, the scope of the problem is around the layer between user and kernel mode driver modules dictated by the driver acrhitecture. This is the reason why it happens on multiple platforms because it shares the platform independent code.

4. It happens in some specific configruations, probably related to UEFI / ACPI but sure not limited by that. This is the reason why people with completely same configs have different result. Their configs differ but not from the average user point of view. Highly likely PoE 2 is only one of the few contributing factors.

5. If the entire environment crashes, the problem affects the whole system, because one of the purpose of the system (hardware + OS + all kernel stuff) is to protect itself from the crashes caused by the isolated limited user-space applications.

6. As for PS5 can you be more specific, because the topic starter complains on the different things.

I'd start to analyze the dumps (some users managed to saved them) and kd the stuff, but it takes A LOT OF EFFORTS knowing it's not something easily catchable. Debugging the kms is a masochism especially if you don't have source code.

"

blacksheepcosmo#0142 wrote:

2. Game consistently freezes after 2+ hours of playtime

Just the game or the system? Are you able to kill the process? Did it ever lead to Kernel Panic?

Yeah I get your point but aren´t all the other games using the exact same architecture? Why are we only getting this type of crash on POE and we´re blaming the system? I can run every other game smoothly, so even if the architecture is one of the factors, it´s the game triggering the crash.

It´s still the game´s fault. I would blame my system if everything else was crashing as well.

Ive been playing nearly every day since the start of EA without any problems except for the Game closing itself without an error Message like 3 or 4 times.

However since the hotfix yesterday the Game will Crash my pc on startup before i Even get to the login screen. I did everything except fresh install of the Game and rolling back to older Windows but there doesnt seem to be a fix.

Ill just stop playing for now but i wish the devs would actually adress the issue.

"

Nyek#6508 wrote:

Nobody as of yet has reported hardware bricking that I can see outside of a single post where the dude came back and said they were taking the mick.

There's more than one, more than two and more than three. If you're really interested, between this 2 threads there has been more than 3 guys replying black screens, unability to boot or something else after repeated crashing. I was checking the threads daily from pages < 100 to 290 more or less, and we got a few hardware killed reports.

You can be as much belligerant as you want and whiteking to your heart's comptempt, but at least get your facts right.

"

vendetta1000#0781 wrote:

I changed to Windows 10 and everything is ok. 24h2 is a problem for many games
Does anyone have problems with Windows 10?

Its well known that even people on Linux are crashing, is a game problem, not the OS.

"

blacksheepcosmo#0142 wrote:

CPU: Intel i9-13900k
GPU: Nvidia RTX 4090 MSI Suprim
GPU Drivers: 565.77
GPU CUDA Version: 12.7
RAM: 64GB DDR5 @ 5600Mhz
Drive: Samsung 2TB 990 NVME
OS: Arch Linux, Hyprland

1. Game runs natively on Linux without having to use proton experimental or wine.
2. Game consistently freezes after 2+ hours of playtime
3. New bug with 0.1.0f where FPS now degrades after 1 hour of playtime rendering the game to be unplayable until I restart the game
4. CPU spikes between loading areas/map. Game freezes/crashes/fails to load during cogwheel (loading maps/areas)

These are the consistent issues I've had within the last 2 weeks.

1. 0.1.0f introduced a new FPS issue
2. CPU issues across the board need to be fixed asap

Hm it sounds like you should rollback the Windows 24H2 security update on your Linux machine. That'll fix it!