Bug Reports (Path of Exile 1) - Suddenly Blue Screen while only playing POE1 on Windows11 - Forum

3rd time of blue screen. No Wall Paper Engine, and no OBS studio are running. Only watching a Twitch stream on Chrome and executing POE. I just let POE hanging there and watch Twitch. The mouse focus is even not in POE. And still blue screen. It is really annoying. ======= minidump ========= *********** Preparing the environment for Debugger Extensions Gallery repositories ********** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ********* Waiting for Debugger Extensions Gallery to Initialize ********** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 44 Microsoft (R) Windows Debugger Version 10.0.27829.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\061825-9921-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ********* Path validation summary ************ Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 26100 MP (32 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff807`aa000000 PsLoadedModuleList = 0xfffff807`aaef4aa0 Debug session time: Wed Jun 18 07:37:29.310 2025 (UTC + 8:00) System Uptime: 0 days 9:34:03.070 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........................................ Loading User Symbols PEB is paged out (Peb.Ldr = 0000006d`ccd2b018). Type ".hh dbgerr001" for details Loading unloaded module list .......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff807`aa500a70 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa184`10dbebe0=000000000000004e 9: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........................................ Loading User Symbols PEB is paged out (Peb.Ldr = 0000006d`ccd2b018). Type ".hh dbgerr001" for details Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ***************************************************************************** PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000006, The hardware PTE and/or the prototype PTE PFN data structures have been corrupted. Arg2: 0000000000c941d0, The page frame number Arg3: fffff3135956aef8, The prototype PTE Arg4: d38f34ebaab004c0, The prototype PTE contents Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 765 Key : Analysis.Elapsed.mSec Value: 2331 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 1 Key : Analysis.Init.CPU.mSec Value: 312 Key : Analysis.Init.Elapsed.mSec Value: 5632 Key : Analysis.Memory.CommitPeak.Mb Value: 103 Key : Analysis.Version.DbgEng Value: 10.0.27829.1001 Key : Analysis.Version.Description Value: 10.2503.24.01 amd64fre Key : Analysis.Version.Ext Value: 1.2503.24.1 Key : Bugcheck.Code.LegacyAPI Value: 0x4e Key : Bugcheck.Code.TargetModel Value: 0x4e Key : Dump.Attributes.AsUlong Value: 0x21808 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0x0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: 0x4E_6_nt!MiDecrementShareCountEx Key : Failure.Hash Value: {c5c73a05-16b8-5b8e-dca4-57d07f4c8b40} Key : Hypervisor.Enlightenments.ValueHex Value: 0x7497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 1 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 38408431 Key : Hypervisor.Flags.ValueHex Value: 0x24a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 0x3f7 BUGCHECK_CODE: 4e BUGCHECK_P1: 6 BUGCHECK_P2: c941d0 BUGCHECK_P3: fffff3135956aef8 BUGCHECK_P4: d38f34ebaab004c0 FILE_IN_CAB: 061825-9921-01.dmp TAG_NOT_DEFINED_202b: * Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x21808 Kernel Generated Triage Dump FAULTING_THREAD: ffffd38f438a4080 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: PathOfExile.ex //<---------------------- POE !!! STACK_TEXT: ffffa184`10dbebd8 fffff807`aa20cee5 : 00000000`0000004e 00000000`00000006 00000000`00c941d0 fffff313`5956aef8 : nt!KeBugCheckEx ffffa184`10dbebe0 fffff807`aa20b3b3 : 00000000`05460001 ffffa184`10dbf050 00000000`00000001 00000000`00000000 : nt!MiDecrementShareCountEx+0x405 ffffa184`10dbec60 fffff807`aa20a6dd : 00000000`00000000 ffffa381`141857f8 00000000`00000000 00000228`30aff000 : nt!MiDecommitSharedPageTail+0x283 ffffa184`10dbed60 fffff807`aa27a33c : ffffa184`10dbf050 00000000`00000082 ffffa381`141857f8 00000000`00000000 : nt!MiDecommitFreePagesTail+0x21d ffffa184`10dbedf0 fffff807`aa278cc5 : ffffa184`10dbef90 ffff9080`00000082 00000000`00000000 00000000`00000000 : nt!MiDecommitPagesTail+0x68 ffffa184`10dbee20 fffff807`aa3abf8a : 00000000`00000000 ffffd38f`00000000 ffffa184`00000082 ffffffff`ffffffff : nt!MiDeleteVaDirect+0x5c5 ffffa184`10dbef40 fffff807`aa3abdab : ffffd38f`4108d2e0 ffffd38f`438a4080 ffffd38f`438a4958 7fffffff`fffffffc : nt!MiDeletePagablePteRange+0x1b6 ffffa184`10dbf200 fffff807`aa8c3d63 : 00000000`00000000 ffffa184`10dbf2c0 ffffd38f`3fc319a0 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x4b ffffa184`10dbf250 fffff807`aa8c3b25 : 00000228`30af0000 ffffd38f`3fc319a0 00000000`00000004 00000000`00000000 : nt!MiDeleteVad+0x17f ffffa184`10dbf300 fffff807`aa8c325b : ffffd38f`3fc319a0 ffffa184`10dbf3a9 00000228`30af0000 00000000`00000000 : nt!MiUnmapVad+0x49 ffffa184`10dbf330 fffff807`aa8c30df : ffffffff`ffffffff 0000006d`00000008 ffffd38e`e7519ef0 00000000`00000000 : nt!MiUnmapViewOfSection+0x137 ffffa184`10dbf410 fffff807`aa6b7c58 : ffffd38f`438a4080 00000003`35fdfa66 ffffd38f`438a4080 ffffd38f`4108d080 : nt!NtUnmapViewOfSectionEx+0x9f ffffa184`10dbf460 00007ffc`ff6256d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 0000006d`da74f4b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`ff6256d4 SYMBOL_NAME: nt!MiDecrementShareCountEx+405 MODULE_NAME: nt IMAGE_VERSION: 10.0.26100.4343 STACK_COMMAND: .process /r /p 0xffffd38f4108d080; .thread 0xffffd38f438a4080 ; kb IMAGE_NAME: ntkrnlmp.exe BUCKET_ID_FUNC_OFFSET: 405 FAILURE_BUCKET_ID: 0x4E_6_nt!MiDecrementShareCountEx OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {c5c73a05-16b8-5b8e-dca4-57d07f4c8b40} Followup: MachineOwner --------- ============ Lastest Client snipet ============= 2025/06/18 07:30:03 33997421 88a91047 [DEBUG Client 2956] Got Instance Details from login server 2025/06/18 07:30:03 33997421 82998930 [INFO Client 2956] [SHADER] Delay: OFF 2025/06/18 07:30:03 33997421 ca3a6a31 [INFO Client 2956] Connecting to instance server at 165.192.83.71:6112 2025/06/18 07:30:03 33997500 ca3a5098 [DEBUG Client 2956] Connect time to instance server was 63ms 2025/06/18 07:30:03 33997593 11869508 [DEBUG Client 2956] Client-Safe Instance ID = 1475026260 2025/06/18 07:30:03 33997593 1186a023 [DEBUG Client 2956] Generating level 69 area "2_11_endgame_town" with seed 1 2025/06/18 07:30:05 33999312 f22b6a00 [INFO Client 2956] Tile hash: 2815062652 2025/06/18 07:30:05 33999312 f22b6a03 [INFO Client 2956] Doodad hash: 45103505 2025/06/18 07:30:05 33999328 e03447a5 [INFO Client 2956] [SCENE] Set Source [(null)] 2025/06/18 07:30:05 33999328 e03447a5 [INFO Client 2956] [SCENE] Set Source [卡魯沿岸] 2025/06/18 07:30:05 33999343 2e06ba62 [DEBUG Client 2956] [SCENE] Height Map Texture: 810 x 540 2025/06/18 07:30:05 33999359 df74df9b [DEBUG Client 2956] [SCENE] Static Walkability Texture: 621 x 414 2025/06/18 07:30:05 33999531 1187ac64 [DEBUG Client 2956] Joined guild named We come from tai fu with 200 members 2025/06/18 07:30:05 33999531 6ad7b838 [DEBUG Client 2956] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 1, seed = 5718, and keystone selection = 2 2025/06/18 07:30:05 33999562 6ad7b838 [DEBUG Client 2956] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 1, seed = 5718, and keystone selection = 2 2025/06/18 07:30:05 33999562 6ad7b838 [DEBUG Client 2956] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 1, seed = 5718, and keystone selection = 2 2025/06/18 07:30:05 33999562 6ad7b838 [DEBUG Client 2956] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 1, seed = 5718, and keystone selection = 2 2025/06/18 07:30:05 33999578 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered 2025/06/18 07:30:05 33999578 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered 2025/06/18 07:30:05 33999578 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered 2025/06/18 07:30:06 33999796 cff945b9 [INFO Client 2956] : <<set:MS>><<set:M>><<set:S>>你已進入：卡魯沿岸。 2025/06/18 07:30:06 34000250 82998930 [INFO Client 2956] [SHADER] Delay: ON 2025/06/18 07:30:11 34004906 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'PlayerPerformedCraft' triggered 2025/06/18 07:30:11 34005218 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'PlayerPerformedCraft' triggered 2025/06/18 07:30:11 34005484 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'PlayerPerformedCraft' triggered 2025/06/18 07:30:11 34005750 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'PlayerPerformedCraft' triggered 2025/06/18 07:30:12 34006218 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'PlayerPerformedCraft' triggered 2025/06/18 07:30:12 34006515 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'PlayerPerformedCraft' triggered 2025/06/18 07:30:44 34038250 cff945b9 [INFO Client 2956] : 完成交易。 2025/06/18 07:30:59 34053562 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered 2025/06/18 07:31:27 34081640 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered 2025/06/18 07:31:35 34089578 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Bored' triggered 2025/06/18 07:31:55 34109718 cff945b9 [INFO Client 2956] $<P†H> 費倫饅頭又大又白: 凜冬之眼冰矛．分裂瓦爾寶珠 2025/06/18 07:32:01 34115250 cff945b9 [INFO Client 2956] $<P†H> 費倫饅頭又大又白: 凜冬之眼冰矛．分裂q 2025/06/18 07:32:24 34138171 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle3MinuteCooldown' triggered 2025/06/18 07:32:24 34138171 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle1MinuteCooldown' triggered 2025/06/18 07:33:24 34198218 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle3MinuteCooldown' triggered 2025/06/18 07:33:24 34198218 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle1MinuteCooldown' triggered 2025/06/18 07:33:58 34232281 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered 2025/06/18 07:34:00 34234703 cff945b9 [INFO Client 2956] $應該是你還沒死吧: 精良的妖魔短匕笑死 2025/06/18 07:34:15 34249687 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered 2025/06/18 07:34:24 34258250 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle3MinuteCooldown' triggered 2025/06/18 07:34:24 34258250 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle1MinuteCooldown' triggered 2025/06/18 07:35:04 34298093 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered 2025/06/18 07:35:24 34318250 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle3MinuteCooldown' triggered 2025/06/18 07:35:24 34318250 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle1MinuteCooldown' triggered 2025/06/18 07:35:38 34332609 cff945b9 [INFO Client 2956] $<P†H> 費倫饅頭又大又白: 虛誕遺鑰玩了這麼久終於打到魔血了 2025/06/18 07:35:50 34344218 cff945b9 [INFO Client 2956] $<OGC123> 愛吃韭菜水餃的直江兼續與他的禁咒貓之陣: 祝福石 2025/06/18 07:36:24 34378265 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle3MinuteCooldown' triggered 2025/06/18 07:36:24 34378265 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle1MinuteCooldown' triggered 2025/06/18 07:36:27 34381031 cff945b9 [INFO Client 2956] $<†OWÃ> NyanCat_coc: 贗品．安姆布的戰甲, 聖戰鎖甲傭兵怎麼不會和我分享耐力球? 2025/06/18 07:36:45 34399031 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'LevelUp' triggered 2025/06/18 07:37:24 34438281 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle3MinuteCooldown' triggered 2025/06/18 07:37:24 34438281 19dbc0 [DEBUG Client 2956] [InGameAudioManager] TalkingPetAudioEvent 'Idle1MinuteCooldown' triggered	Posted by rogerfang#1161 on Jun 17, 2025, 7:51:42 PM Quote this Post
same issue here PFN_LIST_CORRUPT Arg 1: 0x06 9950X3D RTX 5090 using DX12, with 576.52 driver beside the BSOD nvlddmkm event 153 error also occur sometime test passed: msi kombustor, furmark: 1 hour+ memtest86 (4 pass) MHwild benchmark trying 576.80 after DDU and DX11 now update if there's anything new or stabled	Posted by mushroomrusher#4088 on Jun 18, 2025, 1:25:03 AM Quote this Post
I have also been having this issue, only in POE1. Hundreds of hours in other games and 3D software with no incident. 9900X3D RTX 5080 Usually running Vulcan, but I have tried DX11 and DX12 and it makes no difference. I have done just about everything I can find through google, including but not limited to - memory tests, both windows native and memtest86 4 pass, both of them ran on the RAM sticks separately and together - disabled EXPO (XMP) - updated BIOS - Would update chipset drivers but I am on latest already - SFC scan - DISM cleanups - checked health of main and secondary drives - used DDU to roll back GPU driver to 576.02 (what I ran before I started playing poe again/experiencing these issues) - have tried running nothing at all other than poe Still getting the same BSOD. I'm at my wit's end	Posted by Dreadzol#5226 on Jun 18, 2025, 2:40:02 AM Quote this Post
I'm not as tech-savy (well, more that I'm being lazy right now because i've just gone through last year going through 4 brand new pcs with INTEL issues. I'm fatigued on PC issues) but I'm also running into the same error. everything else was working perfectly up to POE launch and suddenly have had this happen 5 times (thought I fixed it as I had a 2-day period without issue, but it came back from what I thought may have caused it) AMD-9 9950x, 4090. Was on most recent game-ready driver pre-league but now updating to 567.80 (doubt this will do anything from seeing what others have said) only things running have been Chrome (it did it once without it open though), PoE Lurker / Awakened trade (I've also had these not running once and had it happen).	Posted by DruidNature#1765 on Jun 18, 2025, 5:52:35 AM Quote this Post
" Dreadzol#5226 wrote: [...] Still getting the same BSOD. I'm at my wit's end Have you tried running PoE in Linux ?	Posted by BlueTemplar85#0647 on Jun 18, 2025, 6:14:37 AM Quote this Post
" BlueTemplar85#0647 wrote: Have you tried running PoE in Linux ? I have not. I have never been a linux kind of guy so I don't really know what your question entails exactly. I don't know what that would serve to achieve or how I would go about doing that Either way I'm much more interested in solving the issue than working around it, if that's what you're suggesting	Posted by Dreadzol#5226 on Jun 18, 2025, 8:41:57 AM Quote this Post
Sure, though depending on what the actual cause is, this might take a while... You're the one saying that you were « at my wit's end ». " Dreadzol#5226 wrote: [...] I don't really know what your question entails exactly. I don't know what that would serve to achieve or how I would go about doing that [...] It might solve your issue and/or make it more clear if that's an issue with those specific drivers and/or your hardware. SteamOS isn't quite officially back to 'desktop' PCs yet, but we do have Bazzite (Fedora Linux) that makes the whole process decently easy enough. The main issue is : do you have a spare, empty hard drive (hopefully SSD) that you can put inside your PC (SATA or hopefully M.2 connectors) ? For a first time it's better to keep things as simple as possible : - only have one hard drive in during any OS installation (no sharing of OSes in a single drive on different partitions). - later selecting the drive you use either by physically changing them, or by picking the starting one in the 'BIOS' (UEFI) (not using on-hard-drive-located GRUB that big Windows updates love to overwrite). (Also you need a spare, empty USB key to install the OS from.)	Posted by BlueTemplar85#0647 on Jun 18, 2025, 12:31:56 PM Quote this Post
Exact same issue here on a 9950x and RTX4070, matching crash dumps. Tests with Cinebench R23, Furmark, MemTest86, all fine on my system. No crashes on other games but very consistent BSODs with specifically PoE1. Just today I think I've had 4-5 system crashes with PoE1 specifically, no other game I've tested with has caused this.	Posted by swedgelord#0701 on Jun 18, 2025, 3:57:40 PM Quote this Post
I'm getting the same issue with same error codes and people posting here. My pc is brand new, and only experienced crashes on POE1. I've updated graphics drivers, chipset drivers, bios updated and still crashing Running the following hardware 9950X3D Rtx 5080 64gb 6k ram Msi mag 870 tomahawk mobo Will be trying other games tomorrow to see if it's specific to path of exile 1	Posted by FlameMino#3163 on Jun 18, 2025, 5:25:14 PM Quote this Post
" BlueTemplar85#0647 wrote: Sure, though depending on what the actual cause is, this might take a while... You're the one saying that you were « at my wit's end ». " Dreadzol#5226 wrote: [...] I don't really know what your question entails exactly. I don't know what that would serve to achieve or how I would go about doing that [...] It might solve your issue and/or make it more clear if that's an issue with those specific drivers and/or your hardware. SteamOS isn't quite officially back to 'desktop' PCs yet, but we do have Bazzite (Fedora Linux) that makes the whole process decently easy enough. The main issue is : do you have a spare, empty hard drive (hopefully SSD) that you can put inside your PC (SATA or hopefully M.2 connectors) ? For a first time it's better to keep things as simple as possible : - only have one hard drive in during any OS installation (no sharing of OSes in a single drive on different partitions). - later selecting the drive you use either by physically changing them, or by picking the starting one in the 'BIOS' (UEFI) (not using on-hard-drive-located GRUB that big Windows updates love to overwrite). (Also you need a spare, empty USB key to install the OS from.) Right, apologies if I came across as dismissive, that was not the intention. I just didnt quite understand why you were suggesting what you did. I don't have a free drive on hand, but I might look into setting this up if the problem persists. Thanks for the explanation!	Posted by Dreadzol#5226 on Jun 19, 2025, 2:24:32 AM Quote this Post