"
That post mistakenly states that this is mostly a Windows 24H2 issue. It is not a Windows issue. The issue arises from improper handling of System APIs by the PoE2 code. By misdiagnosing the issue, they won't be able to fix it. By not fixing that line in that statement, it implies that they are not working on the issue.
The developers have certainly a vast number of dxdiag reports in their hands. They can certainly determine that this is not only a 24H2 issue (which I agree it isnt). As a developer myself, I can assure you that you dont have to worry about that.
Also, during my own testing today, I can see a very clear pattern between server (over)load and theae crashes. I crashed 5 times within 3 minutes when the website was down this evening. Pretty sure that they have even a lot of telemetry data that our clients are sending to them before they crash and they have already started seing patterns.
This really feels like some kind of race condition since it looks like only highend systems crash.
|
Posted bym33ts4k0z#0771on Dec 17, 2024, 6:05:14 PM
|
"
"
That post mistakenly states that this is mostly a Windows 24H2 issue. It is not a Windows issue. The issue arises from improper handling of System APIs by the PoE2 code. By misdiagnosing the issue, they won't be able to fix it. By not fixing that line in that statement, it implies that they are not working on the issue.
The developers have certainly a vast number of dxdiag reports in their hands. They can certainly determine that this is not only a 24H2 issue (which I agree it isnt). As a developer myself, I can assure you that you dont have to worry about that.
Also, during my own testing today, I can see a very clear pattern between server (over)load and theae crashes. I crashed 5 times within 3 minutes when the website was down this evening. Pretty sure that they have even a lot of telemetry data that our clients are sending to them before they crash and they have already started seing patterns.
This really feels like some kind of race condition since it looks like only highend systems crash.
The developers did not check reports sent to them via cloud/drive. We can see that by looking at the access count.
The players who are under lvl 25 and/or haven't finished Act1 cannot DM. Their reports were never received.
So the only reports that were received would be direct messages which directly sends the entire dxdiag as a message. Now did they look at those? We don't know. What we do know is that they did not check dxdiags at cloud/drive.
The moment they realized this is not a Win11 24H2 issue they should have edited that part out. They do not edit that part out because it helps them to misguide people. In every crash thread we have tourists parroting "24H2 bad", we explain to them that we have crash reports from Win10, from Win11, from LINUX...
We have people that lost their hardware because PoE2 devs cooked their homemade Stuxnet-lite, the only difference is that one destroys centrifuges and the other destroys whatever it can get its hands on.
I cannot send/reply to direct messages because my in-game character has not finished Act 1.
What to do:
1)Write a short review about the hard crashes in notepad.
2)Copy and paste it to steam reviews, put up a negative review.
3)Copy and paste it to steam discussions, put it up there.
|
Posted byCainrith#2807on Dec 17, 2024, 9:27:17 PMOn Probation
|
As soon as I updated to 24H2, I had crashes when doing the Trial of the Sekhema during loading screens.
I have 2 monitors and likely also one time tabbed out to do something on the second monitor. The youtube video on the second monitor also froze entirely. I could not control my PC anymore, the mouse was moving every 3 seconds but nothing was responding when being clicked, also task manager would not open. So it crashed 2 times like this and I had hard reset my PC, by holding down the power button, same as it is stated in GGGs known problems list.
Afterwards I reverted the update and went back to 23H2 and had no more crashes ever since.
So whoever has these specific crashes and says it is not related to the update, has no idea.
I'm on a 7800X3D on Gigabyte B650 AORUS ELITE AX with EXPO profile enabled. The gpu is a 4080 with the Nvidia driver 566.36 . My fps limit in game is on 120 fps.
Ubisoft also is in contact with Microsoft about this 24H2 update, they only released a hotfix so far. My guess is that actually Microsoft has to release an update and not the games. I will never go on 24H2, when all kind of games that are unpatched have problems with multithreading.
All other people that generally have crashes might be affected by something else. But my PC is always set up in a very clean way with only the necessary drivers installed.
GeForce RTX 4080 SUPER
AMD Ryzen 7 7800X3D
32GB Ram DDR5-6000
|
|
"
As soon as I updated to 24H2, I had crashes when doing the Trial of the Sekhema during loading screens.
I have 2 monitors and likely also one time tabbed out to do something on the second monitor. The youtube video on the second monitor also froze entirely. I could not control my PC anymore, the mouse was moving every 3 seconds but nothing was responding when being clicked, also task manager would not open. So it crashed 2 times like this and I had hard reset my PC, by holding down the power button, same as it is stated in GGGs known problems list.
Afterwards I reverted the update and went back to 23H2 and had no more crashes ever since.
So whoever has these specific crashes and says it is not related to the update, has no idea.
I'm on a 7800X3D on Gigabyte B650 AORUS ELITE AX with EXPO profile enabled. The gpu is a 4080 with the Nvidia driver 566.36 . My fps limit in game is on 120 fps.
Ubisoft also is in contact with Microsoft about this 24H2 update, they only released a hotfix so far. My guess is that actually Microsoft has to release an update and not the games. I will never go on 24H2, when all kind of games that are unpatched have problems with multithreading.
All other people that generally have crashes might be affected by something else. But my PC is always set up in a very clean way with only the necessary drivers installed.
To anyone who is confused about the Windows 11 24H2 crashes:
That particular error Ubisoft and other games faced was that Windows' "New Feature" was blocking the program's access to system resources, therefore crashing the program but never crashing the PC itself.
The problem PoE2 has is that program is hogging all available system resources due improper usage of system APIs, therefore crashing the program AND the PC itself. (Technically it crashes the OS because OS can no longer get the resources it has to in order to function properly)
People are crashing on Win 10, Win 11, Linux. If PoE2 runs on an OS, there is someone here crashing on that OS.
I cannot send/reply to direct messages because my in-game character has not finished Act 1.
What to do:
1)Write a short review about the hard crashes in notepad.
2)Copy and paste it to steam reviews, put up a negative review.
3)Copy and paste it to steam discussions, put it up there.
|
Posted byCainrith#2807on Dec 18, 2024, 1:24:15 PMOn Probation
|
"
"
As soon as I updated to 24H2, I had crashes when doing the Trial of the Sekhema during loading screens.
I have 2 monitors and likely also one time tabbed out to do something on the second monitor. The youtube video on the second monitor also froze entirely. I could not control my PC anymore, the mouse was moving every 3 seconds but nothing was responding when being clicked, also task manager would not open. So it crashed 2 times like this and I had hard reset my PC, by holding down the power button, same as it is stated in GGGs known problems list.
Afterwards I reverted the update and went back to 23H2 and had no more crashes ever since.
So whoever has these specific crashes and says it is not related to the update, has no idea.
I'm on a 7800X3D on Gigabyte B650 AORUS ELITE AX with EXPO profile enabled. The gpu is a 4080 with the Nvidia driver 566.36 . My fps limit in game is on 120 fps.
Ubisoft also is in contact with Microsoft about this 24H2 update, they only released a hotfix so far. My guess is that actually Microsoft has to release an update and not the games. I will never go on 24H2, when all kind of games that are unpatched have problems with multithreading.
All other people that generally have crashes might be affected by something else. But my PC is always set up in a very clean way with only the necessary drivers installed.
To anyone who is confused about the Windows 11 24H2 crashes:
That particular error Ubisoft and other games faced was that Windows' "New Feature" was blocking the program's access to system resources, therefore crashing the program but never crashing the PC itself.
The problem PoE2 has is that program is hogging all available system resources due improper usage of system APIs, therefore crashing the program AND the PC itself. (Technically it crashes the OS because OS can no longer get the resources it has to in order to function properly)
People are crashing on Win 10, Win 11, Linux. If PoE2 runs on an OS, there is someone here crashing on that OS.
It all sounds understandable, but I was still playing with 23H2 at release and didn't have a single freeze in 50 hours. Then I unsuspectingly updated to 24H2 and stupidly deleted the windows.old folder, so I wouldn't be able to avoid a clean install. Since the update I've had nothing but problems. A friend of mine has the same setup (hardware, 1:1) and 23H2 and it runs like clockwork.
|
Posted by69oVerkill69#4406on Dec 18, 2024, 1:33:39 PM
|
"
"
"
As soon as I updated to 24H2, I had crashes when doing the Trial of the Sekhema during loading screens.
I have 2 monitors and likely also one time tabbed out to do something on the second monitor. The youtube video on the second monitor also froze entirely. I could not control my PC anymore, the mouse was moving every 3 seconds but nothing was responding when being clicked, also task manager would not open. So it crashed 2 times like this and I had hard reset my PC, by holding down the power button, same as it is stated in GGGs known problems list.
Afterwards I reverted the update and went back to 23H2 and had no more crashes ever since.
So whoever has these specific crashes and says it is not related to the update, has no idea.
I'm on a 7800X3D on Gigabyte B650 AORUS ELITE AX with EXPO profile enabled. The gpu is a 4080 with the Nvidia driver 566.36 . My fps limit in game is on 120 fps.
Ubisoft also is in contact with Microsoft about this 24H2 update, they only released a hotfix so far. My guess is that actually Microsoft has to release an update and not the games. I will never go on 24H2, when all kind of games that are unpatched have problems with multithreading.
All other people that generally have crashes might be affected by something else. But my PC is always set up in a very clean way with only the necessary drivers installed.
To anyone who is confused about the Windows 11 24H2 crashes:
That particular error Ubisoft and other games faced was that Windows' "New Feature" was blocking the program's access to system resources, therefore crashing the program but never crashing the PC itself.
The problem PoE2 has is that program is hogging all available system resources due improper usage of system APIs, therefore crashing the program AND the PC itself. (Technically it crashes the OS because OS can no longer get the resources it has to in order to function properly)
People are crashing on Win 10, Win 11, Linux. If PoE2 runs on an OS, there is someone here crashing on that OS.
It all sounds understandable, but I was still playing with 23H2 at release and didn't have a single freeze in 50 hours. Then I unsuspectingly updated to 24H2 and stupidly deleted the windows.old folder, so I wouldn't be able to avoid a clean install. Since the update I've had nothing but problems. A friend of mine has the same setup (hardware, 1:1) and 23H2 and it runs like clockwork.
You can check the main thread and see people there with 23H2 having problems. I have Win10 24H2, I crash.
This particular problem has nothing to do with Win11 other than being installed on it. PoE2 code has something in it that tries to use system APIs in a way they should not be used. This is the main cause of the freeze.
I cannot send/reply to direct messages because my in-game character has not finished Act 1.
What to do:
1)Write a short review about the hard crashes in notepad.
2)Copy and paste it to steam reviews, put up a negative review.
3)Copy and paste it to steam discussions, put it up there.
|
Posted byCainrith#2807on Dec 18, 2024, 2:01:32 PMOn Probation
|
So how is everyone doing after the patch? I seem to be doing much better so far. I’m hopeful that they fixed it. Seeing much less cpu usage and more gpu usage. Still get spikes of high cpu when loading zones but compared to before it’s a lot better so far.
|
Posted bydimmok#2997on Dec 18, 2024, 2:21:20 PM
|
"
So how is everyone doing after the patch? I seem to be doing much better so far. I’m hopeful that they fixed it. Seeing much less cpu usage and more gpu usage. Still get spikes of high cpu when loading zones but compared to before it’s a lot better so far.
Not good. Game still crashes. Check the main thread.
I cannot send/reply to direct messages because my in-game character has not finished Act 1.
What to do:
1)Write a short review about the hard crashes in notepad.
2)Copy and paste it to steam reviews, put up a negative review.
3)Copy and paste it to steam discussions, put it up there.
|
Posted byCainrith#2807on Dec 18, 2024, 2:31:52 PMOn Probation
|
Played 100h without a single crash. Updated to 24H2 and now game hard crashes once an hour or so.
PLEASE don't tell me it's not about Windows update when it DEFINITELY is (at least in my case)
Ryzen 7 3700X/2060 super/32GB RAM/Windows 11 24H2.
|
Posted bySasha_Fast#9104on Dec 18, 2024, 2:32:21 PM
|
"
"
So how is everyone doing after the patch? I seem to be doing much better so far. I’m hopeful that they fixed it. Seeing much less cpu usage and more gpu usage. Still get spikes of high cpu when loading zones but compared to before it’s a lot better so far.
Not good. Game still crashes. Check the main thread.
Yeah I spoke too soon. Just crashed hard. 😭
|
Posted bydimmok#2997on Dec 18, 2024, 7:30:33 PM
|