- This topic has 7 replies, 5 voices, and was last updated 3 years, 7 months ago by
.
-
Posts
-
I just reinstalled my cabinet and I’m now having problems with PuPDMD. I have a PIN2DMD display which works perfectly in tables with DMDExt 1.8 in VPMame and UltraDMD. But whenever PUPDMDCONTROL launches it crashes. This causes Harry Potter Goblet of Fire to crash. PopperDoctor will never displays anything on the DMD and will eventually error out with an RPC error message, and PinUpMenu never displays anything on the DMD.
The machine is fresh with only GeForce Experience(For recording 4k media per pinup wiki), VPX (All in one installer 10.6), DMDExtensions (1.8), Pin2DMD(Just for utilities not using pin2dmd dmdevice files) and PinUPSystem installed.
Has anyone seen a similar issue and resolved it? I would rather not have to reinstall from scratch again.
Looking in Event Viewer I see many crash reports about PUPDMDCONTROL here is the relevant entry contents:
Log Name: Application Source: Application Error Date: 8/5/2020 12:48:53 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-MUBH3M7 Description: Faulting application name: PUPDMD~1.EXE, version: 1.40.4.0, time stamp: 0x5d9ba3ec Faulting module name: clr.dll, version: 4.8.4200.0, time stamp: 0x5ee03350 Exception code: 0xc00000fd Fault offset: 0x004d4cea Faulting process id: 0x12a0 Faulting application start time: 0x01d66b484b471b83 Faulting application path: C:\VISUAL~1\VPinMAME\PUPDMD~1.EXE Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Report Id: 1388a599-54ae-4be7-900c-cc11ca4ddf32 Faulting 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="2020-08-05T16:48:53.445400500Z" /> <EventRecordID>5947</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-MUBH3M7</Computer> <Security /> </System> <EventData> <Data>PUPDMD~1.EXE</Data> <Data>1.40.4.0</Data> <Data>5d9ba3ec</Data> <Data>clr.dll</Data> <Data>4.8.4200.0</Data> <Data>5ee03350</Data> <Data>c00000fd</Data> <Data>004d4cea</Data> <Data>12a0</Data> <Data>01d66b484b471b83</Data> <Data>C:\VISUAL~1\VPinMAME\PUPDMD~1.EXE</Data> <Data>C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll</Data> <Data>1388a599-54ae-4be7-900c-cc11ca4ddf32</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Version=1 EventType=APPCRASH EventTime=132411197335673487 ReportType=2 Consent=1 UploadTime=132411197463978434 ReportStatus=100 ReportIdentifier=7d7f09cb-31fc-4e7c-98fd-34a172c7066e IntegratorReportIdentifier=1388a599-54ae-4be7-900c-cc11ca4ddf32 Wow64Host=34404 Wow64Guest=332 NsAppName=PUPDMD~1.EXE AppSessionGuid=000012a0-0001-000a-831b-474b486bd601 TargetAppId=W:00066163b5a1fe6be4609dedf9dc218220b100000904!000072d8ac0212cf978f56d8401b1cfb277b0bda4f25!PUPDMD~1.EXE TargetAppVer=2019//10//07:20:45:32!0!PUPDMD~1.EXE BootId=4294967295 ServiceSplit=1955463168 TargetAsId=446 IsFatal=1 EtwNonCollectReason=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=PUPDMD~1.EXE Sig[1].Name=Application Version Sig[1].Value=1.40.4.0 Sig[2].Name=Application Timestamp Sig[2].Value=5d9ba3ec Sig[3].Name=Fault Module Name Sig[3].Value=clr.dll Sig[4].Name=Fault Module Version Sig[4].Value=4.8.4200.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=5ee03350 Sig[6].Name=Exception Code Sig[6].Value=c00000fd Sig[7].Name=Exception Offset Sig[7].Value=004d4cea DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.18363.2.0.0.768.101 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=0db4 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=0db40c5e9dca7c83184e5632376886c5 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=a34e DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=a34e0801eab3cbcf09895bc7e9528337 UI[2]=C:\VISUAL~1\VPinMAME\PUPDMD~1.EXE LoadedModule[0]=C:\VISUAL~1\VPinMAME\PUPDMD~1.EXE LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll LoadedModule[4]=C:\Windows\System32\shell32.dll LoadedModule[5]=C:\Windows\System32\ucrtbase.dll LoadedModule[6]=C:\Windows\SYSTEM32\winmm.dll LoadedModule[7]=C:\Windows\SYSTEM32\winspool.drv LoadedModule[8]=C:\Windows\System32\cfgmgr32.dll LoadedModule[9]=C:\Windows\System32\msvcrt.dll LoadedModule[10]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.18362.959_none_2e74f29627888bc1\comctl32.dll LoadedModule[11]=C:\Windows\System32\shcore.dll LoadedModule[12]=C:\Windows\System32\combase.dll LoadedModule[13]=C:\Windows\System32\RPCRT4.dll LoadedModule[14]=C:\Windows\System32\kernel.appcore.dll LoadedModule[15]=C:\Windows\SYSTEM32\WINMMBASE.dll LoadedModule[16]=C:\Windows\System32\SspiCli.dll LoadedModule[17]=C:\Windows\System32\bcrypt.dll LoadedModule[18]=C:\Windows\System32\CRYPTBASE.dll LoadedModule[19]=C:\Windows\System32\bcryptPrimitives.dll LoadedModule[20]=C:\Windows\System32\sechost.dll LoadedModule[21]=C:\Windows\System32\GDI32.dll LoadedModule[22]=C:\Windows\System32\windows.storage.dll LoadedModule[23]=C:\Windows\System32\win32u.dll LoadedModule[24]=C:\Windows\System32\msvcp_win.dll LoadedModule[25]=C:\Windows\System32\gdi32full.dll LoadedModule[26]=C:\Windows\SYSTEM32\PROPSYS.dll LoadedModule[27]=C:\Windows\SYSTEM32\IPHLPAPI.DLL LoadedModule[28]=C:\Windows\System32\advapi32.dll LoadedModule[29]=C:\Windows\System32\OLEAUT32.dll LoadedModule[30]=C:\Windows\System32\profapi.dll LoadedModule[31]=C:\Windows\System32\USER32.dll LoadedModule[32]=C:\Windows\System32\powrprof.dll LoadedModule[33]=C:\Windows\System32\UMPDC.dll LoadedModule[34]=C:\Windows\System32\shlwapi.dll LoadedModule[35]=C:\Windows\System32\cryptsp.dll LoadedModule[36]=C:\Windows\System32\ole32.dll LoadedModule[37]=C:\Windows\SYSTEM32\version.dll LoadedModule[38]=C:\Windows\SYSTEM32\netapi32.dll LoadedModule[39]=C:\VISUAL~1\VPinMAME\dmddevice.dll LoadedModule[40]=C:\Windows\SYSTEM32\NETUTILS.DLL LoadedModule[41]=C:\Windows\SYSTEM32\mscoree.dll LoadedModule[42]=C:\Windows\System32\IMM32.DLL LoadedModule[43]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll LoadedModule[44]=C:\Windows\System32\Msctf.dll LoadedModule[45]=C:\Windows\system32\uxtheme.dll LoadedModule[46]=C:\Windows\SYSTEM32\wtsapi32.dll LoadedModule[47]=C:\Windows\SYSTEM32\WINSTA.dll LoadedModule[48]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.18362.959_none_5f5fe57b821b058f\gdiplus.dll LoadedModule[49]=C:\Windows\SYSTEM32\olepro32.dll LoadedModule[50]=C:\Windows\SYSTEM32\sxs.dll LoadedModule[51]=C:\Windows\System32\clbcatq.dll LoadedModule[52]=C:\Windows\SYSTEM32\DWMAPI.DLL LoadedModule[53]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll LoadedModule[54]=C:\Windows\SYSTEM32\VCRUNTIME140_CLR0400.dll LoadedModule[55]=C:\Windows\SYSTEM32\ucrtbase_clr0400.dll LoadedModule[56]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\a3618d8dcd1f21a09718a75880e4b193\mscorlib.ni.dll LoadedModule[57]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll LoadedModule[58]=C:\Windows\SYSTEM32\wldp.dll LoadedModule[59]=C:\Windows\System32\CRYPT32.dll LoadedModule[60]=C:\Windows\System32\MSASN1.dll LoadedModule[61]=C:\Windows\System32\WINTRUST.dll LoadedModule[62]=C:\Windows\SYSTEM32\amsi.dll LoadedModule[63]=C:\Windows\SYSTEM32\USERENV.dll LoadedModule[64]=C:\ProgramData\Microsoft\Windows Defender\platform\4.18.2007.8-0\X86\MpOav.dll LoadedModule[65]=C:\ProgramData\Microsoft\Windows Defender\platform\4.18.2007.8-0\X86\MPCLIENT.DLL LoadedModule[66]=C:\Windows\SYSTEM32\gpapi.dll LoadedModule[67]=C:\Windows\system32\rsaenh.dll LoadedModule[68]=C:\Windows\SYSTEM32\ntmarta.dll LoadedModule[69]=C:\Users\VisualPinball\AppData\Local\Temp\Costura\6568FF16166D0EC3AB82595E9D577DA9\32\ftd2xx.dll LoadedModule[70]=C:\Windows\System32\SETUPAPI.dll LoadedModule[71]=C:\Users\VisualPinball\AppData\Local\Temp\Costura\6568FF16166D0EC3AB82595E9D577DA9\32\libskiasharp.dll LoadedModule[72]=C:\Windows\SYSTEM32\FONTSUB.dll LoadedModule[73]=C:\Windows\SYSTEM32\dwrite.dll LoadedModule[74]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll LoadedModule[75]=C:\Windows\SYSTEM32\MSVCP140_CLR0400.dll LoadedModule[76]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll LoadedModule[77]=C:\Windows\SYSTEM32\urlmon.dll LoadedModule[78]=C:\Windows\SYSTEM32\iertutil.dll LoadedModule[79]=C:\Windows\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll LoadedModule[80]=C:\Windows\System32\WS2_32.dll LoadedModule[81]=C:\Windows\SYSTEM32\winusb.dll LoadedModule[82]=C:\Windows\SYSTEM32\DEVOBJ.dll LoadedModule[83]=C:\Visual Pinball\VPinMAME\dmddevicePUP.DLL LoadedModule[84]=C:\Windows\SYSTEM32\WindowsCodecs.dll LoadedModule[85]=C:\Windows\SYSTEM32\d3d9.dll LoadedModule[86]=C:\Windows\SYSTEM32\dxcore.dll LoadedModule[87]=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumd.dll LoadedModule[88]=C:\Windows\SYSTEM32\cryptnet.dll LoadedModule[89]=C:\Windows\System32\imagehlp.dll LoadedModule[90]=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvd3dum.dll OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=18363 OsInfo[3].Key=ubr OsInfo[3].Value=959 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1033 OsInfo[7].Key=geoid OsInfo[7].Value=244 OsInfo[8].Key=sku OsInfo[8].Value=101 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=768 OsInfo[11].Key=ntprodtype OsInfo[11].Value=1 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=2779 OsInfo[15].Key=osinsty OsInfo[15].Value=2 OsInfo[16].Key=iever OsInfo[16].Value=11.959.18362.0-11.0.200 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=16295 OsInfo[19].Key=svolsz OsInfo[19].Value=476 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=190318 OsInfo[22].Key=bldtm OsInfo[22].Value=1202 OsInfo[23].Key=bldbrch OsInfo[23].Value=19h1_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.18362.959.amd64fre.19h1_release.190318-1202 OsInfo[30].Key=buildflightid OsInfo[31].Key=edition OsInfo[31].Value=Core OsInfo[32].Key=ring OsInfo[33].Key=expid OsInfo[34].Key=containerid OsInfo[35].Key=containertype OsInfo[36].Key=edu OsInfo[36].Value=0 File[0].CabName=WERInternalMetadata.xml File[0].Path=WER9D0E.tmp.WERInternalMetadata.xml File[0].Flags=327683 File[0].Type=5 File[0].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9D0E.tmp.WERInternalMetadata.xml FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=PUPDMDControl AppPath=C:\VISUAL~1\VPinMAME\PUPDMD~1.EXE NsPartner=windows NsGroup=windows8 ApplicationIdentity=05B4709FB409B0FD163A939FB271B31C MetadataHash=-856391104You need to login in order to like this post: click here
Well the problem solved itself. I had disabled all Nvidia services rebooting after each one. Still no success. I set dmdMirror to false and restarted with still nothing getting displayed on the DMD. Turned off the cabinet for the night and then when I turned it on again the next day DMDPUPCONTROL is no longer crashing and everything works again. Turned back on dmdMirror and all Nvidia services then restarted and now everything works as expected. Glad it’s working, but hate that I have no idea why.
You need to login in order to like this post: click here
Figured out what happened. The libusb driver or operating system must have been in a bad state, and fast boot was enabled in windows 10. This meant that drivers and kernel where not restarting or reloading from scratch on reboots. While the machine was off there was a power outage at the house. This triggered the bios to not use the fast boot save state, but start from scratch which let the driver reload in a working state.
Lesson learned: make sure you know how to disable and/or reset fast load state on your machine and make sure you trigger it if your having problems involving a driver or piece of hardware.
You need to login in order to like this post: click here
Same behavior disable fast boot but nothing changed
Nom de l’application défaillante PUPDMD~1.EXE, version : 1.40.4.0, horodatage : 0x5d9ba3ec
Nom du module défaillant : clr.dll, version : 4.8.4200.0, horodatage : 0x5ee03350
Code d’exception : 0xc00000fd
Décalage d’erreur : 0x004d4cea
ID du processus défaillant : 0x16d0
Heure de début de l’application défaillante : 0x01d670ccdb13a3a2
Chemin d’accès de l’application défaillante : C:\VISUAL~1\VPinMAME\PUPDMD~1.EXE
Chemin d’accès du module défaillant: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
ID de rapport : 726a25f8-8085-487f-98bf-33f2c2c85f46
Nom complet du package défaillant :
ID de l’application relative au package défaillant :You need to login in order to like this post: click here
Correct by doing a .net repair
https://support.microsoft.com/fr-fr/help/2698555/microsoft-net-framework-repair-tool-is-available
You need to login in order to like this post: click here
1 user thanked author for this post.
Same issue here with pindmd v2 device. Running net framework repair fixed it! Thank you and Nailbuster!
You need to login in order to like this post: click here
Got the same problem here, tried everything as described above (full restart, libusb or winusb driver and net framework repair). It still gives the same error code as written by “gadroc”.
What do you do with the net framework repair -> do you reinstall net framework or does it just repair it by itself?
Thats the only thing not working -> would be glad if somebody could help me!
Thx in advance
You need to login in order to like this post: click here
I was exposed to the same issue. The resolution, in my case, was to enable virtualdmd. With only pindmd3 enabled there was a framework error.
[virtualdmd]
enabled =true*AND*
[pindmd3]
enabled = true
COM3Regards,
Francis.
You need to login in order to like this post: click here
Forums are currently locked.
