Jump to content

dmddevice.dll crashing


Wob

Recommended Posts

  • Content Provider

Hi,

I am seeing some random crashes using the latest dll and 2.55 firmware, I posted in the SAMBuild Beta thread as I thought it was caused by a newer version, but it seems to be isolated to tables using my pin2dmd (I have pin2dmd disabled for older tables). I don't see any issues with PBX, but calling vpinmame, either via test or via VPX will cause random crashes. It seems to happen more often with colourised roms, but also happens to non-colourised roms. I have tried at91jit on/off with no effect.

I was having it happen on every 2 or 3rd load of a rom, disabling external dll and it starts working fine. Now I find it seems to run fine for a dozen or so loads, then will crash 3 or 4 times in a row.

Anyone have any guidance on how to track down the issue?

Windows 10 OS

Event log errors below, same type of errors when calling from vpinballx.exe.

>>Log Name:      ApplicationSource:        Application ErrorDate:          14/06/2018 4:46:48 PMEvent ID:      1000Task Category: (100)Level:         ErrorKeywords:      ClassicUser:          N/AComputer:      VPINDescription:Faulting application name: Setup.exe_Visual PinMAME Installer, version: 1.42.0.0, time stamp: 0x5677fa1cFaulting module name: DmdDevice.dll, version: 0.0.0.0, time stamp: 0x5ab693cfException code: 0xc0000005Fault offset: 0x00010524Faulting process ID: 0x920Faulting application start time: 0x01d403ab01c9fa1eFaulting application path: C:\Visual Pinball\VPinMAME\Setup.exeFaulting module path: C:\Visual Pinball\VPINMAME\DmdDevice.dllReport ID: 3c8658e7-714c-4e7f-84c2-f33ed7ba830eFaulting package full name: Faulting package-relative application ID: Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System>   <Provider Name="Application Error" />   <EventID Qualifiers="0">1000</EventID>   <Level>2</Level>   <Task>100</Task>   <Keywords>0x80000000000000</Keywords>   <TimeCreated SystemTime="2018-06-14T06:46:48.295063600Z" />   <EventRecordID>19869</EventRecordID>   <Channel>Application</Channel>   <Computer>VPIN</Computer>   <Security /> </System> <EventData>   <Data>Setup.exe_Visual PinMAME Installer</Data>   <Data>1.42.0.0</Data>   <Data>5677fa1c</Data>   <Data>DmdDevice.dll</Data>   <Data>0.0.0.0</Data>   <Data>5ab693cf</Data>   <Data>c0000005</Data>   <Data>00010524</Data>   <Data>920</Data>   <Data>01d403ab01c9fa1e</Data>   <Data>C:\Visual Pinball\VPinMAME\Setup.exe</Data>   <Data>C:\Visual Pinball\VPINMAME\DmdDevice.dll</Data>   <Data>3c8658e7-714c-4e7f-84c2-f33ed7ba830e</Data>   <Data>   </Data>   <Data>   </Data> </EventData></Event>
>>Log Name:      ApplicationSource:        Windows Error ReportingDate:          14/06/2018 4:46:49 PMEvent ID:      1001Task Category: NoneLevel:         InformationKeywords:      ClassicUser:          N/AComputer:      VPINDescription:Fault bucket 1938266938449532676, type 1Event Name: APPCRASHResponse: Not availableCab Id: 0Problem signature:P1: Setup.exe_Visual PinMAME InstallerP2: 1.42.0.0P3: 5677fa1cP4: DmdDevice.dllP5: 0.0.0.0P6: 5ab693cfP7: c0000005P8: 00010524P9: P10: Attached files:\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER81B7.tmp.dmp\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8235.tmp.WERInternalMetadata.xml\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8234.tmp.csv\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8245.tmp.txtThese files may be available here:C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Setup.exe_Visual_44357b9c14c01be6635b53281dccf7e73b8ec90_f4dec992_063e8745Analysis symbol: Rechecking for solution: 0Report ID: 3c8658e7-714c-4e7f-84c2-f33ed7ba830eReport Status: 268435456Hashed bucket: 18f4e1d03692603efae61b82da2b1704Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System>   <Provider Name="Windows Error Reporting" />   <EventID Qualifiers="0">1001</EventID>   <Level>4</Level>   <Task>0</Task>   <Keywords>0x80000000000000</Keywords>   <TimeCreated SystemTime="2018-06-14T06:46:49.777728800Z" />   <EventRecordID>19870</EventRecordID>   <Channel>Application</Channel>   <Computer>VPIN</Computer>   <Security /> </System> <EventData>   <Data>1938266938449532676</Data>   <Data>1</Data>   <Data>APPCRASH</Data>   <Data>Not available</Data>   <Data>0</Data>   <Data>Setup.exe_Visual PinMAME Installer</Data>   <Data>1.42.0.0</Data>   <Data>5677fa1c</Data>   <Data>DmdDevice.dll</Data>   <Data>0.0.0.0</Data>   <Data>5ab693cf</Data>   <Data>c0000005</Data>   <Data>00010524</Data>   <Data>   </Data>   <Data>   </Data>   <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER81B7.tmp.dmp\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8235.tmp.WERInternalMetadata.xml\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8234.tmp.csv\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8245.tmp.txt</Data>   <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Setup.exe_Visual_44357b9c14c01be6635b53281dccf7e73b8ec90_f4dec992_063e8745</Data>   <Data>   </Data>   <Data>0</Data>   <Data>3c8658e7-714c-4e7f-84c2-f33ed7ba830e</Data>   <Data>268435456</Data>   <Data>18f4e1d03692603efae61b82da2b1704</Data> </EventData></Event>
Thanks,
Wob
Link to comment
Share on other sites

  • Content Provider
57 minutes ago, lucky1 said:

Which DLL do you use ? Freezys or mine ?

Sorry, should have stated that. I'm using yours, I re-downloaded yesterday to ensure it wasn't somehow corrupt, and was having the same issue with the previous version of the dll.

Link to comment
Share on other sites

  • Content Provider

Anticipating the request, I have just installed Freezy's DLL.

I need to test a little more, but Indy 500 seems to be crashing regular, made it crash with your dll within a couple of loads, then since installing Freezys it has loaded a dozen times without crash.

I'll report back after some more testing, is there any pro\con to running 1 dll or the other with a pin2dmd (now that freezys has vni support)?

 

Thanks,

Wob

Link to comment
Share on other sites

  • Content Provider
Basically they should work the same way. Which USB driver do you use WinUSB or LibUSB32 ?
Do you use a frontend to start the table or start directly out of VP ?
I'm using libUSB, I use PBX but I can get it to crash loading VPX directly or even loading the rom via vpinmame setup/test.

Sent from my SM-G935F using Tapatalk

Link to comment
Share on other sites

  • Content Provider

Discovery board, I'll check all the rest and report back. I have been happily chugging along for 12+ months, a few software updates in that time, not much hardware change. But stable, something just seems to have gone out in the last month or so.

Sent from my SM-G935F using Tapatalk

Link to comment
Share on other sites

  • Content Provider

OK, status at the moment.

I'm using Indy 500 (i500_11r) to test as it seems to give me the most crashes (at the moment almost every time), but I see similar results from all roms, just a little more random with others.

  • I was using libusb-win32 (v1.2.6.0) installed using zadig_2.2.exe.
  • I have tried WinUSB (v6.1.7600.16385) also installed using zadig_2.2.exe. Still Crashes.

Are there any pros\cons to either USB Driver? Advice on which one to use?

  • I have 2 other USB Devices, a Pinscape and a Logitech Wireless Keyboard\Mouse, both on another Bus, so Pin2DMD is on it's own Bus. Checked with Windows USB View Tool.
  • libusbk.dll matches up with the current version on github (3.0.7.0)
  • If I disable "Colorize DMD (4 colors)" under the game options I don't see any crashes, I'm using basic color pallets on most tables.
  • So far switching to Freezy's dll seems to fix the issue, which is fine if it has no disadvantages, but happy to help diagnose the issue further if it will help anyone else.

Thanks,

Wob

Link to comment
Share on other sites

  • Content Provider

Here is the pal file, but as I mentioned I am seeing it on multiple tables, this one just seems to be worse.

Tried that DLL and it still crashes, although it seems to be just a second or two later.

pin2dmd.pal

Link to comment
Share on other sites

  • Content Provider

Strange, I have absolutely no crashes starting I500 20 times in a row using the latest sambuild , pin2dmd firmware 2.55 and my DLL on WIn10 64bit.

Does it crash in the middle of the game or at startup ?

Link to comment
Share on other sites

  • Content Provider
Strange, I have absolutely no crashes starting I500 20 times in a row using the latest sambuild , pin2dmd firmware 2.55 and my DLL on WIn10 64bit.
Does it crash in the middle of the game or at startup ?
Just at startup, once loaded its fine, sounds like and identical setup, really not sure what's upset my Apple cart, it's been fine prior to a month or so ago.

Sent from my SM-G935F using Tapatalk

Link to comment
Share on other sites

  • Content Provider
On 13.7.2018 at 9:21 AM, Wob said:

Just at startup, once loaded its fine, sounds like and identical setup, really not sure what's upset my Apple cart, it's been fine prior to a month or so ago.

Sent from my SM-G935F using Tapatalk
 

I think I found it 

Please try this version

 

Link to comment
Share on other sites

  • Content Provider

Thanks, I'm away for a few days but I'll try as soon as I return, only logs I am getting are the windows events in posted earlier.

Sent from my SM-G935F using Tapatalk

Link to comment
Share on other sites

  • Content Provider
On ‎13‎/‎07‎/‎2018 at 7:55 PM, lucky1 said:

I think I found it 

Please try this version

dmddevice.dll

That looks to have done the trick lucky1, Thank you!

It's probably WAY over my head, but what was the issue?

 

Link to comment
Share on other sites

  • Content Provider

Another issue I have noticed (let me know if you would rather a new thread).

Simpsons Pinball Party (simpprty) Colorization seem to take a really long time to load. With colorization unticked the rom loads in a second or 2, with it enabled it takes around 20 seconds, I can't remember it doing this when I first installed it. Apart from the load times it works find, and it does the same thing with both your dll and freezy's. I haven't noticed the issue with any other colorizations. 

 

Link to comment
Share on other sites

  • Content Provider

The crash was caused by the small size of the palette file. I updated the version on github.

The long start time is caused by the large number of palettes that need to be preloaded.

Link to comment
Share on other sites

  • Content Provider

OK, as long as its normal :)

Not to bring to much to the one thread, but I made a comment on the Family Guy Colorization a couple of months back, since 2.55 it seems the pallet on that has gone out of whack, no longer look right.

Link to comment
Share on other sites

  • Content Provider
1 minute ago, Wob said:

OK, as long as its normal :)

Not to bring to much to the one thread, but I made a comment on the Family Guy Colorization a couple of months back, since 2.55 it seems the pallet on that has gone out of whack, no longer look right.

I have added LED color correction to the pin2dmd firmware which may cause the colors to look a little different (brighter) than before, but the colors should be more close to LCD colors if that is what you mean. You can check this by comparing the onscreen output of freezys dll with the LED display.

Link to comment
Share on other sites

  • Content Provider
I have added LED color correction to the pin2dmd firmware which may cause the colors to look a little different (brighter) than before, but the colors should be more close to LCD colors if that is what you mean. You can check this by comparing the onscreen output of freezys dll with the LED display.
No, they are way out of whack, lots of pink and greens, doesn't look at all like it did. I'll test with freezys DLL and maybe video if need be. I did re-download the pal to be sure it wasn't a corruption at my end.

Sent from my SM-G935F using Tapatalk

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
  • Create New...