WinUAE 1.4 crash on start

Hi,

I have just downloaded and installed version 1.4 on my Dell M90 laptop. After the install completed, the application loads, but when i close and then try to re-run it immediately crashes and creates a dmp file.

Has anyone had this problem, i can't get the GUI to load at all.

I have got the dump file available if someone wouldn't mind taking a look.

Many Thanks

Andy

[Toni Wilen]

Email/attach winuaebootlog.txt and dump file, thanks.

Hi Toni,

Thanks for taking the time. I have uploaded both files, but had to add .txt extension to the dmp file as it would not let me post. Hope this is ok.

Thanks again.

Andy

[Mnemesi]

I'm having similar response. Here is a zipped dump report and the boot log. Dropped back to 1.33 for now.

[Toni Wilen]

"Compatibility mode" serial port enumeration can overflow.. (seems I forgot something important) Only workaround is to disable serial ports until it stops crashing. (or disable Bluetooth temporarily, I guess)

i have the same problem here on my notebook. WinUAE crashes on start.

Hi,

I have no serial port on this laptop but it does have bluetooth. I have disbaled it from within the bios but unfortunately it made no difference, has anyone else had any luck?

Going to try 1.3.3 i think.

Toni - Thanks for the prompt feedback .

Andy

[Toni Wilen]

Originally Posted by andyc1864

I have no serial port on this laptop but it does have bluetooth. I have disbaled it from within the bios but unfortunately it made no difference, has anyone else had any luck?

Do you have less than 8 serial ports in winuaebootlog.txt now? If yes, then there is another bug.. (dump shows the crash happening in P96 display mode sorting code but it may not have anything to do with the crash because serial bug will corrupt memory)

Could you try 1.4.0 betas? Which one is the last working (or first crashing) version?

Originally Posted by Toni Wilen

Do you have less than 8 serial ports in winuaebootlog.txt now? If yes, then there is another bug.. (dump shows the crash happening in P96 display mode sorting code but it may not have anything to do with the crash because serial bug will corrupt memory)

Could you try 1.4.0 betas? Which one is the last working (or first crashing) version?

Hi All.

I have found crash problem with version 1.4 beta 6 (all before works fine).
I discover something perhaps usefull - version 1.4beta6+ is working if you delete config in registry but without picasso gfx card (modes are not avaliable in screen mode). After shutdown winuae and start again situation going same as before (winaue crash).
My computer is laptop with bluetooth as well.

Sorry for my english is not perfect yet.
Thom

[Ian]

I have a problem too.

When I first install WinUAE everything works fine, the next time I start it as soon as I click on something that opens a file dialog box it crashes without warning or error message.

I'm using Windows XP 64

Beta 7 was the last version to work "properly".

[Toni Wilen]

Originally Posted by Ian

I have a problem too.

When I first install WinUAE everything works fine, the next time I start it as soon as I click on something that opens a file dialog box it crashes without warning or error message.

I'm using Windows XP 64

Beta 7 was the last version to work "properly".

Probably caused by same bug (if you have more than 8 serial ports listed in winuaelog.txt) but could you also attach/email winuaelog.txt and dump file?

[I am currently ignoring other non-serious reports until this bug is confirmed fixed and update has been released]

[Ian]

There is no crash dump created, but here are the logs.

[Toni Wilen]

Originally Posted by Ian

There is no crash dump created, but here are the logs.

Something else than serial port bug here..

Dump may not be created if Windows error reporting is completely disabled.

[Ian]

I just enabled it, but it still doesn't create a crash dump.

Nothing is added to dr watson32 either.

Anything (free) I can use to monitor WinUAE with?

[Toni Wilen]

Originally Posted by Ian

I just enabled it, but it still doesn't create a crash dump.

Weird..

Originally Posted by Ian

When I first install WinUAE everything works fine, the next time I start it as soon as I click on something that opens a file dialog box it crashes without warning or error message.

Every file dialog? (even hdf/directory harddisk dialog?)

Perhaps some buggy explorer shell extension?

[Ian]

I have events in the log about Microsoft Groove (Part of Office Ultimate 2007) around the times I tested it this morning which does add something to the context menu when in a dialog box I think. There is no reason for Groove to be running as I have no idea what it's supposed to do and never use it.

I haven't tried every dialog box, just the ones for configurations and floppies.

I will do some more testing later.

Hi All Together,

I have got the same problems, like the others too (-> After the first successful start of WinUAE and closing it, the Application won't start for a second time!)...

As the others, I get two Message-boxes telling me, that it won't work

I looked inside the dump file (winuae_1410_20070424_022712.dmp), but sad to say, that I am a lamer , and I don't know how to "read" these kinds of "messages", so I let it very soon...

Then I tried some of the tips in this forum (disabled the COM-Ports and the Printer-Ports) just to see what happens, but there happend nothing

Even if I tried to start it again, nothing happens, even no new dump-files... So, I renamed the dump-file from *.dmp to *.dmp.old just to see, if now there is a new dump-file. And yes, there was a new dump-file. The both dump-files just differ a little...

After that, I read the winuaebootlog.txt file and now I saw something at the end of the file, I read before in the dump.file: The word "Tastatur" (german word for "keyboard") and something with "DirectInput"...

The whole last three lines:
DirectInput enumeration.. Keyboards..
GUID=6F1D2B61-0000D5A0-000011CF-BFC7444553540000:
'Tastatur' 'Tastatur' 00000413 [Keyboard]

I now tried to start (just for "fun") to see, what dxdiag (Ctrl-R -> dxdiag) reports me: And look, it crashed... The second time I started dxdiag, it said something like: ... the last time DirectInput was making problems! Should we just let it out... (sorry for my "english")...

Could it be, that there is something wrong with WinUAEs use of DirectInput?

Here my System:
- Asus P5WDG2 WS Pro
- Intel Core 2 2x 2400Ghz
- 4GB Ram
- ATI Radeon X1950 GT (512MB)
- WinXP SP#2
- DirectX_v9.0c Dezember 2006
- WinUAE 1.4.1.0

Before this system, I had this one (and the same problems
- Asus P4C800-E Deluxe
- Intel Pentium 4 3,2 GHz
- 2GB RAm
- Matrox Parhelia
- WinXP SP#2
- DirectX_v9.0c Dezember 2006
- WinUAE 1.4.0.0, 1.3.2.0, 1.3.1.0



Don't know if the things I wrote here help anyone, but I still hope it does

Greeting from Germany
Toprak

[Toni Wilen]

I looked inside the dump file (winuae_1410_20070424_022712.dmp), but sad to say, that I am a lamer , and I don't know how to "read" these kinds of "messages", so I let it very soon...

It is useless without debugger and other stuff
Email or attach one dump, thanks.

Originally Posted by toprak

The whole last three lines:
DirectInput enumeration.. Keyboards..
GUID=6F1D2B61-0000D5A0-000011CF-BFC7444553540000:
'Tastatur' 'Tastatur' 00000413 [Keyboard]

Try removing all non-critical USB devices and game controllers. Still crashing? (there is at least one known game controller driver that crashes during DirectInput enumeration...)

Hello Again,

Yesterday forgot to say, that there were no USB Devices installed in my PC-System, while I was testing it... And at the moment I am not using a Gamecontroller...

The Files are uploaded...

Greetings from Hammer-Iron-Beach/Germany
Toprak

[Toni Wilen]

It crashes inside directinput. Looks like your keyboard driver has issues.. DXDiag crashing confirms it is not WinUAE problem.


Keyboard manufacturer and model? Did you replace your keyboard when you updated your PC?