WinUAE 4.0.1 x64 keeps crashing

keith.f.kelly · 02 September 2018, 14:07

Got a new laptop (MSI GS65 Stealth Thin 8RF-037). Using the same exact WinUAE + files (HDF, configs, etc) I've used without problems on my old laptop (Lenovo IdeaPad U530 Touch).

On the new laptop, WinUAE boots off the system HDF (Workbench 3.9 w/ BoingBags 1, 2, 3, & 4) fine, boots into TinyLauncher fine... but when I choose any game from the TinyLauncher menu, WinUAE crashes.

Minidump attached.

BTW, it would be super-helpful if you could make matching symbols/PDB available for download with each release so folks like me with the know-how could at least load the minidump up inside WinDBG and get a call stack. Just a suggestion

Toni Wilen · 02 September 2018, 14:44

Symbol file is too large, both 32-bit and 64-bit 7zipped is almost 20M.

Anyway, your crash is in JIT code which usually means something did something too bad or Amiga stack is too low etc... Disable JIT and try again.

(btw, GS65 Stealth Thin includes "a-volute" sound component that, at least old versions, hooks to all executables that use D3D11, and makes winuae d3d11 implementation to fail when switching modes)

keith.f.kelly · 02 September 2018, 20:51

Thanks for the suggestions! But it turned out to be a problem with my Startup-Sequence... somehow, at one point the other day, I must have managed to move TinyLauncher before LoadWB... and that one little thing is what caused all the problems. It's still strange that it caused WinUAE itself to crash (even with JIT disabled and "A-Volute" uninstalled) rather than just causing a crash inside the virtual Amiga... but whatever, I'm happy again

Toni Wilen · 02 September 2018, 20:55

Quote:

Originally Posted by keith.f.kelly

Thanks for the suggestions! But it turned out to be a problem with my Startup-Sequence... somehow, at one point the other day, I must have managed to move TinyLauncher before LoadWB... and that one little thing is what caused all the problems. It's still strange that it caused WinUAE itself to crash (even with JIT disabled and "A-Volute" uninstalled) rather than just causing a crash inside the virtual Amiga... but whatever, I'm happy again

I am not happy yet

Attach new crash dump without JIT enabled, thanks. JIT can crash but non-JIT mode should not crash.

Attach also your config file and log (tick logging option in misc panel to enable it)

keith.f.kelly · 10 September 2018, 02:48

I finally found some time to try to repro this again for you and get a crash dump, but what I'm finding now is the crash only happens with JIT enabled. With JIT disabled, the emulated Amiga just hangs, but WinUAE does not crash. Sorry for the false alarm!

Toni Wilen · 10 September 2018, 20:23

Can you (privately if needed) send me your HDF that crashes under JIT (+config file).

100% reproducible JIT crashes are really rare and this hopefully would help to fix some unknown JIT bug.

keith.f.kelly · 15 September 2018, 19:17

Yes, I can do that. I'm working on paring it down to a minimal/small set of files and configuration that still repro's the issue, so I can send you a reasonably-sized ZIP file.

tygre · 29 October 2018, 01:22

Hi Toni and all!

Sorry to hijack this thread, but my problem seems totally fitting: I have a program that, when clicking a one particular button, causes WinUAE v4.0.1 to crash only when the JIT is enabled (when the JIT is disabled, Enforcer provides hints on the problem).

I cannot provide a log file (!?) when the JIT is enabled because none is created: when I click that particular button, WinUAE disappears, a MS-DOS Console-like window appears and disappears (too fast to read anything, it looks like a dump though), and then nothing. I must rerun WinUAE.

How can I help you track this problem?

Best,

Toni Wilen · 29 October 2018, 18:25

You can try using -log -logflush command line parameters. But JIT related crashes are difficult to debug and usually they happen when program does something bad. You can check latest 4.1.0 beta if it works better (it has some basic "jit crash protection" but it can also make things even worse..)

tygre · 02 November 2018, 02:05

Hi Toni!

Quote:

Originally Posted by Toni Wilen

You can try using -log -logflush command line parameters. But JIT related crashes are difficult to debug and usually they happen when program does something bad. You can check latest 4.1.0 beta if it works better (it has some basic "jit crash protection" but it can also make things even worse..)

Yes, indeed, with WinUAE 4.1.0b7, WinUAE doesn't crash

The emulation "freezes" and it is possible to invoke the UI with F12 and reset/restart the emulation, nice!

Cheers!

PS. The options -log -logflush produces a Console window during the running but no winuaelog.txt file is created, am I doing something wrong?

DamienD · 02 November 2018, 11:06

Quote:

Originally Posted by tygre

PS. The options -log -logflush produces a Console window during the running but no winuaelog.txt file is created, am I doing something wrong?

After WinUAE starts, select "Paths", tick "Enable full logging" before starting your config

tygre · 02 November 2018, 21:12

Thanks DamienD but I already had ticked this option, and still no log is written on the disk... I looked into the WinUAE folder as well as next to the Configurations files, etc.

Toni Wilen · 02 November 2018, 22:02

Check winuaebootlog.txt last line for log path. It also mentions if it is enabled.

tygre · 02 November 2018, 23:46

Hi Toni!

Unfortunately, when I wrote that no log is written on disk, I really meant it: not even "winuaebootlog.txt" (which should be in the same folder as WinUAE.exe, shouldn't it?)

Is there something else that I could do?

Best!

PeterK · 03 November 2018, 01:47

No, the logs are not always appearing in the directory where WinUAE.exe is started from. Open the WinUAE properties page for "Paths" where you can see on the last line to which path/file the output is send.

For example, on my system it's in C:\Users\Public\Documents\Amiga Files\WinUAE\winuaebootlog.txt

tygre · 03 November 2018, 03:40

Hi PeterK and Toni!

Duh! I learned again something new, thanks PeterK

So, I found the logs, Toni! I attached them here... Are they helpful? Don't hesitate if I should do something else to help!

Cheers!

AMIGASYSTEM · 03 November 2018, 09:42

tygre I have no problem running AmiModRadio either on WinUAE 4.0.1 32/64 bit

tygre · 03 November 2018, 20:42

Quote:

Originally Posted by AMIGASYSTEM

tygre I have no problem running AmiModRadio either on WinUAE 4.0.1 32/64 bit

Hi AmigaSystem and thanks!

It is my current (development) version that had a bug that make WinUAE crash badly

Cheers!

AMIGASYSTEM · 03 November 2018, 20:59

I had imagined it, if you need my own test, I'm available

Toni Wilen · 04 November 2018, 17:55

Quote:

Originally Posted by tygre

Hi PeterK and Toni!

Duh! I learned again something new, thanks PeterK

So, I found the logs, Toni! I attached them here... Are they helpful? Don't hesitate if I should do something else to help!

Cheers!

Still no winuaelog.txt included.. and dump file is zero size.

03 November 2018, 09:42	#17
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,248	tygre I have no problem running AmiModRadio either on WinUAE 4.0.1 32/64 bit Last edited by AMIGASYSTEM; 09 November 2018 at 23:24.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Request: Long double (80bit) functions in x86/x64 assembly for WinUAE	Toni Wilen	request.Other	2	20 April 2018 08:50
Anyone had this problem with winuae x64 installer?	Aminic500	support.WinUAE	17	22 October 2017 03:18
WinUAE x64 Crahses	BlackByte	support.WinUAE	9	23 December 2015 12:51
Win7 Ultimate x64 WinUAE 2.2 some games don't work	dorfmopp	support.WinUAE	9	14 September 2010 16:56
WinUAE 2.1, Catweasel, and Windows 7 x64	JeffreyUS	support.WinUAE	1	22 May 2010 14:26

02 September 2018, 14:44	#2
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,507	Symbol file is too large, both 32-bit and 64-bit 7zipped is almost 20M. Anyway, your crash is in JIT code which usually means something did something too bad or Amiga stack is too low etc... Disable JIT and try again. (btw, GS65 Stealth Thin includes "a-volute" sound component that, at least old versions, hooks to all executables that use D3D11, and makes winuae d3d11 implementation to fail when switching modes)

02 September 2018, 20:51	#3
keith.f.kelly Registered User Join Date: Aug 2018 Location: Sammamish, WA, USA Posts: 13	Thanks for the suggestions! But it turned out to be a problem with my Startup-Sequence... somehow, at one point the other day, I must have managed to move TinyLauncher before LoadWB... and that one little thing is what caused all the problems. It's still strange that it caused WinUAE itself to crash (even with JIT disabled and "A-Volute" uninstalled) rather than just causing a crash inside the virtual Amiga... but whatever, I'm happy again

10 September 2018, 02:48	#5
keith.f.kelly Registered User Join Date: Aug 2018 Location: Sammamish, WA, USA Posts: 13	I finally found some time to try to repro this again for you and get a crash dump, but what I'm finding now is the crash only happens with JIT enabled. With JIT disabled, the emulated Amiga just hangs, but WinUAE does not crash. Sorry for the false alarm!

10 September 2018, 20:23	#6
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,507	Can you (privately if needed) send me your HDF that crashes under JIT (+config file). 100% reproducible JIT crashes are really rare and this hopefully would help to fix some unknown JIT bug.

15 September 2018, 19:17	#7
keith.f.kelly Registered User Join Date: Aug 2018 Location: Sammamish, WA, USA Posts: 13	Yes, I can do that. I'm working on paring it down to a minimal/small set of files and configuration that still repro's the issue, so I can send you a reasonably-sized ZIP file.

29 October 2018, 01:22	#8
tygre Returning fan! Join Date: Jan 2011 Location: Montréal, QC, Canada Posts: 1,434	Hi Toni and all! Sorry to hijack this thread, but my problem seems totally fitting: I have a program that, when clicking a one particular button, causes WinUAE v4.0.1 to crash only when the JIT is enabled (when the JIT is disabled, Enforcer provides hints on the problem). I cannot provide a log file (!?) when the JIT is enabled because none is created: when I click that particular button, WinUAE disappears, a MS-DOS Console-like window appears and disappears (too fast to read anything, it looks like a dump though), and then nothing. I must rerun WinUAE. How can I help you track this problem? Best,

29 October 2018, 18:25	#9
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,507	You can try using -log -logflush command line parameters. But JIT related crashes are difficult to debug and usually they happen when program does something bad. You can check latest 4.1.0 beta if it works better (it has some basic "jit crash protection" but it can also make things even worse..)

02 November 2018, 21:12	#12
tygre Returning fan! Join Date: Jan 2011 Location: Montréal, QC, Canada Posts: 1,434	Thanks DamienD but I already had ticked this option, and still no log is written on the disk... I looked into the WinUAE folder as well as next to the Configurations files, etc.

02 November 2018, 22:02	#13
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,507	Check winuaebootlog.txt last line for log path. It also mentions if it is enabled.

02 November 2018, 23:46	#14
tygre Returning fan! Join Date: Jan 2011 Location: Montréal, QC, Canada Posts: 1,434	Hi Toni! Unfortunately, when I wrote that no log is written on disk, I really meant it: not even "winuaebootlog.txt" (which should be in the same folder as WinUAE.exe, shouldn't it?) Is there something else that I could do? Best!

03 November 2018, 01:47	#15
PeterK Registered User Join Date: Apr 2005 Location: digital hell, Germany, after 1984, but worse Posts: 3,366	No, the logs are not always appearing in the directory where WinUAE.exe is started from. Open the WinUAE properties page for "Paths" where you can see on the last line to which path/file the output is send. For example, on my system it's in C:\Users\Public\Documents\Amiga Files\WinUAE\winuaebootlog.txt

03 November 2018, 20:59	#19
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,248	I had imagined it, if you need my own test, I'm available

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)