Jump to content

Recommended Posts

Posted

Same here, crashes on average like once per hour, at random (twice when opening a corpse or container to loot it, but then loot it fine after restarting game) or just when clicking on someone to speak to them or just while running. Gamepass for PC version here.

Posted

Thanks for posting! Are there any entries in the windows Event Viewer?

To check, open Start, type in "Event Viewer" and press Yes if User Activation Control asks you to. Once the next window loads, expand the "Windows Logs" entry in the left frame, and select "Application". On the right hand side, there will be a "Filter current log" option. Click that, then check the Critical, Error, and Warning checkboxes, then press okay.  You will see entries in the middle pane - are there any which coincide with the time of the crash?

Posted (edited)

"You will see entries in the middle pane - are there any which coincide with the time of the crash?"

Yes, what i have to copy?
Edited by Vol4onok
Posted

When you click on one, the bottom half of the middle pane will fill up. Grab what's in the General tab.

If there are a lot, it might be easier to save the log and upload it. You can use the "Save filtered log file as..." (for filtered logs) or "Save all events as..." (for unfiltered ones) on the right to do that. As an example, this is what you might see:

Faulting application name: IndianaWindowsStore-Win64-Shipping.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: IndianaWindowsStore-Win64-Shipping.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000c04e2c
Faulting process ID: 0x1a10
Faulting application start time: 0x01d58be48902879a
Faulting application path: C:\Program Files\WindowsApps\PrivateDivision.TheOuterWorldsWindows10_1.0.369.0_x64__hv3d7yfbgr2rp\Indiana\Binaries\Win64\IndianaWindowsStore-Win64-Shipping.exe
Faulting module path: C:\Program Files\WindowsApps\PrivateDivision.TheOuterWorldsWindows10_1.0.369.0_x64__hv3d7yfbgr2rp\Indiana\Binaries\Win64\IndianaWindowsStore-Win64-Shipping.exe
Report ID: *******
Faulting package full name: PrivateDivision.TheOuterWorldsWindows10_1.0.369.0_x64__hv3d7yfbgr2rp
Faulting package-relative application ID: App

 

Posted

Faulting application name: IndianaWindowsStore-Win64-Shipping.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: IndianaWindowsStore-Win64-Shipping.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000c04e2c
Faulting process id: 0x3470
Faulting application start time: 0x01d58cbc8cf9c5ba
Faulting application path: C:\Program Files\WindowsApps\PrivateDivision.TheOuterWorldsWindows10_1.0.369.0_x64__hv3d7yfbgr2rp\Indiana\Binaries\Win64\IndianaWindowsStore-Win64-Shipping.exe
Faulting module path: C:\Program Files\WindowsApps\PrivateDivision.TheOuterWorldsWindows10_1.0.369.0_x64__hv3d7yfbgr2rp\Indiana\Binaries\Win64\IndianaWindowsStore-Win64-Shipping.exe
Report Id: 87b5c8d6-cdfb-401d-969d-7784a198130a
Faulting package full name: PrivateDivision.TheOuterWorldsWindows10_1.0.369.0_x64__hv3d7yfbgr2rp
Faulting package-relative application ID: App

Posted

Check memory consumption if there are not any memory leaks. Also try to add the game to whitelist in your antivir if you use one.

Posted
7 minutes ago, Pilda said:

Check memory consumption if there are not any memory leaks. Also try to add the game to whitelist in your antivir if you use one.

Just windows security.

Posted
  1. Are you running the game in Fullscreen or Borderless Windowed mode?
  2. What resolution are you running the game at?

I have spent the past 24 hours working on an identical issue and, having done a lot of things, so far setting it to Fullscreen and 1080p resolution has worked. I don't know which did it or why, but... give it a go and see if it helps?

(For the technically minded, already formatted Windows, updated drivers, checked RAM for faults, clean boot, and checked for Windows Defender interference).

DxDiag, full system specs and windows version will help the devs look into additional issues if there are any (see https://support.obsidian.net/article/50-how-do-i-report-a-bug for detailed instructions).

Let me know how you go!

Posted

Ахах. Волчонок, как мило. :blush:

Код ошибки 0xc0000005 – это всегда Memory Acces Violation, ошибка чтения или записи виртуальной памяти (оперативка + файл подкачки). Попробуй не запускать браузер при игре, убедись что файл подкачки достаточного размера (около 8 Гб хватит), если это не поможет проверь оперативную память "Средством проверки памяти",
В 99% это нехватка оперативки, когда на фоне открыт браузер с 100500 вкладами, либо оперативка забита кэшем, который системе некуда выгрузить из-за маленького файла подкачки. Никакие фулскрины тут ни при чем.

Posted

Everyone with this issue – Exception code: 0xc0000005  – it's Memory Acces Violation. To be more specific, you don't have enough free RAM (it can be cashed with various data) or too small Page File. Try to increase Page File size.

Posted
2 minutes ago, Phenomenum said:

Ахах. Волчонок, как мило. :blush:

Код ошибки 0xc0000005 – это всегда Memory Acces Violation, ошибка чтения или записи виртуальной памяти (оперативка + файл подкачки). Попробуй не запускать браузер при игре, убедись что файл подкачки достаточного размера (около 8 Гб хватит), если это не поможет проверь оперативную память "Средством проверки памяти",
В 99% это нехватка оперативки, когда на фоне открыт браузер с 100500 вкладами, либо оперативка забита кэшем, который системе некуда выгрузить из-за маленького файла подкачки. Никакие фулскрины тут ни при чем.

Тут можно по русски писать? 😄
У меня 16 гб оперативной памяти и 7гб файл подкачки, в браузере открыто только 3-4 вкладки и без браузера тоже вылетало.

Posted (edited)

Можно, но лучше не злоупотреблять – некультурно это. Увеличь файл подкачки до 16 Гб, что б уж наверняка. Если вылеты продолжатся, протестируй оперативку - может быть битая память и происходит ошибка при доступе к этой области памяти. Так же это может быть следствием разгона памяти.

Edited by Phenomenum
Posted

Narrowing down the identical issue for someone else, the move to Fullscreen seems to have done the trick. Will report back in a few days.

That error does appear for insufficient RAM, but at its heart its just a segfault, which can happen for any number of reasons. The system I've been troubleshooting has 32GB DDR4.

At any rate, let us know how you go!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...