POE 2 Complete PC Freeze while loading screen

"

SId6Niner#4689 wrote:

More bootlicking. Here is my opinion, people paid for access. They don't have access. They can't play the game. Glad I escaped paying this time due to my previous support. I feel horrible for the people that paid and are experiencing this issue alongside me.

What exactly drives you to post nonstop in these threads doing nothing but **** riding? How much are you getting paid?

You paid for what you paid - for buggy ang glitchy Early Access. You got some points over that, so it's not just access to EA. It's not good that you can't play the game but you accepted the risk. Want to have polished game - wait until release date and don't act like a kid, take responsibility for your actions. This bug eventually will be fixed, play something else or spend your time with the family. It's not neccessary to be angry because of some random videogame.

"

Hidefury#7456 wrote:

Shame is still not fixed. Happy New Year BTW. GGG are you open this year? I understand that you made "good" but your response on this important issue with the game is disgusting :(

Seriously bad form from GGG.

Im on 23H2 and have the issue, many have reported the same.

"

Epies#7036 wrote:

"

Randair#6971 wrote:

"

cursorTarget#1174 wrote:

566.36 is the latest non-beta. Where did you find the new driver?

https://nvidia.custhelp.com/app/answers/detail/a_id/5608/

https://international-gfe.download.nvidia.com/Windows/566.45hf/566.45-desktop-notebook-win10-win11-64bit-international-dch.hf1.exe

566.45 it's hotfix by nvidia

Thanks for posting the links to the hotfix driver. I will be installing it to see if it further improves the game. Hopefully more people try this and have good results!

"

Epies#7036 wrote:

After tens of crashes, I've decided to finally revert to Windows 11 23H2 to see if that fixes it for me.

These are my current specs:

4070 Super
i7-8700k
64GB RAM
Windows 11 Pro 23H2

I'll report back in about two days if my issue has been solved, or as soon as I crash again.

It's been a few weeks since I've reverted from 24H2 to 23H2 and haven't had a crash since. I suggest other people try this as well, however sucky resetting your PC is. It didn't just improve POE but increased stability across other games and programs as well.

Apparently for me the BIOS update did a fix. Now I saw only 1 freeze of game instead of whole pc. AMD B650i R5 7500F & RTX 4070 TI

"

Cainrith#2807 wrote:

Those terms and the law behind them are based on a philosophy, which is also the base of ethics of software engineering.

For the remainder you can use what I've written before and do your own reading to further your knowledge. This way you can fix your understanding.

From the programmers perspective, user application must be limited, isolated, they are buggy by default. Just accept it as fact and build your system around that. Fortunately, 99% or more of professional programmers have already adopted this paradigm. Never ever trust user mode applications. They always try to brick your system. ALWAYS! I still remember DOS times, it was basically hell. Every single exception, software interrupt with unrecoverable error (like zero divisor), deadlock and / or race condition cause the total system hang up despite you're using "good faith" application.

After reboot, you may find that the hard drive is damaged because the heads weren't parked properly and there was no way to park it with diskmon /park when your "OS" (it's a mess, not OS) is hang up. And those FAT error. Old story, again and again, you had to use something like NDD or similar tools.

No thanks, fed enough with that shit. Put that mad "kid" in his jail without windows and lock him inside not letting to ruin the house. Let him raze himself, in his local virtual address space. The entire industry is working exactly in that direction, not vice versa and not standing still. The problem with the growing complexity of the code, with millions of millons lines of code. And this is the primary reason why we still has bugs like this one, not because we don't follow the guidelines and philosophy. The things became too sophisticated over time.

"

Cainrith#2807 wrote:

When creating systems you must balance functionality with security.

It depends on the layer. If we are talking about kernel mode and the OS kernel itself the security must be as close as possible to ideal. Because it's critical part of the OS. If you mess with it, someday your user space program will corrupt your memory or will be exploited by the hackers / cheater like it happened with lsass.exe in Windows 7. After attacking lsass.exe the attacker got the SYSTEM privileges and was able to bypass BE kernel routines preventing the calling of OpenProcess() on arma3.exe and using the protected handles. And you know what happened? Microsoft patched that vulnerability, they didn't ask the cheaters not to abuse the design flaw.

"

Cainrith#2807 wrote:

This is what I've said. The problem in this case is the buggy program. But the program is buggy and if it was not, it would be able to make use of its privileges to provide the service, which its creators designed it in good-faith to provide.

Every single modern desktop OS developed in mind that the user mode app will be buggy as PoE 2 is. It's just reality. So made your OS stable enough to protect itself from the idiots. If you can't, your OS is utter garbage, or the drivers, or UEFI, or altogether.

"

Cainrith#2807 wrote:

I thought about using trusted provider

Okay. Installing the product using "trusted installer" or source doesn't make the product stable, bugless or trustful, because of human errors. With high probability you won't be attacked by that sort of product but the program can consist vulnerabilities and holes. Organizations like Steam Lab or Microsoft WHQL perform limited testing and do not guarantee 100% stability. What happened with the Cyberpunk 2077 and Kingdom Come: Deliverance? Total bugfest, crashs, freezes, including BSODs, because of new "game-ready" drivers, total mess.

Is it possible to write bugless code? Yes, it is possible. And I can tell you how to do that. But this paradigm is completely incompatible with the desktop application market.

"

Cainrith#2807 wrote:

Let me run you through this simple logic:
1) The crash occurs.
2) The crash occurs on NVIDIA.
3) The crash occurs on AMD.
4) The crash occurs on NVIDIA and AMD.

Due to crash happening with the same style, it is obvious that its source is beyond the GPU driver. The only thing that might have been done by NVIDIA is to somehow work around the source of the crash.

We have many people that don't crash. And they are using very similar configurations with the people affected by the bug. Also we didn't see reports from the users with integrated video and the users with Intel Arc. The problem persisted for years outside the PoE 1/2, when you dealt with the shader processing, especially for UE developers.

"

Cainrith#2807 wrote:

However the crash they are referring to is most likely one of the NVIDIA crashes (Broadcast crash, PoE1 = PoE2 crash, failed to create texture crash, high power use coupled with thermal crash, and so on...).

If it was mistakenly posted in separate inherited thread by NVIDIA Representative, shame on him. But whoever has access to ring 0 is responsible for the interrupts being ignored and not handled properly / or any system routines with the higher priority than any user mode process. Let PoE 2 process CTD, but only PoE 2, not the OS.

"

Cainrith#2807 wrote:

Weird how you keep dodging it. None of your messages ever provided helpful information to anyone. You keep minimizing GGGs responsibilities. You constantly attack anyone who ever criticized GGG on this issue. In fact the reason I first had to correct you was because you were using faulty information to browbeat someone.

Yeah, before I proposed to use the windows feature manually you were SILENT and didn't tell anyone to disable it. Interesting, why? autochk.exe executed AUTOMATICALLY by the Task Scheduler. And why were you silent? Huh?

Also I already told why that situation happened. I have some information that I can't post here on the forums but it explains a lot why it is happened, why they left community right after rolling EA out.

Here's hoping that upon the return from the holidays, we get some clear communication about this issue, including the fact that it affects those of us on 23H2 too.

"

cursorTarget#1174 wrote:

You paid for what you paid - for buggy ang glitchy Early Access. You got some points over that, so it's not just access to EA. It's not good that you can't play the game but you accepted the risk. Want to have polished game - wait until release date and don't act like a kid, take responsibility for your actions. This bug eventually will be fixed, play something else or spend your time with the family. It's not neccessary to be angry because of some random videogame.

Except it's not buggy/glitchy EA, it's straight up broken. Nobody in this thread is complaining about not getting a "polished" game. It's unplayable at the lowest possible settings.

The expectation GGG set was for EA to be focused on refining/improving endgame. The issues in this thread effectively brick your character after completing the campaign. I can't do my 3rd/4th asc because the game crashes every 1-5min and mapping is completely out of the question.

On a 12900K/4090, this is ridiculous...

I found a fix that corrected this issue for me, so I figured I post it here. Installing the Nvidia "studio" driver instead of the "game ready" driver has completely eliminated the lag spikes and crashes. You can find this from the pull-down box at the top of the Drivers area in the Nvidia app.

3 weeks and still freezing my pc, fix your game ggg.

I've been watching this post for a while and haven't played the game in about 2 weeks because of this issue. Even with the limited coding knowledge I have (I took about a years worth of programming classes in college), these symptoms point to an infinite loop of sorts and is NOT a Windows issue and is most definitely some sort of coding issue. Also being that its happening in both PoE 1 and 2 is probably some legacy code that got ported into PoE 2. You guys defending GGG saying its not their problem look pretty stupid.