Marvel Rivals

Marvel Rivals

View Stats:
BSOD While compiling shaders.
Computer blue screen crashes while compiling shaders giving the error code "PAGE_FAULT_IN_NON-PAGED_AREA"
Was able to get the game running once after:
>updating my graphics drivers
>Verifying Integrity of game files
>Running Image Servicing and Management Tool
>Scanning for damaged system files

Then the game crashed during the tutorial (right after breaking the wall) and started throwing the same error afterward.

I've also set the game (marvel.exe) to run in compatibility mode for Windows7 to no effect.

Is there a known fix for this, or do I need to just trial & error my way through this?
Last edited by Furlington Boat Cactory; Dec 12, 2024 @ 6:02pm
< >
Showing 1-14 of 14 comments
Tsuru Dec 12, 2024 @ 6:43pm 
Run a scan on your ram for errors
Originally posted by Tsuru:
Run a scan on your ram for errors
Windows Memory Diagnostic detected no errors
Originally posted by Tsuru:
Run a scan on your ram for errors
Ran memtest86: >150 errors....
....yeah, I think that might be it. Guess I need new ram. ♥♥♥♥.
Arc Dec 13, 2024 @ 3:56am 
Which CPU do you have ?
Originally posted by Arc:
Which CPU do you have ?
Intel i3 Quad core
Dobke Dec 13, 2024 @ 4:03am 
Originally posted by Furlington Boat Cactory:
Computer blue screen crashes while compiling shaders giving the error code "PAGE_FAULT_IN_NON-PAGED_AREA"
Was able to get the game running once after:
>updating my graphics drivers
>Verifying Integrity of game files
>Running Image Servicing and Management Tool
>Scanning for damaged system files

Then the game crashed during the tutorial (right after breaking the wall) and started throwing the same error afterward.

I've also set the game (marvel.exe) to run in compatibility mode for Windows7 to no effect.

Is there a known fix for this, or do I need to just trial & error my way through this?
That’s a Page File/Memory Issue.

Please try increasing the amount of page file memory, or setting a fixed amount that’s equal the amount of RAM you have times two.

For example if you have 16GB of RAM, set 32GB of page file memory (Recommended) I know it’s a lot, but it’s a world of difference. At minimum I’d put 24GB.
Originally posted by Dobkey:
Originally posted by Furlington Boat Cactory:
Computer blue screen crashes while compiling shaders giving the error code "PAGE_FAULT_IN_NON-PAGED_AREA"
Was able to get the game running once after:
>updating my graphics drivers
>Verifying Integrity of game files
>Running Image Servicing and Management Tool
>Scanning for damaged system files

Then the game crashed during the tutorial (right after breaking the wall) and started throwing the same error afterward.

I've also set the game (marvel.exe) to run in compatibility mode for Windows7 to no effect.

Is there a known fix for this, or do I need to just trial & error my way through this?
That’s a Page File/Memory Issue.

Please try increasing the amount of page file memory, or setting a fixed amount that’s equal the amount of RAM you have times two.

For example if you have 16GB of RAM, set 32GB of page file memory (Recommended) I know it’s a lot, but it’s a world of difference. At minimum I’d put 24GB.


This had no effect. In fact, the BSOD is happening faster now. Before, the shaders would compile to about 50% before crashing, now it doesn't make it to 20%.

Needle's swinging back to point at bad RAM being the issue.
Dobke Dec 13, 2024 @ 3:46pm 
Originally posted by Furlington Boat Cactory:
Originally posted by Dobkey:
That’s a Page File/Memory Issue.

Please try increasing the amount of page file memory, or setting a fixed amount that’s equal the amount of RAM you have times two.

For example if you have 16GB of RAM, set 32GB of page file memory (Recommended) I know it’s a lot, but it’s a world of difference. At minimum I’d put 24GB.


This had no effect. In fact, the BSOD is happening faster now. Before, the shaders would compile to about 50% before crashing, now it doesn't make it to 20%.

Needle's swinging back to point at bad RAM being the issue.

Aw, damn, my bad.

Have you tried swapping RAMs in place? Or how about removing one at a time and trying the shader compile process?

I don't know if it's an actual memory problem, but who knows? Windows usually gives an specific error code related to RAM when it happens.
Last edited by Dobke; Dec 13, 2024 @ 3:50pm
Intel 13 & 14th Gen processors need to be clocked down because their the corpo are bad at coding.
Last edited by Valvatorez(Cox Cable = awful ISP; Dec 13, 2024 @ 3:48pm
Originally posted by Valvatorez:
Intel 13 & 14th Gen processors need to be clocked down because their the corpo are bad at coding.

Lowering the clock speed of the CPU and disabling the turbo function massively improved things. The game loaded and I was able to get through the basic tutorial and most (everyone but Mantis) of the initial hero tutorials with no issues (except for some slight texture pop-in when Iron-man's model loaded in the in-tutorial's character select screen.) Got the BSOD again after ~15min of play time with the same error.
Medusa Dec 13, 2024 @ 5:13pm 
Originally posted by Furlington Boat Cactory:
Originally posted by Arc:
Which CPU do you have ?
Intel i3 Quad core
But which one
Originally posted by Medusa:
Originally posted by Furlington Boat Cactory:
Intel i3 Quad core
But which one

i3-8350k
AceBoi Jan 10 @ 10:15pm 
I had this issue it was fine before then kept crashing while compiling shaders with the S1 update tried everything online and only way I fixed it was going into my bios disabling XMP running the game and the shaders complied 1st time then restarted pc turned XMP back on and everything is fine hope this helps some people
try unplugging pc. wait 10 seconds and replug pc.
< >
Showing 1-14 of 14 comments
Per page: 1530 50

Date Posted: Dec 12, 2024 @ 5:52pm
Posts: 14