Marvel Rivals

Marvel Rivals

View Stats:
Habibi Dec 6, 2024 @ 1:10pm
Out of video memory trying to allocate a rendering resource.
Every time I try to boot the game it starts initializing the shaders then I'm hit with "Out of video memory trying to allocate a rendering resource. Make sure your video card has the minimum required memory, try lowering the resolution and/or closing other applications that are running. Exiting..."

CPU: 13th Gen Intel(R) Core(TM) i7-13700KF Mhz, 8 Core(s)
Motherboard: Gigabyte z690 GAMING X
GPU: NVIDIA GeForce RTX 3060 Ti

I read online and it seems like the issue has to do with some intel issue and watts and BIOS? I'm super confused, any solid answers? Thank you in advance! :steamthumbsup:
< >
Showing 1-15 of 17 comments
Metthall Dec 6, 2024 @ 1:13pm 
same for me
Queen HawlSera Dec 6, 2024 @ 1:18pm 
I don't even use intel and that ♥♥♥♥ happen for me
Habibi Dec 6, 2024 @ 1:34pm 
I have fixed this, here's what I did:
  1. Install Intel XTU [www.intel.com]
  2. Open the program as Admin

If the program fails due to VBS you can disable it by:
  1. Opening command prompt from the start menu as admin
  2. Copy and paste this command: bcdedit /set hypervisorlaunchtype off
  3. Restart and see if it works. If its still running into issues go to the Windows Start menu, search Core isolation and press Enter to open your Device security settings.
  4. Toggle Memory integrity off and restart your computer.

Inside Intel XTU Switch performance core ratio from whatever number it is to 1 lower number (example if yours says "55x" then switch it to 54x, if it says "53x" then switch it to "52x").

This answer was taken from this Reddit post

Kudos to that person on Reddit, I don't know what to do if you don't have an Intel CPU, I did not come up with the solution, I'm just sharing in case someone else runs into this. Happy gaming everyone and I hope it works for you <3
Last edited by Habibi; Dec 6, 2024 @ 1:34pm
MeatballJunk Dec 6, 2024 @ 3:49pm 
Originally posted by Habibi:
I have fixed this, here's what I did:
  1. Install Intel XTU [www.intel.com]
  2. Open the program as Admin

If the program fails due to VBS you can disable it by:
  1. Opening command prompt from the start menu as admin
  2. Copy and paste this command: bcdedit /set hypervisorlaunchtype off
  3. Restart and see if it works. If its still running into issues go to the Windows Start menu, search Core isolation and press Enter to open your Device security settings.
  4. Toggle Memory integrity off and restart your computer.

Inside Intel XTU Switch performance core ratio from whatever number it is to 1 lower number (example if yours says "55x" then switch it to 54x, if it says "53x" then switch it to "52x").

This answer was taken from this Reddit post

Kudos to that person on Reddit, I don't know what to do if you don't have an Intel CPU, I did not come up with the solution, I'm just sharing in case someone else runs into this. Happy gaming everyone and I hope it works for you <3

Sadly didnt work for me. Hope it works for others
PlanetMars Dec 7, 2024 @ 7:51pm 
Originally posted by Habibi:
I have fixed this, here's what I did:
  1. Install Intel XTU [www.intel.com]
  2. Open the program as Admin

If the program fails due to VBS you can disable it by:
  1. Opening command prompt from the start menu as admin
  2. Copy and paste this command: bcdedit /set hypervisorlaunchtype off
  3. Restart and see if it works. If its still running into issues go to the Windows Start menu, search Core isolation and press Enter to open your Device security settings.
  4. Toggle Memory integrity off and restart your computer.

Inside Intel XTU Switch performance core ratio from whatever number it is to 1 lower number (example if yours says "55x" then switch it to 54x, if it says "53x" then switch it to "52x").

This answer was taken from this Reddit post

Kudos to that person on Reddit, I don't know what to do if you don't have an Intel CPU, I did not come up with the solution, I'm just sharing in case someone else runs into this. Happy gaming everyone and I hope it works for you <3
didn't work
Truen Dec 9, 2024 @ 9:25am 
Same. I've not even been able to play the game yet. Nvidia 4070 ti (re-installed drivers already) /w a ip 14900 processor and 32g ram.
Last edited by Truen; Dec 9, 2024 @ 9:26am
Arc Dec 9, 2024 @ 9:30am 
Update BIOS of your motherboard before your faulty CPU disintegrate itself.
EricMyval Dec 15, 2024 @ 8:19am 
There is a solution! 14th generation Intel and 4070ti. Update Windows, update the video driver and most importantly update the BIOS (Z790-A). Everything starts.
Snuskkutt Dec 18, 2024 @ 3:27pm 
Just updated to latest BIOS on my Asus Prime Z790-A and it solved the issue.
I havesame CPU, and GPU. You don't even know your CPU, it has 16 (sixteen physical cores), not only a mere of 8. 8 Performance cores, 8 Efficient cores, and 24 Threads. Also to those lecturing you to update the BIOS, I have the latest BIOS, the latest drivers, including the latest Nvidia drivers and Windows updates, but that is stil happening when the 3060 Ti is the RECOMMENDED GPU to run this crap of game.
Arc Jan 1 @ 11:30am 
Originally posted by Milo Burik:
.. You don't even know your CPU...
Yes, you do not know how your own CPU works.

E-cores are not used by games, they are used by background tasks for the most part unless there is specific load that benefits from them such as code compilation which in video games would be shader compilation on boot.
Which is preciselly where the issue with Intel Raptor Lake CPU manifests: On full multithreaded load.


Originally posted by Milo Burik:
...Efficient cores, and 24 Threads. Also to those lecturing you to update the BIOS...
You mean Intel by this, right ?

Intel® has identified four (4) operating scenarios that can lead to Vmin shift in affected processors:

Motherboard power delivery settings exceeding Intel power guidance.
a. Mitigation: Intel® Default Settings recommendations for Intel® Core™ 13th and 14th Gen desktop processors.
eTVB Microcode algorithm which was allowing Intel® Core™ 13th and 14th Gen i9 desktop processors to operate at higher performance states even at high temperatures.
a. Mitigation: microcode 0x125 (June 2024) addresses eTVB algorithm issue.
Microcode SVID algorithm requesting high voltages at a frequency and duration which can cause Vmin shift.
a. Mitigation: microcode 0x129 (August 2024) addresses high voltages requested by the processor.
Microcode and BIOS code requesting elevated core voltages which can cause Vmin shift especially during periods of idle and/or light activity.
a. Mitigation: Intel® is releasing microcode 0x12B, which encompasses 0x125 and 0x129 microcode updates, and addresses elevated voltage requests by the processor during idle and/or light activity periods.
https://community.intel.com/t5/Blogs/Tech-Innovation/Client/Intel-Core-13th-and-14th-Gen-Desktop-Instability-Root-Cause/post/1633239

I sure hope you do know about issues with Raptor Lake by now, it's been in the news for several months.
If your CPU is still unstable, RMA it as soon as possible before Intel stops offering replacements for their own faulty product.


Also, you are posting in a thread with a topic of crashing on boot, if you have the error in some other places (loading screen to match, during the match, post match, etc.), other solutions might work for you.
Originally posted by Habibi:
Every time I try to boot the game it starts initializing the shaders then I'm hit with "Out of video memory trying to allocate a rendering resource. Make sure your video card has the minimum required memory, try lowering the resolution and/or closing other applications that are running. Exiting..."

CPU: 13th Gen Intel(R) Core(TM) i7-13700KF Mhz, 8 Core(s)
Motherboard: Gigabyte z690 GAMING X
GPU: NVIDIA GeForce RTX 3060 Ti

I read online and it seems like the issue has to do with some intel issue and watts and BIOS? I'm super confused, any solid answers? Thank you in advance! :steamthumbsup:

Read the warning that popped up when you started the game.
Originally posted by Arc:
Originally posted by Milo Burik:
.. You don't even know your CPU...
Yes, you do not know how your own CPU works.

E-cores are not used by games, they are used by background tasks for the most part unless there is specific load that benefits from them such as code compilation which in video games would be shader compilation on boot.
Which is preciselly where the issue with Intel Raptor Lake CPU manifests: On full multithreaded load.


Originally posted by Milo Burik:
...Efficient cores, and 24 Threads. Also to those lecturing you to update the BIOS...
You mean Intel by this, right ?

Intel® has identified four (4) operating scenarios that can lead to Vmin shift in affected processors:

Motherboard power delivery settings exceeding Intel power guidance.
a. Mitigation: Intel® Default Settings recommendations for Intel® Core™ 13th and 14th Gen desktop processors.
eTVB Microcode algorithm which was allowing Intel® Core™ 13th and 14th Gen i9 desktop processors to operate at higher performance states even at high temperatures.
a. Mitigation: microcode 0x125 (June 2024) addresses eTVB algorithm issue.
Microcode SVID algorithm requesting high voltages at a frequency and duration which can cause Vmin shift.
a. Mitigation: microcode 0x129 (August 2024) addresses high voltages requested by the processor.
Microcode and BIOS code requesting elevated core voltages which can cause Vmin shift especially during periods of idle and/or light activity.
a. Mitigation: Intel® is releasing microcode 0x12B, which encompasses 0x125 and 0x129 microcode updates, and addresses elevated voltage requests by the processor during idle and/or light activity periods.
https://community.intel.com/t5/Blogs/Tech-Innovation/Client/Intel-Core-13th-and-14th-Gen-Desktop-Instability-Root-Cause/post/1633239

I sure hope you do know about issues with Raptor Lake by now, it's been in the news for several months.
If your CPU is still unstable, RMA it as soon as possible before Intel stops offering replacements for their own faulty product.
Also, you are posting in a thread with a topic of crashing on boot, if you have the error in some other places (loading screen to match, during the match, post match, etc.), other solutions might work for you.

Even, maybe, the effieciency cores aren/t used by games, they are still PHYSICAL CORES, therefore the i7 13700K is a SIXTHEEN PHYSICAL CORES CPU.
Also, the microcode it's updated, I have installed the latest UEFI update for my Asus B660M-E D4 motherboard, and set for the Intel recommended settings, no OC ay all.
And also, it's crashing on boot, otherwise I wouldn't posted here. I have by far and beyond the recommended specs for running this piece of crap of a game, and still it has a VRAM memory leak. How 8GB of VRAM for the 1080p resolution couldn't be enough for running this game!?
if you have low vram create a windows page file on your SSd the same size as your physical RAM. if you have an old HDD, replace that ASAP

set your graphics driver to default to system ram when running out of VRAM

this game asks for permissions and compiles shaders on every startup for some reason

i only have 4GB VRAM, but the above solved crashes and allow me to run games at max textures in many games

*i have not had a crash in Marvel Rivals yet
Last edited by Ream Assturd; Jan 2 @ 1:54pm
Arc Jan 2 @ 1:54pm 
On boot it's not a VRAM leak, your CPU is unstable so it's throwing out a bogus error, that's explained here :
https://www.radgametools.com/oodleintel.htm

That or your shader cache got corrupted beforehand.

And 8+8 big.LITTLE cores is not the same as 16 identical cores, in this sense it's the same as AMD's Ryzen 9 X3D chips where one chiplet is prefered by games due to the SRAM cache and it tries to throw process affinity to only half the cores.
While fully multi-threaded workloads like CPU render or code compilation will use by default all available threads.

Modern CPUs are a whole lot more complicated than saying "i have 16 cores", because in reality you are only using half of it to do the heavy lifting.
< >
Showing 1-15 of 17 comments
Per page: 1530 50

Date Posted: Dec 6, 2024 @ 1:10pm
Posts: 17