KaeJo
KaeJo
About
- Username
- KaeJo
- Joined
- Visits
- 24
- Last Active
Comments
-
@s4ty said:
What helped me was
https://www.radgametools.com/oodleintel.htm
especially the SVID Behavior for my Asus Mainboard
Quote:
"Troubleshooting Update from Intel Corporation - Additional troubleshooting steps for ASUS, Gigabyte and MSI motherboards:First, install Intel XTU and run the AVX2 test. If the AVX2 test failure is seen, try these options:
- For ASUS:
Ask customer to change BIOS settings: Advanced (F7)- SVID Behavior: Change to "Intel's Fail Safe"
Reboot the OS and run XTU test again and if the AVX2 test can pass. Run games and see if the issue happens again. - For Gigabyte: …
- For MSI: …"
Yes, this is essentially where the links I posted lead as well. Adjusting BIOS to prevent too much power draw. Sounds like this is the "official" fix, though some other fixes that people have posted help as workarounds as well.
- For ASUS:
-
@KaeJo said:
I figured it out and I'm back to share the results!!
I went searching for CPU + Unreal 5 related issues after reading Brizzyne's post above. I found two Reddit posts that helped me solve the issue for my computer. The first (HERE) explains what is actually going on.I then searched for solutions to this specific issue, which led me HERE. This post talks about how to fix the issue.
In short, if you've overclocked your 13th/14th generation Intel CPU (or in some cases, even left the BIOS default), then you are probably crashing your CPU because Unreal 5 pushes it beyond it's limits per manufacturer recommendations. The second Reddit post gives specific instructions for "underclocking" your BIOS settings to prevent these crashes.
The settings recommended worked for me right out of the gate. When I got to "Initializing Shaders," my CPU spiked all the way to 100% utilization, stayed there for a few seconds, and then I moved past the Shaders step and played a full match without issues.
Hooray!
Back to update that this fix has continued to work for me all week with no other issues / side effects. Seems to be a stable fix.
-
This article makes it seem like it's possible to do, but I don't know that I'd try it myself unless re-installing Windows just wasn't an option.
-
@YeahOkayFineWhatever said:
Okay, so i checked up on all of my settings and turns out I have legacy instead of UEFI. Am i just doomed?
Are you running Windows? If so, I think you would have to do a fresh install of Windows. Here's an article I found from Microsoft:
Unfortunately, I'm not the most knowledgeable about this stuff. I had to do a TON of Googling when I built my PC!
-
I figured it out and I'm back to share the results!!
I went searching for CPU + Unreal 5 related issues after reading Brizzyne's post above. I found two Reddit posts that helped me solve the issue for my computer. The first (HERE) explains what is actually going on.I then searched for solutions to this specific issue, which led me HERE. This post talks about how to fix the issue.
In short, if you've overclocked your 13th/14th generation Intel CPU (or in some cases, even left the BIOS default), then you are probably crashing your CPU because Unreal 5 pushes it beyond it's limits per manufacturer recommendations. The second Reddit post gives specific instructions for "underclocking" your BIOS settings to prevent these crashes.
The settings recommended worked for me right out of the gate. When I got to "Initializing Shaders," my CPU spiked all the way to 100% utilization, stayed there for a few seconds, and then I moved past the Shaders step and played a full match without issues.
Hooray!
-
@brizzyne said:
I have fixed the issue for my computer. It appears that if you have a 13 or 14th gen Intel CPU then it may actually be an issue with your bios power settings. Yes it looks like it is a GPU issue with the out of video memory error but it is actually a CPU issue. I found a thread in the steam discussions forum for DBD that led me to how to fix the issue. Unfortunately if you are crashing and don't have a CPU of those generations it is probably a different issue for you.
Why would you say this and then not share how you fixed it?