OpenMSX only works once and then crashes

Van Murilo Carmello

Resident (39)

14-04-2021, 00:39

Application Compatibility thing - yes, I had already tried compatibility mode and all the options that are there

I created another user, but same problem

Van Grauw

Ascended (10772)

14-04-2021, 00:42

Update your graphics drivers?

Van Murilo Carmello

Resident (39)

14-04-2021, 01:22

Yes, win and Graphics Drivers

Windows 10 Pro - 64 bits, Versão: 21H1 - Compilação: 19043.906
RTX 2060 - Drivers 465,89

Van ren

Paragon (1934)

14-04-2021, 13:52

Murilo Carmello wrote:

Quote:

One thing to try is to run with the SDL renderer (only): openmsx -command "set renderer SDL"

I already tried to open it from the command line and the same thing happens, is that what you are suggesting? I also tried to run the program directly, without the installer, it also didn't work

I suggest running from the cmd line issuing the exact command I gave.

Another thing you can try:

make sure openMSX (and Catapult perhaps) is not running or hanging (task manager);
delete (or rename) the openMSX folder in My Documents (%USERPROFILE%\Documents);
run openmsx.

You can 'reset' (blank state) Catapult by deleting or renaming HKEY_CURRENT_USER\Software\openMSX team\Catapult in the registry (regedit). So you can try that as well before running Catapult.

---
And have you tried the %LOCALAPPDATA% suggestion as well?
So e.g. unzip openmsx zip (17.0RC) into C:\Users\Murilo\AppData\Local\openMSX (you can enter %LOCALAPPDATA% in the address bar of Explorer), then open cmd prompt, issue set OPENMSX_HOME=C:\Users\Murilo\AppData\Local\openMSX\_user & run from this cmd prompt (try including the renderer cmd as described above) (note: OPENMSX_HOME only works with 17RC – there's an updated RC1 available (2021-04-13))

---
Another: if you've only tried the x64 version, try the x86 version.

---
Yet another: desktop compositing (composition)..
While not a trivial matter turning it off in Windows 10 apparently (note the separate section), it makes a difference on e.g. Windows 7 and might be related to the issue: https://digicruncher.com/enable-or-disable-desktop-composition/

Note: on Win7 I used net stop uxsms to disable it, I see no mention of that in that article, not sure if that still works in Win10, it's by far the easiest way (admin console required).
Here's another 'guide' to disable it on Win10 (might be better than the one above, dunno): https://superuser.com/questions/1016170/temporarily-disable-...

---
Finally, you could perhaps look into Nvidia's program 3D settings. If there's a profile for openmsx delete it, or make sure it has e.g. Use the 3D application setting for Vertical sync & Auto for Threaded optimization.

Van Manuel

Ascended (19469)

14-04-2021, 13:51

The SDL/SDLGL-PP thing doesn't address that even Catapult doesn't run. Something really special is going on here. Perhaps this version doesn't allow non-signed applications to do anything?

Van ren

Paragon (1934)

14-04-2021, 14:24

Yeah. Would be interesting to know if e.g. other emulators give issues as well.

Perhaps try DOSBox-X, which includes an SDL2 build (which openMSX >= 16 uses as well). (Or DOSBox Staging.)

Otherwise I could suggest running some system diagnostics, or (at least) a (low-level) memory test.

Although, what @gustavobk wrote is rather interesting, saying it used to work, but then it suddenly stopped working. That would suggest some windows update might be to blame?

@Murilo: did it use to work fine for you as well?
@Murilo/gustavobk: could you check if there was some Windows update just before it stopped working?

Van Briqunullus

Paladin (675)

14-04-2021, 18:42

Manuel wrote:

Perhaps this version doesn't allow non-signed applications to do anything?

AFAIK 21H1 is just a minor update. It's still possible, but I don't expect this causes the problem.

Van Zandig Slaytanic

Resident (44)

14-04-2021, 20:38

Murilo Carmello wrote:

Yes, win and Graphics Drivers

Windows 10 Pro - 64 bits, Versão: 21H1 - Compilação: 19043.906
RTX 2060 - Drivers 465,89

- Open an admin command prompt then type: sfc /scannow
to let it check the system files.

- Could be a certain program loading at startup. Try a clean boot to see if a program is interfering with openMSX.

Van Murilo Carmello

Resident (39)

15-04-2021, 02:37

wow, lots of suggestions
First let me answer what I have already tested and it didn't work:

1) make sure openMSX (and Catapult perhaps) is not running or hanging (task manager);
Yes, it crashes on Task, the strange thing is that even if I close OpenMSX on the task, it still doesn't run anymore, I need to reset the machine

2) delete (or rename) the openMSX folder in My Documents (%USERPROFILE%\Documents);
I already tried deleting, it didn't work

3) Another: if you've only tried the x64 version, try the x86 version.
I’ve tried, and I’ve also tried OpenMSX 17, 16 and 15 versions 32 and 64

4) Perhaps try DOSBox-X, which includes an SDL2 build (which openMSX >= 16 uses as well). (Or DOSBox Staging.)
I tested it, it works perfect ( my pc just doesn't like OpenMSX )

5) - Open an admin command prompt then type: sfc /scannow to let it check the system files.
Done, everthing is fine

ahh, one more information:
It crashes and I can see it in the Task manager, but if I leave it there, after about 10 min or more it works again

Thank you very much to all of you for the tips, now I will test the suggestions that I had not yet thought

Van Murilo Carmello

Resident (39)

15-04-2021, 03:08

You can 'reset' (blank state) Catapult by deleting or renaming HKEY_CURRENT_USER\Software\openMSX team\Catapult in the registry (regedit). So you can try that as well before running Catapult.

Same problem

thinking about reg, I tested the following: uninstalled, then in explorer I searched for OpenMSX and deleted everything I found and then ran 3 programs that clean reg:
Registry Repair
Auslogics Registry Cleaner
MV RegClean 2021 (8.0)
I reset the PC and installed it again

Nothing same problem