Windows 11 BSOD

[cs2nate]

When using Vanishing Bomb the game crashes and i'm not sure which error but a Unreal Engine 5 error pops up real quick and BSOD occurs. i thought this was an issue on Linux because i mainly use arch but i now am on windows 11 and this is also happening. anyone else having related issues with vanishing bomb or any other abilities that's causing UE5 errors which lead to a BSOD? on linux i have to hold the power button in to shutdown when the game crashes because the PC locks up.

[Alex]

If you have BSOD then you should check RAM and other components. This can be major issue and your PC can be damaged.
Game shouldnt impact stability of OS.
Reset BIOS to default settings and disable OC if it enabled.

[the_SLVRFOX]

Someone posted a similar issue several months ago... vanishing bomb caused the game to crash, but didn't cause BSOD. I'd say try checking file integrity, but I'm assuming OP has already done that...

[cs2nate]

Originally posted by Alex Green:

If you have BSOD then you should check RAM and other components. This can be major issue and your PC can be damaged.
Game shouldnt impact stability of OS.
Reset BIOS to default settings and disable OC if it enabled.

this laptop is less then 6 months old and meets the 16 GB recommended RAM requirement. the issue i have noticed is an unreal engine 5 software issue which seems to be causing the BSOD. this is a software issue i believe kinda like the crowdstrike incident maybe. everything runs fine and this isn't every time i vanishing bomb, it's random and when the game crashes out, the UE5 engine error log comes up and then i get the BSOD. BSOD is just like a kernel panic in Linux. i don't think this is a hardware issue as this is the only game this happens to. i don't overclock and i get the same issue on Linux it just doesn't pop up with the UE5 engine error and i have to hold the power button in. windows it at least reboots automatically when it BSOD. i wonder if it's the new anti-cheat heuristics, whatever crowdstrike did when they updated caused all those PCs to BSOD and even Linux a month with prior kernel panics.

Originally posted by the_SLVRFOX:

Someone posted a similar issue several months ago... vanishing bomb caused the game to crash, but didn't cause BSOD. I'd say try checking file integrity, but I'm assuming OP has already done that...

yes i have checked the file integrity.

[the_SLVRFOX]

Is your laptop a Gigabyte or Aorus, and the CPU an i9 13900k or 14900k? I've read that the motherboard may not be properly set up. If so, try changing to these settings in your BIOS:

Enhanced multicore performance: DISABLED (importart)

Energy efficient turbo: ENABLED

Turbo boost technology: ENABLED

Turbo Boost Max Technology 3.0: ENABLED

Package power limit 1 TDP: 125w (Intel’s recommendation for 13900K) (important)

Package power limit 2 TDP: 253w (Intel’s recommendation for 13900K) (important)

[cs2nate]

Originally posted by the_SLVRFOX:

Is your laptop a Gigabyte or Aorus, and the CPU an i9 13900k or 14900k? I've read that the motherboard may not be properly set up. If so, try changing to these settings in your BIOS:

Enhanced multicore performance: DISABLED (importart)

Energy efficient turbo: ENABLED

Turbo boost technology: ENABLED

Turbo Boost Max Technology 3.0: ENABLED

Package power limit 1 TDP: 125w (Intel’s recommendation for 13900K) (important)

Package power limit 2 TDP: 253w (Intel’s recommendation for 13900K) (important)

thanks for the info. sorry i hadn't specified my specs. i have a intel core i7 12650H and a NVIDIA RTX 4050 Laptop GPU. it's an Acer Nitro 5

[the_SLVRFOX]

I'm no expert on this... but from what I'm gleaming off the internet, UE can be really finicky when it comes to the CPU configuration. When it comes to gaming laptops, many of them will utilize customized settings in their BIOS to manage (enhance) CPU performance, essentially overriding the CPU manufacturer's settings. In the example above, the Gigabyte mobo had "enhanced multicore performance" enabled, basically telling the CPU to always have all the cores firing on all cylinders all the time. And with UE being finicky, this could cause a lot of issues, including BSOD. I would suggest going into the BIOS and seeing if your laptop has this sort of setting enabled.

[!! akim ⁧⁧ᵛᵃˡᵛᵉ]

Dude, you're out here catching a *BSOD* from a **vanishing bomb**? That bomb's vanishing your entire PC! 💀

Okay, first off, respect for trying to escape this madness on Arch Linux, but now you’re on Windows 11 and still dealing with Unreal Engine 5 deciding to self-destruct? Yeah, sounds like the game isn’t playing nice with your setup, regardless of OS.

Honestly, though, if both your Linux *and* Windows installs are crashing on this, it’s more likely an issue with how the game’s handling that ability with certain hardware configs—maybe a GPU driver bug or memory leak. Unreal Engine 5 likes to be a drama queen sometimes, especially with newer hardware.

First thing I’d do? Check for any UE5-related patch notes or known issues with the game. Also, make sure you’re running the latest drivers for your GPU on Windows (but maybe don’t go full Arch on this one and roll back just yet). And yo, if it’s consistently the vanishing bomb that’s triggering the crash, maybe avoid it for now—don’t let one ability throw your whole rig into a blue screen spiral.

If that doesn’t fix it, I’d check if the game’s forum has other poor souls dealing with UE5-related BSODs. Misery loves company, right? 😅

[cs2nate]

Originally posted by the_SLVRFOX:

I'm no expert on this... but from what I'm gleaming off the internet, UE can be really finicky when it comes to the CPU configuration. When it comes to gaming laptops, many of them will utilize customized settings in their BIOS to manage (enhance) CPU performance, essentially overriding the CPU manufacturer's settings. In the example above, the Gigabyte mobo had "enhanced multicore performance" enabled, basically telling the CPU to always have all the cores firing on all cylinders all the time. And with UE being finicky, this could cause a lot of issues, including BSOD. I would suggest going into the BIOS and seeing if your laptop has this sort of setting enabled.

thanks i will check out the PCs BIOS settings.

Originally posted by STICKER CAPSULE ENJOYER:

Dude, you're out here catching a *BSOD* from a **vanishing bomb**? That bomb's vanishing your entire PC! 💀

Okay, first off, respect for trying to escape this madness on Arch Linux, but now you’re on Windows 11 and still dealing with Unreal Engine 5 deciding to self-destruct? Yeah, sounds like the game isn’t playing nice with your setup, regardless of OS.

Honestly, though, if both your Linux *and* Windows installs are crashing on this, it’s more likely an issue with how the game’s handling that ability with certain hardware configs—maybe a GPU driver bug or memory leak. Unreal Engine 5 likes to be a drama queen sometimes, especially with newer hardware.

First thing I’d do? Check for any UE5-related patch notes or known issues with the game. Also, make sure you’re running the latest drivers for your GPU on Windows (but maybe don’t go full Arch on this one and roll back just yet). And yo, if it’s consistently the vanishing bomb that’s triggering the crash, maybe avoid it for now—don’t let one ability throw your whole rig into a blue screen spiral.

If that doesn’t fix it, I’d check if the game’s forum has other poor souls dealing with UE5-related BSODs. Misery loves company, right? 😅

ye it's frustrating XD, i will check out UE forums. vanishing bomb doesn't always cause the blue screen, it's random, usually when close facing to a wall when using it. like bombing into the wall.

i could of found a fix maybe, i went into practice range to replicate the issue and first try it worked (facing a white/light wall and vanishing bombing close into the wall). the setting i changed was NVIDIA DLSS Frame Generation from enabled to disabled and then NVIDIA Reflex Low Latency set to On + Boost. the frame generation renders additional frames, not sure if this could be a reason for the BSOD. the NVIDIA Reflex Low Latency, the boost helps the CPU drawing more power to the GPU, so if the issue is fixed it's because of one or both of these settings in my case. i will do more testing in the practice range to see if i can replicate the BSOD again.

[cs2nate]

the fix i thought i found didn't work, switching to TAUU and res scaling on auto (after the latest update) and all settings on low and i haven't had a BSOD since. will update if things change. i have DLSS frame generation off and NVIDIA reflex low latency off as well.

[HiggsLP]

I would also trybturning ALL nvidia features off.
Also set Global Illumination to Static(RTX OFF).

[cs2nate]

Originally posted by HiggsLP:

I would also trybturning ALL nvidia features off.
Also set Global Illumination to Static(RTX OFF).

thanks for that i might of forgot to mention i have that one setting set to static and yes turn off ALL NVIDIA features, i believe that's what i did to "fix" that issue XD