Jump to content

Dorgrin

Members
  • Posts

    39
  • Joined

  • Last visited

Everything posted by Dorgrin

  1. Does reloading that save cause it again? How about a slightly earlier save, does that work? Does a reboot fix it? (Sounds stupid but... I had this earlier and after a reboot it was peachy). And if none of the above helps, are there any entries in the 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?
  2. Does a reboot fix it? Does loading a slightly earlier save fix it? Is there anything in the 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?
  3. Does a reboot help between the first and second play throughts? Is there anything interesting in the 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 game closing the first time?) Did you buy it via Epic Games or the Windows Store / Xbox Game Pass?
  4. Does the game appear in the list if you press Windows key + X, go to Settings, click Apps, and search for The Outer Worlds in the list? If so, do Repair and/or Reset and a reboot fix the problem?
  5. If you go to the Settings app, and then Apps, and search the list for The Outer Worlds, does it appear? If so, click on it and then Advanced Options. You can try to repair it, and if it doesn't work then reset it, using the options there. Failing that, you can also try executing "wsreset" in an elevated command prompt or powershell terminal. If it still doesn't work, I'd uninstall then reinstall the game. You can also try uninstalling and re-installing all *xbox* applications in an elevated powershell prompt: Get-AppxPackage *xbox* | Remove-AppxPackage And reinstall Xbox (Beta) from the store. It'll let you reinstall the other Xbox apps from settings (will actually tell you it needs them). In the rare case you get sign in issues at that point, install the Xbox Console Companion (Beta) app too and login there, then return to the Xbox (Beta) app.
  6. You can also email the support team directly at support@obsidian.net as per https://support.obsidian.net/article/50-how-do-i-report-a-bug
  7. Might be a memory leak not being cleaned up on exit. Grab the Process Monitor from Microsoft (https://docs.microsoft.com/en-us/sysinternals/downloads/procmon), run it as admin, and use Filter > Filter from the menu. Set the first dropdown to "Process name", the second to "Begins with" and the text box to "Indiana", then hit "Add" and "Okay". When you close the game (or any time really) look for anything in the "Result" column that isn't "SUCCESS", in particular "NAME NOT FOUND" or "PATH NOT FOUND". The operation, result and detail will help figure out what happened. You can also compare the timestamp in the left most column with the one in Event Viewer to help you find the specific culprit.
  8. This looks like an outdated or corrupted Windows system or a corrupted game install. What does "winver" say when you run it, and do you have the latest updates? If you're on Version 1903 OS Build 18362, I'd re-install the game.
  9. 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!
  10. Are you running the game in Fullscreen or Borderless Windowed mode? 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!
  11. 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
  12. 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?
  13. Thanks for posting! Are there any errors 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? That info (in particular the "faulting module name" if there is a relevant entry), your save game before any crash, and your dxdiag results (press Windows key + R, enter "dxdiag" and hit enter, and click the button to save the information to a file) will help the development team track any issue down. You can email them at support@obsidian.net or keep using the forum.
  14. Thanks for that - I am troubleshooting a similar issue but one which is causing the PC to power cycle. The error code is fairly broad, but in short the app is trying to do something with memory it isn't allowed access to (or doesn't exist...). Bit odd, but nothing to worry about unless it gives you actual grief. Which build of Windows 10 are you on? (Press Windows key + R, and type winver - it'll say Microsoft Windows, then Version #### (OS Build #####.###) directly below it). Might help the devs locate the problem if it is one.
×
×
  • Create New...