Marvel’s Spider-Man Remastered

Marvel’s Spider-Man Remastered

Ver estadísticas:
SpiderFlash 15 AGO 2022 a las 6:09 a. m.
Unhandled exception at address 0x00000000b7332ebb (code: 0xc0000005): "Access violation"
Memory statistics:
[Crash] Total RAM = 7.8 GB (8004 MB)
[Crash] Avail RAM = 1.1 GB (1131 MB)
[Crash] Total virtual memory = 131072.0 GB (134217727 MB)
[Crash] Avail virtual memory = 131054.7 GB (134200022 MB)
[Crash] Total page file = 19.8 GB (20292 MB)
[Crash] Avail page file = 4.3 GB (4439 MB)
[Crash] Unhandled exception at address 0x00000000b7332ebb (code: 0xc0000005): "Access violation"

Anyone here encountered this kind of problem? The game crashed when I quit the game.
< >
Mostrando 16-29 de 29 comentarios
S1ntax Error 15 AGO 2022 a las 11:49 a. m. 
Publicado originalmente por mrtnptrs:
Publicado originalmente por BlastThyName:
Increase your pagefile people, set it to at least your physical RAM size.
Don't do this, Windows' automatic handling of the pagefile size is always recommended. Changing it can cause games to rely on it too much and as the pagefile is on the disk, this can cause severe stutter and performance issues, rendering some games unplayable....

You have any other ideas? I don't mind changing the page file size as it is easy enough to set it back to windows managed. This is the only game that is crashing on me this consistently.

I have seen a Reddit post in which users are saying the consistent crashes are related to ray-tracing, and I do believe that to be the case because when I disable ray tracing I don't crash. With that said the error from the log does seem to point to memory in some way.
sand.storm 15 AGO 2022 a las 11:51 a. m. 
Publicado originalmente por mrtnptrs:
Publicado originalmente por BlastThyName:
Increase your pagefile people, set it to at least your physical RAM size.
Don't do this, Windows' automatic handling of the pagefile size is always recommended. Changing it can cause games to rely on it too much and as the pagefile is on the disk, this can cause severe stutter and performance issues, rendering some games unplayable....

Yeah Insomniac even states to automatically manage the page files. While mine was set manually to 6GB on my C drive, setting this to auto reduced it to 2GB, going to leave it alone for now.
https://support.insomniac.games/hc/en-us/articles/8397966739341-Video-Memory-Crash

Had another 1.5 hour long session that was crash free since I've knocked my RAM speed down although I'm starting to see the optimization issues people are mentioning as the game does seem to slow down over time.
Arc 15 AGO 2022 a las 12:41 p. m. 
Publicado originalmente por mrtnptrs:
Don't do this, Windows' automatic handling of the pagefile size is always recommended. Changing it can cause games to rely on it too much and as the pagefile is on the disk, this can cause severe stutter and performance issues, rendering some games unplayable....
Publicado originalmente por sand.storm:
...
Yeah Insomniac even states to automatically manage the page files.
They can't do otherwise because it's not that simple:
This error can on systems with high-end hardware, when the Windows page file does not offer enough space to allocate VRAM budget.
i.e. it is set too low or disabled (yes, users that do not understand what this is used for on modern PCs do this).

Windows still ignores large VRAM pools and sets it too low to accomodate VRAM address space.
On systems with (for simplicity) 8GB RAM and 8GB VRAM, you end up crashing like crazy, because Windows cannot allocate this much memory space and system RAM always takes the lead (so you crash due to VRAM not being addressable).

So the amount largely depends on your current config.
⭐️ ǤЯƗΜΜ ⭐ 15 AGO 2022 a las 12:45 p. m. 
0x0000blablabla is a RAM address, RAM means "Random Access Memory", so reporting that number is actually useless

Try setting the paging file of the hard drive that is running the game as "automatic size" or whatever is called
Hans 15 AGO 2022 a las 2:01 p. m. 
Got auto pagefile and literally ran my memory at stock 2133 mhz to see if it's related. No dice.

Don't think that's it. Especially since this PC has ran games without even a hitch for almost a year now.

This game doesn't like some hardware or software combination.

Y'all on Windows 11?

Y'all have 32 gigs of ram?
Última edición por Hans; 15 AGO 2022 a las 2:17 p. m.
S1ntax Error 15 AGO 2022 a las 4:15 p. m. 
Publicado originalmente por Hans:
Got auto pagefile and literally ran my memory at stock 2133 mhz to see if it's related. No dice.

Don't think that's it. Especially since this PC has ran games without even a hitch for almost a year now.

This game doesn't like some hardware or software combination.

Y'all on Windows 11?

Y'all have 32 gigs of ram?

i am on Windows 11 and I do have 32GB of RAM.

I just tried increasing page file I did manage to play longer without a crash, but it still crashed to desktop.

I set my GPU and CPU back to stock just to rule out my overclock despite no other game crashing like this but that didn't help either.
Citizen Alpha 15 AGO 2022 a las 8:38 p. m. 
I had this crashing quite a bit. I found opening the command prompt in admin mode and typing

sfc /scannow

Fixed the drive issues that were creating the crash. It happens still but much, much more rare.
rogb1970 16 AGO 2022 a las 1:24 a. m. 
Yourt sfc may have found some issues, but, they weren't causing the crash. You said yourself that the crash still happens, so, whatever issues sfc found were coincidental.
Hans 16 AGO 2022 a las 2:36 a. m. 
Publicado originalmente por Citizen Alpha:
I had this crashing quite a bit. I found opening the command prompt in admin mode and typing

sfc /scannow

Fixed the drive issues that were creating the crash. It happens still but much, much more rare.

Plus sfc /scannow fixes Windows system file corruptions, not disk errors

You're thinking of chkdsk
butterwaach 19 AGO 2022 a las 1:05 a. m. 
also joining the club of crashing installations:

21:18:32:588 (00015720) > [Crash] Memory statistics:
21:18:32:588 (00015720) > [Crash] Total RAM = 63.9 GB (65449 MB)
21:18:32:588 (00015720) > [Crash] Avail RAM = 44.2 GB (45250 MB)
21:18:32:588 (00015720) > [Crash] Total virtual memory = 131072.0 GB (134217727 MB)
21:18:32:588 (00015720) > [Crash] Avail virtual memory = 130966.7 GB (134109924 MB)
21:18:32:588 (00015720) > [Crash] Total page file = 127.9 GB (130985 MB)
21:18:32:588 (00015720) > [Crash] Avail page file = 98.3 GB (100669 MB)
21:18:32:588 (00015720) > [Crash] Unhandled exception at address 0x000000007fc269c2 (code: 0xc0000005): "Access violation"

im on win 11 and my system is rock stable otherwise - this is something solely MSMR related. initially i thought that it might be due to the fact that i have win 11 insider updates installed, but since more people get the very same issue and most likely dont have the win 11 insider updates running im fairly sure that this can be ruled out.

some official feedback would be really good, at least that the problem is acknowledged by the devs. i could rule out RT as the crashes happen with it on and off. for me the game cant even load, it crashes during the load into the game immediately. the only thing which i found as workaround so far was to lower all ingame settings and then load into the game. once ingame i can crank up everything to max and the game runs fine until it crashes. mostly crashes seem to happen when the game does any loading (spider symbol in the lower right corner) - which means that all cutscenes basically trigger a crash!

on a sidenote, the game runs absolutely fine on my steam deck and never crashed so far.

my HW specs would be:

AMD Ryzen 9 5950X
64GB Gskill TridentZ 3800C16D RAM
ASUS ROG Strix 3080 (10GB) @ 1440p

i tried with DLSS on and off, with RT on and off, with HDR on and off - doesn't make any difference so far.
rogb1970 19 AGO 2022 a las 1:35 a. m. 
Is this with the patch applied?
butterwaach 19 AGO 2022 a las 1:58 a. m. 
both. the patch didn't change anything on my system.
rogb1970 19 AGO 2022 a las 6:14 a. m. 
Oh, hope you have more success with the next one. I might wait till they reckon everything is fixed before I play it again. If this was an indie title, they'd call it Early Access and we'd all be fine with it.
metal spider 19 AGO 2022 a las 6:54 a. m. 
is everyone with this crash on ryzen? maybe you didnt stress the infinity fabric enough when you tuned your ram?this game stresses the cpu a lot more then other games.

im on intel with tuned ram and dont have these crashes,i had some other ones but never with this error message.
< >
Mostrando 16-29 de 29 comentarios
Por página: 1530 50

Publicado el: 15 AGO 2022 a las 6:09 a. m.
Mensajes: 29