Fatal error when starting OpenMW 0.48

[huntertaylor367]

I recently upgraded to an Asus Tuf F15, and am trying to get OpenMW 0.48 to work on a fresh vanilla install of Morrowind before I start modding it from the ground up to take advantage of actually having a relatively powerful computer. I made sure OpenMW is installed on hardware instead of OneDrive as I read that can cause issues, and Morrowind is installed properly, but I get a fatal error whenever I hit 'Play'. Opening up the crash .dmp file in WinDBG, the exception analysis gives this:
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************


KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 531

Key : Analysis.Elapsed.mSec
Value: 757

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 77

Key : Analysis.Init.Elapsed.mSec
Value: 12426

Key : Analysis.Memory.CommitPeak.Mb
Value: 131

Key : Failure.Bucket
Value: INVALID_POINTER_READ_c0000005_openmw.exe!Unknown

Key : Failure.Hash
Value: {c26eba52-cb30-ed3f-a799-215b23e6306c}

Key : Timeline.OS.Boot.DeltaSec
Value: 533908

Key : Timeline.Process.Start.DeltaSec
Value: 1

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


FILE_IN_CAB: openmw-crash.dmp

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
rax=000000f3db8fed00 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=00007ff669f39bdf rsp=000000f3db8feb30 rbp=000000f3db8fee58
r8=00000000000000b0 r9=0000000000000000 r10=00007fff55e90000
r11=000000f3db8feb30 r12=0000000000000000 r13=00000255845c1900
r14=00000255845c1900 r15=000000f3db8fed00
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210202
openmw+0xe09bdf:
00007ff6`69f39bdf 807c19ff00 cmp byte ptr [rcx+rbx-1],0 ds:ffffffff`ffffffff=??
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff669f39bdf (openmw+0x0000000000e09bdf)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

PROCESS_NAME: openmw.exe

READ_ADDRESS: ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

STACK_TEXT:
000000f3`db8feb30 00007ff6`69f3c7b1 : 00000000`00000000 038e38e3`00000000 00000000`00000000 00000000`00000000 : openmw+0xe09bdf
000000f3`db8febd0 00007ff6`69f74b54 : 00000255`00000000 00000255`84e82c01 00000255`845c1900 00000255`845c1948 : openmw+0xe0c7b1
000000f3`db8feef0 00007ff6`69f3fa1e : 00000255`845c1900 00000000`00000000 000000f3`db8ff1a0 00007ff6`6a1505a3 : openmw+0xe44b54
000000f3`db8ff090 00007ff6`69e6ddb4 : 00000255`85d1ed00 00000000`00000024 00000000`00000000 000000f3`db8ff130 : openmw+0xe0fa1e
000000f3`db8ff0e0 00007ff6`69e6e024 : 00000255`85d1ed00 00000255`846083e0 00000255`84fa94f0 000000f3`db8ff130 : openmw+0xd3ddb4
000000f3`db8ff110 00007ff6`698be438 : 00000255`84fa94f0 00000255`8456d820 00000000`00000000 000000f3`db8ff355 : openmw+0xd3e024
000000f3`db8ff230 00007ff6`698bc383 : 00000255`845dade0 00000255`845dade0 00007ff6`6a72aad0 00000000`00000000 : openmw+0x78e438
000000f3`db8ff5a0 00007ff6`698b2cd1 : 00000255`ffaba5d0 00000255`ffaba5d0 00000255`ffb02e90 00000000`00000001 : openmw+0x78c383
000000f3`db8ff900 00007ff6`69c8dbb6 : 00000000`00000000 00000255`ffacb780 00000255`ffacb780 000000f3`db8ffde0 : openmw+0x782cd1
000000f3`db8ffad0 00007ff6`698b2dc6 : 00007ff6`6a308278 00007ff6`6a150229 00007ff6`00000000 00007ff6`6a308000 : openmw+0xb5dbb6
000000f3`db8ffdc0 00007ff6`6a151124 : 00007ff6`6a43ba40 00007ff6`6a151289 00000000`00000000 00000000`00000000 : openmw+0x782dc6
000000f3`db8ffe00 00007fff`65fd257d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : openmw+0x1021124
000000f3`db8ffe40 00007fff`672eaa58 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1d
000000f3`db8ffe70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28


STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: openmw+e09bdf

MODULE_NAME: openmw

IMAGE_NAME: openmw.exe

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_openmw.exe!Unknown

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c26eba52-cb30-ed3f-a799-215b23e6306c}


I am no coder, so I have no idea what this means. Please help?

[psi29a]

Any additional info, like from log files?

[huntertaylor367]

Would the log be something found in the crash.dmp file? All that is in the OpenMW folder in 'My Documents' are the saves and screenshots folders, 3 .cfg files, 2 text docs, one with a list of basic info on openmw such as version number and the other is a wizard file that says I started OpenMW yesterday and nothing else. The last two files are a shaders file with the ending '.yaml' and the crash.dmp file. If the log file is something located elsewhere please let me know and I will see what is there and post it to the forum. I tried to attach the crash file, but the file extension is apparently invalid. Would it help if I somehow got that file to you guys?

[AnyOldName3]

You're not going to be able to analyse the crash dump yourself without the debug symbols and a decent amount of knowledge about OpenMW's internals, so it's definitely best to get the dump to us. As for the log files, it sounds like you've got the super-duper irritating option that hides file extensions enabled. If you go to the View tab in explorer, there should be a checkbox towards the right that enabled file name extensions. Toggle it, and it'll probably turn out one of those text files is actually the log.

[huntertaylor367]

So I will make sure to give that a try and locate the log when I get off work today. With regard to getting the crash file to you, would I need to post it to the gitlab link given in the error message? Or is there some alternate method I should use?

Edit: I have used the instructions that you gave to find the log file. The contents are as follows:

[23:44:04.707 I] OpenMW version 0.48.0
[23:44:04.707 I] Revision: 3b669c2b02
[23:44:04.708 I] Using default (English) font encoding.
[23:44:04.708 W] No such dir: "C:\Users\hunte\Documents\My Games\OpenMW/data"
[23:44:04.708 I] OSG version: 3.6.5
[23:44:04.708 I] SDL version: 2.24.0
[23:44:04.709 I] Loading shader settings file: "C:\Users\hunte\Documents\My Games\OpenMW/shaders.yaml"
[23:44:05.484 I] OpenGL Vendor: NVIDIA Corporation
[23:44:05.485 I] OpenGL Renderer: NVIDIA GeForce RTX 4070 Laptop GPU/PCIe/SSE2
[23:44:05.485 I] OpenGL Version: 4.6.0 NVIDIA 536.45
[23:44:05.485 I] Using reverse-z depth buffer
[23:44:05.486 I] Adding BSA archive C:\Program Files (x86)\Steam\steamapps\common\Morrowind\Data Files\Morrowind.bsa
[23:44:05.489 I] Adding BSA archive C:\Program Files (x86)\Steam\steamapps\common\Morrowind\Data Files\Morrowind - Invalidation.bsa

[AnyOldName3]

Morrowind doesn't benefit from an archive invalidation BSA, and the one that comes with MO2 is known to crash 0.48 (and possibly the original engine, too, as it's not a Morrowind BSA). If that's where it's come from, you can either disable archive invalidation in MO2 (and remove the BSA from your openmw.cfg), or switch to a dev build of OpenMW.

Also, if that invalidation BSA's made it into your Morrowind installation directory, it suggests you might be running OpenMW through MO2. We recommend against that as MO2's VFS has some bugs that affect OpenMW. Instead, there are a couple of MO2 plugins that let you export your MO2 setup so OpenMW can see it.

[huntertaylor367]

Yes, I use MO2 and the exporter plugin. I will try the .cfg edits/fix you suggested. If that fails, I will install the nightly dev build (0.49 I believe) see if that works, and I will update this post to if the issue has been resolvedt. Also for informational purposes, I have cross posted this issue to Gitlab for OpenMW, where I was able to attach the crash.dmp and openmw.log files to that post, link below.
https://gitlab.com/OpenMW/openmw/-/issues/7779

Edit: I found the invalidation archive bsa in both the OpenMW.cfg and in the data files folder of my Morrowind install. After deleting them both, OpenMW 0.48 is working just fine, even with my mod list installed! You guys are true heroes, Morrowind has been my favorite game since childhood. Thank you for helping me get back to Vvardenfell. I will update the aforementioned Gitlab post to mark it resolved and describe the solution. Once again, thank you guys.