Hard crashing PC locks up

"

Waiden#9514 escreveu:

"

Seal4K#3569 escreveu:

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

Same, made clean 23H2 Win installation and had zero freezes since yestared. Normally I would have like 20.

I am on 23h2 and have a million crashes. Tried BES @ -10 and no luck there either.

"

cursorTarget#1174 escreveu:

Blame the developers of underlying layers of your system, including vendors and uefi devs. They are responsible for the hard crashes when USER MODE application crashes.

[/quote]
Like do you want to see the list of games that does not freeze your PC on a REGULAR BASIS?

We are not here to blame nor protest their implementations. We here to help each other troubleshoot and help GGG to expedite the fix or give them signal to focus on for their process.

So to the people coming in:
No effective solutions for the freeze. Your specs are irrelevant. Your OS version is irrelevant. We are just waiting for GGGs remedy or actual fix

Has anyone with hard freezes tried dual-booting a Linux distro to play PoE2? I'm considering it.

"

Fizz000#1161 escreveu:

Has anyone with hard freezes tried dual-booting a Linux distro to play PoE2? I'm considering it.

Someone posted that they were crashing even on Linux.

I imagine they're going to take another swing at these crash issues in a patch tonight.

Here CRASH CRASH CRASH...and CRASH......

"

Oonue#2226 escreveu:

GGG's USER MODE application seems to think it needs 100% of every CPU core every random amount of loading screens somehow even knocking the OS out before it can even get an event out in event viewer. Haven't seen any other legitimate application pull that off in at least 20 years.

Something is seriously wrong with how they handle multithreading and blaming everyone else isn't going to fix it.

Stress tests like OCCT, CPU-bound applications. User mode applications eat as much CPU as the OS allows them to. It's ok if your CPU loaded at 100%. It's not OK if your OS crashes because of that. Also we don't know exact reason of this hang up.

Go and get info how user mode programs interact with the hardware.

"

GPython#5980 escreveu:

he doesn't personally believe in

Out of touch.

"

GPython#5980 escreveu:

! Don't forget also trying to pretend its entirely everyone's own fault instead of the clearly well documented, wide-reaching, and longstanding fault with GGG's games! Very productive!

Oh really? Can you please write to GGG your assumption so they fix the problem if it's SO EASY and well documented. Can we at least have the docs with detailed explanation of what happening on kernel (or lower) level at that moment? I am expecting something like this.

I would just ignore anyone here who is trying to advise that it is your PC. While they might even be correct, it is not going to be for everyone experiencing the exact same crash. It would be far wiser, instead of engaging in pointless replies to these people, to just ignore and watch for official updates.

"

cursorTarget#1174 escreveu:

"

Oonue#2226 escreveu:

GGG's USER MODE application seems to think it needs 100% of every CPU core every random amount of loading screens somehow even knocking the OS out before it can even get an event out in event viewer. Haven't seen any other legitimate application pull that off in at least 20 years.

Something is seriously wrong with how they handle multithreading and blaming everyone else isn't going to fix it.

Stress tests like OCCT, CPU-bound applications. User mode applications eat as much CPU as the OS allows them to. It's ok if your CPU loaded at 100%. It's not OK if your OS crashes because of that. Also we don't know exact reason of this hang up.

Go and get info how user mode programs interact with the hardware.

"

GPython#5980 escreveu:

he doesn't personally believe in

Out of touch.

"

GPython#5980 escreveu:

! Don't forget also trying to pretend its entirely everyone's own fault instead of the clearly well documented, wide-reaching, and longstanding fault with GGG's games! Very productive!

Oh really? Can you please write to GGG your assumption so the fix the problem if it's SO EASY and well documented. Can we at least have the docs with detailed explanation of what happening on kernel (or lower) level at that moment?

I understand what you're doing and trying to accomplish, but I think you need to give it a rest at this point. There are way to many instances proving this is not a personal computer issue and directly pointing to the common denominator here which is that this is only happening with POE2 EA. I play a ton of different games. Repeating what's already been said further; this ONLY HAPPENS with POE2. Period. Again - Common denominator.

Just because it could be a Windows issue doesn't mean it is.
Just because it could be a GGG issue doesn't mean it is.

We don't have enough information. Or maybe point me in the direction of someone who has actual data in case I missed it. GGG are the only ones who may have insight. Making a straw man argument and trying to defend it, either way, is pointless. Despite hundreds of pages in several threads so far, nobody really knows jack. Shader caches? Maybe. Vulkan? Maybe. DX12? Maybe. Windows 24H2? Maybe. Etc.

I don't think any of us are going to be able to do GGG's job for them, sadly. Pray for a good patch tonight.

"

cursorTarget#1174 escreveu:

It's "AS IS" software, you accept the risks.

As is software does not work like that in theory or practice. Both in USA and EU there are laws that specify unreasonable risks, which crashes due to software actually count as. "As is" does not cover faulty software that goes beyond typical expectations for software defects and cause possible hardware damage. You would find that courts may find that such risks exceed the reasonable scope.

"

cursorTarget#1174 escreveu:

"

Cainrith#2807 escreveu:

You are on a topic discussing potential hardware damage and offer a solution that not only does not check for hardware damage but would most probably miss it. Therefore it looks like you are trying to be misleading on purpose -if you are knowledgeable- or if we were to give you the benefit of doubt, simple inadequacy and being way over your head.

It's recommended way by Microsoft to check integrity of the file system. And yes, in this case you also accept all risks. Windows do it automatically from time to time.

What you suggested, "chkdsk /f" is for fixing logical file system errors on the drive. It has no chance of actually catching a hardware error. It will either correct the file system inconsistency temporarily (but will cause further problems down in the line) or fail entirely. And best case here is it failing entirely.

What the topic was: Checking for Hardware Damages, Hardware related problems.

What you should have suggested but did not: "chkdsk /r" which includes all the functionality of /f but goes further by checking for bad sectors on the drive. For hardware issues however, it is 2025 and most people are using SSDs, hence you should have mentioned SMART software instead.

The risks of repeated use of chkdsk is known and that is why it is not recommended to use this function repeatedly. Using it once in a while is not the case in this thread where crashes occur frequently during a single day's play session.

Please stop cluttering this thread any further and stop harassing people by your half baked knowledge about issues. Please stop telling people to "Go and get info how user mode programs interact with the hardware." when you don't even understand the difference between simple chkdsk commands.

Enough is enough. Go away.