Jump to content
  • Sign Up

Dorgrin

Members
  • Content Count

    39
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Dorgrin

  • Rank
    (1) Prestidigitator

Profile Information

  • Location
    Australia
  • Xbox Gamertag
    Dorgrin
  • PSN Online ID
    Dayereth
  • Steam
    Dorgrin
  • Interests
    Technology, politics, games, books, friends. Especially friends. And my cat.

Badges

  • Deadfire Backer Badge
  • Deadfire Fig Backer

Recent Profile Visitors

140 profile views
  1. 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.
  2. 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!
  3. Does it still happen in proper Fullscreen mode? Are there any error logs? See my instructions above for details on how to check.
  4. 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.
  5. 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.
  6. 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.
  7. 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
  8. 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.
  9. 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).
  10. Does restarting your PC and using a slightly earlier save file help at all?
  11. Does restarting your PC and using a slightly earlier save make a difference?
  12. 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.
  13. 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
×
×
  • Create New...