Jump to content

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


Recommended Posts

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:

 

 

mm.jpg

 

mm2.jpg

 

 

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...

Link to comment
Share on other sites

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.

Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Asus 1080ti EK-waterblock - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus PG278Q 27" QHD Gsync 144Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X 

Link to comment
Share on other sites

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 by sew333
Link to comment
Share on other sites

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:

Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Asus 1080ti EK-waterblock - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus PG278Q 27" QHD Gsync 144Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X 

Link to comment
Share on other sites

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.

 

 

Link to comment
Share on other sites

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.

Z790, 13700K, RTX4080, 32 gig RAM, Warthog,  WarBRD base , Virpil Pedals, Pico 4

 

Link to comment
Share on other sites

And this thread is related to DCS how? :P

Both applications require a pc?

 

Am I missing something here :huh:

System specs:

 

i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU

HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM

 

~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH

Link to comment
Share on other sites

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:

 

 

mm.jpg

 

mm2.jpg

 

 

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!

Mainboard: ASUS Maximus X Hero Intel Z 370

CPU: Intel Core i7-8086K @ 4.0 GHz

Memory: 32GB Corsair Dominator Platinum DDR4-3000

Graphics Card: ASUS NVIDIA GeForce RTX 3080 10GB

Monitor ASUS PA 329 32" @ 4K

1 SSD Samsung 860 PRO 256 GB

1 SSD Samsung 860 PRO 4 TB

Windows 10 - 64 V. 2004

CH Pro combatstick, throttle and pedals

Link to comment
Share on other sites

[...]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. ;)

i9-9900K @5GHz, Z390 Aorus Pro, 32GB DDR4-3200MHz, EVGA RTX 2080Ti FTW3 Ultra, Seasonic Focus+ Platinum 850W PSU, TM Warthog HOTAS, CH Pro pedals, 2x MFD's, MT deskmounts, Asus 32" 1440p display, EDTracker Pro Wireless, HP Reverb

Link to comment
Share on other sites

Z790, 13700K, RTX4080, 32 gig RAM, Warthog,  WarBRD base , Virpil Pedals, Pico 4

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...