Hard crashing PC locks up

"

Seal4K#3569 wrote:

I'm back from the test.

Tested on Windows 11 23H2 clean install.
played 2 days with no PC freeze.

I think the problem only from Windows 11 24H2

Affirmative, if you're using a X3D CPU this is the best solution. Been playing a week straight no hard crashes.

Disable multithreading when porting. Anything that involves a loading screen. Reenable it after you load into an area.

"

atirad#4630 wrote:

"

Seal4K#3569 wrote:

I'm back from the test.

Tested on Windows 11 23H2 clean install.
played 2 days with no PC freeze.

I think the problem only from Windows 11 24H2

Affirmative, if you're using a X3D CPU this is the best solution. Been playing a week straight no hard crashes.

Not a guaranteed fix though unfortunately.

7800x3d

Tested on Windows 10 22H2 clean install.
Tested on Windows 11 22H2 clean install.
Tested on Windows 11 23H2 clean install.

Crash still happening almost instantly on load screens.

I have same issue, temporary fix is to disable multithreading before entering a loading screen / portal, keep it off in town etc then when I return back to combat I turn multithreading back on, zero crashes but it's a pain to have to do this.

Ryzon 7700x
4070 Super
Windows 11

"

GPython#5980 wrote:

I can't believe that you genuinely believe that an issue that's been happening to thousands of people for actual years isn't real because it's never happened to you. That makes sense!

I never told "it's not real". I dunno, maybe I am not clear enough. The entire point of my statement: there is some serious shit involved into the problem. And it is directly related to underlaying sub-systems of your OS.

It doesn't matter how long the problem persists. If it was never fixed in the past - the issue will appear again in the future. And that's what happened to some users. Debugging kms is not something trivial. Basically I hate that process even with the modern tools avalable like VMs and VirtualKD. It's definetely a hell for the GGG to deal with it. Especially if they don't have experience with the kernel stuff.

"

carljohnfranz#3708 wrote:

I have same issue, temporary fix is to disable multithreading before entering a loading screen / portal, keep it off in town etc then when I return back to combat I turn multithreading back on, zero crashes but it's a pain to have to do this.

Ryzon 7700x
4070 Super
Windows 11

I will try this one, since I dont want to disable it for my complete PC...

nice Idea

BES with a max utilization of 90% for the PoE process and I haven't had a single one of these freezes for the past 5 days.

"

GPython#5980 wrote:

"

atirad#4630 wrote:

"

Seal4K#3569 wrote:

I'm back from the test.

Tested on Windows 11 23H2 clean install.
played 2 days with no PC freeze.

I think the problem only from Windows 11 24H2

Affirmative, if you're using a X3D CPU this is the best solution. Been playing a week straight no hard crashes.

Not a guaranteed fix though unfortunately.

7800x3d

Tested on Windows 10 22H2 clean install.
Tested on Windows 11 22H2 clean install.
Tested on Windows 11 23H2 clean install.

Crash still happening almost instantly on load screens.

Are you getting the same crashes where the PC locks up with the mouse moving slowly and music still playing but PC is frozen? From what I'm seeing there's different types of crashes but that specific one was the crashes I was experiencing and Windows 23H2 has fixed it.

We are not here to protest windows implementation of cpu scheduling. We are here to report that GGG must upload a fix such that our PCs do no freeze JUST LIKE ALL THE OTHER GAMES
Do you understand this simple axiom

"

cursorTarget#1174 wrote:

"

GPython#5980 wrote:

It has nothing to do with Windows. This has been thoroughly tested over and over again for nearly a decade now. It is not hardware or software dependent. This is a GGG issue. Stop spreading misinformation.

U have no clue how the modern (and even older) operating systems work and interact with the hardware. People like you easy to trick to buy some trashy PSU or motherboard, or install "Top of the Best of the Best of the Best Windows" just for 200$.

As I have mentioned above, a failsafe is not a feature and should not be treated as such. Just because you have a seatbelt on and your car is equipped with an airbag doesn't mean its okay for you to crash.

"

cursorTarget#1174 wrote:

Learn at least basics and you will see how the internal kitchen of your OS is complex. If the game freezes your entire system, then your operating system (and device drivers) are ALLOWING this to happen due to some serious and unusual interaction within its kernel/devices. I already dropped the links to the basics, find some time to read.

An end user does not have any responsibility of learning how their OS works. In this case knowing it doesn't help though, because you only need basic reasoning skills to deduce that the problem is on PoE2/GGG: Does this happen with other games? Does this happen with other software? Does this happen with other games across different OS? Does this happen with other software across different OS?. The answers for these are NO. Therefore this problem, happening only with GGG's PoE2, is a PoE2 problem.

"

cursorTarget#1174 wrote:

PS I forgot.
After hard crash use chkdsk.exe to check your system drive manually to make sure there is no data corruption on your system partition

chkdsk /f <system_drive_name>
for ex:
chkdsk /f c:

This shows the extent of your knowledge and lack of understanding on your part. Honestly speaking the fact that you are being patronising on this thread despite the fact that your knowledge lead you to offer a non-hardware checking solution for a suspected hardware problem makes you look like a troll or a tool. Please stop harassing people in this thread.

"chkdsk /f c:" when there is hardware damage, running chkdsk /f c: may miss the issue(I use "may" sparingly here, it will miss it in most cases), potentially reporting that no problems were found. This is because the /f parameter focuses exclusively on logical file system errors rather than assessing the physical health of the storage medium.

For example On SSDs, sudden power loss can lead to corrupted flash cells or degraded performance in specific regions of the drive. This would not be identified by chkdsk /f.

To add, issues with the drive’s controller or firmware are beyond the scope of chkdsk altogether, as they pertain to hardware rather than the file system.

In this case they should be using chkdsk /r. BUT: chkdsk /r must be used sparingly, as the physical sector check may cause unnecessary wear. There is also the fact that SSDs handle bad sectors differently using internal wear-leveling mechanisms.

To check an SSD for problems a better approach would be to use its own software (SMART softwares). In SMART the user can see "Reallocated Sectors" which indicate the number of bad sectors replaced with spare sectors. "Wear Leveling Count" which shows how much wear the SSD has experienced. "Uncorrectable Errors" which shows read/write errors that cannot be corrected. And "Percentage Lifetime Used" shows how much of the SSD's life span has been consumed.