POE 2 Complete PC Freeze while loading screen
" how many? probably a couple hundred i didn't count them i can't give a precise number. how did i know? asking the client when and how the problem started happening. what kinda problems ? everything from computers freezing, crashing, blue screen, keyboard and mouse stopped working or simply just critical system functions that stopped working there is many many more. why does this happen? because by setting for example path of exile priority to realtime you are essentially telling that program to take complete control over your CPU that's why a bunch of other stuff "CAN" give you problems. you didn't get these problems ever? LUCKY YOU! that doesn't mean that it hasn't yeeted a good amount of computers again, don't believe me? FINE! use it. not my problem. just warning people that it " CAN " cause trouble. does it happen to everyone? no. still take this realtime priority thing with caution. why would i lie about something as simple as this. lmao makes 0 sense i am simply just warning people that leaving your game for hours on realtime priority can cause issues i have seen it a lot with my own eyes from my clients. |
|
Uff-Da. 208 pages. I had this in POE1 and my workaround there is working here.
The consistent program/app I have open was brave, while having YouTube loaded/playing/paused. On PE1 I'd switch to DX-11, but this is not really an option in POE2. System: Laptop -Nvidia RTX4070 GPU -AMD Ryzen 7000 CPU -2nd monitor connected by HDMI - This is what I play on After forced re-boot: Let windows load Run POE 1/2 (before anything else) Move to preferred monitor, save, close, re-launch POE, and now one can open other programs. I usually lock my PC. However, if it is re-started I do have to repeat the process. |
|
This is day 21...
Furthermore, I ask anyone who sees this message to please give a negative review for Path of Exile 2 on Steam. |
|
" I test this solution, works for me, i play several hours without any crashes/frezzes. tks |
|
" I got 2 days of no crashes with disabling CORE0 and CORE1 every PoE startup, until today when the game made the PC freeze like 2 times. Testing @Lordrayearth's suggestion. I am ... almost done. |
|
" Couple of hundreds machines were damaged because your clients set the Real Time Priority for the processes? Not because they already had failed cooling system or messed up with the fan profile in UEFI Setup? I am not saying you are liar but you made a very far-reaching statement that setting rela-time priority can damage the system. Without any explanation in which situation it may happen. Let me explain. 1. Real Time priority doesn't override the ring 0 priority as the other guy already told above. The system has access to all its critical functionality via System Interrupts. The entire ring 0 has higher priority over everything in your system. This is how concept of preemptive multitasking implemented in the all modern OS. The OS always has control over any process, even if it's "Real Time" because interrupts (for the instance from System Timer) fires and the scheduler code starts to execute. Your CPU forcefully switches to execute the code in privileged kernel mode, stopping the current executing of your user mode program. Even more Interrupts can interrupt themselves executing interrupt handler with higher priority (lower IRQL). 2. Fan Control is managed by your UEFI, and the core part is I/O chip (or module). It was introduced on purpose to separate CPU from the controlling critical system in case if it is loaded to 100% and doesn't process interrupts. For example if cli command has been executed and then you loaded CPU with some heavy tasks stressing FPU for example. In this case CPU will not respond, because executing ring 0 code will never be interrupted by incoming hardware interrupts. And thanks to the motherboard / UEFI design (and the engineers), your CPU won't melt down, because the Fan Control is managed by the independed system. 3. If you mess with the profile, you still can damage your CPU even with such design by manipulating UEFI_FSL and UEFI_FIF ACPI objects via your user mode + kernel mode programs. It allows to change the fan profile dynamically via "average joe fan control program" but in this case it's completely user fault if he messed the things up. 4. Throttling. The last hope. Modern CPUs will reduce their clock frequency bellow the base in case of Tmaxop (maximum operational temperature) reached. It's not very reliable if the T spiked to the higher level in very short period of time but still. So, setting PoE to Real Time won't result in one program hogging your entire CPU by the single program, but from my point of view it's useless since we have some response from NVIDIA Representative. Just another one "bandaid". It may help to some users, but it's not actual fix. Yes, you will probably experience "freeze"-like with your keysboard, mouse, window moving but it's not something that can damage the system if it doesn't have internal defect or you changed your profile intentially to burn your CPU. |
|
I have to say, RealTime as a workaround to the freezing loading screens has been giving me issues. It has also given me issues when done thu PoEUnlocker 1.0.2 version. It gave me issues I never had before, not even with the first version of the program.
It DOES fix the freeze every time, and allows the game to keep running, however it very often completely messes up the sound of my computer, making it distorted, almost bass boosted and crackly, and led to a single bluescreen citing the usual overclock fail BSOD message, likely something being too much for the -30 PBO2 offset I had, whatever it did. The sound issue is likely just the driver or the interface of my external audio interface being messed up and is fixed by a restart or unplugging and replugging it, though the BSOD is annoying. Hence why I prefer to still use the 1.0.0 version without that feature, it's better for my setup that the game just freezes fully than the other issues that are popping up when it adjusts Real Time Priority. It's not a big deal, and I don't know if it can physically damage parts or cause any lasting issues, but I just wanted to add some credit and weight to that Real Time isn't a solution without risks or problems. |
|
" Why do you refer to UEFI? Did you mean BIOS? Or is it something else? Isn't BIOS executed on my CPU so it can stuck completely? |
|
" Yes, chatgpt. The LLM that is totally never making up shit because it's just that. A large language model. Stop spreading bullshit because you read it somewhere. If real-time affinity could damage hardware then it wouldn't exist on a consumer UI. Real-time Priority can at-most freeze the OS. It will mostly jist make your pc slow down to a crawl. You cean also research this by not asking chatgpt, but actually reading the official documentation. Show proof of your claims or stop replying. You're spreading misleading information and your only backing is allegedly computers that were destroyed because of an OS level tweak. Devops Emgineer btw. I am "an IT guy". You are wrong. Now to the topic. Real-time won't fix the issues with drivers that crash and cause kernel level issues. Hi im Nobsi
My Name is Nobsi and im a Nobsiian Did i mention that my Name is Nobsi? |
|
" That's client orientation for you. They write one message near the start of this topic and put this problem to the "priority issues", just right beside "sometimes not working teleport", I laughed my ass of, it looks like mocking, hard PC crashes and sometimes a problem that need a relog, definitely same level problems. And mostly people asking for some info from developers, at least "we're not forget, still on it", but nothing. They went on holidays with clear mind, and you, payer, sit, wait and hope for a fix maybe, sometime, whatever we don't care. As I said before, when you got million of sales, who are this little 300 pages on forum Last edited by DanteKannCry#7497 on Dec 26, 2024, 6:30:49 PM
|
|