Metro Exodus - c0000005 - memory access violation crashing after long time.

[sew333]

Monitor:AORUS AD27QD

 

Cpu: i7-9900K stock 4.7 with Noctua NH-D15

 

Gpu: Rtx 2080 Ti Aorus Xtreme Waterforce ( stock no oc,temps max 63C on load )

 

Ram: 32gb 2x16 GB DDR4 GSKILL 3000MHZ XMP

 

Psu: Seasonic Ultra Prime Titanium 850W

 

mobo: Asus Prime Z390-A

 

SSD: Crucial 1TBHDD: WB BLUE 1 TB

 

Case: Cooler Master Cosmos C700P

 

 

 

Hello. I have a question. When i left game running Metro Exodus for hours ,like 12-30 hours,it will crash after that time. Sometimes after 12 hours,20 hours or 30 hours.

Crash is something about c0000005 - memory access violation.

 

NULL POINTER WRITE.

 

Not driver crash. Event log nothing about driver crash. Just BUGTRAP crash.

 

Screens from debugger:

 

 

 

 

 

Is my hardware ok? I dont have any crashes in other games or benches. Realbench passing too ,memtest no errors. I am on newest nvidia drivers.Using MSI AFTERBURNER + RTSS.

 

 

Somebody said that this to me:"any game should not be crash no matter how long you play or idle...

[BitMaster]

Is your RAM overclocked ?

 

Have you enabled a XMP Profile that maybe your board cant really support properly ( obviously ).

 

 

I tell you, I can tune my RAM so it passes all tests and brute benchmarks but will BSOD with the typical suspects ( IRQ not less or equal; Page Fault bla bla... ) after a few days, sometimes weeks... and that is WAY below my XMP rating for the kit. Some boards are just not tolerant with some RAM kits.

 

Revert your RAM to 2133MHz and see if it runs w/o crashing for as long as you want it.

[sew333]

This happens only in Metro Exodus and after 12-30 hours. No at beggining.

 

And this is not BSOD but game crash.

 

Also ram tests and MEMTEST86 no errors.

 

And XMP enableed thats all.

 

 

NULL POINTER WRITE exception

is software not hardware/memory

Edited February 5, 2020 by sew333

[Mars Exulte]

12-30 hours? Jeez man, you doing some hardcore marathons??? Lol Sounds like you can avoid it by taking a break once a day :D

[BitMaster]

You should ask the Geeks in Metro Exodus Forum if you think it is a software error.

 

How could we possibly know here at ED's DCS Forum ????

 

:doh::book::music_whistling:

[Sn8ke_iis]

This is like Deja Vu. I'm pretty sure I saw this exact question posted on Reddit in the last couple weeks.

 

Anyway, I don't think you should be judging the stability of your system because you pause and/or leave a game running for 12-30 hours. I wouldn't consider that real world usage.

 

You'd be amazed at the problems rebooting can solve as it wipes the memory. Imagine trying to do math problems on the same chalkboard without erasing it from the previous class. Rebooting gives you a clean slate. It's become common for people to leave their computers on all the time, but rebooting is good thing to do before gaming and/or troubleshooting.

 

This would only be an issue if you were rendering something overnight in software like Blender. You can run Prime95 overnight or put a Blender render demo on a loop overnight if you are doing something where a crash will actually cost you time and money.

 

I wouldn't worry about it if your system is showing stability in day to day usage and passes stress tests. I think you're just chasing gremlins.

[Bearskin]

This is like Deja Vu. I'm pretty sure I saw this exact question posted on Reddit in the last couple weeks.

 

 

 

I saw this too, something about going to work, leaving the game running for 12+ hours and when returning the game had crashed.

[DerFangzahn]

Maybe be crashed after 12+ hours. Not his PC. :)

[sirrah]

And this thread is related to DCS how? :P

Both applications require a pc?

 

Am I missing something here :huh:

[ac5]

Monitor:AORUS AD27QD

 

Cpu: i7-9900K stock 4.7 with Noctua NH-D15

 

Gpu: Rtx 2080 Ti Aorus Xtreme Waterforce ( stock no oc,temps max 63C on load )

 

Ram: 32gb 2x16 GB DDR4 GSKILL 3000MHZ XMP

 

Psu: Seasonic Ultra Prime Titanium 850W

 

mobo: Asus Prime Z390-A

 

SSD: Crucial 1TBHDD: WB BLUE 1 TB

 

Case: Cooler Master Cosmos C700P

 

 

 

Hello. I have a question. When i left game running Metro Exodus for hours ,like 12-30 hours,it will crash after that time. Sometimes after 12 hours,20 hours or 30 hours.

Crash is something about c0000005 - memory access violation.

 

NULL POINTER WRITE.

 

Not driver crash. Event log nothing about driver crash. Just BUGTRAP crash.

 

Screens from debugger:

 

 

 

 

 

Is my hardware ok? I dont have any crashes in other games or benches. Realbench passing too ,memtest no errors. I am on newest nvidia drivers.Using MSI AFTERBURNER + RTSS.

 

 

Somebody said that this to me:"any game should not be crash no matter how long you play or idle...

 

Hello? This is a DCS Forum, you are in the wrong place!

[Demon_]

Maybe be crashed after 12+ hours. Not his PC. :)

[Slug72]

[...]something about going to work, leaving the game running for 12+ hours and when returning the game had crashed.

 

This seemed strangely familiar... yup, he had a similar experience here with BF5 a few months ago.

 

Since the common factor is an otherwise-stable system crashing an FPS game after 12+hrs unattended use, the obvious solution would appear to be... don't leave FPS games running for 12+hrs unattended. ;)

[Bearskin]

Well he is definitely seeking an answer

 

 

https://forums.overclockers.co.uk/threads/metro-exodus-c0000005-memory-access-violation-crash-after-20-hour.18877179/

 

 

https://forums.overclockers.co.uk/threads/weird-crash-and-after-moment-system-restarted-on-9900k-and-2080-ti.18874912/

Edited February 9, 2020 by Bearskin