Dorgrin

It's definitely a bug that happens - I have random crashes without any errors. Still trying to pin down why! Glad you managed to progress though, I have no doubt Obsidian is working hard to find and squash such bugs.

I'm so sorry for the frustration. If it's any help, that file system error appears to be an issue with the drive, not the game per se. I still strongly recommend running a check to avoid any other issues, just in case. But I totally understand. Thank you for the well wishes, and I wish you the best too!

Sorry! I missed that.

Does it still happen in proper Fullscreen mode? Are there any error logs? See my instructions above for details on how to check.

Okay, that's harder to deal with then. Devs will need to look into it. To help (maybe), grab the Process Monitor (https://docs.microsoft.com/en-us/sysinternals/downloads/procmon) and run it when you play the game. When it crashes, check the relevant time entry (will be end of the log) and see what the game was doing. That'll help look further into the problem. You'll need to filter the entries because you'll see everything that's going on on your system. To do that, go to Filter > Filter in the top menu, set the first dropdown to "Process name", the second to "Starts with" and the text box to "Indiana" without the quotes. Then click add and okay, and you'll just see what the game executable is up to. Post back with the last few entries once you have them on a crash; if nothing else, it'll help the devs find the faulting code.

Interesting. Grab the Process Monitor (https://docs.microsoft.com/en-us/sysinternals/downloads/procmon) and run it when you play the game. When it crashes, check the relevant time entry (will be end of the log) and see what the game was doing. That'll help look further into the problem. You'll need to filter the entries because you'll see everything that's going on on your system. To do that, go to Filter > Filter in the top menu, set the first dropdown to "Process name", the second to "Starts with" and the text box to "Indiana" without the quotes. Then click add and okay, and you'll just see what the game executable is up to. Post back with the last few entries once you have them on a crash; if nothing else, it'll help the devs find the faulting code.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/microsoft-public-symbols might help with the symbols. I'm afraid I'm at a loss here, hopefully someone more familiar with this error can help.

Okay! Sorry for the delay, been out and about all day (Australian time zone). For the event log, click that Application error and check what the General tab below says... what's the faulting module and application, and the error code? For the second, use this tutorial (any step will do, they're in order of increasing complexity) to check your filesystem and repair it if there are any problems: https://www.tenforums.com/tutorials/40734-drive-error-checking-windows-10-a.html#option1

That's super weird, but glad it's fixed!

Looks like your GPU is throttling itself. Try reinstalling the latest driver using a clean installation (there's a checkbox during the wizard that says "Perform a clean installation"). Give it a reboot after the install too. Also, make sure your PC is dusted and the GPU heatsink is clean. Let us know how you go.

I have that same error. Have you run the system integrity check like I described and seen if that makes any difference? Full instructions are at https://support.microsoft.com/en-us/help/4026529/windows-10-using-system-file-checker. Since you seem to know your way around Windows, do you get any useful information from the dump file when you examine that memory address? I wonder what command is being run... (info on how at https://www.tenforums.com/tutorials/5558-windbg-basics-debugging-crash-dumps-windows-10-a.html).

Does restarting your PC and using a slightly earlier save file help at all?

Does restarting your PC and using a slightly earlier save make a difference?

Out of curiosity, does it continue to crash if you reboot the PC and use a slightly earlier save? As for errors, open the start menu, type "Event Viewer" and run it. In the left pane, expand "Windows logs" and then click "Application". On the right pane, find "Filter current log" and click it. Tick the "Critical", "Warning" and "Error" check boxes, then click okay. In the middle pane, look for any entries that correspond to the time of the crash. When you click on an entry, the bottom half of the middle pane will show its details - in particular, you're looking for the text in the "General" tab.

Well, you should really upgrade to Windows 10 at some point, since support for Windows 7 ended in 2015 and extended support is ending in January 2020... but onto the problem! Does the below answer (source: https://answers.unrealengine.com/questions/918179/how-i-fix-this-issue-is-bv04-to-continued-with-the.html) from the Unreal Engine forums help at all? In particular, we want to test and rule out any HDD and RAM errors which might be causing a problem. Let us know how you go

To clarify, what happens when you right click the windows logo in the task bar, go to Shut down or sign out, select restart, and then try again? Does it work then? Ideally you and Piwcio would make new thread sbecause your problems are different to the OP's and we're hijacking their thread

That indicates a problem loading a file into memory, and Windows is closing to prevent damage. Are you using the Store or the Epic version of the game? I'm curious if there's any more detail 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? (When you select one, its details appear on the lower half of the middle pane - the text in the "General" tab is what you'll want to look for). Also, I feel like verifying the integrity of the system might be an idea. Press Windows key + X, click Command Prompt (Administrator) or PowerShell (Administrator) (whichever shows up), and run the below command. Reboot, then try again. sfc /scannow Could also just be a bad install - verify the files if Epic, reinstall if Store. Let us know how you go.

Try running it in fullscreen mode instead of borderless windowed... Otherwise, if you still have issues, may we know your Windows version (Windows key + R, type "winver" without quotes, second line beneath the logo - version and build), and whether there are any errors in the Event Viewer? To check the event viewer, 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? (When you select one, its details appear on the lower half of the middle pane - the text in the "General" tab is what you'll want to look for).

I know this will sound patronising, and I don't intend it to be, but is there enough room on the drive? (I have had someone completely not notice that they were trying to install to a drive that doesn't have the room). The Windows Store should give you a code if you (via the Xbox app) click on the download status once it has an error, and click "View error details" (or words to that effect). Any luck? Failing that, do other games install to that drive? I wonder if there's some drive failure going on...

Did you reboot and/or load a different save? Sometimes happens to me too Glad it's working!

What's the windows version and build at? (Press Windows key + R, type "winver" and it'll be the second line beneath the logo). Are there any entries in the Event Viewer for the game at that time? 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?

This seems specific to the Epic Games version, and related to their launcher. I'd try disabling cloud saves if you can, and making sure you don't have a firewall preventing communications. Otherwise, might be an idea to also ask them until you can get support from a dev here. Sorry if this doesn't help much, I don't have the Epic version, just the Store version.

As per Tactile_coast's post, try a clean install of Windows from new media, see https://www.microsoft.com/en-au/software-download/windows10 for details on the process (you'll need a USB stick of at least 8GB). That should hopefully fix it up. Let us know how you go

Is there an error 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? Does running it in Fullscreen (not Borderless windowed) mode help? (Sounds stupid but I've had success depending on the problem...)