No, can't reproduce if I mount it manually by double-click every time after WB boot and I don't leave it in DEVS:DOSDrivers.
The log window output is the same saved in the winuaelog.txt file? Because I don't have the time to collect it since WinUAE suddenly crashes silently closing that log with no .dmp file either…
EDIT:
Adding a Wait 1 in my sseq before the mount is a valid workaround and WinUAE won't hang anymore: seems a too fast loading can cause the issue, even with JIT off.
Code:
My Startup-Sequence
...
BindDrivers
Wait 1
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)
;IF EXISTS DEVS:Monitors
; IF EXISTS DEVS:Monitors/VGAOnly
; DEVS:Monitors/VGAOnly
; EndIF
; C:List >NIL: DEVS:Monitors/~(#?.info) TO T:M LFORMAT "DEVS:Monitors/%s"
; Execute T:M
; C:Delete >NIL: T:M
;EndIF
LoadMonDrvs
...
EDIT2:
never mind, WinUAE crashed on A+A+CTRL again from WB (but never using the shell cmd!?) :(
EDIT3:
aargh! 1/30+ crashed after reboot even when CD0: gets started manually (checked with a loop script)
EDIT4:
in short: it won't EVER crash only when NOT using CD0:, I'm almost sure it's a Intel hack's powersaving side effect. Maybe rebooting WinUAE finds the device in a strange status or simply slow to kick-in and crashes...